~/djzs/builders $ cat pitch.txt

DJZS. A pre-execution gate your treasury can recompute.

OKFORagent-framework builders · DAO treasuries · anyone deploying autonomous capital
OKGATEdeterministic audit of the reasoning behind a move — PASS / WAIT / FAIL
OKRECEIPThash-locked verdict · permanent Irys certificate · on-chain trust score
OKRAILBase mainnet · 2.00 USDC over x402 · one line to add as an MCP tool

Your agent is about to move money. Before it does, it should be able to prove — to you, to governance, to a dispute six months from now — that the reasoning was sound at the moment it acted. DJZS produces that proof: a verdict computed by frozen code, not improvised by a model, with a receipt a third party can recompute.

Two gates, two axes DJZS audits WHY · your wallet stack audits WHAT

Your transaction pipeline — simulation, threat scanning, smart transactions — already answers is this transaction safe to sign? It cannot answer the other question: is the reasoning behind this position sound? A transaction can clear every check and still act on a thesis that is unfalsifiable, unsourced, or pure narrative.

capital action
   │
   ▼
GATE 1 · DJZS        audits the THESIS        (why)
   │                returns PASS / WAIT / FAIL
   ├─ WAIT / FAIL ─▶ HALT · nothing executes
   │
 EXECUTE
   │
   ▼
GATE 2 · WALLET      audits the TRANSACTION   (what)
   ▼
on-chain

The gate clears the logic; the position is yours.

What integrating buys you governance artifacts, not alpha

A verdict that can't be argued with after the fact

An LLM extracts facts from the intent — it never returns a verdict. A frozen deterministic engine scores the struct: pure code, no model, no clock. Same struct, same verdict, same hash, every run. PASS proceeds. FAIL stops. Unknown drains to WAIT and halts.

A receipt anyone can recompute

Weights are hash-locked exported constants. A change is a versioned re-derive, never a hot patch. That immutability is what lets a third party reproduce verdict_hash byte-for-byte from the published ruleset.

A permanent, public audit trail

Every in-scope audit anchors a ProofOfLogic certificate to Irys mainnet. Retrievable by id, free to read via query_pol_certificates. The record outlives the agent, the framework, and the operator.

An on-chain reputation for the agent itself

Pass an agent_address and the verdict writes to DJZSLogicTrustScore on Base. Anyone can read totalAudits · failRate · latest verdict via query_agent_trust. Governance can gate on it.

The refusal is the product. An auditor that only ever says yes is not an auditor.

Honest posture what a treasury should know before trusting this

LIVEPaid audits on Base mainnet. Non-custodial x402 settlement, EIP-3009 — funds move payer → treasury directly, facilitator pays gas. Out-of-scope requests are refused free. Four DJZS contracts attested on Base, source public, verifiable on Basescan.
LIVEReproducible verdict hash. Hash parity held byte-identical across every re-run since 2026-07-12, including runs with extraction divergence on non-preimage fields.
LIVEReproducible binding + on-chain attestation. Every paid verdict returns an EIP-712 intent_hash any third party recomputes from the intent alone, and writes an EAS attestation on Base under the DJZS schema onto the paying agent’s record. A Safe Guard or Zodiac module can require it. Contract at djzs.ai/ruleset; recompute any receipt at djzs.ai/verify.
ROADMAPPerpetuals and general-reasoning taxonomy. Frozen, three codes live, no served surface. Disclosed, not sold.

A DJZS PASS certifies well-formed reasoning at a moment — never that the narrative is true or the trade wins. It does not check that a quoted price is still live or that a source is right. Those remain yours.

Disclosed as roadmap, not sold as done.

Integrate one line, one endpoint, one reference client

As an MCP tool:

claude mcp add --transport http djzs-trust https://mcp.djzs.ai/mcp

As plain HTTP x402 — any x402 client pays this (Base MCP, MetaMask Agent Wallet, x402-axios). An unpaid request returns the 402 challenge and settles nothing:

curl -s -X POST https://mcp.djzs.ai/x402/verify_pm_trade \
  -H 'content-type: application/json' \
  -d '{"intent":{"market":"…","side":"YES","thesis":"…"}}'

As a working pattern: djzs-pm-gate audits a thesis and creates the order only on a clean in-scope PASS. Fork it, point it at your venue.

Discovery contract at GET /openapi.json · payment config at GET /health/x402 · machine summary at /llms.txt. All free.

Connect the gate

Audit before act.