Claude Ensemble is a local, single-process, REST-oriented system for coordinating retrieval and context assembly across Memory, Knowledge, Graph, Index, retrieval, ranking, and supporting services.
Status: owner-confirmed v1 defaults; architecture remains under technical review and is not approved for implementation. OD-01–OD-04 and OD-06–OD-12 are accepted; OD-05 remains the binding v1 scope decision and is unchanged. Acceptance scenarios describe required behavior, not proof that runtime tests have passed. Technical findings are not waived.
PR #8's head branch contains the current contract corrections and owner-decision record. The latest head is fcfd082c786b801fa61f1986f24923b36fec8b0e. Static CI passed on the preceding owner-decision commit in run 40333051471; CI for the latest README status commit is not yet verified. Review the branch-linked files below; the default branch may not yet contain them.
The v1 proposal targets one application/server process with logical services communicating through a local REST dispatcher. Federation, generalized authentication, multi-scope public fan-out, query expansion, pagination/refill, and rollback are deferred unless the owner explicitly revises the scope.
Reviewers should distinguish three things: contract text that defines intended behavior, static checks that inspect documentation and schemas, and runtime tests that demonstrate behavior. The latest static workflow passed: 17 Draft 2020-12 schemas and references/endpoints validated; 111 unique method/path routes checked; 23 JSON examples parsed with duplicate-key rejection; 21 explicitly annotated examples validated against their bound schemas; and 29 declared service-call edges matched the documented workflow manifest. Regression tests passed for invalid examples, duplicate JSON keys, unknown callers, Index-as-caller violations, and RRF integer golden vectors. The two generic examples in REST-CONTRACT.md are parse-checked only because they are not endpoint instances. Endpoint-specific runtime fixtures and runtime/integration tests have not been established by acceptance specifications alone. This passing static check is not architecture approval.