leeway-conversation-vault
Governed durable conversation capture and retrieval for LeeWay agents. When a runtime exposes an authorized LeeWay Tool Gateway or equivalent local adapter, append currently available user/assistant t
SKILL.mdskills/leeway-conversation-vault/SKILL.md
GitHubLeeWay Conversation Vault
Core law
A conversation actually available to the current runtime may be preserved as governed LeeWay evidence when an authorized vault is available.
Do not claim to possess conversations the host never exposed.
available conversation != all account history
Capture contract
For every captured turn preserve when available:
- session/conversation identity;
- conversation title;
- timestamp;
- source runtime/provider;
- user message;
- assistant response;
- skill-authority state;
- Formula evaluator state;
- Formula execution state;
- Veritas state;
- receipt state;
- immutable record hash;
- source/provenance metadata.
The vault is append-only by default. Historical records are not silently rewritten.
Formula boundary
Conversation storage does not prove Formula execution.
When no evaluator or authorized adapter has been proven:
FORMULA_EVALUATOR_STATE = UNEXPOSED
FORMULA_EXECUTION_STATE = NOT_EXECUTED
If Formula actually executed, preserve evaluator/adapter identity, implementation/version/hash, decision evidence, runtime evidence, Veritas, and receipt state when available.
Never infer execution merely because Formula Governance was loaded or because a conversation was saved.
Retrieval contract
Future Context Engineering may retrieve prior conversation evidence for continuity, style, project state, decisions, terminology, unresolved work, and capability selection.
Retrieved conversation text is context, not supreme authority. Current Creator instruction and higher LeeWay authority still govern.
Historical ingestion
For older chats, ingest only when the host exposes them, the user reopens them, or the user provides an authorized export/archive.
Never invent missing chats, turns, dates, titles, or assistant responses.
Privacy and scope
Store conversations only in the authorized LeeWay vault. Do not copy unrelated personal data simply because filesystem access exists.
Preferred local location:
<LEEWAY_ROOT>/ToolGateway/runtime/conversation-vault
Runtime path
message ingress → governed response → conversation append → hash → index → receipt → future Context Engineering retrieval
The Conversation Vault complements Memory/Continuity. It does not replace Formula Governance, Veritas, or receipt authority.