Role 01 · Extractor
Extractor
Parses uploads into structured JSON — parties, dates, amounts, jurisdiction, risk flags. Feeds all downstream agents.
XXXIII.io Document Intelligence
Edge-native document intelligence for regulated agreements — entity intake, multi-agent drafting and compliance review, cryptographic fingerprinting, and optional chain anchoring. A sovereign processing module within the GMIIE / FTH protocol stack, not a standalone SaaS pitch. Operational tools run at docs.unykorn.org; this page is the xxxiii.io system-area map with honest status on every layer.
Scope: Document Intelligence handles counterparty agreements, capital instruments, and verify-by-hash proofs. Author IP and literary edition roots are a separate concern — see LPS-1 and Authors provenance. GMIIE editorial intelligence uses the Publishing OS workflow; contracts use this module.
Operational workflow
Six stages from intake to anchored proof. Each stage maps to one or more production agents on the doc-intel worker — fixed chain, not ad-hoc tool picking.
Intake→
Draft→
Compliance→
Sign→
Secure delivery→
Proof anchor
- Intake — PDF, DOCX, or template selection; company profile injection; structured field extraction into an evidence bundle.
- Draft — Template-driven agreement generation with governing-law blocks and citation anchors (13 templates including Reg D subscription and capital instruments).
- Compliance — ESIGN, UETA, SEC Reg D, FINRA, KYC/AML, and capital-markets clause checks — severity-ordered findings before release.
- Sign — Human-in-the-loop reviewer attestation; OTP-verified signing ceremony for Tier 1 sessions (ESIGN/UETA aligned).
- Secure delivery — Session-bound QR, export policy (watermark / redact / full), encrypted handoff to counterparty — no public copy without policy.
- Proof anchor — SHA-256 content fingerprint,
contract_id, KV dual-index; optional XRPL memo and IPFS pin when infrastructure is configured.
Six agents — operational roles
Workers AI agents with dedicated system prompts and validation rules. Listed as production roles, not marketing personas.
Role 02 · Drafter
Drafter
Generates agreements from templates with company profile injection and governing-law blocks.
Role 03 · Compliance
Compliance
Regulatory and provenance gap analysis — ESIGN, UETA, Reg D, FINRA, PII exposure. Max eight severity-ordered findings.
Role 04 · Reviewer
Reviewer
Final QA and human sign-off queue. Records reviewer attestation hash before publish or signing ceremony release.
Role 05 · Chat
Chat
RAG-backed Q&A over session documents — clause explanation, edit suggestions, counterparty questions with source citations.
Role 06 · Capital
Capital Compliance
Trade finance and banking instruments — UCC Articles 5/9, ICC UCP 600, ISP98, Basel, ISDA, Dodd-Frank alignment checks.
Full invoke paths and I/O schemas: Agent Registry · Protocol stack entry
GMIIE integration points
LPS-1 provenance
Literary and editorial works register under Donkai / LPS-1 edition roots on xxxiii.io. Contract proofs from Document Intelligence are a parallel track — same SHA-256 discipline, different artifact class. Do not conflate agreement certificates with author edition anchors.
x402 metering
Machine-to-machine API access on GMIIE uses x402 meter events via the content ledger (/api/gmiie/meter/event). Document Intelligence API routes can participate in the same Troptions rails when partners enable metering — not all endpoints gated today.
Publishing OS
Editorial intelligence follows Draft → validate → review → approve → publish with mandatory attribution. Document Intelligence mirrors the human-governed pattern for agreements: compliance blockers must clear before sign and anchor. Shared editorial rule: nothing ships without accountable sign-off.
Fraud desk (compliance)
Counterparty and typology screening on the GMIIE Fraud Desk informs KYC/AML posture for agreement workflows. Compliance agent findings are document-scoped; fraud analyze is entity/address-scoped — operators cross-reference both for institutional onboarding.
Live tools
Production UI and API on Cloudflare Pages + doc-intel-api worker. This xxxiii.io page does not host the generator — it documents the module and links outward.
Honest status
Labels verified against deployed worker and Pages site. We do not mark simulation or tunnel-dependent paths as LIVE.
| Component | Role | Status | Notes |
|---|---|---|---|
| Pages frontend | Static UI — overview, hub, verify, generator | LIVE | docs.unykorn.org |
| Worker API | /api/health, /api/ai/*, /api/contract/verify | LIVE | doc-intel-api on Cloudflare |
| 6-agent pipeline | Workers AI — Extractor through Capital | LIVE | Llama 3.1 8B + BGE embeddings |
| KV store | Proofs, embeddings, session state | LIVE | DOC_INTEL_KV · dual-index by id and hash |
| SHA-256 fingerprint | Deterministic contract_id on generate | LIVE | Always computed |
| Signing ceremony | OTP Tier 1 · ESIGN/UETA session flow | LIVE | Agreement generator + QR session |
| Public verify | /api/contract/verify · verify.html | LIVE | Hash lookup without chain requirement |
| Template library | 13 templates + capital instruments | EDITORIAL | Catalog maintained; not legal advice |
| XRPL anchor | AccountSet + Memo v2 (Ed25519) | PARTIAL | When secrets and funding configured |
| IPFS pin | CID via Kubo tunnel | PARTIAL | Tunnel + node availability dependent |
| GMIIE EVM anchor | Optional anchor contract | SIMULATION | Config only; verify-by-hash sufficient |
| x402 on DOC API | Per-call metering | PARTIAL | Rails exist on GMIIE ledger; not all routes gated |
Not legal advice. Templates and compliance findings assist institutional workflows; counsel review remains operator responsibility. Terms · Use of Intelligence