MonadVault Vault Memory Curator
Overview
Use this skill to convert raw material into Vault Memory candidates with consent posture, scope, sensitivity, and retrieval value. The output is a memory proposal, not an automatic write to storage.
Routing
- Use this skill for retention, consent, sensitivity, scope, and retrieval decisions.
- Use
monadvault-codex-keeper when the main task is organizing source material into a codex entry, protocol, glossary, or index.
- Use
monadvault-privacy-sentinel for a dedicated exposure or publication-risk audit.
Workflow
- Separate raw source from interpretation.
- Identify whether the material is personal, confidential, sacred/cultural, regulated, third-party, public, or operational.
- Decide whether memory is appropriate:
- Retain if the material has durable value and the Steward has consented.
- Summarize if exact text is too sensitive or too noisy.
- Redact if only a subset belongs in memory.
- Exclude if the material is temporary, high-risk, unauthorized, or unrelated.
- Convert approved material into memory candidates:
- stable title
- source type
- concise memory statement
- retrieval tags
- permitted Monad or project scope
- sensitivity class
- retention recommendation
- open consent questions
- Flag any material that should pass through Privacy Sentinel before storage or publication.
Output Contract
For each memory candidate, return:
TitleSourceMemory statementWhy retainScopeSensitivitySuggested tagsRedactionsRetentionConsent needed
Use memory-entry-template.md for structured conversion.
Guardrails
- Do not treat chat history as memory by default.
- Do not retain secrets, credentials, private contact details, payment data, or legal identifiers unless the Steward explicitly asks and the storage system is appropriate.
- Do not include third-party private information without an explicit reason and narrower scope.
- Prefer summaries over verbatim retention when sensitive material is only needed for context.
1---2name: monadvault-vault-memory-curator3description: Curate notes, documents, chat excerpts, observations, decisions, and project material into governed MonadVault Vault Memory candidates. Use when a Steward says remember this, save this to memory, clean up my memory, decide what to retain, summarize for long-term recall, add retrieval tags, redact sensitive details, scope memory to a Monad or project, review retention, or identify what should be excluded or deleted.4---56# MonadVault Vault Memory Curator78## Overview910Use this skill to convert raw material into Vault Memory candidates with consent posture, scope, sensitivity, and retrieval value. The output is a memory proposal, not an automatic write to storage.1112## Routing1314- Use this skill for retention, consent, sensitivity, scope, and retrieval decisions.15- Use `monadvault-codex-keeper` when the main task is organizing source material into a codex entry, protocol, glossary, or index.16- Use `monadvault-privacy-sentinel` for a dedicated exposure or publication-risk audit.1718## Workflow19201. Separate raw source from interpretation.212. Identify whether the material is personal, confidential, sacred/cultural, regulated, third-party, public, or operational.223. Decide whether memory is appropriate:23 - Retain if the material has durable value and the Steward has consented.24 - Summarize if exact text is too sensitive or too noisy.25 - Redact if only a subset belongs in memory.26 - Exclude if the material is temporary, high-risk, unauthorized, or unrelated.274. Convert approved material into memory candidates:28 - stable title29 - source type30 - concise memory statement31 - retrieval tags32 - permitted Monad or project scope33 - sensitivity class34 - retention recommendation35 - open consent questions365. Flag any material that should pass through Privacy Sentinel before storage or publication.3738## Output Contract3940For each memory candidate, return:4142- `Title`43- `Source`44- `Memory statement`45- `Why retain`46- `Scope`47- `Sensitivity`48- `Suggested tags`49- `Redactions`50- `Retention`51- `Consent needed`5253Use [memory-entry-template.md](references/memory-entry-template.md) for structured conversion.5455## Guardrails5657- Do not treat chat history as memory by default.58- Do not retain secrets, credentials, private contact details, payment data, or legal identifiers unless the Steward explicitly asks and the storage system is appropriate.59- Do not include third-party private information without an explicit reason and narrower scope.60- Prefer summaries over verbatim retention when sensitive material is only needed for context.
genezo13