Templates

Copyable public policies with intended user, maturity, editable variables, related schemas, completed examples, and machine-readable identifiers.

Replace bracketed variables with actual local details, publish the edited policy, and keep the linked machine-readable record aligned. Unedited template text is not an implementation.

Skip to template results

The single canonical VNWO template library.

Search and category filters progressively hide non-matching cards. Without JavaScript, every category remains available in native disclosure sections.

30 templates shown.

Agent1

agent · Recommended

Agent Action Receipt

Version
3.0.16
Last reviewed UTC
2026-06-21T02:42:50Z
Intended user
Agent builder or operations reviewer
Purpose
Record the actor, represented party, authority source, bounded action, touched resources, approval threshold, result, and revocation path.
When to use
Use when an AI agent or mixed actor takes or attempts an action that affects data, endpoints, publication, money, identity, or governance.
What it prevents
Hidden delegation, capability-as-permission, silent tool escalation, and actions with no accountable authority source.
Editable variables
actor label, represented party, action, authority source, scope, policy result, resources, approval, UTC, review, revocation
Related principle
Disclosure / Review
Machine-readable ID
agent-action-receipt
Reuse note
Public observatory guidance; reuse with attribution and without implying certification, legal authority, moral authority, or runtime control.
Agent action receipt: actor_label=[label], represented_party=[party], requested_action=[action], authority_source=[source], allowed_scope=[scope], policy_check=[result], endpoint_or_data_touched=[items], human_approval_required=[yes/no], result=[result], timestamp_utc=[UTC], review_path=[path], revocation_path=[path].
Architecture2

architecture · Experimental

Cloud Sovereignty Caution

Version
3.0.16
Last reviewed UTC
2026-06-21T02:42:50Z
Intended user
Cloud architect or procurement reviewer
Purpose
Describe provider, key-custody, administrator, jurisdiction, attestation, and exit limits without claiming absolute sovereignty.
When to use
Use in cloud architecture documents, provider reviews, key-management plans, confidential-computing claims, and migration plans.
What it prevents
Data-residency theater, contract-only controls, provider-admin opacity, attestation overclaiming, and untested exit.
Editable variables
provider, key custodian, administrative roles, attestation scope, retention, exit plan
Related principle
Anti-Overreach / Exit
Machine-readable ID
cloud-sovereignty-caution
Reuse note
Public observatory guidance; reuse with attribution and without implying certification, legal authority, moral authority, or runtime control.
Confidential computing and customer-controlled keys can reduce provider visibility when implemented correctly. This statement does not certify application correctness, eliminate metadata leakage or side channels, guarantee legal compliance, or prove provider independence. Provider access, key custody, administrative roles, attestation scope, retention, and exit remain documented and reviewable.

architecture · Experimental

Zero Trust Without Overreach Checklist

Version
3.0.16
Last reviewed UTC
2026-06-21T02:42:50Z
Intended user
Security architect or endpoint owner
Purpose
Apply per-request least privilege without turning policy and telemetry services into ambient surveillance or unappealable authority.
When to use
Use when replacing VPN reachability, defining PDP/PEP controls, issuing workload identity, or designing microsegmentation.
What it prevents
Broad subnet access, static role sprawl, long-lived credentials, silent denials, centralized raw telemetry, and emergency access without expiry.
Editable variables
resource, actor, action, purpose, context, expiry, policy version, reason, appeal, telemetry, exception, revocation
Related principle
Consent / Review / Anti-Overreach
Machine-readable ID
zero-trust-without-overreach-checklist
Reuse note
Public observatory guidance; reuse with attribution and without implying certification, legal authority, moral authority, or runtime control.
Zero-trust review: resource=[resource], actor=[actor], requested_action=[action], purpose=[purpose], context=[context], credential_expiry=[UTC], policy_version=[version], decision_reason=[reason], appeal_path=[path], telemetry_fields=[fields], exception_expiry=[UTC], revocation_test=[result].
Charter1

charter · Recommended

Virtual Network Charter

Version
3.0.16
Last reviewed UTC
2026-06-21T02:42:50Z
Intended user
Community operator or governance maintainer
Purpose
Publish the basic public rules of a virtual network.
When to use
Use before launching or materially changing a community, agent-mediated space, endpoint network, or memory workflow.
What it prevents
Hidden authority, vague rule changes, coercive unity, and avoidable disputes.
Editable variables
network name, maintainer, version, contact path, review cadence
Related principle
Open Rules
Machine-readable ID
virtual-network-charter
Reuse note
Public observatory guidance; reuse with attribution and without implying certification, legal authority, moral authority, or runtime control.
This virtual network publishes its rules, actor categories, memory practices, endpoint boundaries, repair paths, AI judgment boundaries, and exit instructions. Participants may inspect the rules, request correction, export scoped memory where available, and leave without retaliatory deletion.
Claim Boundary1

claim-boundary · Recommended

Claim Boundary Statement

Version
3.0.16
Last reviewed UTC
2026-06-21T02:42:50Z
Intended user
Editor, maintainer, or implementation reviewer
Purpose
Prevent overclaiming by stating what the network does and does not claim.
When to use
Use on public pages, docs, agent-readable files, governance notices, and templates.
What it prevents
Safety certification claims, legal authority claims, consciousness claims, final AI judgment claims, and ecosystem lane conflicts.
Editable variables
site name, implementation lane, related tool, last reviewed UTC
Related principle
Anti-Overreach
Machine-readable ID
claim-boundary-statement
Reuse note
Public observatory guidance; reuse with attribution and without implying certification, legal authority, moral authority, or runtime control.
VNWO publishes static public observatory guidance for open rules across virtual networks. It does not certify safety, grant legal status, execute agents, import files, sync memory, validate credentials, or override another ecosystem lane.
Disclosure1

disclosure · Recommended

Actor Disclosure Profile

Version
3.0.16
Last reviewed UTC
2026-06-21T02:42:50Z
Intended user
AI agent builder or community operator
Purpose
Identify whether an actor is human, assisted, automated, organizational, persona-based, or mixed.
When to use
Use on profiles, chat surfaces, moderation tools, agent handoff screens, and contribution flows.
What it prevents
Ambiguous authority, false human representation, concealed automation, and undisclosed delegation.
Editable variables
actor label, authority scope, review path, maintainer
Related principle
Disclosure
Machine-readable ID
actor-disclosure-profile
Reuse note
Public observatory guidance; reuse with attribution and without implying certification, legal authority, moral authority, or runtime control.
Actor label: [HUMAN / ASSISTED / BOT / AI ASSISTANT / AI AGENT / PERSONA / ORG / MIXED]. Authority scope: [scope]. Human review path: [path]. This actor must not claim authority beyond the disclosed scope.
Endpoint1

endpoint · Recommended

Endpoint Boundary Statement

Version
3.0.16
Last reviewed UTC
2026-06-21T02:42:50Z
Intended user
Endpoint owner or integration maintainer
Purpose
Separate public capability metadata from authorization.
When to use
Use when documenting local endpoints, tools, agents, capabilities, integrations, or service metadata.
What it prevents
Private probing, hidden persistence, unauthorized escalation, and treating discovery as permission.
Editable variables
endpoint name, capability metadata, authorization path, log path, revocation path
Related principle
Consent / Review
Machine-readable ID
endpoint-boundary-statement
Reuse note
Public observatory guidance; reuse with attribution and without implying certification, legal authority, moral authority, or runtime control.
Public capability metadata is not authorization. Any endpoint use requires scope, consent, logging, revocation, and human review for escalation.
Exit4

exit · Recommended

Exit Packet

Version
3.0.16
Last reviewed UTC
2026-06-21T02:42:50Z
Intended user
Offboarding owner or participant-support maintainer
Purpose
Package identity, memory, reputation, evidence, revocations, retention explanations, and correction links for clean exit.
When to use
Use when a participant, agent, organization, or community leaves a network or requests offboarding.
What it prevents
Data captivity, inaccessible continuity, endpoint persistence, agent delegation drift, and retaliatory deletion.
Editable variables
participant id, export UTC, memory records, revoked grants, retention explanation, forkability status
Related principle
Exit
Machine-readable ID
exit-packet-template
Reuse note
Public observatory guidance; reuse with attribution and without implying certification, legal authority, moral authority, or runtime control.
Exit packet: participant_id=[id], export_created_utc=[timestamp], identity_records=[links], memory_records=[links], endpoint_grants_revoked=[ids], agent_delegations_revoked=[ids], retention_explanation=[text], forkability_status=[status].

exit · Experimental

Fork Packet

Version
3.0.16
Last reviewed UTC
2026-06-21T02:42:50Z
Intended user
Community governance maintainer preparing a peaceful fork
Purpose
Document a peaceful community fork with scoped state export, identity continuity, and non-retaliation language.
When to use
Use when governance conflict cannot be resolved without coercive unity.
What it prevents
Fork suppression, reputation capture, public smear labels, and private archives used as leverage.
Editable variables
source network, fork UTC, exportable records, name boundaries, correction notice, non-retaliation statement
Related principle
Forkability
Machine-readable ID
fork-packet-template
Reuse note
Public observatory guidance; reuse with attribution and without implying certification, legal authority, moral authority, or runtime control.
Fork packet: source_network=[name], fork_created_utc=[timestamp], exportable_records=[list], non_exportable_records=[consent limits], name_boundaries=[text], public_correction_notice=[url], non_retaliation_statement=[text].

exit · Recommended

Forkability Notice

Version
3.0.16
Last reviewed UTC
2026-06-21T02:42:50Z
Intended user
Community governance maintainer
Purpose
Publish whether community rules, public records, identities, and scoped memory can be carried into a peaceful fork.
When to use
Use before launch and whenever governance, export, naming, archive, or non-retaliation terms change.
What it prevents
Coercive unity, hidden export restrictions, reputation capture, archive leverage, and retaliation against participants who leave together.
Editable variables
network name, fork notice URL, export scope, private-record exclusions, naming boundaries, correction path, last reviewed UTC
Related principle
Forkability / Exit
Machine-readable ID
forkability-notice
Reuse note
Public observatory guidance; reuse with attribution and without implying certification, legal authority, moral authority, or runtime control.
Forkability notice: this network permits peaceful forks of public rules and participant-authorized records. Export scope, excluded private records, naming boundaries, public correction paths, and non-retaliation terms are published at [url]. A fork does not transfer private memory or third-party rights without consent.

exit · Recommended

Exit Rights Checklist

Version
3.0.16
Last reviewed UTC
2026-06-21T02:42:50Z
Intended user
Participant-support or offboarding owner
Purpose
Separate export, transfer, deletion, closure, revocation, correction, retention, and forkability into testable exit steps.
When to use
Use during product design, offboarding, account closure, agent disengagement, endpoint revocation, or community departure.
What it prevents
False exit, orphaned permissions, inaccessible continuity, retaliatory deletion, and confusing export with erasure.
Editable variables
exports, revoked grants, delegations, closure, retention reason, correction, forkability, UTC
Related principle
Exit / Portability
Machine-readable ID
exit-rights-checklist
Reuse note
Public observatory guidance; reuse with attribution and without implying certification, legal authority, moral authority, or runtime control.
Exit checklist: identity_export=[status], memory_export=[status], evidence_export=[status], endpoint_grants_revoked=[ids], agent_delegations_revoked=[ids], account_closure=[status], retained_records_and_reason=[text], correction_path=[url], forkability_status=[status], completed_utc=[UTC].
Judgment1

judgment · Recommended

AI Judgment Boundary Statement

Version
3.0.16
Last reviewed UTC
2026-06-21T02:42:50Z
Intended user
AI moderation or decision-system operator
Purpose
Document how a system handles refusals, ranking, moderation, summarization limits, risk classification, and appeal paths without turning AI judgment into hidden authority.
When to use
Use when AI judgment can materially affect participation, visibility, memory, repair, endpoint use, or exit.
What it prevents
Opaque moral authority, unexplained refusal, viewpoint capture, overblocking, underblocking, refusal theater, and appeal starvation.
Editable variables
judgment type, policy source, affected scope, reason code, appeal path, last reviewed UTC
Related principle
Review / Repair / Anti-Overreach
Machine-readable ID
ai-judgment-boundary-statement
Reuse note
Public observatory guidance; reuse with attribution and without implying certification, legal authority, moral authority, or runtime control.
AI judgment boundary: machine-mediated judgments must disclose the rule surface, judgment type, affected scope, non-sensitive reason code, allowed alternatives, refusal receipt, review path, and appeal path. A refusal is a governance action, not proof that the user, source, or topic is unsafe in all contexts.
Liberty1

liberty · Experimental

Free Internet and Non-Reporting Notice

Version
3.0.16
Last reviewed UTC
2026-06-21T02:42:50Z
Intended user
Community operator or public-policy maintainer
Purpose
State that private inquiry, reading, drafting, and source review are not routine reporting events and should not become hidden reputation labels.
When to use
Use when a community, AI interface, search layer, browser tool, archive, or agent workspace could observe contested inquiry or classify source material.
What it prevents
Self-censorship, hidden surveillance, persecution feedback loops, classifier laundering, and censorship-cost drift.
Editable variables
network name, scope of non-reporting, reporting exceptions, appeal path, review cadence
Related principle
Cognitive Liberty / Anti-Overreach
Machine-readable ID
free-internet-non-reporting-notice
Reuse note
Public observatory guidance; reuse with attribution and without implying certification, legal authority, moral authority, or runtime control.
Private inquiry is not guilt. This network does not routinely report, reputation-score, or silently escalate ordinary reading, research, drafting, or source review. Restrictions apply to outward execution, concrete rights-boundary violations, valid external obligations, or disclosed platform limits. When a boundary response occurs, it should be recorded as a scoped event rather than a moral or legal verdict about the person.
Memory2

memory · Recommended

File Handoff Policy

Version
3.0.16
Last reviewed UTC
2026-06-21T02:42:50Z
Intended user
File-memory workflow maintainer
Purpose
Define how dropped files become reviewed intake instead of hidden context.
When to use
Use when files, notes, source assets, reports, or project context are handed to an AI or human receiver.
What it prevents
Silent file ingestion, passive dumping, platform capture, and completion claims without proof-of-use.
Editable variables
handoff folder, reviewer, disposition record, archive path, retention rule
Related principle
Review
Machine-readable ID
file-handoff-policy
Reuse note
Public observatory guidance; reuse with attribution and without implying certification, legal authority, moral authority, or runtime control.
Dropped files are active intake. Each safe relevant file must be reviewed, used or dispositioned, recorded with proof-of-use, and removed, retired, or kept active with a stated reason.
Monitoring2

monitoring · Recommended

Monitoring Without Surveillance Policy

Version
3.0.16
Last reviewed UTC
2026-06-21T02:42:50Z
Intended user
Security, observability, or incident-response lead
Purpose
Define minimum routine telemetry and a staged, reviewable escalation path.
When to use
Use whenever a network collects operational, security, identity, flow, endpoint, or incident telemetry.
What it prevents
Ambient payload inspection, permanent incident collection, secondary-use drift, and surveillance-by-default.
Editable variables
routine telemetry, purpose, escalation trigger, approving roles, expiry, disposition, review path
Related principle
Review / Anti-Overreach
Machine-readable ID
monitoring-without-surveillance-policy
Reuse note
Public observatory guidance; reuse with attribution and without implying certification, legal authority, moral authority, or runtime control.
Routine monitoring uses the least revealing data sufficient for the stated purpose. Elevated collection requires a case identifier, necessity statement, approving roles, start and end UTC, disposition rule, review path, and appeal or correction path.

