|
Some checks failed
ci / build (push) Has been cancelled
SCOPE.md was the register-generated stub. It now names the planes and the packages behind them, the wire contract as the boundary, and what the framework deliberately does not own -- the interfaces, the campaigns, backend authority, and Phase D. Adds three boundary tests, because most "does this belong in fluid-core?" arguments reduce to one of them: could the control plane be killed right now with no runtime effect; does this require the target API to change or link anything; and would this be here if the Hall of Helix did not exist. FLUID-WP-0009 T02 moves to progress. pr-hall-of-helix was created and registered early, because the provisioning work needed a home for the presence spec. The campaign itself has not moved, which is the part the "after FT-WP-0001 T12" sequencing was protecting. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0172sgCZEEDJcnQmr4SGDvKa Assistant: claude-code Assistant-Model: opus Assistant-Process: 1361245@bnt-lap001 Assistant-Session: b3b428ef-f3e6-4688-b091-01f71461d66a |
||
|---|---|---|
| .. | ||
| FLUID-WP-0001-statehub-bootstrap.md | ||
| FLUID-WP-0002-foundations-and-wire-contract.md | ||
| FLUID-WP-0003-deterministic-data-plane.md | ||
| FLUID-WP-0004-publication-and-control-apis.md | ||
| FLUID-WP-0005-fluid-insight.md | ||
| FLUID-WP-0006-fluid-science.md | ||
| FLUID-WP-0007-conformance-and-self-validation.md | ||
| FLUID-WP-0008-fluid-telegram-handover.md | ||
| FLUID-WP-0009-campaign-repos-and-example-separation.md | ||