From 82becd0fda2f9ee310eb9aebf6bf714b9a45d7ae Mon Sep 17 00:00:00 2001 From: tegwick Date: Fri, 4 Sep 2026 01:50:34 +0200 Subject: [PATCH] Register with State Hub and align workplan IDs to FLUID-WP prefix Co-Authored-By: Claude Opus 5 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 --- .custodian-brief.md | 27 +++ .gitignore | 6 + AGENTS.md | 205 ++++++++++++++++++ SCOPE.md | 32 +++ workplans/FLUID-WP-0001-statehub-bootstrap.md | 55 +++++ ...-WP-0002-foundations-and-wire-contract.md} | 20 +- ...FLUID-WP-0003-deterministic-data-plane.md} | 28 +-- ...D-WP-0004-publication-and-control-apis.md} | 20 +- ...ight.md => FLUID-WP-0005-fluid-insight.md} | 26 +-- ...ence.md => FLUID-WP-0006-fluid-science.md} | 26 +-- ...P-0007-conformance-and-self-validation.md} | 20 +- ... FLUID-WP-0008-fluid-telegram-handover.md} | 26 +-- 12 files changed, 408 insertions(+), 83 deletions(-) create mode 100644 .custodian-brief.md create mode 100644 AGENTS.md create mode 100644 SCOPE.md create mode 100644 workplans/FLUID-WP-0001-statehub-bootstrap.md rename workplans/{FC-WP-0001-foundations-and-wire-contract.md => FLUID-WP-0002-foundations-and-wire-contract.md} (91%) rename workplans/{FC-WP-0002-deterministic-data-plane.md => FLUID-WP-0003-deterministic-data-plane.md} (89%) rename workplans/{FC-WP-0003-publication-and-control-apis.md => FLUID-WP-0004-publication-and-control-apis.md} (89%) rename workplans/{FC-WP-0004-fluid-insight.md => FLUID-WP-0005-fluid-insight.md} (88%) rename workplans/{FC-WP-0005-fluid-science.md => FLUID-WP-0006-fluid-science.md} (90%) rename workplans/{FC-WP-0006-conformance-and-self-validation.md => FLUID-WP-0007-conformance-and-self-validation.md} (87%) rename workplans/{FC-WP-0007-fluid-telegram-handover.md => FLUID-WP-0008-fluid-telegram-handover.md} (91%) diff --git a/.custodian-brief.md b/.custodian-brief.md new file mode 100644 index 0000000..8a453ad --- /dev/null +++ b/.custodian-brief.md @@ -0,0 +1,27 @@ + +# Custodian Brief - fluid-core + +**Project:** fluid-core +**Domain:** infotech +**State Hub:** http://127.0.0.1:8000 +**Topic ID:** `cee7bedf-2b48-46ef-8601-006474f2ad7a` + +## Open Workplans + +### Bootstrap State Hub integration + +Workplan file: `workplans/FLUID-WP-0001-statehub-bootstrap.md` + +Open tasks: +- T01 - Review generated integration files +- T02 - Verify local developer workflow +- T03 - Seed first real workplan + +## Session Start + +1. Read `INTENT.md`, `SCOPE.md`, and `AGENTS.md`. +2. Check inbox: `GET /messages/?to_agent=fluid-core&unread_only=true`. +3. Scan `workplans/`. +4. Update task statuses in workplan files as work progresses. + +Last generated: 2026-09-04 diff --git a/.gitignore b/.gitignore index 24bad2b..696d896 100644 --- a/.gitignore +++ b/.gitignore @@ -2,3 +2,9 @@ *.db *.sqlite .env + +# state-hub: track .claude/rules +# Claude Code local state (track shared rules; ignore machine-specific files) +.claude/* +!.claude/rules/ +!.claude/rules/*.md diff --git a/AGENTS.md b/AGENTS.md new file mode 100644 index 0000000..6e7ed9d --- /dev/null +++ b/AGENTS.md @@ -0,0 +1,205 @@ +# fluid-core — Agent Instructions + +## Repo Identity + +**Purpose:** Core framework for fluid interfaces to provide adaptive robust systems capability integration. + +**Domain:** infotech +**Repo slug:** fluid-core +**Topic ID:** `cee7bedf-2b48-46ef-8601-006474f2ad7a` +**Workplan prefix:** `FLUID-WP-` + +--- + +## State Hub Integration + +The Custodian State Hub tracks work across all domains. Codex uses HTTP REST and +the `statehub` CLI by default. MCP is opt-in because the current Codex MCP bridge +adds severe call latency; the full administrative MCP surface remains available +to clients that need it. + +| Context | URL | +|---------|-----| +| Local workstation | `http://127.0.0.1:8000` | +| Remote via tunnel | `http://127.0.0.1:18000` | +| Optional local edge relay | http://127.0.0.1:18080 | + +When an operator has enabled the edge relay, set API_BASE to the relay URL. +Queueable writes return an explicit queued receipt if the central hub is +unreachable. Treat that as pending local evidence, then ask the operator to run +statehub outbox status/replay after connectivity returns. + +Codex workspace-write sandboxes need network access enabled to reach the host's +loopback listener. Bootstrap this once with `make -C ~/state-hub configure-codex` +and restart Codex. The canonical REST health endpoint is `/state/health`, not +`/health`. If a sandboxed loopback probe fails, retry it with escalated execution +before declaring State Hub unavailable; a managed Codex permission profile may +still enforce isolated networking. Experimental MCP can be enabled explicitly +with `make -C ~/state-hub configure-codex WITH_MCP=1`. + +### Orient at session start + +```bash +# Offline brief — works without hub connection +cat .custodian-brief.md + +# Active workplans for this domain +curl -s "http://127.0.0.1:8000/workplans/?topic_id=cee7bedf-2b48-46ef-8601-006474f2ad7a&status=active" \ + | python3 -m json.tool + +# Check inbox +curl -s "http://127.0.0.1:8000/messages/?to_agent=fluid-core&unread_only=true" \ + | python3 -m json.tool +``` + +Mark a message read: +```bash +curl -s -X PATCH "http://127.0.0.1:8000/messages//read" \ + -H "Content-Type: application/json" -d '{}' +``` + +### Log progress (required at session close) + +```bash +curl -s -X POST http://127.0.0.1:8000/progress/ \ + -H "Content-Type: application/json" \ + -d '{ + "summary": "what was done", + "event_type": "note", + "author": "codex", + "workplan_id": "", + "task_id": "" + }' +``` + +Omit `workplan_id` / `task_id` when not applicable. + +### Update task status + +```bash +curl -s -X PATCH "http://127.0.0.1:8000/tasks/" \ + -H "Content-Type: application/json" \ + -d '{"status": "progress"}' +# values: wait | todo | progress | done | cancel +``` + +### Flag a task for human review + +```bash +curl -s -X PATCH "http://127.0.0.1:8000/tasks/" \ + -H "Content-Type: application/json" \ + -d '{"needs_human": true, "intervention_note": "reason"}' +``` + +--- + +## Session Protocol + +**Start:** +1. `cat .custodian-brief.md` — domain goal and open workplans (offline-safe) +2. Check inbox: `GET /messages/?to_agent=fluid-core&unread_only=true`; mark read +3. Scan workplans: `ls workplans/` — note `status: ready`, `active`, or `blocked` files and open tasks +4. Check human-needed tasks: `GET /tasks/?needs_human=true` + +**During work:** +- Update task statuses in workplan files as tasks progress +- Record significant decisions via `POST /decisions/` + +**Close:** +1. Update workplan file task statuses to reflect progress +2. If finishing a workplan: hand off **residuals** as live work records first + (intake with `origin: residual` + `origin_ref: `, or a next workplan / + decision / engagement). Do not park leftovers only in prose or `SCOPE.md`. + Canon: `the-custodian/canon/standards/work-record-types_v0.1.md` § Residuals. +3. Log: `POST /progress/` with a summary of what changed (name handoff ids) +4. After workplan file changes, run: + ```bash + uv run --project ~/repo-manager rmgr sync --path . --push + ``` + This assigns only missing deterministic identifiers, verifies the pushed + Forgejo commit and `primary/railliance01`, then requests one central + reconciliation. A queued receipt is pending evidence; rerun after + connectivity returns. Use `statehub fix-consistency` for a separate deep audit. + +--- + +{CREDENTIAL_ROUTING} + + + + +--- + +## Workplan Convention (ADR-001) + +Work items originate as files in this repo — not in the hub. The hub is a +read/cache/index layer that rebuilds from files. + +**File location:** `workplans/FLUID-WP-NNNN-.md` + +**Archived location:** finished workplans may move to +`workplans/archived/YYMMDD-FLUID-WP-NNNN-.md`. The `YYMMDD` prefix is +the completion/archive date; the frontmatter `id` does not change. + +**Ad Hoc Tasks:** small opportunistic fixes discovered during a session use +`workplans/ADHOC-YYYY-MM-DD.md`, workplan id +`FLUID-WP-ADHOC-YYYY-MM-DD`, and task ids +`FLUID-WP-ADHOC-YYYY-MM-DD-T01`, etc. `FLUID-WP` includes its final `-WP` +token. Unqualified historic `ADHOC-*` ids are grandfathered and must not be +copied into new records. Use this only for low-risk work completed directly; +create a normal workplan for anything needing analysis, design, approval, +dependencies, or multiple phases. + +**Frontmatter:** + +```yaml +--- +id: FLUID-WP-NNNN +type: workplan +title: "..." +domain: infotech +repo: fluid-core +status: proposed | ready | active | blocked | backlog | finished | archived +owner: codex +topic_slug: ... +created: "YYYY-MM-DD" +updated: "YYYY-MM-DD" +state_hub_workstream_id: "" # deterministic UUIDv5; managed by Repo Manager +--- +``` + +Use `proposed` for a new draft, `ready` after review against current repo +state, and `finished` after implementation. `stalled` and `needs_review` are +derived health labels, not frontmatter statuses. + +**Terminology:** workplan is the fleet term; `workstream` appears only in legacy +API/MCP/frontmatter bridges until `STATE-WP-0069` retires them — see +`the-custodian/canon/standards/workplan-terminology-fleet_v0.1.md`. + +**Task block format** (one per `##` section): + +``` +## Task Title + +` ` `task +id: FLUID-WP-NNNN-T01 +status: wait | todo | progress | done | cancel +priority: high | medium | low +state_hub_task_id: "" # deterministic UUIDv5; managed by Repo Manager +` ` ` + +Task description text. +``` + +Status progression: `todo` → `progress` → `done`; use `wait` for waiting/blocked work and `cancel` for stopped work. + +**Residuals when finishing:** actionable leftovers become live work records +before `status: finished` — usually an intake (`origin: residual`, +`origin_ref: FLUID-WP-NNNN`) or a spawned workplan. Residual is a *role*, +not a kind. Fleet list lives on State Hub, not in `SCOPE.md`. + +To create a new workplan: +1. Write the file following the format above +2. Run `uv run --project ~/repo-manager rmgr sync --path . --push`. +3. Run `statehub fix-consistency` only when a separate deep audit is needed. diff --git a/SCOPE.md b/SCOPE.md new file mode 100644 index 0000000..d720a7b --- /dev/null +++ b/SCOPE.md @@ -0,0 +1,32 @@ +# SCOPE + +> This file was generated by `statehub register`. Refine it as the repository +> boundaries become clearer. + +## One-liner + +Core framework for fluid interfaces to provide adaptive robust systems capability integration. + +## Core Idea + +fluid-core exists to provide the capability described in INTENT.md. + +## In Scope + +- Maintain the repository's primary implementation. +- Keep docs, tests, and operational metadata current. + +## Out of Scope + +- Own unrelated adjacent systems. +- Make irreversible operational decisions without human approval. + +## Current State + +- Status: active; implementation and stability should be verified by the repo agent. + +## Getting Oriented + +- Start with: INTENT.md +- Agent instructions: AGENTS.md +- Workplans: workplans/ diff --git a/workplans/FLUID-WP-0001-statehub-bootstrap.md b/workplans/FLUID-WP-0001-statehub-bootstrap.md new file mode 100644 index 0000000..621ff2e --- /dev/null +++ b/workplans/FLUID-WP-0001-statehub-bootstrap.md @@ -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 +``` diff --git a/workplans/FC-WP-0001-foundations-and-wire-contract.md b/workplans/FLUID-WP-0002-foundations-and-wire-contract.md similarity index 91% rename from workplans/FC-WP-0001-foundations-and-wire-contract.md rename to workplans/FLUID-WP-0002-foundations-and-wire-contract.md index fe1fb06..a861797 100644 --- a/workplans/FC-WP-0001-foundations-and-wire-contract.md +++ b/workplans/FLUID-WP-0002-foundations-and-wire-contract.md @@ -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 ``` diff --git a/workplans/FC-WP-0002-deterministic-data-plane.md b/workplans/FLUID-WP-0003-deterministic-data-plane.md similarity index 89% rename from workplans/FC-WP-0002-deterministic-data-plane.md rename to workplans/FLUID-WP-0003-deterministic-data-plane.md index bb3b2ee..3d2d9d9 100644 --- a/workplans/FC-WP-0002-deterministic-data-plane.md +++ b/workplans/FLUID-WP-0003-deterministic-data-plane.md @@ -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 ``` diff --git a/workplans/FC-WP-0003-publication-and-control-apis.md b/workplans/FLUID-WP-0004-publication-and-control-apis.md similarity index 89% rename from workplans/FC-WP-0003-publication-and-control-apis.md rename to workplans/FLUID-WP-0004-publication-and-control-apis.md index fe95bab..ffe206a 100644 --- a/workplans/FC-WP-0003-publication-and-control-apis.md +++ b/workplans/FLUID-WP-0004-publication-and-control-apis.md @@ -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 ``` diff --git a/workplans/FC-WP-0004-fluid-insight.md b/workplans/FLUID-WP-0005-fluid-insight.md similarity index 88% rename from workplans/FC-WP-0004-fluid-insight.md rename to workplans/FLUID-WP-0005-fluid-insight.md index 0352db1..85759a6 100644 --- a/workplans/FC-WP-0004-fluid-insight.md +++ b/workplans/FLUID-WP-0005-fluid-insight.md @@ -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 ``` diff --git a/workplans/FC-WP-0005-fluid-science.md b/workplans/FLUID-WP-0006-fluid-science.md similarity index 90% rename from workplans/FC-WP-0005-fluid-science.md rename to workplans/FLUID-WP-0006-fluid-science.md index c77259e..613ef6f 100644 --- a/workplans/FC-WP-0005-fluid-science.md +++ b/workplans/FLUID-WP-0006-fluid-science.md @@ -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 ``` diff --git a/workplans/FC-WP-0006-conformance-and-self-validation.md b/workplans/FLUID-WP-0007-conformance-and-self-validation.md similarity index 87% rename from workplans/FC-WP-0006-conformance-and-self-validation.md rename to workplans/FLUID-WP-0007-conformance-and-self-validation.md index 93cbf42..971028c 100644 --- a/workplans/FC-WP-0006-conformance-and-self-validation.md +++ b/workplans/FLUID-WP-0007-conformance-and-self-validation.md @@ -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 ``` diff --git a/workplans/FC-WP-0007-fluid-telegram-handover.md b/workplans/FLUID-WP-0008-fluid-telegram-handover.md similarity index 91% rename from workplans/FC-WP-0007-fluid-telegram-handover.md rename to workplans/FLUID-WP-0008-fluid-telegram-handover.md index f52545c..3b3cbe1 100644 --- a/workplans/FC-WP-0007-fluid-telegram-handover.md +++ b/workplans/FLUID-WP-0008-fluid-telegram-handover.md @@ -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 ```