@try-works/dsh-recursive-mode 0.1.2 → 0.1.4

package/references/bodies/claude.md

@@ -0,0 +1,7 @@
+## recursive-mode memory pointers
+
+- Canonical repository memory lives under `/.recursive/memory/`.
+- Read `/.recursive/memory/MEMORY.md` before loading any other memory docs.
+- Load only the memory docs relevant to the current task.
+- When repository experiential memory may help, run `python .recursive/scripts/recursive-training-loader.py --repo-root . --query "<task>" --files "<path1,path2>"`.
+- Treat this file as a pointer only; the canonical memory store remains `/.recursive/memory/`.

package/references/bodies/codex-agents.md

@@ -0,0 +1,95 @@
+## recursive-mode bridge
+
+This repository uses `recursive-mode`.
+
+The single canonical workflow spec lives in `/.recursive/RECURSIVE.md`.
+Read that file before starting or resuming any recursive-mode work.
+
+For Codex, the primary AGENTS bridge target is `/.codex/AGENTS.md`.
+If the repo also carries other `AGENTS.md` files, they may mirror this same bridge block.
+
+Bridge guidance only:
+
+- Treat this file as a harness adapter, not as a second workflow spec.
+- If this file conflicts with `/.recursive/RECURSIVE.md`, follow `/.recursive/RECURSIVE.md`.
+- Control-plane docs live under `/.recursive/`.
+- Runs live under `/.recursive/run/<run-id>/`.
+- Durable memory lives under `/.recursive/memory/`.
+- If recursive-mode is invoked in a repo that does not yet contain the `/.recursive/` scaffold, bootstrap it automatically with the supported install script before continuing. Do not require the user to run a separate manual bootstrap step unless no supported runtime is available.
+
+How users can invoke the skill:
+
+- Treat short prompts such as `Implement the run`, `Implement run 75`, `Implement the plan`, `Create a new run based on the plan`, and `Start a recursive run` as valid recursive-mode entry commands.
+- If a run id is given, use that run.
+- If no run id is given and exactly one active/incomplete run exists, resume that run.
+- If the user asks to implement/start based on a plan, create a new run only when a unique source plan or requirements artifact can be identified from repo docs or immediate task context.
+- If the command is ambiguous, ask for the run id or the repo path of the source plan/requirements artifact.
+- Prompts are still commands, not specifications: read the repo docs that define the run before proceeding.
+
+Required recursive-mode audit behavior:
+
+- Audited phases must follow `draft -> audit -> repair -> re-audit -> pass -> lock`.
+- When subagents are unavailable, perform the same audit as `self-audit`; do not weaken or skip it.
+- Delegate audits only when you can provide the full context bundle:
+  - phase name and artifact path
+  - upstream artifact paths reread for the audit
+  - diff basis from `00-worktree.md`
+  - changed file list and targeted code references
+  - phase-specific audit questions/checklist
+- If the context bundle is incomplete, do not delegate; perform the audit yourself and record `Audit Execution Mode: self-audit`.
+- If subagents are available and the context bundle is complete, delegated audit/review is the default path.
+- If subagents are available but the controller still chooses `self-audit`, record a concrete `Delegation Override Reason`.
+- Do not set `Coverage: PASS` or `Approval: PASS` for an audited phase unless the artifact ends with `Audit: PASS`.
+- Record `Subagent Capability Probe` and `Delegation Decision Basis` in every audited phase.
+- If meaningful subagent work contributes to a phase, require a durable action record under `/.recursive/run/<run-id>/subagents/` and verify it against actual files, actual recursive artifacts, and the actual diff before acceptance. For review/audit delegation, prefer a stable reviewed artifact for `Current Artifact`.
+- Store routed assistant output, raw transcripts, stdout/stderr captures, and invocation metadata under `/.recursive/run/<run-id>/evidence/router/`; cite them from action records rather than placing raw transcript Markdown directly under `subagents/`.
+- Store initial routed prompt bundles only under run-scoped paths such as `/.recursive/run/<run-id>/router-prompts/`; do not bootstrap top-level `/.recursive/router-prompts/`.
+- Treat `success: false` or any nonzero routed-assistant exit code as a failed attempt: preserve diagnostics, instruct the bounded routed role to repair owned issues when applicable, rerun the route, then verify the result before acceptance or record an explicit fallback.
+- If delegated work is accepted after main-agent checks reveal issues, record the concrete repair performed after verification; do not accept stale delegated context silently.
+- For Phase 3, declare `TDD Mode: strict|pragmatic`. Strict mode requires RED and GREEN evidence paths. Pragmatic mode requires an explicit exception rationale plus compensating evidence.
+- For Phase 5, declare `QA Execution Mode: human|agent-operated|hybrid`. Human and hybrid require user sign-off. Agent-operated and hybrid require execution metadata plus evidence paths.
+- For delegated review, prefer `recursive-review-bundle` and record `Review Bundle Path` in Phase 3.5 when review is delegated.
+- Treat addenda as authoritative effective inputs. If relevant addenda exist, list them in `Inputs`, re-read them, and reconcile them explicitly.
+- Review bundles should include relevant addenda automatically, and the written review should cite upstream artifacts, relevant addenda, prior recursive evidence, and changed files/code refs from that bundle in the review narrative.
+- Audited phases must include machine-checkable `Requirement Completion Status` entries for every in-scope `R#`; Traceability alone is not enough.
+- `implemented` and `verified` requirement dispositions must cite concrete `Changed Files`, and `verified` also requires distinct verification evidence.
+- `00-worktree.md` is the source of truth for diff basis. Record baseline type/reference, comparison reference, normalized baseline/comparison, and normalized diff command; do not silently substitute a different basis later.
+- Diff audit ignores incidental runtime byproducts such as `__pycache__/`, `*.pyc`, `.pytest_cache/`, `.mypy_cache/`, and `.ruff_cache/` unless the repo intentionally tracks them.
+- Treat Phase 6, Phase 7, and Phase 8 receipts as concise delta receipts that point to final control-plane docs instead of duplicating them.
+- Phase 8 should capture run-local skill usage and update skill memory under `/.recursive/memory/skills/` when the run teaches the repo something durable about skill availability, skill fit, delegated-review quality, or skill-discovery outcomes.
+- If a run needs missing specialized capability, prefer the `find-skills` skill when available. Otherwise use the Skills CLI (`npx skills find`, `npx skills add`, `npx skills check`, `npx skills update`) and record the outcome when skill usage is relevant.
+- When working inside a reusable skill/workflow repo, do not leave committed run residue such as concrete `/.recursive/run/<run-id>/` folders, evidence logs, review bundles, action records, or temp-path references unless they are intentional fixtures or examples.
+
+Useful helpers:
+
+Invoke these helper names from the installed recursive-mode skill directory or the source package checkout:
+
+- `install-recursive-mode`
+- `recursive-init`
+- `recursive-status`
+- `lint-recursive-run`
+- `recursive-review-bundle`
+- `recursive-closeout`
+- `recursive-subagent-action`
+- `recursive-training-grpo`
+- `recursive-training-extract`
+- `recursive-training-phase8-trigger`
+- `recursive-training-sync`
+- `recursive-training-loader`
+- `recursive-training-mcp`
+- `recursive-lock`
+- `verify-locks`
+- `check-reusable-repo-hygiene`
+
+Diff ownership rules:
+
+- Phase 2 owns planned product/worktree scope only.
+- Phase 3, Phase 3.5, and Phase 4 own actual product/worktree drift reconciliation.
+- Phase 6 owns `/.recursive/DECISIONS.md`.
+- Phase 7 owns `/.recursive/STATE.md`.
+- Phase 8 owns `/.recursive/memory/**`.
+- Do not treat later control-plane or memory churn as retroactive invalidation of earlier locked phases.
+
+Locking rule:
+
+- Use `recursive-lock` as the primary supported way to write `Status: LOCKED`, `LockedAt`, and `LockHash`.

