Role-based pathways

VNWO Use Cases

Choose the evidence problem first, then produce a bounded record that another person can inspect, correct, and use without treating VNWO as an operating authority.

Get the Starter Pack See Complete Examples

How to choose

Start with the decision or boundary that needs evidence.

Do not begin by adopting every VNWO artifact. Identify one consequential event, authority boundary, memory decision, participation process, endpoint, judgment, repair, or exit obligation. Publish the smallest coherent record and connect it to its sources and review path.

Affected participant or facilitator

I need affected people to shape a decision

Declare the open decision lever, influence level, access supports, dissent, dispositions, corrections, non-retaliation, and exit.

Expected record: Participation record and decision-change record

Plan meaningful participation Copy participation templates

AI builder or agent operator

I build AI agents

Publish actor labels, authority envelopes, approval triggers, stop points, revocation, and repair.

Expected record: Actor disclosure and agent authority envelope

Scope agent authority Publish agent disclosure

Community operator

I run an AI-assisted community

Start with the civic application profile, charter, moderation receipt, appeal, governance change, and exit.

Expected record: Public charter, judgment receipt, and appeal path

Choose a community profile Inspect complete examples

Memory steward or handoff reviewer

I manage memory or file handoff

Declare memory classes, proof-of-use, retention, correction, retirement, export, and UAIX boundaries.

Expected record: File handoff plus disposition and proof-of-use ledger

Govern file memory Copy memory templates

Moderator, reviewer, or appeal owner

I review moderation or AI judgment

Use reason codes, evidence references, version notes, safer alternatives, and appeal records.

Expected record: AI judgment receipt and repair record

Document AI judgment Design repair and appeals

Endpoint or capability owner

I expose endpoints or local capabilities

Keep public capability metadata separate from authorization, scope, logging, refusal, and revocation.

Expected record: Endpoint boundary and revocation record

Define endpoint boundaries Apply bounded zero trust

Work-system designer

I document AI-mediated work

Publish actor, authority, data and memory use, work receipts, no-op triggers, human review, repair, and offboarding.

Expected record: AI-mediated work application profile

Document AI-mediated work Review a completed work case

Offboarding or continuity owner

I need exit and offboarding

Publish export, revocation, identity closure, retention explanation, and forkability before conflict.

Expected record: Exit packet and revocation checklist

Design an exit path Plan for a peaceful fork

AI reader or deployment reviewer

I verify identity and release integrity

Resolve canonical identity, release parity, direct public files, disambiguation, and source routing.

Expected record: Machine-reader parity and source-routing review

Verify canonical identity Inspect machine-readable governance

Completion test

A pathway is complete only when a reviewer can trace consequence and correction.

The responsible actor and authority are named.
The source, version, event, and resulting record are linked.
Missing evidence, refusals, dissent, and no-op reasons remain visible.
Review, correction, revocation, export, and exit routes are usable.

Expanded implementation guidance

Theory, minimum practice, stronger practice, and failure modes

Why this matters

Use cases should route a concrete evidence problem to the smallest coherent record set. Role labels help orientation, but the consequential decision, authority boundary, source, review path, and exit condition remain the governing scope.

Minimum implementation

Name the role, problem, expected record, primary guidance, related example or template, implementation owner, and completion test.

Stronger implementation

Add a completed fictional case, local source map, review owner, correction path, and evidence showing that the promised record is actually published and usable.

Concrete example

An endpoint owner selects the endpoint-boundary pathway and produces a capability profile, authority rule, refusal code, expiry, logging limit, and revocation record.

Common failure modes

Generic links such as learn more
Role chosen without a defined decision
Every template adopted without need
No expected record
No review or exit path

Build networks people can leave and still choose to trust.

Start the Guide Get the Starter Pack

Start with the decision or boundary that needs evidence.

Use case pathways and expected records

I need affected people to shape a decision

I build AI agents

I run an AI-assisted community

I manage memory or file handoff

I review moderation or AI judgment

I expose endpoints or local capabilities

I document AI-mediated work

I need exit and offboarding

I verify identity and release integrity

A pathway is complete only when a reviewer can trace consequence and correction.

Theory, minimum practice, stronger practice, and failure modes

Why this matters

Minimum implementation

Stronger implementation

Concrete example

Common failure modes

Build networks people can leave and still choose to trust.