菜单
Use when auditing or repairing provenance, compilation coverage, stale synthesis, unresolved questions, circular corroboration, nested-boundary isolation, or legacy research drift within one named Markdown knowledge-vault research boundary.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | ariadne:research-stewardship |
| description | Use when auditing or repairing provenance, compilation coverage, stale synthesis, unresolved questions, circular corroboration, nested-boundary isolation, or legacy research drift within one named Markdown knowledge-vault research boundary. |
Audit one named research boundary first. Repair only deterministic, meaning-preserving drift through a declared exact write set.
audit, repair, or legacy-adoption explicitly.audit mode perform zero mutations: no reports in the vault, metadata normalization, link edits, queue items, or opportunistic fixes. Return findings and a proposed exact write set in chat.repair mode state the exact allowed_write_set before editing. Keep every mutation inside it. A newly discovered path is deferred until it is explicitly added.The selected boundary does not authorize sibling scopes, parent/root navigation, or downstream destinations. Folder ancestry does not establish boundary membership.
Audit the declared boundary for:
derived_from provenancecompiled without a derived noteReport semantic ambiguity; do not guess. A structurally valid boundary may still be semantically stale.
Automatic repair is limited to:
No other automatic repair is allowed. Each edit must be supported by existing canonical structure, remain inside the exact write set, preserve user content, and be idempotent: a second repair run produces no further mutations.
Always defer evidence-role classification, provenance-root merging or deletion, contradiction or supersession resolution, compilation versus source-only decisions, synthesis rewrites, promotion, moves, renames, merges, deletion, cross-scope rehoming, and any ambiguous link target.
Read a nested child boundary for context when needed, but do not repair it under the parent's contract. Before any child edit, read the child's descriptor plus all applicable ancestor and local instructions, then construct and declare a child-specific exact allowed_write_set. Do not inherit or reuse the parent's set. Parent conventions never overwrite a child's explicit contract. A parent rollup includes only the child descriptors listed in rollup_boundaries.
Treat older pipelines without a supported research_schema as legacy. Audit may inventory them, but adoption is opt-in and scope-local. In legacy-adoption mode map existing structure first, preserve stable paths, adopt before creating parallels, and add a descriptor only after mapping is unambiguous or confirmed. Apply only allowlisted repairs automatically; propose moves, renames, template changes, and synthesis changes for review.
After repair or opt-in adoption, run scoped research validation first:
validate_vault.js "/path/to/vault" --scope "<scope_path>" --profile research
Then run whole-vault validation to detect collateral effects. Re-run stewardship in audit mode or compare hashes to prove idempotency. Scoped findings must remain a subset of whole-vault findings for the same state.
Report mode, target boundary, instructions read, findings, exact write set, repairs, deferrals, scoped validation, whole-vault validation, and second-run idempotency. Recommended cadence is weekly for active or automated-ingest research, monthly for stable research, and event-driven after large imports, major synthesis changes, or detected drift.
Design or modify Markdown knowledge-vault navigation: folder hubs, agent navigation, routing matrices, workstream graphs, optional Bases/view layers, templates, health-check rules, and long-term traversability.
Use when creating, promoting, importing, nesting, or reorganizing scopes inside an existing Markdown knowledge vault with inherited parent and child scope rules.
Validate the structure of an agent-maintained Markdown knowledge vault with deterministic CLI checks for YAML/frontmatter, broken wikilinks, Markdown orphans, scope wiring, and optional Obsidian-compatible view files.
Bootstrap an agentic Markdown knowledge vault for projects, research, learning, life systems, and other long-running knowledge work. Use when creating a new vault, installing the base folder structure, templates, AGENTS.md, CLAUDE.md, Agent navigation files, and optional Obsidian-compatible Bases.
Create or update workspace-level instruction files for code repositories or ordinary project folders, including AGENTS.md, CLAUDE.md, GEMINI.md, local override files, and Ariadne vault-link blocks. Use when a user wants to initialize, repair, or refresh workspace instructions, connect a workspace to a registered Ariadne vault or scope, or make instructions portable across Codex, Claude Code, Gemini CLI, and other agent runtimes without duplicating global discovery.
Run maintenance and health checks for agent-maintained Markdown knowledge vaults: broken links, orphan notes, stale hubs, invalid frontmatter, uncompiled raw sources, stale queues, unresolved questions, optional Base coverage, and health reports.