coulomb/fluid-core
5
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
fluid-core/workplans/FLUID-WP-0001-statehub-bootstrap.md
tegwick 8516c6bb13
Some checks are pending
ci / build (push) Waiting to run
Details
Close FLUID-WP-0001: fill bootstrap files and document the toolchain 
Replace the generated credential-routing placeholder and generic purpose
text with repo facts, record the install/test/lint/build/run commands in
AGENTS.md, and point T03 at the existing FLUID-WP-0002…0009 sequence
instead of seeding a duplicate workplan.

Assistant: grok
Assistant-Session: 01a09dc6-3f0e-78f1-a884-c8b2daa3e2b6
2026-09-14 04:44:35 +02:00

3.3 KiB
Raw Permalink Blame History

id type title domain repo status owner topic_slug created updated related state_hub_workstream_id
FLUID-WP-0001 workplan Bootstrap State Hub integration infotech fluid-core finished worsch fluid-core 2026-09-04 2026-09-14
FLUID-WP-0002
FLUID-WP-0008
FLUID-WP-0009
b5c231e1-9d06-5772-95a7-01cc0bf62051

Bootstrap State Hub integration

Core framework for fluid interfaces to provide adaptive robust systems capability integration.

Outcome: generated integration files reviewed against the implemented repo; developer commands documented in AGENTS.md; first implementation work already exists as FLUID-WP-0002 … FLUID-WP-0009 (no duplicate seeded).

Residuals: none open from this bootstrap. Live follow-on work is FLUID-WP-0008 (Telegram handover; remaining tasks are human-blocked) and FLUID-WP-0009 (campaign-repo pattern and a second interface).

Review Generated Integration Files

id: FLUID-WP-0001-T01
status: done
priority: high
state_hub_task_id: "f106ac45-c90b-5115-a0de-e986839b19f9"

Review INTENT.md, SCOPE.md, AGENTS.md, and .custodian-brief.md. Replace generated placeholders with repo-specific facts where needed.

Done 2026-09-14:

  • Replaced the unresolved {CREDENTIAL_ROUTING} token in AGENTS.md with the fleet credential-routing section (to_agent=fluid-core).
  • Replaced the generated repo-description purpose in AGENTS.md and README.md with the SCOPE one-liner.
  • Recorded that the repo topic is helix-forge but workplans currently index under the custodian topic; session-start query is now by repo_id.
  • Set INTENT.md status: active (was draft).
  • Noted in SCOPE.md that the gateway is a library in internal/runtime and cmd/fluid-gateway is reserved and empty.
  • .custodian-brief.md is generated by fix-consistency — not edited by hand.

Verify Local Developer Workflow

id: FLUID-WP-0001-T02
status: done
priority: high
state_hub_task_id: "1e3f26fe-4a1a-5f96-8dd6-962dd844402e"

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.

Done 2026-09-14. This repo has no CLAUDE.md / stack-and-commands.md; the commands are in AGENTS.md (Local developer workflow) and mirrored in README.md. Verified locally: make validate, make vet, make build, make test, make conformance, and go run ./cmd/fluid --help. Full check is make all && make conformance, matching .github/workflows/ci.yml.

Seed First Real Workplan

id: FLUID-WP-0001-T03
status: done
priority: medium
state_hub_task_id: "2428db4a-c6ad-547d-acf3-9163ea17ae20"

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:

statehub fix-consistency

Done 2026-09-14 by pointing at existing work, not creating a duplicate.

The first implementation workplan is FLUID-WP-0002 (foundations and the wire contract), already status: done. The sequence through conformance is FLUID-WP-0003 … FLUID-WP-0007 (all done). The live next work is FLUID-WP-0008 (Telegram handover) and FLUID-WP-0009 (campaign repos and a second interface).