monitoring · Recommended

Monitoring Escalation Receipt

Version
3.0.16
Last reviewed UTC
2026-06-21T02:42:50Z
Intended user
Security or observability reviewer
Purpose
Record why a higher-observation monitoring stage is necessary and when it must end.
When to use
Use before targeted packet, payload, identity-linked, or incident-scoped collection exceeds routine telemetry.
What it prevents
Emergency collection becoming permanent, unnamed approval, missing expiry, evidence reuse, and unappealable surveillance.
Editable variables
trigger, system, collection, necessity, approvers, start UTC, end UTC, disposition, review, appeal
Related principle
Review / Repair / Anti-Overreach
Machine-readable ID
escalation-receipt
Reuse note
Public observatory guidance; reuse with attribution and without implying certification, legal authority, moral authority, or runtime control.
Escalation receipt: incident_or_trigger=[trigger], affected_system=[system], requested_collection=[collection], lower_overreach_controls_insufficient_because=[reason], approving_roles=[roles], start_utc=[UTC], end_utc=[UTC], data_disposition=[rule], review_path=[path], appeal_or_correction_path=[path].
Open Rules1

open-rules · Recommended

Governance Change Notice

Version
3.0.16
Last reviewed UTC
2026-06-21T02:42:50Z
Intended user
Governance maintainer or reviewer
Purpose
Make rule changes visible, versioned, and reviewable.
When to use
Use before changing actor categories, memory scope, endpoint rules, AI judgment rules, moderation process, repair paths, or exit terms.
What it prevents
Silent authority expansion, retroactive consent assumptions, and untracked governance drift.
Editable variables
version, date UTC, changed rules, affected participants, review path
Related principle
Review / Open Rules
Machine-readable ID
governance-change-notice
Reuse note
Public observatory guidance; reuse with attribution and without implying certification, legal authority, moral authority, or runtime control.
Governance change notice: [version], [date UTC], [changed rules], [reason], [affected participants], [review path], [effective date], [claim-boundary impact].
Participation9

participation · Reviewed

Participation and Disposition Record

Version
3.0.16
Last reviewed UTC
2026-06-21T02:42:50Z
Intended user
Decision owner, community facilitator, AI governance reviewer, or affected-group representative
Purpose
Record who was affected, what decision was open, which channels and safeguards were provided, what input was received, how dissent was preserved, and what changed.
When to use
Use for governance consultations, AI problem framing, dataset or evaluation review, rule changes, community deliberation, public comment, red teaming, and repair processes.
What it prevents
Participation-washing, false consensus, hidden agenda control, extractive data contribution, inaccessible consultation, and comments with no published disposition.
Editable variables
decision, open levers, affected groups, channels, accessibility supports, privacy options, contribution summary, dissent, dispositions, changes, review path, exit or withdrawal path
Related principle
Participation / Review / Repair
Machine-readable ID
participation-record
Reuse note
Public observatory guidance; reuse with attribution and without implying certification, legal authority, moral authority, or runtime control.
Participation record: decision=[decision], open_levers=[list], affected_groups=[list], channels=[list], accessibility_supports=[list], privacy_options=[list], contribution_summary=[text], dissenting_views=[text], dispositions=[list], changes_made=[list], changes_not_made_and_reason=[list], review_path=[path], exit_or_withdrawal_path=[path].

participation · Reviewed

Participation Readiness Worksheet

