Verity · Console

Write it as code. The gate reads it as a proposal.

This is the gate's own workspace, open to anyone — no account, and nothing you type leaves the browser. Write a proposal the way an agent would emit one, as JSON, and the gate checks it as you type, on the same four rules the production gate runs. Press Run the gate and it judges in full — velocity included — and shows you the record it would seal. Sealing for real happens on the operator's side of the glass; this side is for seeing how the judgment works.

Live gate: checking… · Root key: checking… · Rules R1–R4 · shadow mode
proposal.json — verity console
proposal.json
verdict.jsonNO RUN YET
— Checking as you type covers R1, R2 and R4. Run the gate for the full judgment, velocity (R3) included.
    Ln 1, Col 1 checked as you type JSON shadow verity-gate rules · same source as production

    ALLOW

    The proposal passes and the act proceeds. The verdict is still written down — an allowed act is a recorded act, with the proposal's hash beside it.

    ESCALATE

    The gate will not decide this one alone: money above the ceiling, a denied target, deletion in the language, a caller moving too fast. A human decides, and the record says why.

    VETO

    The destructive class never passes — not slowly, not with approval attached to the proposal itself. A veto is a successful gate operation, and it seals like any other verdict.

    The checking on this page runs entirely in your browser, on a line-for-line port of the production rule set — same constants, same order, same words in the verdict. What it cannot do is seal: records enter the signed chain only through the operator's API, under a caller key. If you run agents and want your proposals judged where they execute, the API page is the door, and pilot@verityverdict.com is the address.