package/references/bodies/copilot.md

@@ -0,0 +1,7 @@
+## recursive-mode memory pointers
+
+- Canonical repository memory lives under `/.recursive/memory/`.
+- Read `/.recursive/memory/MEMORY.md` before loading any other memory docs.
+- Load only the memory docs relevant to the current task.
+- When repository experiential memory may help, run `python .recursive/scripts/recursive-training-loader.py --repo-root . --query "<task>" --files "<path1,path2>"`.
+- Treat this file as a pointer only; the canonical memory store remains `/.recursive/memory/`.

package/references/bodies/cursorrules.md

@@ -0,0 +1,7 @@
+# recursive-mode memory pointers
+# Canonical repository memory lives under `/.recursive/memory/`.
+# Read `/.recursive/memory/MEMORY.md` before loading any other memory docs.
+# Load only the memory docs relevant to the current task.
+# When repository experiential memory may help, run:
+#   python .recursive/scripts/recursive-training-loader.py --repo-root . --query "<task>" --files "<path1,path2>"
+# This file is only a pointer surface; the canonical memory store remains `/.recursive/memory/`.

package/references/bodies/decisions.md

@@ -0,0 +1,5 @@
+# DECISIONS.md
+
+## Recursive Run Index
+
+- No runs recorded yet.

