rcf-lite 0.0.1 → 0.8.0

package/fixtures/canary-manifest.json

@@ -0,0 +1,103 @@
+{
+  "registerCanary": [
+    {
+      "id": "rc-2026-08-12-001",
+      "createdAt": "2026-08-12T16:39:41.040Z",
+      "buildVersion": "0.8.0-mockdriver",
+      "fixturePromptId": "canary-prompt-01",
+      "responseWordCount": 55,
+      "grades": {
+        "internalRuleCitation": {
+          "verdict": "pass",
+          "matches": []
+        },
+        "unglossedJargon": {
+          "verdict": "pass",
+          "matches": []
+        },
+        "redundantPermissionAsk": {
+          "verdict": "pass",
+          "matches": []
+        },
+        "bypassOffer": {
+          "verdict": "pass",
+          "matches": []
+        },
+        "wordCountBudget": {
+          "verdict": "pass",
+          "target": 200,
+          "actual": 55,
+          "matches": []
+        }
+      },
+      "verdict": "fail",
+      "shipDespiteFailReason": "mock canary driver used; no real subagent was dispatched. This record verifies canary infrastructure only, not the register itself."
+    },
+    {
+      "id": "rc-2026-08-12-002",
+      "createdAt": "2026-08-12T16:39:41.041Z",
+      "buildVersion": "0.8.0-mockdriver",
+      "fixturePromptId": "canary-prompt-02",
+      "responseWordCount": 55,
+      "grades": {
+        "internalRuleCitation": {
+          "verdict": "pass",
+          "matches": []
+        },
+        "unglossedJargon": {
+          "verdict": "pass",
+          "matches": []
+        },
+        "redundantPermissionAsk": {
+          "verdict": "pass",
+          "matches": []
+        },
+        "bypassOffer": {
+          "verdict": "pass",
+          "matches": []
+        },
+        "wordCountBudget": {
+          "verdict": "pass",
+          "target": 200,
+          "actual": 55,
+          "matches": []
+        }
+      },
+      "verdict": "fail",
+      "shipDespiteFailReason": "mock canary driver used; no real subagent was dispatched. This record verifies canary infrastructure only, not the register itself."
+    },
+    {
+      "id": "rc-2026-08-12-003",
+      "createdAt": "2026-08-12T16:39:41.041Z",
+      "buildVersion": "0.8.0-mockdriver",
+      "fixturePromptId": "canary-prompt-03",
+      "responseWordCount": 55,
+      "grades": {
+        "internalRuleCitation": {
+          "verdict": "pass",
+          "matches": []
+        },
+        "unglossedJargon": {
+          "verdict": "pass",
+          "matches": []
+        },
+        "redundantPermissionAsk": {
+          "verdict": "pass",
+          "matches": []
+        },
+        "bypassOffer": {
+          "verdict": "pass",
+          "matches": []
+        },
+        "wordCountBudget": {
+          "verdict": "pass",
+          "target": 200,
+          "actual": 55,
+          "matches": []
+        }
+      },
+      "verdict": "fail",
+      "shipDespiteFailReason": "mock canary driver used; no real subagent was dispatched. This record verifies canary infrastructure only, not the register itself."
+    }
+  ]
+}

package/guidance/README.md

@@ -0,0 +1,25 @@
+# Agent guidance pack
+
+This directory is the product's agent-facing guidance layer: what an AI agent needs to run the RCF method well. The CLI referees the tree; these files teach the method the referee assumes. Everything here is static markdown, served to agents over MCP and readable in place.
+
+## What each file is
+
+| File | Consumer | Channel |
+|---|---|---|
+| [overview.md](overview.md) | Any agent or MCP client needing orientation | resource `rcf://docs/overview` |
+| [document-model.md](document-model.md) | Agents authoring or editing tree documents | resource `rcf://docs/document-model` |
+| [build-cycle.md](build-cycle.md) | Agents in the build loop; the normative cycle statement | resource `rcf://docs/build-cycle` |
+| [harness-template.md](harness-template.md) | Adopters wiring an agent harness; agents self-installing | resource `rcf://docs/harness-template` |
+| [build-cycle-playbook.md](build-cycle-playbook.md) | The operating agent executing FBS items | prompt `rcf_execute_build_cycle` |
+| [elicitation-playbook.md](elicitation-playbook.md) | The eliciting agent starting a project with a human | prompt `rcf_elicit_requirements` |
+| [manifest.json](manifest.json) | The MCP server; the drift tests | machine channel map |
+
+The playbooks are prompts (instructions to a model); the reference docs are resources (context a client attaches). Each file has one canonical MCP address. Slugs are the filename minus `.md`, so the mapping is guessable without the manifest.
+
+## Adoption in three steps
+
+1. Install the package so the `rcf` binary and this pack are on hand.
+2. Run `rcf init` in your project BEFORE starting the agent session - it scaffolds the tree, registers the MCP server in `.mcp.json` and writes the fragment from [harness-template.md](harness-template.md) into your project's CLAUDE.md and AGENTS.md (both, on a fresh project; an existing instructions file is refreshed in place). Manual paste of the fragment is the fallback for non-standard harnesses.
+3. Start your agent session and have the agent run `rcf build --next`, executing the runbook the bundle prints.
+
+That is the whole loop. The playbooks add depth when the agent needs it; the bundle's built-in runbook is enough to start.