Architecture · Intent & ECO
ECO Dimensions
The Execution Context Object (ECO) scores evidence across five independent dimensions. Each dimension graduates through three severity levels independently.
The Five Dimensions
Dimension 01
Coverage
What percentage of modules relevant to this task have been indexed and are structurally available?
Dimension 02
Freshness
How many commits behind HEAD is the index? Is the working tree dirty?
Dimension 03
Mapping
Can every spec reference (module name, symbol, file path) be resolved to a real codebase entity?
Dimension 04
Conflict
Do any two retrieval sources return contradictory structural facts about the same entity?
Dimension 05
Graph
Is the dependency traversal complete, or was it truncated at a hub node or depth limit?
Severity Levels per Dimension
| Level | Threshold | Effect |
|---|---|---|
| OK | Dimension passes all checks | No action |
| warn | Soft failure — evidence degraded but usable | Logged, reported to consumer |
| escalate | Hard soft failure — evidence unreliable | Lane forced up, analyst notified |
| block | Critical failure — cannot proceed | Pipeline halts, requires human input |
Dimension Thresholds
| Dimension | warn | escalate | block |
|---|---|---|---|
| Coverage | < 90% | < 70% | < 50% |
| Freshness | 1 commit behind | 3+ commits behind | dirty tree + 1+ behind |
| Mapping | 1 unresolved ref | 2–3 unresolved | any ref to non-existent module |
| Conflict | 1 soft conflict | 1 hard conflict | unresolvable conflict |
| Graph | truncated at depth | hub node capped | > 40% blast radius unknown |
See Severity Escalation for how these combine into lane classification.