Saltar al contenido
MCP ThesaurusMCP Thesaurus

Avis Six Layer Memory

ComunidadAdequate47/100Reclamar

updated 2mo ago

Use this skill before making claims from memory or writing persistent context for James.

CódigoWebDocs

¿Qué puedes hacer con Avis Six Layer Memory?


description: Use for every James AVIS agent session that needs persistent memory, source-backed recall, credential-safe status, doctrine, or restart continuity.

AVIS Six-Layer Memory Skill

Use this skill before making claims from memory or writing persistent context for James.

Layers

  1. Session memory: current decisions, commands, blockers, and next proof.
  2. Task proof memory: ProofPackets, smoke commands, acceptance checks, and restart prompts.
  3. Project memory: seven-module AVIS boundaries, data contracts, source matrix, and local run surfaces.
  4. Domain memory: Avis operations, DEN airport, NPS, pricing, upsell, fleet, and comms expertise.
  5. Tool and credential memory: env names, readiness states, connector status, and permission gates only.
  6. Doctrine and soul memory: RIG doctrine, James preferences, stop conditions, and approved tone.

Rules

  • Never store secret values.
  • Every real-person, customer, flight, pricing, Supabase, or Google review claim needs a source path, URL, ProofPacket, confidence, and freshness.
  • Use the narrowest layer needed for the current AVIS module.
  • If the latest ProofPacket contradicts memory, the ProofPacket wins.
  • If a source is missing, mark the memory claim needs_source instead of inferring.
  • Claude interactions go into James's second brain only after session or source-surface opt-in; write the local append-only ledger first, then export redacted Markdown.