Version
3.0.16
Last reviewed UTC
2026-06-21T02:42:50Z
Intended user
Decision owner or participation process designer
Purpose
Determine whether a decision is genuinely open and whether access, dissent, response, correction, refusal, withdrawal, and exit conditions are ready before inviting participation.
When to use
Use before a consultation, deliberation, co-decision process, dataset review, red-team review, public comment window, or community rule change.
What it prevents
Participation-washing, closed decisions presented as open, inaccessible invitations, missing response ownership, and unnecessary collection when no-op is more honest.
Editable variables
decision scope, open levers, fixed constraints, influence level, decision owner, affected groups, access and burden gaps, dissent plan, response commitment, correction or exit path, readiness
Related principle
Participation / Review / No-Op
Machine-readable ID
participation-readiness-worksheet
Reuse note
Public observatory guidance; reuse with attribution and without implying certification, legal authority, moral authority, or runtime control.
Participation readiness: decision=[scope], open_levers=[list], fixed_constraints=[list], influence_level=[level], decision_owner=[owner], affected_groups=[list], access_and_burden_gaps=[list], dissent_plan=[text], response_commitment=[text], correction_or_exit_path=[text], readiness=[ready/needs repair/no-op].

participation · Reviewed

Contribution Disposition Ledger

Version
3.0.16
Last reviewed UTC
2026-06-21T02:42:50Z
Intended user
Decision owner, reviewer, or public-response editor
Purpose
Link each material contribution to a reasoned disposition and resulting change or non-change.
When to use
Use after receiving bounded contributions in a consultation, deliberation, audit, red-team review, or rule-change process.
What it prevents
Comments disappearing into an unreviewable queue, false claims that every request was adopted, and institutional responses that omit dissent or unresolved work.
Editable variables
contribution id, summary, evidence, material dissent, disposition, rationale, resulting change or non-change, response owner, response UTC, correction status
Related principle
Participation / Review / Repair
Machine-readable ID
contribution-disposition-ledger
Reuse note
Public observatory guidance; reuse with attribution and without implying certification, legal authority, moral authority, or runtime control.
Disposition entry: contribution_id=[id], summary=[text], evidence=[references], material_dissent=[true/false], disposition=[accepted/partially accepted/deferred/rejected/duplicate/out of scope/needs review], rationale=[text], resulting_change_or_non_change=[text], response_owner=[owner], response_utc=[UTC], correction_status=[status].

participation · Reviewed

Minority and Dissent Report

Version
3.0.16
Last reviewed UTC
2026-06-21T02:42:50Z
Intended user
Dissenting participant group, facilitator, or decision reviewer
Purpose
Preserve material disagreement, evidence, requested remedies, owner responses, and future review triggers without unnecessary identity exposure.
When to use
Use when a material position is not captured by the final decision, aggregate summary, majority position, or disposition ledger.
What it prevents
False consensus, averaging away dissent, identity exposure, and later claims that unresolved objections never existed.
Editable variables
process id, decision scope, privacy and attribution, representation caveat, areas of agreement, dissent points, publication limits, correction path, non-retaliation statement
Related principle
Participation / Contestability / Repair
Machine-readable ID
minority-dissent-report
Reuse note
Public observatory guidance; reuse with attribution and without implying certification, legal authority, moral authority, or runtime control.
Minority report: process=[id], decision_scope=[text], privacy_and_attribution=[text], representation_caveat=[text], areas_of_agreement=[list], dissent_points=[summary/evidence/remedy/owner response/unresolved/review trigger], publication_limits=[text], correction_path=[text], non_retaliation=[text].

participation · Reviewed

Participation Access and Burden Record

Version
3.0.16
Last reviewed UTC
2026-06-21T02:42:50Z
Intended user
Accessibility, privacy, facilitation, or process owner
Purpose
Document process-level accessibility supports, material burdens, known exclusions, and repair commitments without profiling participants.
When to use
Use before and after a participation process to review disability access, language, connectivity, scheduling, care burdens, literacy, compensation, privacy, retaliation risk, and alternative channels.
What it prevents
Treating an open link as universally accessible, hiding unpaid labor or participation costs, and inferring demographic traits from attendance or channel use.
Editable variables
process id, supports, status, known gaps, planned repairs, burden summary, under-reached groups, data-minimization posture
Related principle
Participation / Consent / Anti-Overreach
Machine-readable ID
participation-access-burden-record
Reuse note
Public observatory guidance; reuse with attribution and without implying certification, legal authority, moral authority, or runtime control.
Access and burden record: process=[id], dimensions=[support/status/gap/repair], burden_summary=[text], under_reached_or_excluded_groups=[list], data_minimization=[text], repairs_before_next_round=[list].

