Menu
Re-derive the vault configuration from first principles. Use when accumulated drift makes incremental adjustment insufficient.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Add a new knowledge domain to an existing vault. Creates domain-specific MOCs, templates, and vocabulary mappings.
Research-backed vault evolution guidance. Toggle features (self-space, semantic search), rebalance MOCs, adjust dimensions with full rationale.
Query the Ars Contexta research methodology. Answers 'why does my system do X?' with research-backed explanations from 249 interconnected claims.
Analyze the vault's knowledge graph. Subcommands: orphans, density, bridges, synthesis, traverse, clusters, stats.
Run vault health diagnostics. 3 modes: quick (schema+orphans+links), full (all 8 categories), three-space (boundary violations).
Contextual guidance and command discovery. Shows available skills, agents, and intelligent suggestions based on vault state.
| name | reseed |
| description | Re-derive the vault configuration from first principles. Use when accumulated drift makes incremental adjustment insufficient. |
| tags | ["architecture","reset","derivation"] |
Delegates to: @ars-contexta:vault-architect
Invoke this skill when the user feels their vault has drifted significantly from how they actually work, when incremental adjustments are no longer sufficient, or when they want a clean derivation without losing their notes.
Friction Audit Phase
Read ops/derivation.md to understand the original rationale and ops/observations/ for accumulated friction signals. Surface a brief summary to the user:
Conversation Phase Run a fresh derivation conversation as in the setup skill, but seeded with what was learned from friction observations. Open with: "Your vault has been running for a while. Let's re-derive from scratch — tell me how your actual usage differs from what you expected."
Listen for:
Derivation Phase Map fresh signals to the 8 configuration dimensions. Where signals conflict with the original derivation, flag the tension explicitly and let the user decide which to honour.
Proposal Phase Show a diff-style summary of what will change:
Explicitly state: "Your notes in notes/ and self/ will not be modified."
Wait for confirmation before proceeding.
Backup Phase Before overwriting any file, create timestamped backups:
ops/derivation.md → ops/archive/derivation-{YYYY-MM-DD}.mdops/derivation-manifest.md → ops/archive/derivation-manifest-{YYYY-MM-DD}.mdops/config.yaml → ops/archive/config-{YYYY-MM-DD}.yamlcopilot-instructions.md → ops/archive/copilot-instructions-{YYYY-MM-DD}.mdCLAUDE.md → ops/archive/CLAUDE-{YYYY-MM-DD}.mdGeneration Phase
Regenerate ops/ configuration, context files, and templates from the new derivation. Do not modify any file outside of ops/, templates/, copilot-instructions.md, and CLAUDE.md.
Validation Run the 15 kernel primitive checks against the regenerated configuration. Report PASS/FAIL and surface any regressions introduced by the new derivation.