Proposals · sp-0002
Describe specialists as files
openDiscussion and state illustrated
- Problem
- Specialists are defined in code, so a new role cannot be proposed without changing the software.
- Change
- Describe each specialist in a file with its role, inputs, outputs and output contract, validated like templates.
- Consequences
- Existing specialists need descriptions; the software reads specialists from files.
- Source
- Standard Explorer §8: "Specialists as files: Planned."
Discussion
The steering group decides after the discussion and publishes the decision with its reasons here.
Which existing building blocks would fail conformance after this change? A list would help maintainers plan new versions.