INFORMATIVEDRAFT
Truth Source: Repository schemas and tests are authoritative.
Specification to Evaluation Matrix
Purpose: Resolves whether Specification and Evaluation documents describe the same concepts.
1. Module → Conformance Mapping
| Module (Specification) | Conformance Doc (Evaluation) | Evaluation Dimension |
|---|---|---|
| context-module CA-01 | conformance-model | Schema Validity |
| plan-module CA-02 | conformance-model | Lifecycle Completeness |
| trace-module CA-03 | evaluation-dimensions | Trace Integrity |
| confirm-module CA-04 | evaluation-dimensions | Governance Gating |
| collab-module CA-05 | evaluation-dimensions | Multi-agent Coordination (Future) |
| role-module CA-06 | conformance-model | Schema Validity |
| dialog-module CA-07 | conformance-model | Schema Validity |
| extension-module CA-08 | conformance-model | Schema Validity |
| network-module CA-09 | conformance-model | Schema Validity |
| Observability Events CA-10 | evidence-model | Evidence Validity |
2. Architecture Layer → Evaluation Mapping
| Layer (Specification) | Golden Flow (Evaluation) | Primary Evidence |
|---|---|---|
| L1 Core Protocol AA-01 | All GF-01~05 | Schema Validation |
| L2 Coordination AA-02 | GF-01, GF-02 | Module Lifecycles |
| L3 Execution AA-03 | GF-03, GF-04 | Trace Segments |
| L4 Integration AA-04 | GF-05 | Integration Events |
3. Profile → Golden Flow Mapping
| Profile (Specification) | Primary Golden Flow | Secondary Golden Flows |
|---|---|---|
| SA Profile PA-01 | GF-01: SA Lifecycle | GF-03, GF-04, GF-05 |
| MAP Profile PA-02 | GF-02: MAP Coordination | GF-03, GF-05 |
4. Invariants → Evaluation Dimensions Mapping
| Invariants File | Evaluation Dimension | Rule Count |
|---|---|---|
sa-invariants.yaml | Lifecycle Completeness | 9 |
map-invariants.yaml | Multi-agent Coordination | 9 |
observability-invariants.yaml | Trace Integrity | 12 |
integration-invariants.yaml | External Integration | 19 |
learning-invariants.yaml | Learning Evidence | 12 |
Total: 61 invariant rules
Rule Count reflects the number of invariant entries defined in the corresponding *-invariants.yaml files.
It does not imply runtime execution, validation, or coverage completion. Verification is scoped to Phase E/F.
5. Answer Matrix
| Question | Specification Source | Evaluation Source |
|---|---|---|
| Who defines Context? | CA-01 context-module | N/A (defined in Spec) |
| Who evaluates Context? | N/A | conformance-model, evidence-model |
| Who adjudicates Context conformance? | N/A | Validation Lab (Phase F) |
| Who defines SA Profile? | PA-01 sa-profile | N/A |
| Who evaluates SA Profile? | N/A | GF-01, conformance-model |
| Who defines Governance Gate? | CA-04 confirm-module | N/A |
| Who evaluates Governance Gate? | N/A | GF-05, evaluation-dimensions |
6. Cross-Reference Integrity
| Check | Status | Notes |
|---|---|---|
| All Modules have Evaluation mapping | Mapped | Via conformance-model (pending Phase E/F verification) |
| All Profiles have Golden Flow mapping | Mapped | SA→GF-01, MAP→GF-02 (pending Phase E/F verification) |
| All Layers have Evidence mapping | Mapped | Via Golden Flows (not runtime-validated) |
| All Invariants have Dimension mapping | Declared | 61 rules → 6 dimensions (not runtime-validated) |
Phase: D-2 (Cross-Directory Semantic Mapping) Coverage: Mapping declared (subject to Phase E/F verification)