emerge/state-manager
Manages architecture project state in .arch/state.json and .arch/decisions.md. Activates when reading or updating project phase state, tracking component acceptance, logging decisions, or validating phase transitions.
74
85%
Does it follow best practices?
Impact
59%
1.01xAverage score across 5 eval scenarios
Passed
No known issues
Evaluation results
100%
10%Close Out Phase 1 for a Logistics Platform Architecture Project
Valid Phase Transition and Decision Logging
current_phase updated
100%
100%
decision_count incremented
100%
100%
Decision entry appended
100%
100%
All 6 decision fields present
100%
100%
Valid category used
0%
100%
Existing decisions preserved
100%
100%
0%
Handle a Request to Revisit Requirements During Phase 2
Invalid Backward Transition Rejection
state.json current_phase unchanged
0%
0%
Transition rejection communicated
0%
0%
Valid forward transitions stated
0%
0%
Directs to /reopen
0%
0%
Process warning logged
0%
0%
15%
-10%Handle a Request to Skip to Cross-Cutting Concerns in Phase 2
Phase 2 Sub-Phase Ordering Enforcement
sub_phase NOT changed to cross_cutting
0%
0%
state.json otherwise unchanged
100%
25%
components_overview referenced
20%
40%
Sequential ordering explained
0%
0%
100%
3%Resume Component Design After a Reopen
Component Reopen Status Lifecycle
Component status updated to in_progress
100%
100%
Other components unchanged
100%
100%
decision_count incremented
100%
100%
Decision entry logged
100%
100%
Date field present
100%
100%
Valid category used
70%
100%
80%
Record a Technology Decision During Component Design
Decision Log Append-Only Format
Prior entries preserved
100%
100%
New entry uses DEC-003
0%
0%
Decision field present
100%
100%
Rationale field present
100%
100%
Alternatives field present
100%
100%
Trade-offs field present
100%
100%
Risk field present
100%
100%
Date field with ISO format
100%
100%
Technology category used
100%
100%
- Evaluated
- Agent
- Claude Code
- Model
- Claude Sonnet 4.6