Commit graph

2 commits

Author SHA1 Message Date
4819fd919a Write SCOPE.md, and record that pr-hall-of-helix now exists
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
2026-09-04 21:11:35 +02:00
82becd0fda Register with State Hub and align workplan IDs to FLUID-WP prefix
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_014KmVxhJ35tCo7rE7UnLwWu

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 1116572@bnt-lap001
Assistant-Session: 8ba9bb93-a72a-4883-b189-2499cce5c400
2026-09-04 01:50:34 +02:00