Skip to content

waittim/MemoryCustodian / skills/memory-custodian

memory-custodian

Flagged

Use when a project contains docs/memory/, or when the user asks to remember, retrieve, update, compact, forget, or audit project memory. MemoryCustodian manages local plain-text project memory with minimal context loading.

references/routing-policy.md

View on GitHub
# Deterministic Routing Policy

The manifest routes a bounded context pack from explicit task and scope inputs. It does not prove semantic relevance.

## Inputs

- Canonical tasks: `general`, `planning`, `implementation`, `artifact`, `preferences`, `history`, `maintenance`.
- Touched or planned repo-relative paths supplied with repeatable `--path`.
- Explicit enabled modules supplied with `--rule`, `--profile`, or `--area`.

Protocol 0.8 uses case-sensitive POSIX globs. `*` and `?` stay within one segment; `**` spans complete segments.
Paths are lexically contained in the project, checked against symlink escape, and need not exist yet. The CLI never
reads touched-file content to infer an area.

## Completeness

`COMPLETE` means the enabled routing dimensions received enough explicit input. `INCOMPLETE` means scope may change
the pack—for example, a substantial task has enabled path-routed areas but no paths or explicit areas. `AMBIGUOUS`
is reserved for a future versioned exclusivity policy or documented compatibility mapping. Routing schema 1 defines
neither; `exclusive-group` is an unknown key and therefore `INVALID`. `INVALID` means manifest grammar, metadata, or
input violates the protocol.

Use `--strict-routing` before substantial planning, implementation, debugging, or review. An incomplete inspection
MAY show the shared safety baseline, but it is not an approved context pack.

## Explain

`read --explain` gives every enabled module exactly one file disposition: `loaded`, `skipped`,
`missing-required`, `missing-optional`, or `invalid`. Budget omissions are separate entry dispositions and use a real
Entry ID or stable file/unit reference. Stable `MC-ROUTE-*`, `MC-SKIP-*`, `MC-MISSING-*`, and `MC-OMIT-BUDGET`
codes state observable causes; skipped never means “not relevant.”

Root `constraints.md` is the generated safety baseline for substantial tasks. Custom Protocol 0.6 routes are
preserved during migration; missing root-constraint coverage remains a routing safety warning until reviewed.
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall