← VANACONTENT HISTORYWHAT CHANGED · RULE-BASED ANALYSIS
Update to VANA
Snapshot Sep 30, 2026 · 23:07 UTC · version 1.0.0
Collection source: not recorded for this historical snapshot.
First saved snapshot
No earlier snapshot is available to establish a change.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"name": "vana-run",
"description": "Continue a saved protocol. Use when the user asks for the next step, records progress, reviews progress, or changes an active protocol.",
"included_files": [
{
"relative_path": "references/log-format.md",
"size_in_bytes": 1083
}
],
"skill_md_contents": "---\nname: vana-run\ndescription: Continue a saved protocol. Use when the user asks for the next step, records progress, reviews progress, or changes an active protocol.\n---\n\n# Protocol runner\n\nProtocols persist as files in the user's Data:\n\n```\nprotocols/<slug>/protocol.md one protocol: seven H1 sections\nprotocols/<slug>/log/<YYYY-MM-DD>.md one file per day, time-headed entries\n```\n\nThe user's Data is behind the Vana MCP server. Read a protocol or log with its `read_file` tool, save with `write_file`, and list or search with `run_command`.\n\nThe saved protocol is the source of truth. Read it before you choose the next action, record progress, or review progress. Use the protocol's own steps, names, units, adaptations, and review rules.\n\nWhen the user names a protocol loosely, list `protocols/` and match the slug. If more than one protocol matches, ask which one they mean.\n\nA run is the work completed while following a protocol. Its log records enough state to determine progress and the next action.\n\n## Continue a protocol\n\n1. Read `protocol.md` and the most recent log entries.\n2. Find the next unfinished action from `# Protocol` and the recorded progress.\n3. Apply a relevant rule from `# Adaptation` when the user's context calls for one. Name the rule you applied.\n4. Give the user the complete next action with every detail the protocol specifies.\n\nThis branch is complete when the user can act without opening the saved file.\n\n## Record progress\n\n1. Read [Log format](references/log-format.md).\n2. Take the fields and units from `# Tracking & Review`. Ask a question only when a missing value would change the saved entry or the next action.\n3. Add the entry to `protocols/<slug>/log/<YYYY-MM-DD>.md` for the date when the work happened. Read an existing file first because `write_file` replaces the whole file.\n4. Confirm what you saved in one line.\n\nThis branch is complete when the log preserves the user's report in the shape defined by the protocol.\n\n## Review progress\n\n1. Read the log span the review covers.\n2. Compare the entries with the goal and review rules in `# Tracking & Review`.\n3. State what is complete, what remains, and any pattern supported by the entries.\n4. End with the next action. When the protocol defines review choices, use one of those choices and cite the log entries that support it.\n\nThis branch is complete when the user knows their current progress and what to do next.\n\n## Change the protocol\n\nGather the requested change and the relevant progress from the log. Use `/vana-create` to revise the saved protocol. Replace `protocol.md` and preserve its log.\n"
}SHA-256: 4d5fac2f0ed7a045b37f056045543fd9227ab041a77698c69e17df52f98a3a80