Claude Ensemble is being redesigned from a clean baseline.
The previous implementation is preserved in FlossWare-Archives/claude-ensemble-legacy. Treat it as historical evidence, not as an architectural blueprint.
We will specify the system before implementing it:
- Functional inventory
- Service, component, and algorithm boundaries
- Language-neutral contracts
- Ownership of persistence, identity, provenance, indexing, and recovery
- Acceptance criteria
- Implementation in complete, testable vertical slices
See docs/RESTART.md for the working plan.
The companion Notion index is the claude-ensemble documentation entry. It links to the project's Notion-side documentation and identifies the current review status. Public web access to that Notion page must be enabled separately in Notion.
The v1 contract baseline was merged in PR #8: Resolve architecture and contract findings. Runtime implementation is proceeding in small, reviewable slices. The initial Chunking runtime and REST tests are under review in PR #9; it is not merged yet.
- Service contracts
- JSON Schemas
- Architecture review acceptance baseline
- Functional traceability matrix
- Owner decision register
- Service call-graph validator
- Service-call workflow manifest
- Contract regression tests
- Contract validation GitHub Actions workflow
The contract-validation workflow runs Draft 2020-12 schema/reference/endpoint-binding checks, duplicate-key-safe parsing of both backtick and tilde JSON fences, schema validation for explicitly annotated examples, the documented service-call workflow manifest, and regression tests for invalid examples/callers and RRF integer golden vectors. Unannotated examples are parse-checked only; the validator reports this distinction explicitly. See workflow runs for the current result. These are static/specification checks, not runtime, crash/recovery, integration, or latency test evidence. Owner confirmation is recorded for OD-01–OD-04 and OD-06–OD-12; OD-05 remains the binding v1 scope decision and is unchanged. Owner decisions establish the v1 scope baseline, but do not waive technical findings. Every runtime slice still requires current-head code review, regression tests, and passing CI before merge.
Use Python 3.12 or newer. Install the test dependencies and run the same suite used by CI:
python -m pip install -r requirements-test.txt
python scripts/validate_contracts.py
python scripts/check_service_call_graph.py
python -m unittest discover -s tests -vThe test dependency list includes jsonschema, which validates the Draft 2020-12 contract schemas and runtime responses.