Concepts
Orientation layer for the protocol model
Concepts clarify how the rule layer works before the reader moves into canonical reference. This surface exists to orient, not to replace the active protocol model.
Concept spine
Start with explanation, then move into reference
The Concepts mode explains why the protocol layer exists and how its core pieces relate. It should stay lighter than Reference and route the reader toward the active model.
How Interaction Works
Why structured participation is needed before canonical reference.
Open →
Message Model
How the envelope carries recognizable participation across systems.
Open →
Task Lifecycle
How protocol participation moves through named states and valid transitions.
Open →
Validation & Versioning
How participation remains checkable, durable, and compatible over time.
Open →
Interoperability
How shared interpretation depends on one formal interaction grammar.
Open →
Canonical handoff
Concepts should hand off into the active protocol surface
Once the conceptual frame is clear, the center of gravity moves to Reference and then to Releases for visible publication continuity.
Use Concepts for orientation
Clarify the rule layer and its boundaries before implementation work.
Use Reference as the active model
Move into canonical protocol sections once the conceptual frame is clear.
Use Releases for publication history
Track visible protocol change, release posture, and continuity over time.