Spec topic type with defined workflow states
LOGOS must support a Spec topic type with a defined workflow
that moves a specification from initial draft through review
and approval to linked implementation.
Why It's Needed
Design before implementation is a core NEXUS principle. Specs
are written before code. But a spec is not a static document —
it moves through stages. Without a defined workflow, there is
no shared understanding of where a spec is in its lifecycle,
whether it is safe to implement from, or whether it has been
reviewed and approved.
Talkyard has no mechanism for this. A wiki post can be edited
but carries no state. A Problem topic has New/Planned/Started/
Done which is close but not the right shape — it implies
something is broken rather than something being designed.
The Requirement
A Spec topic type exists with the following workflow states:
- Draft — being written, not ready for review
- Under Review — complete enough to review, feedback
being gathered - Approved — reviewed and accepted as the basis for
implementation - Linked to Implementation — implementation exists and
is linked back to this spec
State transitions are explicit actions, not just edits. Each
transition is a timestamped event with the actor recorded.
Current state is visible in topic listings.
Relationship to Implementation
An Approved spec is the input to AI-assisted code generation.
The spec is not documentation after the fact — it is the
source from which implementation is generated. Linking
implementation back to the spec closes the loop and makes
the connection traceable in both directions.
Acceptance
A user creates a Spec topic. It begins in Draft state. After
editing it is moved to Under Review. After review it is moved
to Approved. Implementation is created and linked — the topic
moves to Linked to Implementation. The full state history is
visible. The link to implementation is navigable in both
directions — from spec to implementation and from
implementation back to spec.
Sources
- LOGOS → Requirements → Custom topic types with definable status workflows (this Spec type is a concrete instance of that requirement)
- LOGOS → Requirements → Event-sourced storage as the foundation (state transitions are events)