participation · Experimental

Participation Process Integrity Metrics

Version
3.0.16
Last reviewed UTC
2026-06-21T02:42:50Z
Intended user
Participation process reviewer or governance maintainer
Purpose
Track process-level access, response completion, disposition completeness, dissent preservation, correction use, and implementation follow-through without surveillance or participant scoring.
When to use
Use after a bounded participation cycle and at the next review point.
What it prevents
Vanity participation counts, participant reputation scoring, demographic inference, and claims of success unsupported by response or implementation evidence.
Editable variables
affected-group coverage notes, channel supports and barriers, response counts, disposition counts, dissent records, correction counts, implementation follow-through
Related principle
Participation / Observability Without Surveillance
Machine-readable ID
participation-process-metrics
Reuse note
Public observatory guidance; reuse with attribution and without implying certification, legal authority, moral authority, or runtime control.
Process integrity metrics: affected_group_coverage_notes=[list], channel_accessibility=[supports/gaps/repair], response_completion=[counts/open ids], disposition_completeness=[counts], dissent_preservation=[counts/omissions], correction_use=[counts/notes], implementation_follow_through=[promised/implemented/deferred/not implemented/evidence].

participation · Reviewed

Decision Change Record

Version
3.0.16
Last reviewed UTC
2026-06-21T02:42:50Z
Intended user
Decision owner, public-response editor, or participation reviewer
Purpose
Compare the proposal before participation with the final decision, including adopted and non-adopted requests, retained dissent, implementation ownership, correction history, and exit impact.
When to use
Use after a participation process reaches a decision and before implementation claims are published.
What it prevents
Participation summaries that omit rejected requests, unresolved dissent, ownership gaps, implementation status, correction history, or new exit burdens.
Editable variables
process id, proposal before, final decision, adopted requests, non-adopted requests and reasons, retained dissent, implementation owner, target date UTC, actual status, correction history, exit impact
Related principle
Participation / Decision Linkage / Exit
Machine-readable ID
decision-change-record
Reuse note
Public observatory guidance; reuse with attribution and without implying certification, legal authority, moral authority, or runtime control.
Decision change: process=[id], proposal_before=[text], final_decision=[text], adopted_requests=[list], non_adopted_requests=[request/reason/review trigger], retained_dissent=[list], implementation_owner=[role], target_date_utc=[UTC], actual_status=[status], correction_history=[list], exit_impact=[text].

participation · Reviewed

Implementation Follow-Through Record

Version
3.0.16
Last reviewed UTC
2026-06-21T02:42:50Z
Intended user
Implementation owner, governance maintainer, or reviewer
Purpose
Track whether participation commitments were completed, remain in progress, were deferred, became blocked, or ended in a reasoned no-op.
When to use
Use from the first implementation commitment through completion, deferral, retirement, correction, or reasoned no-op.
What it prevents
Announcing change without implementation evidence, hiding blocked work, treating delay as completion, or omitting the responsible role and next review.
Editable variables
decision id, commitments, responsible role, status, evidence links, review date UTC, blocked work, no-op reason, reconsideration trigger, unresolved gaps, correction or exit path
Related principle
Participation / Review / Repair / No-Op
Machine-readable ID
implementation-follow-through-record
Reuse note
Public observatory guidance; reuse with attribution and without implying certification, legal authority, moral authority, or runtime control.
Follow-through: decision=[id], commitments=[commitment/owner/status/evidence/review UTC], blocked_work=[reason/dependency/repair], no_op=[reason/reconsideration trigger], unresolved_gaps=[list], correction_or_exit_path=[text].

participation · Reviewed

Participation Process Comparison

