fluid-core/workplans/FLUID-WP-0007-conformance-and-self-validation.md

id	type	title	domain	repo	status	owner	topic_slug	created	updated	planning_priority	planning_order	depends_on
FLUID-WP-0007	workplan	Conformance suite and self-validation	infotech	fluid-core	active	worsch	fluid-core	2026-09-04	2026-09-04	high	6	FLUID-WP-0006

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.

T01 - Echo interface fixture

id: FLUID-WP-0007-T01
status: todo
priority: high

examples/echo-interface — two revisions, R-1 deliberately inefficient (list then filter), R-2 the convenience form. This is the smallest honest reproduction of the Blueprint §33 worked example.

T02 - Minimal conformance assertions

id: FLUID-WP-0007-T02
status: todo
priority: high

The seven requirements of API Standards §36, asserted as tests rather than claimed in a README.

T03 - Architectural invariant checks

id: FLUID-WP-0007-T03
status: todo
priority: high

The mechanically checkable subset of Blueprint §55. Invariant 2 (evolution can stop without stopping the API) and invariant 9 (AI-generated artifacts untrusted until verified) matter most and get dedicated tests.

T04 - Failure containment matrix

id: FLUID-WP-0007-T04
status: todo
priority: high

Blueprint §34. Kill the control plane, the evidence store and the telemetry pipeline in turn; assert the data plane keeps serving from cached published configuration each time.

T05 - End-to-end loop in CI

id: FLUID-WP-0007-T05
status: todo
priority: high

The full §50 vertical slice automated: two revisions, a 90/10 experiment, fitness comparison, promotion, complete audit trail.

T06 - Integration guide

id: FLUID-WP-0007-T06
status: todo
priority: medium

docs/integration-guide.md — how to put an existing API of any stack behind fluid-core without modifying it.