Local cognitive engine. One core. One trainer. One response surface. One action layer.
Owner intent flows through one path:
owner prompt → objective/constraints → evidence → operations → validation → repair → artifact → proof/uncertainty/choice records → learning update when allowed → response
No closed cognitive modes. No task-type menus. No output-shape enums.
/api/chatis the public turn endpoint. It calls the cognitive core directly.- The router returns compatibility hints only. The engine composes behavior from turn state, not mode selection.
- Large-file ingestion uses a bounded-window incremental path. It does not buffer full files into RAM above the small-file threshold.
pnpm review:releaseboots an isolated instance, runs real scenarios against real server routes, and writesdata/review/public-release-review.mdand.json.- Connector action results are task evidence by design. Explicit owner intent is required for ingestion/training.
- Proof, uncertainty, and choice records are produced for serious outputs.
- Alpha trace is emitted for meaningful operations.
corepack enable
pnpm install --frozen-lockfile
pnpm build
pnpm lint
pnpm test
pnpm review:releasePOST /api/chat— canonical cognitive-core turn endpoint.GET /api/health— readiness.GET /api/artifacts— artifact listing.GET /api/alpha/trace— alpha transition trace.GET /api/learning/events— learning event log.GET /api/proof/state— proof/uncertainty state./api/connectors/*— action connectors (evidence only unless explicitly ingested)./api/evidence/*— evidence retrieval.
- OCR and audio transcription are optional dependencies. The engine reports exact missing preconditions when they are absent.
- DOCX/XLSX/PDF parsing depends on optional parser binaries. The release review reports the exact missing precondition when parsing cannot proceed.
- Full production brain training is out of scope for this hardening pass.
- Legacy compatibility routes remain but are not the public cognitive model.
Run pnpm review:release. It creates isolated temp storage, seeds deterministic fixtures, starts the server on an ephemeral port, executes scenarios, collects evidence/artifacts/alpha/learning/proof records, writes reports, and tears down cleanly.
The review report is the proof surface.