Reversible by default
Promotion is not a permanent silence mechanism. Packets retain lineage and can be retired when invalid, expired, contradicted, or superseded.
Packet lifecycle
From context to reusable memory.
Every stage repeats the invariant: who said this, what is it allowed to affect, and when does it stop being valid?
Eight inspectable stages
The buttons update the inspector with JavaScript. The same content is available in native disclosure elements below.
Semantic fallback lifecycle
These native details elements remain usable without JavaScript and expose the complete content to assistive technologies.
1. Capture
Collect context with visible source and scope.
Invariant check: Who said this?
2. Normalize
Shape the packet without erasing provenance.
Invariant check: What fields must travel forward?
3. Govern
Apply authority state, use boundary, and constraints.
Invariant check: What is it allowed to affect?
4. Serialize
Emit JSON, Markdown, UAI, or other transport-neutral forms.
Invariant check: Can an agent parse it without guessing?
5. Teach
Translate the packet into human-facing explanation.
Invariant check: Does education stay separate from runtime policy?
6. Execute
Use only where explicitly authorized and constrained.
Invariant check: What guardrails prevent widening?
7. Evaluate
Compare outcome to source, boundary, and expected use.
Invariant check: What changed, and who reviewed it?
8. Retire or promote
Expire, archive, quarantine, or promote with evidence.
Invariant check: When does it stop being valid?
Transport-neutral
The same packet can be represented as JSON, Markdown, UAI memory, or page text while preserving source and allowed use.
Human-reviewable
Every transformation on this site is inspectable through ordinary files, visible controls, and static examples.