internal/

Package activity is the append-only record of what an agent actually did.

Package advice is what a checkpoint receipt says about the checkpoint it just wrote: the placeholders it dropped and the fields it kept as given but doubts.

Package agent is the conversational assistant.

Package agentprompt carries the instructions an agent should read before it uses Logos.

Package announce decides how loudly Logos says what it just did.

Package auto is what Logos does without being asked, in one place.

Package bootstrap seeds a cold vault from the git history already on disk.

Package buildinfo holds the one version string this product reports.

Package claudemem finds claude-mem's local store.

Package consent tracks whether the app is allowed to call agent.Learn after a chat exchange without asking first.

Package contextpack assembles everything needed to work on something into one bundle.

Package deadend answers one question: has this been tried before?

Package dream is the nightly consolidation pass — logos sleeping on the day.

Package flavor holds the assistant's identity and how present it makes itself.

Package gitstate reads what the repository was, so a checkpoint does not have to rely on being told.

Package graph builds the memory graph the widget renders.

Package health answers "is this actually working", and is careful about the difference between a thing that is fine and a thing nobody looked at.

Package index is the rebuildable cache.

Package ingest turns another coding agent's transcript into a Logos checkpoint *candidate* — never a checkpoint, and never by replaying the transcript.

Package insight surfaces observations the vault already contains but nobody has stated out loud: a blocker that has survived several checkpoints without being resolved, a memory nobody has drawn on in months.

Package mcpserver exposes logos's memory layer as an MCP server.

Package memory is the assistant's persistent memory.

Package ops is each operation once, for every surface.

Package procedure answers the question before_you_try's dead-end half leaves unanswered: not just what was ruled out, but what is known to work, including the trap in doing it the obvious way.

Package project auto-detects the pieces of work a life is organised around and assembles a dossier for each — its notes, the people involved, the files it touches, its goals, and recent progress — without the user filing anything.

Package provider is one client for every model runtime.

Package reflection is descriptive statistics over long-term memory.

Package rename moves every trace of a project from one name to another, so that renaming a project is an ordinary edit rather than an event that costs you your history.

Package replay is "catch me up since I've been away."

Package router decides which model does which job.

Package scope answers one question — what is the work in this directory called — the same way for every caller, so that a hook, the CLI and the MCP server cannot disagree about it.

Package secret masks credentials in text before it is written to the vault.

Package secretary tracks the open loops an agent or a person has left open — "I'll send the deck", "waiting on the vendor" — so they can be surfaced again without depending on anyone remembering to check.

Package selfupdate implements `logos update`: check GitHub for a newer release, verify it actually runs on this machine, then replace the running binary.

Package session records what an agent was doing, so a different agent can pick it up.

Package setup connects logos to the agents that will use it.

Package testenv keeps test runs away from the developer's real host CLIs.

Package text holds the small string-shortening helpers that were copied, subtly differently, into half a dozen packages.

Package textmatch is the small lexical toolkit two subsystems needed at once.

Package transcript reads other coding agents' on-disk session logs and normalises them into a common shape.

Package untrusted renders vault content that was written by someone else's agent, not by logos itself.

Package usage is the ledger `logos usage` reads: what each context pack cost against what it drew from, and each time a recorded dead end was handed back to an agent about to retry it.

Package vault reads and writes notes in the Obsidian vault.

Package when resolves the time expressions people put in questions.