atmina

Use when connected to the Atmina MCP server — your shared memory. Recall (search) before answering from training; capture decisions/findings; update existing memory; consolidate a KB's memory into a reviewed current-state view. Covers orientation, file writes/uploads, search, audit, and the run→review→promote routine loop.

Promotes working-layer notes into durable Atmina wiki primitives with typed evidence, pins in-KB spans, marks unlocated claims unattested, and reads the page back to prove the record survived. Use when committing a decision, fact, procedure, preference, relationship, or open question through write_file or write_files, including after a user correction, a surprising durable lesson, or a decision settled with a stated reason.

Runs an out-of-band report-only maintain pass over an Atmina Knowledge Base — idle-gated, proposing same-intent merges and claim repairs, flagging contradictions and stale_after, archiving obsolete pages to KB-root archive/ when they are not cited as in-KB evidence, proposing linkify of bare catalog paths, reporting durable pages that have never been recalled alongside broken references and unconnected pages (each count stating the scope it covered), and writing a short trail in chronicle/. Use when an operator asks to maintain memory, repair claims, archive obsolete knowledge, linkify wiki paths, review recall or link health, or run an attestation sweep — never during an in-band user task, and never as a task's finally.

Records working-layer notes and end-of-task session notes (offered first, written only on a yes) in an Atmina Knowledge Base so candidates stay out of organisational truth. Org default is chronicle/YYYY-MM-DD-<slug>.md; personal or single-agent scope may use journal/ or one durable file; never writes wiki/, compiled views, or source mirrors. A session note is an index of the task, what was gathered, what was decided, and wiki paths and system-of-record locators — not a transcript. Gathering sources is not a durable write. Nothing notable is a successful no-op. Use when mid-task candidates or a session note need to land in the working layer, or when an agent would otherwise save a brief, finding, or transcript into the wiki.

Recalls durable Atmina memory with verify-before-act. Orients, matches applies_to via exhaustive list_files (not search), searches wiki/ with recency boosts, reads the smallest set, and verifies artifact claims on the computed attestation block before acting — never substituting a near match, never writing memory. Use when recalling, looking up, or acting on a decision, procedure, fact, preference, relationship, or open question already on file in an Atmina Knowledge Base, or when the user asks to remember, look up, or bring them up to speed.

Seeds an organisation Knowledge Base with the atmina-memory layout — directory-card pages for the six durable primitives, a Chronicle working-layer card, a wiki home, a kb-profile at wiki root (intensity default middle), and a schema-2 wiki/nav.yaml whose first section is a hand-curated Start here. Registers applies_to as a scalar string pointer when the caller is owning-team admin. Use when standing up a new organisational wiki, seeding an empty Knowledge Base for the atmina-memory pack, or inserting a missing Start here section without overwriting durable pages.