Static evidence packet patterns

Trace Logger

Build reviewable, privacy-minimized evidence packets for actions, refusals, handoffs, repairs, and decisions without giving VNWO live telemetry or private-system access.

Open Work Receipt Template Review Work Observation

Purpose and boundary

Publish the smallest packet that makes consequential work inspectable.

A trace packet is a static evidence record, not a continuous activity feed. It should let a reviewer reconstruct the bounded event without exposing unrelated private content, credentials, raw prompts, secret reasoning, or broad behavioral history.

VNWO supplies documentation patterns only. It does not execute agents, import logs, validate credentials, authorize endpoints, collect telemetry, investigate incidents, or certify that a trace is complete or truthful.

Trigger conditions

Create a packet when work changes authority, access, memory, rights, or review state.

An automated action affects a person

Record the actor, authority, inputs, reason code, output, review trigger, and repair path.

A request is refused or deferred

Preserve the reason, missing evidence or authority, safer alternative, expiry, and escalation path.

A rule, model, or source changes

Link the before and after versions and state which interpretation or outcome changed.

A repair or appeal closes

Record the correction, retained disagreement, implementation status, and remaining exit option.

Publishing workflow

From event to reviewable record

Scope the event. Name one consequential action, refusal, decision, repair, or handoff.
Reference sources. Link stable rule, request, evidence, model, policy, and release identifiers.
Minimize the record. Exclude secrets and unrelated personal data; summarize sensitive context when the review purpose permits.
Declare limits. State missing evidence, uncertainty, authority limits, retention, and conditions that require human review.
Close the loop. Publish correction, appeal, rollback, export, revocation, expiry, and final disposition where applicable.

Fictional example

Agent declines to publish a draft

Event: Publication request refused; local draft preserved.
Reason: Publishing authority was not delegated and a named human approval was absent.
Evidence: Authority envelope v2.1 and request record WR-042.
Next action: Request human review or export the draft; no credentials or private prompts are included.

Download Work Observation Receipt Review No-Op Receipts Review Observability Limits

Expanded implementation guidance

Theory, minimum practice, stronger practice, and failure modes

Why this matters

A trace packet makes one consequential event reconstructable without converting observability into ambient surveillance. The record should preserve source, authority, reason, uncertainty, review, repair, and disposition while minimizing unrelated private data.

Minimum implementation

Record event ID, timestamp, actor, authority, action or no-op, source references, version, boundary status, outcome, human-review trigger, correction path, and retention or expiry.

Stronger implementation

Add signed or checksum-backed references, a privacy review, before/after versions, appeal and repair disposition, redaction rationale, export path, and a test showing the record can be used without private-system access.

Concrete example

A publication refusal packet links the authority envelope and request, states that human approval was absent, preserves the local draft, excludes credentials and private prompts, and identifies the review route.

Common failure modes

Raw secrets or full conversations published
Live telemetry treated as required
No actor or authority
Reason code without source
Trace retained indefinitely
Packet described as proof of truth or safety

Build networks people can leave and still choose to trust.

Start the Guide Get the Starter Pack