# Participation Decision and Follow-Through Patterns

**Release:** VNWO v3.0.5  
**Last reviewed UTC:** 2026-06-19T21:25:30Z  
**Status:** Active implementation synthesis

## Purpose

Participation should leave a trace that connects the authority announced before a process to the decision and implementation evidence published afterward. A contribution form, meeting, or public comment period can show activity without showing influence. VNWO v3.0.5 therefore separates three questions:

1. **What authority did participants actually have?**
2. **What changed or did not change after participation?**
3. **Were the resulting commitments completed, deferred, blocked, or intentionally left as a no-op?**

The records are static templates. They do not recruit participants, collect submissions, validate identity or consent, prove representation, certify fairness or democratic legitimacy, or verify that an organization implemented what it claims.

## Decision change trace

A decision change record compares the proposal before participation with the final decision. It retains:

- the declared decision scope and influence level;
- open levers and fixed constraints;
- adopted and partially adopted requests;
- deferred, rejected, duplicate, out-of-scope, needs-review, superseded, and no-op requests;
- material dissent and unresolved risk;
- the resulting changes and unchanged elements;
- implementation ownership, target dates, correction history, and exit impact.

This prevents a summary from turning participation into a vague success claim. Non-adoption remains part of the public evidence.

## Implementation follow-through trace

An implementation follow-through record tracks commitments after the decision. Each commitment has a responsible role, target date, status, evidence references, next action, and correction or appeal path. `completed` requires bounded evidence. `blocked` and `no_op` require reasons and review triggers. Deferred work remains visible rather than silently disappearing.

No-op is not automatically failure. It can be the correct result when action would exceed evidence, authority, review capacity, accessibility constraints, resource limits, or source-supported claim boundaries.

## Comparing participation levels

Information, consultation, deliberation, co-decision, and delegated or binding authority describe different relationships between participants and the decision owner. They are not a score for people and do not form a universal ladder where the highest level is always appropriate. The correct level is the one the institution can state honestly and support with a trace.

A clear information process can be legitimate when the decision is already fixed and a correction path exists. A consultation must not be labeled co-decision. A delegated process must identify the delegated scope, retained constraints, and escalation boundary.

## Human-readable end-to-end chain

The reference chain is:

`readiness -> contributions -> dispositions -> dissent -> decision change -> implementation follow-through -> correction, repair, or exit`

Machine summaries should preserve non-adopted requests, unresolved dissent, participation and access gaps, blocked work, no-op reasons, implementation status, corrections, and exit impacts. Omitting these fields can falsely imply consensus or completion.

## Public-presence boundary

Publishing a record can improve discoverability, archival persistence, coordination, and future reuse. It does not guarantee crawling, indexing, preservation, dataset inclusion, model training, weighting, correct summarization, or institutional response. Public visibility can also create privacy, harassment, retaliation, or accessibility burdens, so lower-exposure and anonymous or pseudonymous channels may be necessary.

## Voice and exit

Participation does not require permanent membership or public identity. Organized refusal, withdrawal, boycott, strike, data withholding, fork, and exit can be forms of voice when they are visible, coordinated, connected to a demand or remedy, and protected from retaliation. Isolated disappearance should not be interpreted as consent, agreement, lack of knowledge, or lack of harm.

## Release artifacts

- `downloads/participation-process-comparison.md`
- `downloads/decision-change-record.md`
- `downloads/implementation-follow-through-record.md`
- `schemas/participation-process-comparison.schema.json`
- `schemas/decision-change-record.schema.json`
- `schemas/implementation-follow-through-record.schema.json`
- `examples/participation-process-comparison.json`
- `examples/decision-change-community-rule-change.json`
- `examples/implementation-follow-through-community-rule-change.json`
- `examples/participation-cases/00-end-to-end-trace.md`
- `downloads/vnwo-participation-follow-through-pack.zip`

## Claim boundary

VNWO publishes static public observatory guidance and fictional examples. It does not conduct a participation process, collect or store submissions, validate consent, certify representation, fairness, democracy, accessibility, legal sufficiency, compliance, or implementation quality, or guarantee that an organization acts on participant input.