The library

A submission-platform intake that cryptographically signs each document on receipt, surfacing a badge that records the time of receipt and the submitter's identity without claiming to prove authorship.

A consent-and-disclosure step where a submitter optionally presents a verified credential and attaches a self-asserted 'submission process attestation' claim bound to that identity.

A 'preparation method' section in the intake form with a one-tap default and progressively disclosed structured fields for those who used AI or submit on an organization's behalf.

A submission flow that picks a proof-of-personhood tier proportionate to the stakes, always offering a lower-friction fallback so no single method is a hard gate.

A guided composition environment with sectioned fields, a non-blocking paste-disclosure prompt, and quietly captured session metadata, sitting beside a one-field free-text escape hatch.

An optional composition timeline and per-section source-annotation affordance that lets a submitter (but never requires them to) show how a piece was built and where each part came from.

An intake that scales how hard it asks to what the submission decides: a one-line self-declaration for a minor comment, a binding identity-linked attestation for a formal proceeding, on a form built so identity verification can be switched on later without a redesign.

A consent screen that renders a scope object as a plain-language permission a citizen can grant or narrow, with a sensible default bundle.

An attorney-facing screen that mints a time-limited, organization-specific access code from a registered delegation, which a relying organization enters to verify authority.

A bank-hosted consent screen reached by redirect that lists the requested scopes in plain language and feeds a standing consent dashboard for review and revocation.

A delegation receipt screen that renders the machine-readable consent record as a plain-language summary of scope, parties, temporal bounds, and an action log.

A delegation-management dashboard backed by a verification service that agencies query to confirm an agent's authority and revocation status in real time.

An identity-provider flow that issues a delegation credential binding a verified citizen identity to an agent operator, which relying agencies verify.

A government service that classifies each requested action by sensitivity and, for sensitive ones, pauses the agent and pushes a confirmation or re-authentication challenge to the citizen.

A client-authenticated nomination screen that registers a chosen agent at a typed authorization level, supporting several concurrent agents for different services.

A policy-management console where a citizen sets conditional sharing rules in advance that the authorization server evaluates when an agent later requests access.

An advance-directive style flow that records a primary and secondary agent with explicit excluded actions and stores the credential where clinical or institutional workflows can read it.

A plain-language agent-management interface layered over a cryptographic identity protocol, showing what the agent may do, what it has done, and a stop control.

A check-your-answers screen rendered before confirmation, where each agent-supplied answer carries its data provenance and a change link.

A confirmation screen that issues a saveable receipt naming the agent, the delegation authority, the data sources, and a unique reference.

A single audit record rendered through three views, selectable by role: citizen summary, caseworker decision points, and full regulatory trace.

A reasons panel at the review checkpoint stating why the agent reached its recommendation, in citable plain-language form.

A 'dispute this action' affordance on each receipt that opens a complaint pre-filled with the action record and a service-side response clock.

A liability statement at the review checkpoint naming who is responsible if the agent's action contains errors.

A reversibility badge at the authorization checkpoint classifying the action as reversible, amendable, compensable, or irreversible.

An operations console that turns 'measure the aggregate, not the transaction' into a fleet-level error-rate monitor with pre-declared thresholds and a halt-and-rollback control.

An agent output annotated with a confidence band and an action-tied caveat, so the citizen sees both how sure the agent is and what happens next.

A service-page trust mark whose every claim is a tap-through to the algorithmic transparency record, audit report, or bias-testing result that substantiates it.

An autonomy dial with a ladder of delegation levels (informational, guided, supervised, delegated) that exposes one level at a time with a conservative default, a per-level escape hatch, and capability boundaries the citizen cannot be silently moved past.

An interaction that opens by stating it is AI, links to a two-tier transparency record (a public-summary tier and a technical-detail tier), and raises real-time moments ("I am about to submit this form on your behalf; this cannot be undone") at the points that matter.

A consent-style screen that labels the interaction with one of three plain automation levels and, before any consequential action, shows what the agent will do and what data it will access.

An interaction that states, at each stage, which named human role will review the outcome and how to reach a person, with the override pathway no harder than accepting the agent's output.

A delegation control where successful use can expand scope and a single action contracts it instantly, with the non-agent channel always available at equal service quality.

A submission portal that checks a per-person counter against a verified identity before accepting a new application, showing the citizen how many submissions remain in the current period.

An intake form built from constrained fields (drop-downs, date pickers, document-upload requirements) with conditional branching, ending in an explicit escape pathway to human review.

A human-verification step that issues a privacy-preserving, rate-limited token via device attestation, with an in-person fallback that mints an equivalent time-limited token.

A municipal budgeting platform where residents propose, deliberate on, and vote for projects under a published spending envelope, with an accountability dashboard tracking delivery.

A petitions site with tiered response commitments (e.g. a written response at one threshold, debate consideration at another), where signing is gated by verified identity and the page surfaces quality signals alongside the raw count.

An audit tool that maps a service's behavioral journey, scores each friction point, and tags it as exclusionary (remove), rationing (replace with a purpose-built mechanism), or reflective (preserve but redesign for agents).

