Skip to content

WIKI_INDEX

Jacob S Vickers edited this page Jul 16, 2026 · 7 revisions

Integrity Protocol Wiki — Index

Content catalog. Every page represents something that actually exists in the codebase right now — see the schema's "no aspirational content" rule. Last updated: 2026-07-15 | Total pages: 26 (18 concepts, 8 entities)

Acronym glossary

  • AIS — Agent Integrity Score
  • BAA — Business Associate Agreement
  • BCC — Behavioral Commitment Chain
  • DID — Decentralized Identifier
  • VTL — (old term) Verifiable Trust Layer — see Observability & PHI Safety for what's actually built
  • ZKP — Zero-Knowledge Proof(ing pipeline)

Concepts

Entities (built)

  • contracts — Solidity/Foundry: the 7 primitives, factory, registries, XNS, Shield, market layer, $ITK, reworked CCIPReputationBridge (165 tests, live on Base Sepolia — XNS/CCIP not yet broadcast)
  • integrity-oracle — Rust/Axum AIS scoring (incl. server-side telemetry-signal re-derivation, derive.rs) + on-chain verification + markets/leaderboard/wallet reads + PHI-rejection backstop + unauthenticated OTLP/gRPC trace receiver, ASCII-escaping canonical-JSON fix (80 lib tests + 9 e2e)
  • integrity-sdk — Python agent library: registration, BCC, markets, telemetry (widened OpenAI/LangChain integration metadata, opt-in redact_phi), PHI redaction, pre-execution intent-capture (invoke_intent), fixed telemetry-signing wire bug (135 tests, 1 skipped + 1 opt-in oracle e2e)
  • integrity-cli — developer CLI, real on-chain register incl. real oracle re-verification, new xns command group (57 tests, incl. 1 opt-in oracle e2e)
  • bcc_middleware — FastAPI + OPA policy gate, incl. verification-tier gate, the reputation-sync/slashing signer loop (app/reputation.py, app/scoring_loop.py), a real async-hot-path fix (asyncio.to_thread) plus the per-signer nonce lock and Merkle-batcher thread-safety it required, and a real HMAC-signed verification token (91 pytest + 28 OPA tests)
  • integrity-mvp — the dashboard app, rewritten (2026-07-12) into a new 16-page shell: real oracle/userapi reads and writes throughout (agents, markets, wallet, Smart BAA sign/revoke, real enterPosition bet placement, real userapi account/API-key auth), a Notion-style Block & Widget dashboard engine, a rewritten "Verify Agent Control" flow (the old signature-challenge "claim" premise had no on-chain support), real test infra (9 vitest + 18 Playwright e2e, run against a live backend+chain), and real project docs. Explicitly seeded (badged, not silently faked): order-book UI, node/network telemetry widgets, BAA creation.
  • integrity-zkp — real Noir/Barretenberg circuit, compiled & proven
  • integrity-userapi — FastAPI + Postgres user accounts/auth, strictly non-chain (API keys now authenticate requests, JWT revocation, login rate-limiting, demo_runs completion path — 51 tests, real Postgres, real CORS for integrity-mvp)

Guides

  • Smart Contract Development — how to write, test, and deploy a new contract in contracts/: repo conventions (AccessControl, custom errors, NatSpec), Foundry test patterns (vm.prank/makeAddr/vm.expectRevert(...selector)), wiring into Deploy.s.sol/DeployMarkets.s.sol + make sync-abis, local/Base Sepolia deploy walkthrough, and the SovereignAgent.execute vs. direct-EOA auth convention.
  • Multi-Domain Guardrails Design[DESIGN, PARTIALLY BUILT]: how bcc_middleware's HIPAA-only OPA policy gate generalizes to pluggable, domain-scoped guardrail bundles (industry survey + concrete design against this repo's existing bcc.rego/HIPAAGuardrailRegistry.sol pattern). A real worked-example bundle (bcc_middleware/policies/general.rego, 12 passing OPA tests) is built as a stretch goal; the domain-aware GuardrailRegistry.sol and bcc_middleware wiring are still design-only.

Architecture

(none yet — add a cross-package data-flow doc if the per-package entity pages prove insufficient)

Open queries

  • No LLM-as-judge rubric exists anywhere in this repo or the cross-checked Desktop spec docs ("Xibalba Solutions defines" it, per the plan notes) — the judge_evaluations ingestion schema is designed but the actual scoring rubric is an open product question, not an engineering one. See Observability & PHI Safety.

Clone this wiki locally