Infrastructure · Data Structures
Spec
Rigorous requirement definition
Definition
Mechanism
A rigorous definition of requirements for an Artifact. It defines the shape, behavior, and Constraints that a target must satisfy. Distinct from Plan (how to build) or Goal (what to achieve), a Spec is the 'Definition of Done'.
Invariants
- Verifiability: Every requirement must be testable (binary pass/fail).
- Immutability: Once defined, the Spec acts as a fixed contract.
Risks
Failure modes
None stated.
Relationships
Builds on
References
Immutable data unit
Non-negotiable boundary condition
Specification of desired end state
An ordered sequence of steps to achieve a goal
Used by
References
Non-compensatory acceptance contract; consumer Verify yields Solution or FrameError
Structured problem definition artifact
Test a stated relation among the outputs of several runs, which needs no exact expected answer for any single run
Mind
Bind an implementation to an external specification by a pinned version, a two-way map and a ledger of deviations
Mind
Check the specification itself against intent and its own consequences before trusting conformance to it
Codified aesthetic standards
Mind
Confirming alignment with truth or spec
Accepts
Mind
Low-cost prototype generation
Reference
Data schema
{
"type": "object",
"description": "Schema for Spec",
"properties": {
"requirements": {
"type": "array",
"items": {
"type": "string"
},
"description": "The testable requirements the target must satisfy. Required: a Spec with none defines nothing."
},
"constraints": {
"type": "object"
}
},
"required": [
"requirements"
]
}