Skip to content

Last1 Standards

Version: 1.0
Effective date: 2025-02-06
Status: Authoritative

This document is the single authoritative standards document governing certification, validation, appeals, identity, and enforcement limits for Last1. Supporting specifications (identity model, validation layers, certification states, appeals) are referenced where indicated and are consistent with these Standards.


1. Purpose & Scope

Last1 Standards establish the constitutional rules and boundaries for how Last1 governs certification, validation, identity, and due process. They apply to all use of the Last1 platform in relation to certification and validation. They are intended to be read and applied in a calm, restrained manner. They do not constitute marketing or promotional material.

Scope includes: the meaning of certification states; the principles of layered validation; identity and participation safeguards for beneficiaries and organizations; appeals and remediation; and the limits of automated and human governance. Scope does not extend to pricing, product features, or operational implementation details except where those touch certification or validation policy.


2. What Last1 Standards Govern

  • Certification: The definitions and semantics of certification states (Active, Conditional, Paused, Revoked) and the principles under which status is assigned or changed.
  • Validation: The layered validation model and the principle that no single layer is sufficient or determinative.
  • Identity and participation: The roles (Organization, Staff, Beneficiary, Observer), data classification (required, optional, prohibited), and participation guardrails that protect beneficiaries from coercion and mandatory identification.
  • Appeals and due process: The process and timelines for notice, response, human review, and decision before any adverse certification change.
  • Governance and revision: How these Standards are revised and versioned.

3. What They Explicitly Do NOT Govern

  • Pricing, plans, or commercial terms. Standards do not set or govern pricing, tiers, or billing.
  • Product features or UI. Standards define policy and principles, not feature specifications or user interface.
  • Organizations’ internal policies. Organizations may have their own policies (e.g., consent, data retention) provided they do not conflict with these Standards.
  • Funders’ or partners’ use of certification information. How third parties use certification status is outside the scope of these Standards, except that Last1 will not use certification for scoring, ranking, or public shaming (see Section 6 and supporting documents). Last1 will not comply with funder or partner requests that would violate the identity, validation, or certification safeguards in these Standards or the red lines set out in backlash-pressure-test.md.
  • Legal or regulatory compliance. Standards are internal governance; they do not purport to satisfy specific legal or regulatory requirements in any jurisdiction.

4. Validation Principles

Validation of an organization’s activities and standing is based on multiple layers of evidence. The full specification is in validation-layers.md. The following principles are binding:

  • No single layer is sufficient or determinative. The five layers—Declarative, Structural, Operational, Observational, Temporal—are considered together. No one layer, including beneficiary response or non-response, can by itself determine certification or validation outcome.
  • Beneficiary confirmation is not proof of delivery. Optional acknowledgments or responses from beneficiaries may inform context but are never sufficient or determinative for validation or certification.
  • Silence is not failure. Non-response from beneficiaries must not be treated as a negative signal for the organization or for certification.
  • Human governance. Certification and validation decisions are made by human governance. Automated systems may detect patterns or support workflow but may not decide certification, infer intent, or assess effectiveness. See validation-layers.md for the AI boundary.

5. Identity & Participation Safeguards

Identity and participation are defined in identity-model.md. The following safeguards are binding:

  • Beneficiary ≠ User ≠ Identity Subject. Beneficiaries may have no user account. Last1 does not require beneficiaries to verify identity. Government-issued ID is never required for beneficiaries.
  • Participation is optional and non-determinative. Beneficiary participation in check-ins, surveys, or other outreach is optional. The system never requires a beneficiary to respond for an organization to remain in good standing.
  • Last1 will never require: mandatory government ID for beneficiaries; mandatory beneficiary response as a condition of standing or certification; adverse inference from non-response; or surveillance framing. Single-point beneficiary confirmation is not proof of delivery.

6. Certification States (Definitions Only)

Certification states are categorical. Full definitions are in certification-states.md. Summary:

State Meaning (summary) Reversibility (summary)
Active Certification in good standing; evidence consistent with Standards. May transition to Conditional, Paused, or Revoked.
Conditional Certification in effect with specified conditions or follow-up. May return to Active when conditions are met.
Paused Certification temporarily suspended pending review or remediation. May return to Active or Conditional after review.
Revoked Certification withdrawn after due process. Reapplication/recertification per governance.

Prohibitions: No scoring, no ranking, no public shaming, no automated enforcement. Transitions between states are determined by human governance following due process and appeals.


7. Appeals & Due Process

Appeals and remediation are specified in appeals-remediation.md. The following are binding:

  • Certification status changes are informational and non-punitive. Changes to certification status do not constitute punishment, penalty, or public shaming.
  • Notice before adverse change. Before any adverse certification change (to Conditional, Paused, or Revoked), the organization receives written notice of the proposed change, the basis in evidence and Standards, and the right to respond or appeal within a defined period (no less than 30 calendar days unless exigent circumstances are documented).
  • Human review. All appeals and responses are reviewed by a human decision-maker. No adverse certification change is made solely by automated process.
  • Decision and rationale. The organization receives a decision with rationale; effective date of any status change is stated. Further appeal options, if any, are communicated.

8. Governance & Revision Control

  • Authority. Last1 Standards are maintained and revised by the governance body designated by Last1. Changes are versioned and dated.
  • Revision process. Substantive changes to these Standards follow a defined review process (including, where appropriate, internal approval and notice to affected organizations). Revision history is retained.
  • Effective date. Each version has an effective date. New versions supersede prior versions from their effective date.
  • References. Supporting documents (identity-model.md, validation-layers.md, certification-states.md, appeals-remediation.md) are part of the Standards framework. In case of conflict between a supporting document and this master document, this document prevails.

End of Last1 Standards v1.0