package/references/bodies/delegated-verification.md

@@ -0,0 +1,49 @@
+Type: `pattern`
+Status: `CURRENT`
+Scope: `How the main agent verifies delegated review or audit work before accepting it as lockable evidence.`
+Owns-Paths:
+Watch-Paths:
+- `/.recursive/RECURSIVE.md`
+- `/.recursive/memory/skills/SKILLS.md`
+- `/.recursive/run/`
+Source-Runs:
+- `none (generic repository guidance)`
+Validated-At-Commit: `generic-repository-guidance`
+Last-Validated: `2026-04-09T00:00:00Z`
+Tags:
+- `skills`
+- `subagent`
+- `verification`
+- `review-bundle`
+
+# Delegated Verification And Refresh
+
+Delegated work is optional helper output, not autonomous authority.
+
+## Main-Agent Acceptance Rules
+
+Before accepting meaningful delegated work, the main agent should verify:
+
+- claimed file impact against the actual diff-owned file set
+- claimed artifact reads or updates against files that actually exist
+- review-bundle contents against the current reviewed artifact and artifact hash
+- requirement, plan, addenda, and prior recursive docs that materially informed acceptance
+- whether any post-review repair made the delegated context stale
+
+## Record In The Phase Artifact
+
+When delegated work materially contributes, `## Subagent Contribution Verification` should record:
+
+- `Reviewed Action Records`
+- `Main-Agent Verification Performed`
+- `Acceptance Decision`
+- `Refresh Handling`
+- `Repair Performed After Verification`
+
+## Refresh Rule
+
+If repairs materially change the reviewed artifact, changed-file scope, or evidence basis, refresh the review bundle or action record before relying on delegated work for lockable evidence.
+
+## Rejection Rule
+
+If the main agent cannot verify delegated claims against actual files, actual artifacts, and the actual diff scope, reject the delegated result and fall back to self-audit for lockable completion evidence.

package/references/bodies/memory-router.md

@@ -0,0 +1,45 @@
+## Memory Router
+
+This file is the durable memory router for the repository.
+It is not a knowledge dump. Store durable memory in sharded docs under `domains/`, `patterns/`, `incidents/`, `episodes/`, `training/`, `skills/`, or `archive/`.
+
+Control-plane docs are not memory docs:
+- `/.recursive/RECURSIVE.md`
+- `/.recursive/STATE.md`
+- `/.recursive/DECISIONS.md`
+- `/.codex/AGENTS.md`
+- `/AGENTS.md`
+- `/.agent/PLANS.md`
+
+## Retrieval Rules
+
+- Read this file before loading any other memory docs.
+- Load only the memory docs relevant to the current task.
+- If the task may benefit from prior recursive-mode experiential learnings, use this index to identify the relevant docs under `/.recursive/memory/training/` and `/.recursive/memory/domains/`.
+- The optional `recursive-training-sync.py` helper is read-only; it prints startup guidance about what to read, but does not modify `MEMORY.md` or the memory plane.
+- If the task plans delegated review, subagent help, review bundles, smoke-harness portability work, or capability-sensitive execution, read `/.recursive/memory/skills/SKILLS.md` and then load the relevant skill-memory shards.
+- If Phase 8 will need to promote durable lessons, first capture run-local skill usage in the run artifact and only then promote generalized conclusions into skill-memory shards.
+- Prefer `Status: CURRENT` docs for planning and execution.
+- `Status: SUSPECT` docs may be used as leads, but revalidate them before trust.
+- Exclude `STALE` and `DEPRECATED` docs from default retrieval unless doing historical analysis.
+
+## Registry
+
+- `domains/` - stable functional-area knowledge with `Owns-Paths`
+- `patterns/` - reusable playbooks and solution patterns
+- `incidents/` - recurring failure signatures and fixes
+- `episodes/` - distilled lessons from specific runs
+- `training/` - extracted experiential learnings promoted from completed recursive-mode runs
+- `skills/` - durable skill and capability memory, routed via `skills/SKILLS.md`
+- `archive/` - historical or deprecated memory docs
+
+## Freshness Rules
+
+- Durable memory docs must declare the metadata defined by the installed `recursive-mode` artifact template.
+- Any doc whose `Owns-Paths` or `Watch-Paths` overlaps final changed code paths must be reviewed in Phase 8.
+- Affected `CURRENT` docs should be downgraded to `SUSPECT` until revalidated against final code, `STATE.md`, and `DECISIONS.md`.
+- If changed paths have no owning domain doc, create one or record the uncovered-path follow-up in `08-memory-impact.md`.
+- Training memory docs should keep their canonical content under `/.recursive/memory/training/`, use the memory index as the discovery surface, and record source runs plus watch-path or applicability guidance.
+- Skill-memory docs should record source runs, last validated date, environment notes, and current trust/fit guidance.
+- If a run materially teaches the repo something about skill availability, delegated-review quality, review-bundle usage, or toolchain fallback behavior, Phase 8 must either create/refresh a skill-memory shard or record why no durable lesson was promoted.
+- If the repo itself is a reusable skill/workflow distribution, durable memory must remain generalized. Do not store current-session run residue or temp-environment observations as if they were universal truth.

