chore: retire Discussion Framework workflow and retain lessons
Test / Tests and coverage
Intrepid/Prometeu/Studio/pipeline/head This commit looks good

This commit is contained in:
2026-11-16 16:45:34 +00:00
parent cd001ce2d9
commit fa37d0d0c7
8 changed files with 18 additions and 17 deletions
+4 -3
View File
@@ -22,9 +22,10 @@ The runtime repository owns PBX, ISA, admission and VM execution. Studio's
their separate provenance and synchronization policy. [Roadmaps](../roadmaps/)
describe cross-domain planning, not an alternative contract source.
The operational lifecycle is `agenda -> decision -> plan -> implement -> lesson`.
Keep its artifacts in `discussion/` and use the local `discussion` CLI for state
transitions, validation and housekeeping. See [repository instructions](../../AGENTS.md).
Engineering discussions, decisions, plans and execution evidence are maintained
in the enclosing workspace's [AI Engineering project](../../../.ai-engineering/README.md).
Published lessons and supporting assets remain in `discussion/lessons/`.
See [repository instructions](../../AGENTS.md).
## Navigation verification
+3 -2
View File
@@ -41,7 +41,8 @@ are stable and do not imply language-version numbers.
Write specs in English with title, status, scope, authority, normative rules,
non-goals and conformance/exit criteria. Keep one owner per detailed contract;
summaries link to it. Only settled decisions may change normative behavior.
Agendas, decisions and plans live in `discussion/`, and completed teaching
material lives in `discussion/lessons/`; they are not parallel spec sources.
Engineering discussions, decisions and plans live in the enclosing workspace's
AI Engineering project. Published teaching material remains in
`discussion/lessons/`; neither is a parallel spec source.
See the [specification guide](../README.md) for other domains.
@@ -411,7 +411,7 @@ mature gameplay library is not a prerequisite.
- Replacing compiler, Packer, LSP, VM or human Debug semantics; a new general-purpose Studio source editor.
- Remote MCP, accounts/OAuth and network runtime discovery. Studio-owned stdio and local Codex preparation are the explicit DEC-0061 additions.
- Additional language implementation, persistent operation recovery or automatic task resumption.
- Integrated discussion-framework agendas/decisions/plans in the product; those are future work, not this runtime/DEV/MCP contract.
- Product-integrated engineering workflow management is outside this runtime/DEV/MCP contract.
## Exit Criteria