chetana

Session captures happen automatically via Stop hooks that ingest finished transcripts into staged atoms under ~/.dharma/knowledge/staging/<date>/. Review them with chetana status or by reading the daily capture directory, then promote verified atoms explicitly.

Run chetana ingest <source> --kind pdf, webclip, or note to write the content as a staged atom. Staged atoms are not trusted until you explicitly promote them with chetana promote after review.

Stale atoms are revived by default, not quarantined. The revival flow reads the atom, scans the corpus for new neighbors and answered questions, proposes patches, and appends a revival_chain entry to its provenance. Quarantine is an opt-in last resort via chetana decay --quarantine.

No. Promotion from staged to trusted is a deliberate trust boundary and never happens automatically. The chetana promote and revive --apply commands require explicit user confirmation, and all writes route through governance gates that validate signatures and provenance.

The CLI requires a Python environment where dharma_swarm.chetana is importable. Try the dev worktree venv, the repo's .venv/bin/python, or python3 with the repo on PYTHONPATH; if none work, install with pip install -e ".[mcp,dev]" from the checkout.

Avoid chetana for general-purpose Python scripting, runtime daemon or gate operations, and current in-flight chat history, since captures only happen on session Stop. It is scoped strictly to memory operations on atoms, staging, and the knowledge graph.