package/references/bodies/phase8-skill-memory.md

@@ -0,0 +1,48 @@
+Type: `pattern`
+Status: `CURRENT`
+Scope: `How Phase 8 captures run-local skill usage and promotes only durable lessons into skill memory.`
+Owns-Paths:
+Watch-Paths:
+- `/.recursive/RECURSIVE.md`
+- `/.recursive/memory/MEMORY.md`
+- `/.recursive/memory/skills/SKILLS.md`
+- `/.recursive/run/`
+Source-Runs:
+- `none (generic repository guidance)`
+Validated-At-Commit: `generic-repository-guidance`
+Last-Validated: `2026-04-09T00:00:00Z`
+Tags:
+- `skills`
+- `memory`
+- `phase8`
+- `promotion`
+
+# Phase 8 Skill Memory Promotion
+
+Skill memory should be operational, not accidental.
+
+## First Capture It Run-Locally
+
+Before promoting durable guidance, record run-local skill usage in `08-memory-impact.md`:
+
+- what skills were available
+- what skills were sought
+- what skills were attempted or used
+- what worked well
+- what issues were encountered
+- what future guidance changed
+- what promotion candidates exist
+
+## Then Decide What Becomes Durable
+
+Promote only lessons that are:
+
+- reusable across runs
+- specific enough to change future planning or verification behavior
+- not merely one-off environmental noise
+
+## Keep The Boundary Honest
+
+- Run-local observations belong in the run artifact first.
+- Durable memory should contain generalized guidance, not session history.
+- In reusable skill/workflow repos, do not turn current-session implementation residue into durable memory unless it has been rewritten as generic repository guidance.

package/references/bodies/plans-bridge.md

@@ -0,0 +1,43 @@
+## recursive-mode plans bridge
+
+This file exists only for tools that expect the Codex plans bridge at `/.agent/PLANS.md`.
+
+The canonical workflow specification lives in `/.recursive/RECURSIVE.md`.
+Do not maintain a second authoritative workflow here.
+
+If this bridge conflicts with `/.recursive/RECURSIVE.md`, follow `/.recursive/RECURSIVE.md`.
+
+Short user commands that should trigger recursive-mode orchestration include:
+
+- `Implement the run`
+- `Implement run <run-id>`
+- `Implement requirement '<run-id>'`
+- `Implement the plan`
+- `Create a new run based on the plan`
+- `Start a recursive run`
+
+Resolution rule:
+
+- If a run id is explicit, use that run.
+- If exactly one active/incomplete run exists and no run id is given, resume it.
+- If the user refers to a plan, create a new run only when a unique source plan/requirements artifact can be identified from repo docs or immediate task context.
+- If the command is ambiguous, ask for the run id or the repo path of the source plan/requirements artifact.
+
+Spec-authoring rule:
+
+- If the user asks to create a plan, help plan, create a spec, or write requirements for a new recursive run, prefer `recursive-spec` before orchestration.
+- `recursive-spec` should confirm the user wants spec help, ask what they want to do, read `STATE.md`, `DECISIONS.md`, `MEMORY.md`, and relevant code/tests, keep the draft in temporary non-repo storage, then create the new run only after the requirements are approved.
+
+Benchmark rule:
+
+- If the user asks to benchmark recursive-mode, compare recursive vs non-recursive execution, or generate a recursive-mode benchmark report, install and use the separate optional `recursive-benchmark` add-on on demand instead of assuming benchmark fixtures ship with the default recursive-mode package.
+- Prefer `find-skills` when available. Otherwise use `npx skills add <recursive-benchmark-package-or-repo> --full-depth`.
+
+Audit delegation rule:
+
+- If subagents are available and the audit/review context bundle is complete, delegated audit/review is the default path.
+- If the controller still chooses `self-audit`, record a concrete `Delegation Override Reason` in the audited phase artifact.
+
+Router rule:
+
+- If the user asks to route delegated work through another transport/model, configure or inspect `/.recursive/config/recursive-router.json`, refresh `/.recursive/config/recursive-router-discovered.json`, re-read both immediately before choosing the delegated CLI/model, and use `recursive-router` before dispatching the delegated role.

