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
This commit is contained in:
tegwick 2026-09-04 01:50:34 +02:00
parent c2cfe86d88
commit 82becd0fda
12 changed files with 408 additions and 83 deletions

View file

@ -0,0 +1,55 @@
---
id: FLUID-WP-0001
type: workplan
title: "Bootstrap State Hub integration"
domain: infotech
repo: fluid-core
status: ready
owner: worsch
topic_slug: fluid-core
created: "2026-09-04"
updated: "2026-09-04"
---
# Bootstrap State Hub integration
Core framework for fluid interfaces to provide adaptive robust systems capability integration.
## Review Generated Integration Files
```task
id: FLUID-WP-0001-T01
status: todo
priority: high
```
Review `INTENT.md`, `SCOPE.md`, `AGENTS.md`, and `.custodian-brief.md`.
Replace generated placeholders with repo-specific facts where needed.
## Verify Local Developer Workflow
```task
id: FLUID-WP-0001-T02
status: todo
priority: high
```
Identify the repo's install, test, lint, build, and run commands. Add or refine
those commands in the agent instructions so future coding sessions can verify
changes confidently.
## Seed First Real Workplan
```task
id: FLUID-WP-0001-T03
status: todo
priority: medium
```
Create the first implementation workplan for the repository's most important
next change. After workplan file updates, run the sync locally from this repo
checkout:
```bash
statehub fix-consistency
```

View file

