reality-feedback-create
Skill2 starsChanged 24 days agoMITView on GitHub
Layered eval architecture, Layer 4 auto-create. Fires from the Stop hook chain after critic_dispatch. Appends an entry to the reality_feedback.sqlite ledger when the classifier verdict is high-stakes, with surface inference + outcome window + Critic metadata. Operator labels the outcome later via weekly review (skills/reality-review-weekly/SKILL.md). Outcomes feed a Layer 1 v2 classifier's training set over months.
In this repository57 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- llms.txtllms.txt
- advisorSkill
- agent-dispatchSkill
- arenaSkill
- audit-pypi-model-packageSkill
- branching-workflowSkill
- code-reviewSkill
- criticSkill
- cron-child-oauth-auditSkill
- daily-forestSkill
- deep-researchSkill
- diagnose-cron-timeoutSkill
- dreamingSkill
- eod-summarySkill
- filingSkill
- forest-synthesisSkill
- goalsSkill
- graph-hygieneSkill
- ideaSkill
- inline-tagsSkill
- intel-analyzerSkill
- longformSkill
- loop-experimentSkill
- loop-librarySkill
- meta-memory-reviewSkill
- office-hoursSkill
- open-loopsSkill
- plan-ceo-reviewSkill
- plan-design-reviewSkill
- prdSkill
- progressive-disclosureSkill
- reality-review-weeklySkill
- recallSkill
- reconcile-extractionSkill
- redactSkill
- repo-auditSkill
- research-digestSkill
- review-gateSkill
- run-long-job-detachedSkill
- saveSkill
- scopeSkill
- self-auditSkill
- shadow-test-local-classifierSkill
- signal-scorerSkill
- skill-auditSkill
- skill-chainingSkill
- spawn-agent-in-tenantSkill
- spawn-tenantSkill
- split-log-rows-by-session-kindSkill
- subagent-delegationSkill
- telegram-dump-routerSkill
- telegram-reply-toolSkill
- verify-stackSkill
- wave-planSkill
- weekly-retroSkill
The file
Files
Reality-feedback auto-create skill
Layer 4 of the layered eval architecture. Auto-creates ledger entries for high-stakes outputs so their outcome can be graded later. The discipline is: at output time, capture the prediction. At outcome time (days/weeks later), grade actual vs predicted. Over months, the deltas feed a Layer 1 v2 classifier's training set.
Example output (ledger entry shape)
{
"id": "rfb-2026-05-11-001",
"ts_created": "2026-05-11T05:40:00+00:00",
"session_id": "s_2026-05-11-build",
"stake_class": "high",
"stake_signals": ["draft", "outbound", "high-value-proposal"],
"predicted_surface": "counter-offer should test a higher retainer + shorter term",
"outcome_window_days": 30,
"outcome_due": "2026-06-10",
"outcome": null,
"critic_metadata": {"score": 8.4, "passes": 3, "concerns": ["could be premature pattern-lock at n=2"]}
}Conversation context (prior)
Auto-fired by the Stop hook chain. runs AFTER classifier_dispatch + critic_dispatch + (optionally) save_handler. The prior conversation is the just-completed turn whose output triggered the high-stake classification. The script walks logs/session.jsonl back to find the most-recent stake_classified event with class=high + the matching tool-output that produced it.
Output format
Returns ONE row appended to data/reality_feedback.sqlite table outcomes:
| column | type | description |
| id | TEXT PK | rfb-YYYY-MM-DD-NNN |
| ts_created | ISO8601 | when created |
| session_id | TEXT | source session identifier |
| stake_class | TEXT | always "high" for entries created by this skill |
| stake_signals | JSON | array of classifier signals |
| predicted_surface | TEXT | prediction this skill captured |
| outcome_window_days | INT | when grading should happen |
| outcome_due | DATE | computed: ts_created + window |
| outcome | TEXT (nullable) | filled in later via skills/reality-review-weekly/SKILL.md |
| critic_metadata | JSON | from Critic dispatch (score / passes / concerns) |
When to fire
Auto-fired by scripts/pipeline/reality_feedback_create.py from the Stop hook chain (after critic_dispatch). Conditions: stake_classified event in the current turn = high. Cooldown via session.jsonl walk-back: if a reality_entry_created event already exists for the current turn, skip.
Manual invocation (operator override): use this skill when the classifier missed a high-stakes output but you want it tracked. Run the script with --manual flag (TODO: add CLI manual mode).
Ledger schema
memory/state/reality_feedback.sqlite, table entries:
| col | type | meaning |
| id | INT PK | auto-increment |
| timestamp | TEXT | ISO8601 of output emission |
| surface | TEXT | post / proposal / recommendation / outreach / positioning / other |
| summary | TEXT | 1-3 sentence summary of output |
| prediction | TEXT | nullable: extracted from Critic verdict reason if SHIP/SHIP_WITH_FIXES |
| expected_outcome_window_days | INT | when to surface for review |
| outcome | TEXT | positive / negative / neutral / unknown / NULL (= unmarked) |
| outcome_marked_at | TEXT | ISO8601 of operator marking |
| classifier_metadata | TEXT | JSON of stake_classified event |
| critic_verdict | TEXT | JSON of critic_verdict event (nullable) |
Indexes: (outcome, timestamp) for the weekly-review query, (surface) for per-surface analysis.
Surface inference (best-effort)
| Signal | Surface | Window (d) |
matched_rules has external:post OR doc-type:public-output OR **1/N** thread numbering | post | 2 |
| matched_rules has draft:email / draft:dm / external:counterparty | outreach | 30 |
| matched_rules has deal:quote / money:amount | proposal | 14 |
| text mentions event / venue / sponsorship / activation | positioning | 14 |
| matched_rules has a domain-authority signal (and not a post) | recommendation | 30 |
| fallback | other | 14 |
A public post wins over a proposal when both signals are present (posts are public-bound, a proposal is an internal draft → different review urgency).
Hard rules
- Async / non-blocking. Single SQLite insert. Latency budget <50ms. WAL mode handles concurrent writes from a rapid Stop chain.
- Cooldown via session.jsonl walk-back. One entry per turn. If
reality_entry_createdis already in the current turn, skip. - Fail-open silently. Any error → exit 0, log to errors.jsonl. The hook MUST NOT block the session.
- Window defaults are starting points. Per-surface fine-tuning is a Layer 4 v2 deliverable; v1 ships fixed defaults.
- No outcome at create time. Outcome is operator-marked via the weekly review skill, NOT inferred. Auto-grading is a separate (future) skill.
Pairs with
- Layer 1 classifier (
scripts/eval/stake_classifier.py): fires this skill when stake:high. - Layer 2 Critic (
skills/critic/SKILL.md): provides verdict metadata stored in the ledger; SHIP_WITH_FIXES outcomes flagged for special review. - Weekly review (
skills/reality-review-weekly/SKILL.md): consumes ledger entries where outcome IS NULL and timestamp + window has elapsed.
Source archive
Layer 4 auto-create deliverable of the layered eval architecture. Pairs with the weekly review skill that grades what this one captures.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

