Last1 Identity & Participation Model¶
This document defines how beneficiaries and other actors participate in Last1 without coercion, surveillance, or mandatory identification. It supports credible validation while protecting vulnerable populations.
1. Roles¶
Organization¶
A legal or operational entity (e.g., nonprofit, VSO) that uses Last1 to define programs, track outcomes, and optionally participate in certification. The organization is the primary contracting and accountability subject for platform use.
Staff¶
Individuals who act on behalf of an organization: they log into the platform, manage programs and beneficiaries, record activities, and respond to escalations. Staff are linked to organizations via membership and roles (e.g., org_admin, member, provider). Staff are Users in the system.
Beneficiary¶
A person who is served by an organization’s programs. In Last1:
- Beneficiary ≠ User. A beneficiary may have no user account. They are represented by a beneficiary record (e.g., alias, optional contact info) maintained by the organization.
- Beneficiary ≠ Identity Subject. Last1 does not require beneficiaries to prove or verify their identity. A beneficiary may optionally link to a user account (e.g., to access a portal); the platform role “beneficiary” in that case denotes that linked user, not the broader concept of “person served.”
- Beneficiary participation in check-ins, surveys, or acknowledgments is optional and non-determinative. The system never requires a beneficiary to respond in order for the organization or its programs to remain in good standing.
Observer (system-level)¶
System-level role for audit, compliance, and governance. Observers do not represent organizations or beneficiaries; they operate under defined access and use limits for oversight and support (e.g., platform administration, appeals review). Not a product role exposed to nonprofits or beneficiaries.
2. Data Classification by Role¶
Organization¶
| Classification | Data |
|---|---|
| Required | Name, account/contract relationship to Last1, designation of authorized staff. |
| Optional | Description, branding, program and outcome definitions, certification-related documentation. |
| Prohibited | Last1 does not require or store government-issued IDs for organizations beyond what is necessary for billing/legal identity where contractually required. |
Staff (Users)¶
| Classification | Data |
|---|---|
| Required | Identity sufficient to authenticate and authorize (e.g., email, credential). |
| Optional | Name, profile image, preferences. |
| Prohibited | Government ID is not required for staff to use the platform. |
Beneficiary¶
| Classification | Data |
|---|---|
| Required | None. Last1 does not require any beneficiary data for an organization to use the platform. Organizations may choose to create beneficiary records with minimal identifiers (e.g., alias only). |
| Optional | Alias, contact channel (e.g., email, phone) for optional outreach; consent flags; optional demographic or program-related data at the organization’s discretion and under their own policies. |
| Prohibited | Government-issued ID is never required for beneficiaries. Last1 will not request, collect, or use government ID for beneficiary verification or participation. Beneficiary verification (if any) is the organization’s responsibility and must not be mandated by the platform. |
Observer¶
| Classification | Data |
|---|---|
| Required | Access controls and audit trail consistent with governance policy. |
| Optional | As defined by governance. |
| Prohibited | Use of data for purposes other than oversight, support, or appeals as defined in Last1 Standards. |
3. Participation Guardrails¶
Last1 will never require the following:
- Mandatory government-issued ID for beneficiaries (or for staff, beyond any lawful contract requirement).
- Mandatory beneficiary response to check-ins, surveys, or any other outreach as a condition of an organization’s standing or certification.
- Adverse inference from non-response. Silence or lack of response from a beneficiary must not be used to infer failure, non-delivery, or lack of impact.
- Surveillance framing. The platform does not frame beneficiary engagement as monitoring or surveillance; it is optional participation to support organizational learning and optional acknowledgment.
- Single-point beneficiary confirmation as proof of delivery. Beneficiary confirmation (when present) may inform context but is not sufficient or determinative for validation or certification.
Organizations may impose their own internal policies (e.g., consent, contact preferences) provided they do not conflict with these guardrails.
4. Hard Rules (Encoded)¶
The following are binding on all Last1 functionality and documentation:
- Beneficiary confirmation ≠ proof of delivery. Any acknowledgment or response from a beneficiary may be used only as one input among many. It does not constitute proof that services were delivered or that outcomes were achieved.
- System validation must not hinge on individual responses. Validation and certification rely on layered evidence (declarative, structural, operational, observational, temporal). No single layer—and no single beneficiary response—is sufficient or determinative.
- Silence ≠ failure. Non-response, unavailability, or refusal to participate by a beneficiary must not be treated as a negative signal for the organization or for certification.
5. FAQ — Identity & Participation¶
Do beneficiaries need to verify their identity?¶
No. Last1 does not require beneficiaries to verify their identity. Organizations may use aliases and optional contact information to manage their own records. Government-issued ID is never required for beneficiaries. If an organization chooses to allow beneficiaries to link a user account (e.g., for a client portal), that is optional and at the organization’s discretion.
What happens if beneficiaries don’t respond?¶
Nothing adverse. Beneficiary participation in check-ins, surveys, or other outreach is optional. Non-response is not used to infer failure, non-delivery, or lack of impact. Validation and certification are based on layered evidence (what the organization declares, how programs are structured, operational activity, optional observational data, and continuity over time). Silence from beneficiaries does not by itself affect an organization’s standing or certification status.