Menu
Use when the `.aoa` session-memory filesystem contract, registry, generated indexes, naming policy, live hooks, or Codex grounding need health checks.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Use when a `.aoa` session-memory root must be created, installed, checked, repaired, or prepared for Codex hook-based session archiving.
Use when an indexed `.aoa` session needs provisional first-pass distillation into lessons, decisions, failures, and automation candidates without promoting them to reviewed truth.
Use when an agent needs evidence from prior `.aoa` sessions about how a skill, MCP, hook, tool, API, goal, eval, test, validator, script, decision, error, receipt, or other recurring operational entity was used, what happened nearby, and which raw or segment refs prove it.
Use in any Codex session when the user mentions `.aoa`, session memory, Codex transcripts, compaction, prior session rehydration, hook failures, or AoA session-memory validation.
Use when an agent needs to build or query the portable `.aoa` SQLite search index for archived Codex sessions, with evidence refs and freshness checks.
Use when the live Codex PreCompact and PostCompact hook path must be proven through `.aoa` using the Codex app-server compact probe.
| name | aoa-session-memory-doctor |
| description | Use when the `.aoa` session-memory filesystem contract, registry, generated indexes, naming policy, live hooks, or Codex grounding need health checks. |
| license | Apache-2.0 |
| metadata | {"aoa_scope":"session-memory","aoa_invocation_mode":"manual"} |
Use this for local health and repair orientation. doctor checks consistency;
it does not replace audit.
Run the narrow filesystem and metadata doctor first:
python3 scripts/aoa_session_memory.py doctor \
--workspace-root <workspace-root> \
--aoa-root <aoa-root>
The default route is intentionally fast on large live archives. It checks required surfaces, manifests, registry and generated-surface presence without parsing every event in every segment index.
When live hooks and Codex grounding matter, run:
python3 scripts/aoa_session_memory.py doctor \
--workspace-root <workspace-root> \
--aoa-root <aoa-root> \
--check-live-hooks \
--check-user-skill \
--check-codex-grounding
When the task is specifically to validate event payloads inside segment index files, use the explicit deep route:
python3 scripts/aoa_session_memory.py doctor \
--workspace-root <workspace-root> \
--aoa-root <aoa-root> \
--deep-segment-indexes
ok=truestatus=current or an explicitly deferred live-tail statusproblems--check-user-skill was requested, the global router points at this
installDo not treat a green doctor as completion readiness. Use audit for that.