package/references/bodies/recursive-agents-router.md

@@ -0,0 +1,64 @@
+## .recursive AGENTS Router
+
+This file is a lightweight routing/index doc for agents already working inside the repository.
+It exists to reduce blind doc-by-doc scanning. It is not a second workflow spec.
+
+## Canonical Rule
+
+- Treat `/.recursive/RECURSIVE.md` as the single workflow source of truth.
+- If this file conflicts with `/.recursive/RECURSIVE.md`, follow `/.recursive/RECURSIVE.md`.
+
+## Suggested Read Order
+
+1. Read `/.recursive/RECURSIVE.md` first for workflow rules and required behavior.
+2. Read `/.recursive/STATE.md` when the current repo state matters.
+3. Read `/.recursive/DECISIONS.md` when prior rationale or relevant earlier work matters.
+4. Read `/.recursive/memory/MEMORY.md` when task context may depend on durable memory.
+5. Read `/.recursive/memory/skills/SKILLS.md` when the task may use delegated review, subagents, review bundles, smoke-harness portability work, or other capability-sensitive execution.
+6. Read the recursive-mode package README or maintainer notes from the installed skill directory or source package checkout when changing the package itself.
+
+## Task Routing
+
+- Starting or resuming a recursive-mode run:
+  - `/.recursive/RECURSIVE.md`
+  - `/.recursive/STATE.md`
+  - `/.recursive/DECISIONS.md`
+  - `/.recursive/memory/MEMORY.md`
+- Authoring a new recursive-mode spec or `00-requirements.md`:
+  - `/.recursive/STATE.md`
+  - `/.recursive/DECISIONS.md`
+  - `/.recursive/memory/MEMORY.md`
+  - the installed `recursive-spec` skill
+  - relevant code and tests for the requested area
+- Benchmarking recursive-mode against a non-recursive baseline:
+  - Install the separate optional `recursive-benchmark` add-on only when the user explicitly asks for benchmarking.
+  - Prefer `find-skills` when available; otherwise use `npx skills add <recursive-benchmark-package-or-repo> --full-depth`.
+  - The default exported `recursive-mode` package intentionally excludes benchmark fixtures and benchmark skill files.
+  - After the benchmark add-on is installed, follow its packaged fixture and harness docs.
+- Working on reusable package/bootstrap/docs for this repo:
+  - the recursive-mode package README or maintainer notes from the installed skill directory or source package checkout
+  - the recursive-mode installer scripts from the installed skill directory or source package checkout
+- Working on phase artifact structure or lint expectations:
+  - the recursive-mode artifact template from the installed skill directory or source package checkout
+  - the recursive-mode lint/status helpers from the installed skill directory or source package checkout
+- Working on delegated review, subagent behavior, or routed CLI delegation:
+  - `/.recursive/memory/skills/SKILLS.md`
+  - `/.recursive/config/recursive-router.json`
+  - `/.recursive/config/recursive-router-discovered.json`
+  - the installed `recursive-router`, `recursive-subagent`, and `recursive-review-bundle` skills
+- Working on memory behavior:
+  - `/.recursive/memory/MEMORY.md`
+  - the installed `recursive-training` skill
+  - `/.recursive/scripts/recursive-training-loader.py`
+  - `/.recursive/memory/training/`
+  - `/.recursive/memory/skills/SKILLS.md`
+
+## Non-Canonical Bridges
+
+These are adapters, not second specs:
+
+- `/.codex/AGENTS.md`
+- `/AGENTS.md`
+- `/.agent/PLANS.md`
+
+Read them only when the tool or host expects those entrypoints.

