Cognitive OS is a local-first control plane for turning messy, ongoing conversational intent into dependency-aware, reviewable work. It is the bounded planning, permission, review, and learning layer of the larger Cognitive OS.
The current implementation is an early dry-run prototype. It performs no network calls, starts no background services, invokes no external assistant runtime, and cannot merge or deploy anything.
-
Run the local verification suite. It requires Python 3.9+ and no runtime dependency outside the standard library:
python3 -m unittest discover -v
-
Run the synthetic end-to-end dry run with its temporary ledger:
python3 -m pip install -e .
cognitive-os run \
--manifest examples/fixtures/layer5_end_to_end.json \
--store /tmp/cognitive-os-demo.jsonl
python3 -m examples.layer5_end_to_end_demo- Inspect the implementation reports for the end-to-end decision packet, and the Stage 1 continuity, confidence, redacted lineage, and stream-revision layers, plus the private-data policy, session-private lineage, and accepted-plan packet bridge. The current review gate is the exact legacy migration plan. Those reports link each implemented claim to focused tests and a synthetic demonstration.
- Read the architecture index, decision records, and roadmap for the current decision boundaries and deferred work.
The remaining commands exercise focused Stage 1 demonstrations:
python3 -m examples.stage1a_intent_continuity_demo
python3 -m examples.stage1b_semantic_confidence_demo
python3 -m examples.stage1c_redacted_lineage_demo
python3 -m examples.stage1d_stream_revision_demo
python3 -m examples.stage1e_private_data_policy_demo
python3 -m examples.stage1f_session_private_lineage_demo
python3 -m examples.stage1g_accepted_plan_packet_demo
python3 -m examples.stage1h_legacy_migration_plan_demoImplemented layers include a typed, append-only Intent Inbox/event ledger, a
conservative intent-atom lifecycle with explicit human confirmation boundaries,
and a restart-safe dependency/conflict/cluster intent graph. The dry-run PR
Compiler emits dependency-closed plans and bounded execution briefs; the local
CLI returns one decision packet. Stage 1 adds local cognitive branches,
deterministic confidence metadata, redacted structural lineage export, and
stream-revision atomicity. The repository also contains a validated,
draft-only historical integration contract in docs/archive/; it intentionally
does not create an adapter.
None of these artifacts authorize writes to other repositories or services. They do not make network calls, access an external assistant runtime, invoke a coding agent, create or merge pull requests, deploy, or start a background service.
Run the complete synthetic demo with a temporary private ledger:
python3 -m examples.layer5_end_to_end_demoThe legacy event path preserves exact input text. Keep real-input ledgers under
an ignored/private path such as data/; never commit personal conversations.
The opt-in Stage 1F v2 path instead keeps content in process-local session memory
and persists structural lineage only; it does not migrate legacy events.
Human confirmation, confidence, and a dry-run plan are not permission signals. Children are read-only, and only explicit human promotion can create a superseding parent version. Public lineage packets contain structural, scope-specific pseudonymous references rather than raw source or local IDs. Continuity commands bind to the exact projected stream revision, so competing writes fail closed or reconcile only an exact idempotent retry.
Stage 1E adds typed conservative data-policy defaults: session-only raw source, exact-scope structural search, single-project reasoning, and effect-free reversible quarantine plans. Its audit deliberately reports that the legacy ledger still embeds private fields; no deletion or retention enforcement is claimed yet.
Stage 1F enforces session-only storage for new v2 capture and extraction: raw source, statements, and metadata are absent from immutable events, while digest-bound structure survives restart. Clearing the vault drops process references but does not claim secure-memory erasure.
Stage 1G binds the exact current accepted plan version and a scoped graph digest to one deterministic draft decision packet. Compilation is pure and local; it writes no event and grants no execution permission.
The Stage 1H review branch inventories exact private-bearing legacy events and derives structural targets without exposing their values. It is explicitly non-executable and performs no rewrite, quarantine, deletion, or file mutation.
Licensed under the MIT License. See LICENSE.