Protocol and domain
Executable protocol tests and the F#/.NET domain build pass without warnings.
Release 00.1
Private shadow alpha
CC10 → CC11 · Memory and automation plane
A system that can
show its work.
CC11 gives a personal system memory without giving a model the keys. Sources stay sources. Claims keep their status. Actions keep their receipts. Authority remains explicit.
System figure 01 / The evidence path
01SourceBytes · digest · origin
02MemoryCore + labelled lab
03EvidenceTests · receipts · limits
04Owner gateApprove · pause · revoke
05Typed actionBounded public effect
NO INVISIBLE MEMORY01
NO SELF-PROMOTION02
NO UNTYPED AUTHORITY03
NO CLAIM WITHOUT STATUS04
01 / Position
The premise
Faster generation moves the bottleneck. It does not remove responsibility.
When software can be generated in minutes, the scarce work becomes intent, evidence, memory and permission. CC11 treats those as architecture—not prompt etiquette.
It combines a conservative record with an experimental EIDOS lane. Both may inform decisions. Only one may become ratified truth, and only through an explicit promotion gate.
Read the public EIDOS doctrine ↗02 / Operating model
One path, visible states
The model does not get to declare itself correct.
Select a stage to inspect what crosses the boundary—and what does not.
The record starts before the summary.
Original bytes, provenance and digest remain addressable. A generated summary may help retrieval, but never replaces its source.
- May enter
- Owner-approved files, sessions and typed records
- Must leave
- A stable source identity and immutable digest
- Hard boundary
- No silent mutation, no invented provenance
03 / Generation shift
Continuity, not a reset
CC10 operates.
CC11 remembers why.
Capability
CC10 / working reference
CC11 / research release
Daily surface
Private apps and operator actions
Matrix-first conversation with visible receipts
Memory
Searchable DWH and session archive
Versioned Core plus labelled experimental lane
Automation
Typed actions and approval boundaries
Common events, idempotency and replayable outcomes
Research
Operational case study
CDD/EIDOS claims, evidence packs and promotion gates
Status
Running system
Private shadow alpha
04 / Release ledger
Proof, not promise
A release page should disclose the unfinished work.
This ledger separates observed checks from pending gates. It is a public summary, not a substitute for private operational evidence.
Verified
Shadow memory core
PostgreSQL/pgvector and the private API run resource-bounded and non-authoritative.
Hot restore path
Encrypted offsite receipt and representative control-data restore checks pass.
Retrieval evaluation
The frozen comparison of structured filters, full-text and vector retrieval remains open.
Full integration receipt
The Matrix → agent → typed action → outcome path is not yet release-evidenced end to end.
Default cutover
Promotion, durability, rollback and complete restore gates still block a stable release.
Snapshot: 30 July 2026 · Claims are deliberately narrower than the private receipts.
05 / Release film
Thirty seconds, sound-off native
Memory is not authority.
A typographic field note about the boundary at the centre of CC11. No synthetic people. No stock future. The system itself is the visual language.
Film transcript
AI can generate an answer. CC11 asks what the answer is allowed to become. Sources stay intact. Claims keep their status. Experiments stay labelled. Evidence travels with the change. Authority remains explicit. CC11. A system that can show its work. Private shadow alpha.
06 / Public research
The method stays inspectable
The public work is CDD.
The private system is the case study.
Paper and claims
Research claims carry scope, provenance and epistemic status. Proposed is not disguised as verified.
Inspect Research Studio source ↗Framework and engine
The F# kernel, CLI and MCP surface make model, drift and evidence machine-checkable.
Inspect source ↗Reference project
CourseForge explores a data-minimal course-to-learning-game pipeline with synthetic public fixtures.
See CourseForge ↗CDD Studio
Drill from premise and claim through specification, test, code and release evidence.
Open the public demo ↗07 / Boundary
Public by review, private by default
The showcase is not the system.
Public
- Sanitised architecture and doctrine
- Synthetic examples and reproducible tests
- Bounded release claims and known limits
- Framework, papers and research snapshots
Private
- Personal memory and source documents
- Credentials, routes and infrastructure detail
- Operational receipts and recovery material
- Owner conversations and approval evidence
Follow the release