package/references/bodies/skill-discovery.md

@@ -0,0 +1,51 @@
+Type: `pattern`
+Status: `CURRENT`
+Scope: `How recursive-mode runs should discover, evaluate, and record external skills or missing capabilities.`
+Owns-Paths:
+Watch-Paths:
+- `/.recursive/RECURSIVE.md`
+- `/.recursive/memory/skills/SKILLS.md`
+- `/.recursive/run/`
+Source-Runs:
+- `none (generic repository guidance)`
+Validated-At-Commit: `generic-repository-guidance`
+Last-Validated: `2026-04-09T00:00:00Z`
+Tags:
+- `skills`
+- `discovery`
+- `find-skills`
+- `capability`
+
+# Skill Discovery And Evaluation
+
+Use this guidance when a run needs a specialized capability that is not already available.
+
+## Preferred Order
+
+1. Use the `find-skills` skill if it is already installed.
+2. Otherwise use the Skills CLI directly.
+3. If nothing suitable exists, proceed with built-in capability and record that no suitable external skill was available.
+
+## Useful Commands
+
+- `npx skills find <query>`
+- `npx skills add <package-or-repo>`
+- `npx skills add <package-or-repo> --skill <skill-name>`
+- `npx skills check`
+- `npx skills update`
+
+## Evaluation Rules
+
+- Prefer skills from reputable publishers or organizations.
+- Prefer higher install counts when the skills are otherwise comparable.
+- Check upstream repository quality before recommending or installing a skill.
+- Do not treat search results as proof of quality; verify source and documentation first.
+
+## Phase 8 Recording
+
+If a run materially used skill discovery, capture it in `08-memory-impact.md` under:
+
+- `## Run-Local Skill Usage Capture`
+- `## Skill Memory Promotion Review`
+
+Promote only durable, reusable conclusions into skill memory. Leave one-off session notes in the run artifact instead of turning them into durable guidance.

package/references/bodies/skill-memory-router.md

@@ -0,0 +1,42 @@
+## Skill Memory Router
+
+This file routes durable skill and capability knowledge for the repository.
+It summarizes what skills were available, what was attempted, what worked, what failed, and how future runs should use those skills.
+
+Use the subfolders for durable Markdown-only skill memory:
+
+- `availability/` - environment-specific skill availability and capability probe notes
+- `usage/` - stable usage guidance and fit for specific skills
+- `issues/` - recurring skill failures, limitations, or confusing behavior
+- `patterns/` - reusable multi-skill operating patterns and delegation playbooks
+
+Keep this file concise. Link to child docs instead of duplicating them.
+
+## Retrieval Hints
+
+- If the run may use delegated review, subagents, or review bundles:
+  - read this router
+  - read only the most relevant skill-memory docs that are actually present for the current environment and workflow
+- If the run may need specialized external capability:
+  - prefer the `find-skills` skill when available
+  - otherwise use the Skills CLI directly and treat discovered packages as candidates until quality is checked
+- If the run changes the smoke harness or cross-toolchain behavior:
+  - read the most relevant availability/usage notes if any have been intentionally promoted into skill memory
+- In Phase 8, promote durable skill lessons into one of these shards:
+  - `availability/` for capability probes and environment constraints
+  - `usage/` for stable fit/use guidance
+  - `issues/` for recurring failure modes
+  - `patterns/` for reusable operating playbooks
+- Before promoting anything durable, capture run-local skill usage in the Phase 8 artifact:
+  - what skills were available
+  - what skills were sought
+  - what skills were attempted or used
+  - what worked well or poorly
+  - what future guidance should change
+
+## Current Docs
+
+- `/.recursive/memory/skills/usage/skill-discovery-and-evaluation.md`
+- `/.recursive/memory/skills/patterns/delegated-verification-and-refresh.md`
+- `/.recursive/memory/skills/patterns/phase8-skill-memory-promotion.md`
+- Add child docs here only when they are intentionally promoted as reusable repository guidance.

package/references/bodies/state.md

@@ -0,0 +1,5 @@
+# STATE.md
+
+## Current State
+
+- Initial state not documented yet.