fluid-core/workplans/FC-WP-0005-fluid-science.md
tegwick c2cfe86d88 Establish fluid-core scaffold, intent, and phased workplans
Adds the repository structure, INTENT.md declaring the wire-contract
boundary, and seven workplans covering Blueprint Phases A-C plus the
fluid-telegram handover.

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:49:12 +02:00

2.8 KiB

id type title domain repo status owner topic_slug created updated planning_priority planning_order depends_on
FC-WP-0005 workplan FLUID Science - the adaptation loop closes (Blueprint Phase C) infotech fluid-core active worsch fluid 2026-09-04 2026-09-04 high 5
FC-WP-0004

FC-WP-0005 - FLUID Science

Hypotheses, experiments, fitness and promotion. Entirely human-driven — the Daimon is deliberately absent. Blueprint §50 says the success criterion is proving this loop works cleanly and safely, not autonomous coding.

T01 - Hypothesis records and lifecycle

id: FC-WP-0005-T01
status: todo
priority: high

Schema doc §2: DRAFT, READY, PRIORITIZED, DESIGNING, EXPERIMENTING, EVALUATING, then ACCEPTED, REJECTED, SUPERSEDED or DEFERRED. Keep observation, explanation, prediction, intervention and result separate — schema doc §18 warns that collapsing them into one narrative destroys criticism and auditability.

T02 - Competition groups

id: FC-WP-0005-T02
status: todo
priority: medium

Rival explanations of one pressure coexist (schema doc §6). Preserving uncertainty is a feature.

T03 - Hypothesis API

id: FC-WP-0005-T03
status: todo
priority: medium

Blueprint §44.3: create, compare, prioritize, attach candidate, record outcome.

T04 - Experiment controller

id: FC-WP-0005-T04
status: todo
priority: high

Blueprint §16. Declares hypothesis, control, candidate, cohorts, allocation, metrics, guardrails, start and stop conditions, maximum duration. Per §17 it must not touch traffic directly: it writes routing policy the router consumes. Experiments are interruptible.

T05 - Experiment API

id: FC-WP-0005-T05
status: todo
priority: medium

Blueprint §44.4: create, start, change bounded allocation, stop, record metrics, finalize.

T06 - Fitness evaluation against hypotheses

id: FC-WP-0005-T06
status: todo
priority: high

Wire the fitness engine to experiments. Success criteria may not be changed after results are visible without recording the amendment (§18).

T07 - Promotion controller

id: FC-WP-0005-T07
status: todo
priority: high

PROMOTE, EXPAND_EXPERIMENT, RETAIN_AS_OPTION, MODIFY, REVERT, ABANDON, DEFER recorded as decisions with an authorizing actor (§19). Human authority only.

T08 - Append-only event log

id: FC-WP-0005-T08
status: todo
priority: high

Every transition above as a fluid_event (schema doc §15). FLUID evolution is itself a system behavior that must remain reconstructable.

T09 - Audit trace command

id: FC-WP-0005-T09
status: todo
priority: high

fluid audit trace <revision> reconstructs pressure, hypothesis, revision, experiment, fitness and decision, answering all eleven questions in API Standards §25.