mirror of
https://github.com/openprose/prose.git
synced 2026-09-19 05:55:05 +08:00
Jose Montes de Oca
2c338823f3
With the Reactor harness in its own repository, the language describes its run-phase model for what it is rather than after one implementation of it. - concepts/reactor.md → concepts/reconciler.md; spec/02 keeps only the contract any conforming harness must satisfy (02-Harness.md) and spec/03 becomes 03-AuthoringPattern.md. "Reactor" in the model sense is now "the reconciler" across the Skill, std, and the examples. - The example corpus is harness-neutral: authored intent plus the observable behaviour a harness must preserve. Quick Start examples carry the Skill's own flow (prose compile → promote → prose serve) and say what serve waits for; expanded-topology examples state what src/ ships and what a harness's expansion produces from it. - The Skill's run-flow docs agree with each other and with the spec: serve defines the manifest promotion step, compile names what ir-v0.md emits, ir-v0.md is the authoritative IR contract, and the spec lists compile/serve/status as in-session verbs that a conforming harness may deliver durably outside the session. - A harness-surface conformance test keeps product tokens out of the Skill, spec, std/co, and root docs, outside the README's Harnesses section and the Skill changelog. Skill 0.16.0; runtime_contract stays 2. The Skill changelog records the migration so prose upgrade can route workflows that used prose react.