A correction ledger showing why a rule exists, what it changed and how to undo it.
A correction is evidence from a specific session and source locator. Preserve the exact case of API_KEY in the rule; case folding would turn a useful instruction into a contradictory one.
Start with a learner workspace
Repository memory and state, Verification gates. Language foundation: TypeScript object types.
Use Node 22.18+ and Python 3.10+ for the grader. Core TypeScript runs without package installation.
python3 scripts/project_test.py workflow-hooks --init learning-artifacts/workflow-hooks
python3 scripts/project_test.py workflow-hooks --stage 1 --path learning-artifacts/workflow-hooksBuild route
- Capture corrections with provenance
- Count independent sessions
- Approve and select scoped rules
- Persist rules across sessions
Run with your own inputs
After completing the stages, these commands run your workspace code on the original Orchard examples. Replace the sample paths with your own files.
node learning-artifacts/workflow-hooks/cli.ts capture orchard-rules.json projects/workflow-hooks/examples/corrections.jsonl
node learning-artifacts/workflow-hooks/cli.ts inspect orchard-rules.jsonTo inspect the complete reference first, replace learning-artifacts/workflow-hooks with projects/workflow-hooks/solution in the same command. JSON results use schema_version: 1; paths and argument examples are explicit so another tool can consume them.
Integration boundary
capture, inspect, approve, retire and emit are file-based commands. emit returns neutral JSON with additional_context and resolvable evidence; an agent integration must map that field to its documented hook interface. Approval requires the current digest. Stores are versioned, atomic and single-writer.
python3 scripts/project_test.py workflow-hooks --all --solution --strict
python3 scripts/project_test.py workflow-hooks --all --path learning-artifacts/workflow-hooks --strictThe first command checks the reference. The second checks your implementation. The published examples and tests are regression evidence, not a production certification or an unseen benchmark.