A published adjudication dashboard tracking appeal receipts, disposals, backlog, and the proportion overturned in the claimant's favor, used to size tribunal capacity to true demand.

A reviewer console that groups semantically similar submissions into argument clusters with a visible distinctness ratio, each cluster expandable to the underlying submissions.

A submission-record view that collapses each campaign to a single representative entry, discloses how many submissions it represented and who organized it, and marks whether each submission arrived through a verified route. It reports provenance and size; it does not try to classify which submissions were machine-written.

A real-time opinion map that plots participants into clusters and surfaces consensus statements (broad agreement across clusters) separately from divisive ones.

A consultation results dashboard that renders three side-by-side figures (raw submissions, distinct arguments, and verified distinct submitters), with campaign responses labeled rather than hidden.

An inline submission-flow nudge that detects template similarity and offers to help the submitter add a personal perspective, with a clear, non-blocking 'submit as written' path.

A prioritization interface that gives each participant a credit budget and shows the intensity-weighted result, with a plain-language explanation of how votes are weighted.

A service entry point that offers the citizen a free, government-aligned agent alongside (or instead of) any commercial agent they already hold.

A pre-submission review screen that shows the citizen, in plain language, exactly what their agent changed, including any change to the substance of what they said, before anything is sent.

An explicit channel-choice control at each service entry point, with the equivalence commitment held to account through reported processing times and success rates for non-agent users.

An agent interface that ships recognized accessibility-standard compliance plus conversational-accessibility affordances: adjustable pace, plain language by default, pause/resume, and a reviewable transcript.

An intake flow that defaults to plain language, detects and confirms the citizen's language, and surfaces an explicit competence indicator (with interpreter fallback) when operating in an under-resourced language.

A community-oversight surface: an anonymized agent-interaction-log review panel for affected communities, plus an in-conversation 'did this say what you meant?' feedback control.

A provider-and-interest disclosure surface shown when a third-party agent acts on a citizen's behalf, naming the provider, principal and any commercial relationship, with a one-tap switch to the public-option agent.

A tiered provision surface: a basic public agent for routine tasks and an enhanced agent for appeals and disputes, with a human-escalation path present throughout rather than added afterward.

A pre-deployment exclusion-risk assessment that names the populations a service will fail and commits outreach and a non-agent route for each, with disaggregated uptake reporting feeding back to keep those commitments honest.

A public registry listing that pairs a human-readable trust badge with a standardized machine-readable mark embedded in the tool's interface, filterable by impact level and assessment status.

A standardized, dual-rendered label (human-readable for citizens, machine-readable for agents) with a small mandatory field set (data source, last updated, accuracy claim, accountable party, license) and richer fields for higher-risk domains.

A citizen-facing supply-chain status indicator that translates raw bill-of-materials data into a single meaningful signal ('all dependencies current, no known vulnerabilities' vs '3 critical vulnerabilities upstream'), backed by a machine-readable document for agents.

A tiered submission-and-review flow (automated scan for all tools, human review for high-risk categories) paired with a mandatory structured disclosure section and a public, auditable statement of the review criteria.

A risk-classification gate that routes a tool into a certification tier based on its intended purpose and the consequence of its outputs, with lifecycle obligations (post-market monitoring, bias assessment) attached to higher tiers.

A self-assessment workflow structured around four risk-management functions that maps a tool's answers onto defined certification tiers.

An answer surface with mandatory inline per-claim citations and an expandable source panel showing the authoritative source, its date, and institutional provenance, with machine-readable provenance metadata for downstream agents.

A self-service certification wizard that classifies a tool by consequence and routes it to Tier 1 (publish a standardized nutrition label, no review), Tier 2 (peer review against published criteria), or Tier 3 (independent conformity assessment with accuracy testing).

A point-of-submission jurisdiction badge that names where the data is processed, whose law can reach it, and whether it stays onshore.

At the moment a citizen uses an AI assistant, a plain-language disclosure that the protection already matches what they are doing — which AI handles it, where it runs, who operates it, and whose law can reach it — led by reassurance and a way forward, not a tier number.

A contextual indicator that names the model, its hosting jurisdiction, and its transparency-register record at the point a citizen interacts with the service.

A jurisdiction-disclosure component that fires at the data-submission step rather than on page load, presents any alternatives symmetrically, and exposes structured metadata for the citizen's agent.

A transfer-mechanism status indicator: a binary or graded signal an agent queries before committing data, surfaced to the citizen only on high-sensitivity transactions.

A contextual assurance line, backed by sector-aware routing, that tells the citizen their data stayed within the jurisdiction the sector's law requires.

A model provenance label that names the provider, training jurisdiction, hosting jurisdiction, and governing law, surfaced at the point a citizen interacts with the AI.

A sovereignty supply-chain summary card: a nutrition-label-style view of jurisdictional exposure across every layer of the AI processing stack, queryable by the citizen's agent.

A sovereignty checkpoint that resolves silently to a minimal indicator when the infrastructure tier matches the data classification, and surfaces a clear disclosure plus choice only on mismatch.