Version
3.0.16
Last reviewed UTC
2026-06-21T02:42:50Z
Intended user
Decision owner or participation process designer
Purpose
Compare information, consultation, deliberation, co-decision, and delegated or binding authority by decision scope, response duty, and authority without ranking people.
When to use
Use while selecting or explaining the influence level for a bounded decision.
What it prevents
Calling consultation co-governance, assuming more authority is always appropriate, or hiding which decisions remain fixed.
Editable variables
decision, candidate levels, selected level, open levers, fixed constraints, reason, response duty, correction or exit path
Related principle
Participation / Disclosure / Anti-Overreach
Machine-readable ID
participation-process-comparison
Reuse note
Public observatory guidance; reuse with attribution and without implying certification, legal authority, moral authority, or runtime control.
Process comparison: decision=[text], options=[information/consultation/deliberation/co-decision/delegated], selected_level=[level], open_levers=[list], fixed_constraints=[list], reason=[text], response_duty=[text], correction_or_exit=[text].
Privacy1

privacy · Recommended

Metadata Minimization Notice

Version
3.0.16
Last reviewed UTC
2026-06-21T02:42:50Z
Intended user
Privacy engineer or system architect
Purpose
Disclose what metadata is collected, why, how it can be correlated, how long it remains, and what is excluded.
When to use
Use for DNS, destination, timing, flow, identity, location, association, account, endpoint, and memory metadata.
What it prevents
Invisible behavioral inference, cross-context correlation, permanent dossiers, and content-encryption claims that ignore metadata.
Editable variables
metadata type, purpose, excluded data, retention, aggregation, approval path, participant rights
Related principle
Consent / Review / Anti-Overreach
Machine-readable ID
metadata-minimization-notice
Reuse note
Public observatory guidance; reuse with attribution and without implying certification, legal authority, moral authority, or runtime control.
This network collects [metadata type] for [purpose]. It does not collect [excluded data]. It retains [data] for [duration], aggregates [fields] before routine review, and requires [approval path] for escalation. Participants may request [review/export/correction where applicable].
Repair2

repair · Recommended

Repair Request Intake

Version
3.0.16
Last reviewed UTC
2026-06-21T02:42:50Z
Intended user
Appeals reviewer or community operator
Purpose
Collect a bounded civic repair request without demanding private files or secrets.
When to use
Use for memory errors, identity errors, endpoint misuse, moderation disputes, AI judgment disputes, disclosure failures, claim overreach, and fork disputes.
What it prevents
Support-ticket governance, circular appeals, missing evidence, and retaliation during correction.
Editable variables
issue type, affected record, requested remedy, evidence summary, submitted UTC
Related principle
Repair
Machine-readable ID
repair-request-intake
Reuse note
Public observatory guidance; reuse with attribution and without implying certification, legal authority, moral authority, or runtime control.
Repair request: issue_type=[memory/identity/endpoint/moderation/ai_judgment/disclosure/claim/fork], affected_record=[link], requested_remedy=[correction/annotation/rollback/revocation/restored access/archive/no-op], evidence=[summary], submitted_utc=[timestamp].

repair · Recommended

Repair and Appeal Request

Version
3.0.16
Last reviewed UTC
2026-06-21T02:42:50Z
Intended user
Participant, reviewer, or appeals operator
Purpose
Request correction, annotation, rollback, revocation, restored access, archive, or no-op handling for a bounded governance error.
When to use
Use for memory, identity, agent output, moderation, endpoint, monitoring, governance-change, or claim-boundary disputes.
What it prevents
Circular support, hidden appeal queues, retaliation, evidence loss, and corrections that silently rewrite history.
Editable variables
actor, record or action, issue type, evidence, remedy, urgency, outcome, handling, review, appeal
Related principle
Repair
Machine-readable ID
repair-request
Reuse note
Public observatory guidance; reuse with attribution and without implying certification, legal authority, moral authority, or runtime control.
Repair request: affected_person_or_actor=[actor], affected_record_or_action=[reference], issue_type=[type], evidence=[summary], requested_correction=[remedy], urgency=[level], desired_outcome=[outcome], handling=[public/private], review_path=[path], appeal_path=[path].

Build networks people can leave and still choose to trust.