@ -1,12 +1,12 @@
---
id: FC-WP-0001
id: FLUID-WP-0002
type: workplan
title: "FLUID foundations and the wire contract"
domain: infotech
repo: fluid-core
status: active
owner: worsch
topic_slug: fluid
topic_slug: fluid-core
created: "2026-09-04"
updated: "2026-09-04"
planning_priority: high
@ -17,7 +17,7 @@ related_repos:
- fluid-substack
---
# FC-WP-0001 - Foundations and the wire contract
# FLUID-WP-0002 - Foundations and the wire contract
Establish the boundary before any code depends on it. fluid-core integrates
out of process, so its contract is a set of on-the-wire artifacts, not a Go
@ -29,7 +29,7 @@ Reference: `spec/FluidHypothesisRevisionSchema.md`, `spec/ArchitectureBlueprint.
## T01 - Repository scaffold and INTENT
```task
id: FC-WP-0001-T01
id: FLUID-WP-0002-T01
status: done
priority: high
```
@ -40,7 +40,7 @@ boundary and the four invariants this repo defends hardest.
## T02 - Record schemas
```task
id: FC-WP-0001-T02
id: FLUID-WP-0002-T02
status: todo
priority: high
```
@ -53,7 +53,7 @@ the interop surface, per its §1.
## T03 - Descriptor and policy schemas
```task
id: FC-WP-0001-T03
id: FLUID-WP-0002-T03
status: todo
priority: high
```
@ -65,7 +65,7 @@ readable without any fluid-core code.
## T04 - Type generation
```task
id: FC-WP-0001-T04
id: FLUID-WP-0002-T04
status: todo
priority: high
```
@ -76,7 +76,7 @@ types are prohibited — drift between spec and implementation must fail CI.
## T05 - Spec examples as fixtures
```task
id: FC-WP-0001-T05
id: FLUID-WP-0002-T05
status: todo
priority: high
```
@ -88,7 +88,7 @@ build breaks.
## T06 - Build, CI and identifier conventions
```task
id: FC-WP-0001-T06
id: FLUID-WP-0002-T06
status: todo
priority: medium
```
@ -99,7 +99,7 @@ identifier prefix helpers from schema doc §16: `H- R- E- P- BR- D- EV- F- C-`.
## T07 - Architecture decision records
```task
id: FC-WP-0001-T07
id: FLUID-WP-0002-T07
status: todo
priority: medium
```

View file

@ -1,21 +1,21 @@
---
id: FC-WP-0002
id: FLUID-WP-0003
type: workplan
title: "Deterministic data plane (Blueprint Phase A)"
domain: infotech
repo: fluid-core
status: active
owner: worsch
topic_slug: fluid
topic_slug: fluid-core
created: "2026-09-04"
updated: "2026-09-04"
planning_priority: high
planning_order: 2
depends_on:
- FC-WP-0001
- FLUID-WP-0002
---
# FC-WP-0002 - Deterministic data plane
# FLUID-WP-0003 - Deterministic data plane
The production request path. No AI, no analysis, no dependency on the control
plane. Blueprint §5 and §34: the gateway must keep serving when everything
@ -24,7 +24,7 @@ above it is dead.
## T01 - Edge gateway
```task
id: FC-WP-0002-T01
id: FLUID-WP-0003-T01
status: todo
priority: high
```
@ -35,7 +35,7 @@ shape limits. Blueprint §5.1 — the gateway must not invent interface semantic
## T02 - Revision resolver
```task
id: FC-WP-0002-T02
id: FLUID-WP-0003-T02
status: todo
priority: high
```
@ -47,7 +47,7 @@ without an auditable reason is a defect.
## T03 - Revision router
```task
id: FC-WP-0002-T03
id: FLUID-WP-0003-T03
status: todo
priority: high
```
@ -59,7 +59,7 @@ read from routing policy the router does not author.
## T04 - Contract validator
```task
id: FC-WP-0002-T04
id: FLUID-WP-0003-T04
status: todo
priority: high
```
@ -70,7 +70,7 @@ of the revision artifact and is content-addressed.
## T05 - Backend connector layer
```task
id: FC-WP-0002-T05
id: FLUID-WP-0003-T05
status: todo
priority: high
```
@ -82,7 +82,7 @@ language-agnostic promise is kept.
## T06 - Response policy
```task
id: FC-WP-0002-T06
id: FLUID-WP-0003-T06
status: todo
priority: medium
```
@ -93,7 +93,7 @@ detail (§5.7).
## T07 - Telemetry emitter
```task
id: FC-WP-0002-T07
id: FLUID-WP-0003-T07
status: todo
priority: high
```
@ -104,7 +104,7 @@ backpressure must never block or slow a request. Test it under a stalled sink.
## T08 - Evidence store
```task
id: FC-WP-0002-T08
id: FLUID-WP-0003-T08
status: todo
priority: high
```
@ -115,7 +115,7 @@ summaries exist only as derived views (§26).
## T09 - Intent store
```task
id: FC-WP-0002-T09
id: FLUID-WP-0003-T09
status: todo
priority: high
```
@ -127,7 +127,7 @@ was made.
## T10 - Operator CLI, first commands
```task
id: FC-WP-0002-T10
id: FLUID-WP-0003-T10
status: todo
priority: medium
```

View file

@ -1,21 +1,21 @@
---
id: FC-WP-0003
id: FLUID-WP-0004
type: workplan
title: "Revision publication pipeline and control APIs"
domain: infotech
repo: fluid-core
status: active
owner: worsch
topic_slug: fluid
topic_slug: fluid-core
created: "2026-09-04"
updated: "2026-09-04"
planning_priority: high
planning_order: 3
depends_on:
- FC-WP-0002
- FLUID-WP-0003
---
# FC-WP-0003 - Publication and control APIs
# FLUID-WP-0004 - Publication and control APIs
Nothing reaches the router unsigned. The deterministic policy gate is built now,
before anything can generate candidates, so a future Daimon has nowhere to
@ -24,7 +24,7 @@ bypass.
## T01 - Publication pipeline
```task
id: FC-WP-0003-T01
id: FLUID-WP-0004-T01
status: todo
priority: high
```
@ -35,7 +35,7 @@ CHECK, SIGN, PUBLISH, ROUTE. Each stage emits an audit event.
## T02 - Descriptor signing and verification
```task
id: FC-WP-0003-T02
id: FLUID-WP-0004-T02
status: todo
priority: high
```
@ -47,7 +47,7 @@ tested.
## T03 - Revision API
```task
id: FC-WP-0003-T03
id: FLUID-WP-0004-T03
status: todo
priority: high
```
@ -57,7 +57,7 @@ Blueprint §44.1: create, verify, publish, set state, query lineage.
## T04 - Intent API
```task
id: FC-WP-0003-T04
id: FLUID-WP-0004-T04
status: todo
priority: medium
```
@ -69,7 +69,7 @@ governed — the API records a proposal, it does not enact one.
## T05 - Deterministic policy gate
```task
id: FC-WP-0003-T05
id: FLUID-WP-0004-T05
status: todo
priority: high
```
@ -83,7 +83,7 @@ policy.
## T06 - Trust model in the type system
```task
id: FC-WP-0003-T06
id: FLUID-WP-0004-T06
status: todo
priority: medium
```

View file

@ -1,21 +1,21 @@
---
id: FC-WP-0004
id: FLUID-WP-0005
type: workplan
title: "FLUID Insight - observation plane (Blueprint Phase B)"
domain: infotech
repo: fluid-core
status: active
owner: worsch
topic_slug: fluid
topic_slug: fluid-core
created: "2026-09-04"
updated: "2026-09-04"
planning_priority: high
planning_order: 4
depends_on:
- FC-WP-0003
- FLUID-WP-0004
---
# FC-WP-0004 - FLUID Insight
# FLUID-WP-0005 - FLUID Insight
Turn traffic into evidence. Deterministic heuristics only at this stage — no
model inference anywhere in this workplan.
@ -23,7 +23,7 @@ model inference anywhere in this workplan.
## T01 - Telemetry ingest and normalizer
```task
id: FC-WP-0004-T01
id: FLUID-WP-0005-T01
status: todo
priority: high
```
@ -34,7 +34,7 @@ normalized interaction event (Blueprint §6.1).
## T02 - Redaction and privacy filter
```task
id: FC-WP-0004-T02
id: FLUID-WP-0005-T02
status: todo
priority: high
```
@ -46,7 +46,7 @@ FLUID learns about the interface, not about people.
## T03 - Cohort engine
```task
id: FC-WP-0004-T03
id: FLUID-WP-0005-T03
status: todo
priority: medium
```
@ -57,7 +57,7 @@ not be more specific than the analysis requires.
## T04 - Interaction topology analyzer
```task
id: FC-WP-0004-T04
id: FLUID-WP-0005-T04
status: todo
priority: high
```
@ -68,7 +68,7 @@ error counting.
## T05 - Pressure classifier
```task
id: FC-WP-0004-T05
id: FLUID-WP-0005-T05
status: todo
priority: high
```
@ -79,7 +79,7 @@ in every case.
## T06 - Pressure registry
```task
id: FC-WP-0004-T06
id: FLUID-WP-0005-T06
status: todo
priority: high
```
@ -91,7 +91,7 @@ deserves adaptation.
## T07 - Fitness engine
```task
id: FC-WP-0004-T07
id: FLUID-WP-0005-T07
status: todo
priority: high
```
@ -102,7 +102,7 @@ distinct. Baseline and measurement window are retained, never recomputed.
## T08 - Explicit feedback collector
```task
id: FC-WP-0004-T08
id: FLUID-WP-0005-T08
status: todo
priority: medium
```
@ -113,7 +113,7 @@ treated as authority to change anything.
## T09 - CLI and pressure API
```task
id: FC-WP-0004-T09
id: FLUID-WP-0005-T09
status: todo
priority: medium
```

View file

@ -1,21 +1,21 @@
---
id: FC-WP-0005
id: FLUID-WP-0006
type: workplan
title: "FLUID Science - the adaptation loop closes (Blueprint Phase C)"
domain: infotech
repo: fluid-core
status: active
owner: worsch
topic_slug: fluid
topic_slug: fluid-core
created: "2026-09-04"
updated: "2026-09-04"
planning_priority: high
planning_order: 5
depends_on:
- FC-WP-0004
- FLUID-WP-0005
---
# FC-WP-0005 - FLUID Science
# FLUID-WP-0006 - FLUID Science
Hypotheses, experiments, fitness and promotion. Entirely human-driven — the
Daimon is deliberately absent. Blueprint §50 says the success criterion is
@ -24,7 +24,7 @@ proving this loop works cleanly and safely, not autonomous coding.
## T01 - Hypothesis records and lifecycle
```task
id: FC-WP-0005-T01
id: FLUID-WP-0006-T01
status: todo
priority: high
```
@ -37,7 +37,7 @@ collapsing them into one narrative destroys criticism and auditability.
## T02 - Competition groups
```task
id: FC-WP-0005-T02
id: FLUID-WP-0006-T02
status: todo
priority: medium
```
@ -48,7 +48,7 @@ uncertainty is a feature.
## T03 - Hypothesis API
```task
id: FC-WP-0005-T03
id: FLUID-WP-0006-T03
status: todo
priority: medium
```
@ -58,7 +58,7 @@ Blueprint §44.3: create, compare, prioritize, attach candidate, record outcome.
## T04 - Experiment controller
```task
id: FC-WP-0005-T04
id: FLUID-WP-0006-T04
status: todo
priority: high
```
@ -71,7 +71,7 @@ Experiments are interruptible.
## T05 - Experiment API
```task
id: FC-WP-0005-T05
id: FLUID-WP-0006-T05
status: todo
priority: medium
```
@ -82,7 +82,7 @@ finalize.
## T06 - Fitness evaluation against hypotheses
```task
id: FC-WP-0005-T06
id: FLUID-WP-0006-T06
status: todo
priority: high
```
@ -93,7 +93,7 @@ after results are visible without recording the amendment (§18).
## T07 - Promotion controller
```task
id: FC-WP-0005-T07
id: FLUID-WP-0006-T07
status: todo
priority: high
```
@ -104,7 +104,7 @@ recorded as decisions with an authorizing actor (§19). Human authority only.
## T08 - Append-only event log
```task
id: FC-WP-0005-T08
id: FLUID-WP-0006-T08
status: todo
priority: high
```
@ -115,7 +115,7 @@ itself a system behavior that must remain reconstructable.
## T09 - Audit trace command
```task
id: FC-WP-0005-T09
id: FLUID-WP-0006-T09
status: todo
priority: high
```

View file

@ -1,21 +1,21 @@
---
id: FC-WP-0006
id: FLUID-WP-0007
type: workplan
title: "Conformance suite and self-validation"
domain: infotech
repo: fluid-core
status: active
owner: worsch
topic_slug: fluid
topic_slug: fluid-core
created: "2026-09-04"
updated: "2026-09-04"
planning_priority: high
planning_order: 6
depends_on:
- FC-WP-0005
- FLUID-WP-0006
---
# FC-WP-0006 - Conformance and self-validation
# FLUID-WP-0007 - Conformance and self-validation
Prove the loop mechanically before a real workload depends on it. Everything
here runs in CI with no human steps and no external services.
@ -23,7 +23,7 @@ here runs in CI with no human steps and no external services.
## T01 - Echo interface fixture
```task
id: FC-WP-0006-T01
id: FLUID-WP-0007-T01
status: todo
priority: high
```
@ -35,7 +35,7 @@ reproduction of the Blueprint §33 worked example.
## T02 - Minimal conformance assertions
```task
id: FC-WP-0006-T02
id: FLUID-WP-0007-T02
status: todo
priority: high
```
@ -46,7 +46,7 @@ claimed in a README.
## T03 - Architectural invariant checks
```task
id: FC-WP-0006-T03
id: FLUID-WP-0007-T03
status: todo
priority: high
```
@ -58,7 +58,7 @@ until verified) matter most and get dedicated tests.
## T04 - Failure containment matrix
```task
id: FC-WP-0006-T04
id: FLUID-WP-0007-T04
status: todo
priority: high
```
@ -70,7 +70,7 @@ configuration each time.
## T05 - End-to-end loop in CI
```task
id: FC-WP-0006-T05
id: FLUID-WP-0007-T05
status: todo
priority: high
```
@ -81,7 +81,7 @@ fitness comparison, promotion, complete audit trail.
## T06 - Integration guide
```task
id: FC-WP-0006-T06
id: FLUID-WP-0007-T06
status: todo
priority: medium
```

View file

@ -1,25 +1,25 @@
---
id: FC-WP-0007
id: FLUID-WP-0008
type: workplan
title: "Handover: HelixForge Telegram identity and hall-of-helix channel"
domain: infotech
repo: fluid-core
status: active
owner: worsch
topic_slug: fluid
topic_slug: fluid-core
created: "2026-09-04"
updated: "2026-09-04"
planning_priority: high
planning_order: 7
depends_on:
- FC-WP-0006
- FLUID-WP-0007
related_repos:
- fluid-telegram
- helix-forge
- hall-of-helix
---
# FC-WP-0007 - Handover to fluid-telegram
# FLUID-WP-0008 - Handover to fluid-telegram
The point of the whole sequence. Establish a Telegram identity for HelixForge
and a channel publishing hall-of-helix entries, as the first real FLUID
@ -32,7 +32,7 @@ in the `fluid-telegram` repository.
## T01 - Interface evolution intent
```task
id: FC-WP-0007-T01
id: FLUID-WP-0008-T01
status: todo
priority: high
```
@ -46,7 +46,7 @@ entities, change membership, or touch credentials.
## T02 - Bot identity
```task
id: FC-WP-0007-T02
id: FLUID-WP-0008-T02
status: todo
priority: high
```
@ -59,7 +59,7 @@ Blueprint §28.1 runtime identity.
## T03 - Channels
```task
id: FC-WP-0007-T03
id: FLUID-WP-0008-T03
status: todo
priority: high
```
@ -72,7 +72,7 @@ published publicly.
## T04 - Revision R-1 contract
```task
id: FC-WP-0007-T04
id: FLUID-WP-0008-T04
status: todo
priority: high
```
@ -83,7 +83,7 @@ priority: high
## T05 - Telegram adapter and connector contract
```task
id: FC-WP-0007-T05
id: FLUID-WP-0008-T05
status: todo
priority: high
```
@ -96,7 +96,7 @@ error mapping.
## T06 - Cohorts, telemetry and redaction
```task
id: FC-WP-0007-T06
id: FLUID-WP-0008-T06
status: todo
priority: high
```
@ -107,7 +107,7 @@ Telegram user identity (Canon ID-01) out of the evidence store entirely.
## T07 - First competing hypotheses
```task
id: FC-WP-0007-T07
id: FLUID-WP-0008-T07
status: todo
priority: high
```
@ -121,7 +121,7 @@ highest-value place to start.
## T08 - Live experiment and audit
```task
id: FC-WP-0007-T08
id: FLUID-WP-0008-T08
status: todo
priority: high
```
@ -133,7 +133,7 @@ reconstructs the whole chain. This is the §50 slice on a real workload.
## T09 - Runbook and handover package
```task
id: FC-WP-0007-T09
id: FLUID-WP-0008-T09
status: todo
priority: medium
```