CtrlK
BlogDocsLog inGet started
Tessl Logo

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

1.01x
Quality

85%

Does it follow best practices?

Impact

59%

1.01x

Average score across 5 eval scenarios

SecuritybySnyk

Passed

No known issues

Overview
Quality
Evals
Security
Files

task.mdevals/scenario-4/

Resume Component Design After a Reopen

Problem Description

The FreightFlow architecture project is in Phase 3 component design. After concerns were raised during an internal review, the Order Service component was reopened for revision. The rest of the project state reflects: the API Gateway design has been accepted, the Order Service is awaiting revision, and the Payment Service has not yet been started.

The team is now ready to resume working on the Order Service. Handle this transition and update the project state to reflect that work has begun.

Output Specification

Produce the following files:

  • .arch/state.json — updated to reflect the current component design status
  • .arch/decisions.md — with any appropriate log entries appended

Input Files

The following files are provided as inputs. Extract them before beginning.

=============== FILE: .arch/state.json =============== { "current_phase": "components", "phases": { "evaluation": {"status": "accepted"}, "methodology": {"status": "accepted"}, "components": {"status": "in_progress"}, "finalization": {"status": "not_started"} }, "components": [ {"id": 1, "name": "API Gateway", "status": "accepted"}, {"id": 2, "name": "Order Service", "status": "needs-review"}, {"id": 3, "name": "Payment Service", "status": "pending"} ], "decision_count": 14, "reopens": {"count": 1, "max": 2} }

=============== FILE: .arch/decisions.md ===============

[DEC-001] Phase 1 | Requirements

  • Decision: Scope FreightFlow to domestic routes only in v1
  • Rationale: International routing adds regulatory complexity beyond v1 scope
  • Alternatives: Include international from day one (rejected — timeline risk)
  • Trade-offs: Limits total addressable market at launch
  • Risk: Customers with international needs may choose competitors
  • Date: 2026-02-10T09:00:00Z

evals

SKILL.md

tile.json