INFORMATIVEDRAFT
Truth Source: Repository schemas and tests are authoritative.
Semantic Anchor Registry
Purpose: Provides a unified semantic coordinate system for the entire MPLP documentation ecosystem.
1. Concept Anchors (CA)
Core concept definitions. Each anchor corresponds to an indivisible protocol concept.
| ID | Concept | Definition Source | Schema | Description |
|---|---|---|---|---|
| CA-01 | Context | context-module.md | mplp-context.schema.json | Execution boundary and environment definition |
| CA-02 | Plan | plan-module.md | mplp-plan.schema.json | Step-based task structure |
| CA-03 | Trace | trace-module.md | mplp-trace.schema.json | Execution history record |
| CA-04 | Confirm | confirm-module.md | mplp-confirm.schema.json | Governance approval gate |
| CA-05 | Collab | collab-module.md | mplp-collab.schema.json | Multi-agent session |
| CA-06 | Role | role-module.md | mplp-role.schema.json | Agent role and capabilities |
| CA-07 | Dialog | dialog-module.md | mplp-dialog.schema.json | Multi-turn conversation |
| CA-08 | Extension | extension-module.md | mplp-extension.schema.json | Extension point registration |
| CA-09 | Network | network-module.md | mplp-network.schema.json | Communication topology |
| CA-10 | Event | observability | mplp-*-event.schema.json | Observability events |
1.1 Derived Concepts
Important concepts derived from core concepts (no independent schema):
| ID | Concept | Parent | Definition Source | Description |
|---|---|---|---|---|
| CA-11 | Step | CA-02 (Plan) | plan-module.md | Single execution unit in Plan |
| CA-12 | Segment | CA-03 (Trace) | trace-module.md | Single record fragment in Trace |
| CA-13 | Decision | CA-04 (Confirm) | confirm-module.md | Approval decision in Confirm |
| CA-14 | Participant | CA-05 (Collab) | collab-module.md | Participant in Collab |
| CA-15 | Message | CA-07 (Dialog) | dialog-module.md | Single message in Dialog |
2. Lifecycle Anchors (LA)
Lifecycle stages defining temporal state transitions of protocol objects.
| ID | Lifecycle Stage | Transition | Definition Source | Evaluation Ref | Description |
|---|---|---|---|---|---|
| LA-01 | Intent → Plan | Intent Parsing | l2-coordination-governance.md | - | Parse intent into structured plan |
| LA-02 | Plan → Confirm | Governance Gate | confirm-module.md | GF-05 | High-risk action approval |
| LA-03 | Confirm → Execution | Approval Release | l3-execution-orchestration.md | GF-01 | Execute after approval |
| LA-04 | Execution → Trace | Observability | trace-module.md | GF-01 | Execution recording |
| LA-05 | Trace → Snapshot | State Capture | l3-execution-orchestration.md | - | State snapshot |
| LA-06 | Drift → Recovery | Drift Detection | l3-execution-orchestration.md | GF-03 | Drift detection and recovery |
| LA-07 | Delta → Replan | Delta Intent | l2-coordination-governance.md | GF-04 | Incremental intent replanning |
2.1 Status Enumerations
| Object | Status Enum | Definition Source |
|---|---|---|
| Context | draft → active → suspended → archived → closed | CA-01 |
| Plan | draft → proposed → approved → in_progress → completed/failed/cancelled | CA-02 |
| Trace | pending → running → completed/failed/cancelled | CA-03 |
| Confirm | pending → approved/rejected/cancelled | CA-04 |
| Collab | draft → active → suspended → completed/cancelled | CA-05 |
3. Governance Anchors (GA)
Governance and authority related anchors defining protocol control boundaries.
| ID | Governance Concept | Definition Source | Scope | Description |
|---|---|---|---|---|
| GA-01 | MPGC Authority | protocol-truth-index.md | Protocol | Protocol Governance Committee authority |
| GA-02 | Frozen Status | versioning-policy.md | Protocol | Frozen spec immutability |
| GA-03 | Normative vs Informative | conformance-model.md | Documentation | Normative/informative document classification |
| GA-04 | Self-Declaration | EXTERNAL_TRUST_OVERVIEW.md | Conformance | Self-declaration conformance model |
| GA-05 | Forbidden Terms | protocol-truth-index.md | All | Forbidden terminology list |
3.1 Authority Split
| Layer | Authority | Scope |
|---|---|---|
| Protocol | MPGC | Schemas, Invariants, Normative Specification docs |
| Evaluation | None (informative) | Golden Flow scenarios, conformance/evidence models |
| Documentation | Documentation Governance | docs/* informative content |
| Website | Website Governance | mplp.io content |
4. Architectural Anchors (AA)
Four-layer architecture anchors defining protocol structural layers.
| ID | Layer | Definition Source | Scope | Description |
|---|---|---|---|---|
| AA-01 | L1 Core Protocol | l1-core-protocol.md | Schema | Declarative schema + invariants |
| AA-02 | L2 Coordination | l2-coordination-governance.md | Module | Module lifecycle and state |
| AA-03 | L3 Execution | l3-execution-orchestration.md | Runtime | Execution orchestration and state management |
| AA-04 | L4 Integration | l4-integration-infra.md | Infra | External system integration |
5. Kernel Duty Anchors (KD)
11 cross-cutting concerns defining protocol horizontal responsibilities.
| ID | Kernel Duty | Definition Source (Normative) | Explained Source (Informative) |
|---|---|---|---|
| KD-01 | Coordination | coordination.md | coordination-explained.md |
| KD-02 | Error Handling | error-handling.md | error-handling-explained.md |
| KD-03 | Event Bus | event-bus.md | event-bus-explained.md |
| KD-04 | Learning & Feedback | learning-feedback.md | learning-feedback-explained.md |
| KD-05 | Observability | observability.md | observability-explained.md |
| KD-06 | Orchestration | orchestration.md | orchestration-explained.md |
| KD-07 | Performance | performance.md | performance-explained.md |
| KD-08 | Protocol Versioning | protocol-versioning.md | protocol-versioning-explained.md |
| KD-09 | Security | security.md | security-explained.md |
| KD-10 | State Sync | state-sync.md | state-sync-explained.md |
| KD-11 | Transaction | transaction.md | transaction-explained.md |
6. Profile Anchors (PA)
Execution profile anchors.
| ID | Profile | Definition Source | Invariants File | Description |
|---|---|---|---|---|
| PA-01 | SA (Single Agent) | sa-profile.md | sa-invariants.yaml | Single agent configuration |
| PA-02 | MAP (Multi-Agent) | map-profile.md | map-invariants.yaml | Multi-agent configuration |
7. Golden Flow Anchors (GF)
Evaluation scenario anchors.
| ID | Golden Flow | Scenario Source | Evidence Focus |
|---|---|---|---|
| GF-01 | SA Lifecycle | gf-01.mdx | Context → Plan → Trace |
| GF-02 | MAP Coordination | gf-02.mdx | Multi-agent handoffs |
| GF-03 | Drift Detection | gf-03.mdx | Drift → Recovery |
| GF-04 | Delta Intent | gf-04.mdx | Delta → Replan |
| GF-05 | Governance | gf-05.mdx | Confirm gates |
8. Anchor Statistics
| Category | Count |
|---|---|
| Concept Anchors (CA) | 15 |
| Lifecycle Anchors (LA) | 7 |
| Governance Anchors (GA) | 5 |
| Architectural Anchors (AA) | 4 |
| Kernel Duty Anchors (KD) | 11 |
| Profile Anchors (PA) | 2 |
| Golden Flow Anchors (GF) | 5 |
| Total | 49 |
9. Usage
This registry is used for:
- Documentation Navigation: Quickly locate concept definition sources
- Semantic Alignment: Verify cross-directory concept consistency
- Phase F Mapping: Baseline coordinates for truthfulness mapping
- Validation Lab: Evidence tag reference
Phase: D-1 (Semantic Anchor Definition) Total Anchors: 49