Reality Check

Verify the result without replacing it.

Reality Check adds read-only annotations to the object already moving through a HACP combo. It checks what supports the result, what it assumes, and the concrete things it points at.

This repository remains the stable home of this deck. New experimental Games, Decks, and Cards now develop in the central Control Decks catalogue.

The problem

A polished answer can hide the wrong repository, a stale source, or an assumption nobody checked. Replacing the answer during verification loses the object everyone was discussing. Reality Check keeps it intact and attaches the evidence needed to judge it.

The flagship combo

CHECK ASSUMPTIONS → CHECK SOURCES

First expose the premises that matter. Then verify the evidence needed to support them.

THINK PROPOSE → REALITY CHECK ASSUMPTIONS → REALITY CHECK SOURCES

The proposal stays intact. Reality Check appends two annotations and passes the same Working Object onward.

Install

Install the HACP session adapter once, then the deck. Without a compatible adapter the commands may appear, but the session is not fully HACP-conforming.

Codex

codex plugin marketplace add control-decks/human-agent-control-protocol
codex plugin add hacp@hacp
codex plugin marketplace add control-decks/reality-check
codex plugin add reality-check@reality-check

Use $reality-check:help or play $reality-check:check-sources.

Claude Code

claude plugin marketplace add control-decks/human-agent-control-protocol --scope user
claude plugin install hacp@hacp --scope user
claude plugin marketplace add control-decks/reality-check --scope user
claude plugin install reality-check@reality-check --scope user

Use /reality-check:help or play /reality-check:check-sources.

The deck

Card	Annotation	What it verifies
CHECK SOURCES	reality-check/sources-checked	Material claims, evidence, freshness, contradictions, and unknowns
CHECK ASSUMPTIONS	reality-check/assumptions-checked	Explicit and necessary implicit premises
CHECK TARGETS	reality-check/targets-checked	Files, repositories, endpoints, accounts, entities, and deliverables

All three cards resolve once and remain read-only. They preserve the object's binding, status, kind, content, and existing annotations. Each new annotation keeps the Binding actually inspected, even after later cards transform the object.

CHECK ASSUMPTIONS uses the full conversation when it starts a combo without an object. Placed after another operation, it checks that operation's result.

Combos

THINK TO PLAN → CHECK SOURCES → WORK IMPLEMENT → THINK EXPLAIN

The material claims supporting the plan are checked, then its implementation result is explained as one cross-deck object.

WORK LOCAL ONLY → CHECK SOURCES

Only local files, cached artifacts, command output, and conversation context are consulted. Remote claims are marked unverified locally.

WORK EVIDENCE REQUIRED → CHECK ASSUMPTIONS → CHECK SOURCES → WORK IMPLEMENT

Implementation proceeds only when the accumulated annotations support the dependent work.

Rules

• Cards resolve in their written position; no hidden reordering.
• Every check uses live allowed evidence when available.
• An annotation never rewrites the result it checks.
• Evidence, inference, contradiction, and unknown remain distinct.
• Active controls from another deck still govern tool access.
• The response contains one trace and the smallest useful set of findings.

HACP

Reality Check implements HACP Draft 0.4: Cards are the interface. Control is the protocol. Its scoped annotations travel with the shared Working Object and advertise open evidence traits without naming another deck's cards. Cards are explicit human commands and cannot be inferred or replayed by the agent.

Detailed reference

• Canonical card metadata: hacp.deck.json
• Provider-independent behavior: plugins/reality-check/skills
• Protocol: Human-Agent Control Protocol

MIT © thevzion · Published by Control Decks