T-16h (yesterday, 21:00 CEST): Damon describes the gap — CBP filer code acquired, ACE sandbox open, missing is the byte-exact software layer. T-0h (now): 326 tests green across the three priority clearances (Type 1 · Type 11 · T-1), live transformation demo at catair.atwenture.com/simulator, component-flow map at /process, Damon's 14-point checklist answered end-to-end. This isn't a pitch anymore. It's a kickoff.
A ten-entity ontology — Module · Transaction · Record · DataElement · CodeTable · ErrorCode · BusinessRule · Workflow · RevHistory · PGAIntegration — extracted from every PDF, linked with typed edges, queryable by code.
Damon's network routes ~350,000 customs filings per month per operating company — Type 1, Type 11, and T-1 clearances flowing through the compliance software we're building. Damon's own pricing anchor: $0.12 per clearance (his words, this meeting). The math is trivial. The work is to make it real.
Business model: equity-partnership + per-clearance volume. Not day-rate. Not projections. Damon has the filer code, the ACE sandbox, the volume, and the network. The question isn't "will customers buy?" — it's "can we ship byte-exact compliance fast enough?"
Plus 18,691 typed edges connecting records, fields, codes, and rules — and a cross-jurisdiction concept map with 87 typed concepts spanning US, UK, EU and Mexico.
From a single MCP call (e.g. catair_get_record("entry_summary_r10")), the builder-agent produces:
Below: the typed knowledge graph our Builder-Agent reads. Every node is a compliance entity, every edge is a schema relationship — extracted from 100 CBP specification PDFs.
Every node carries a page reference. Every edge is typed. The graph is the product.
Not a deck. Not a plan. Real code, in a repository, deployed to production. The three Damon-priority clearance types — Type 1 (C_01), Type 11 (C_11), T-1 In-Bond (QP/WP) — are byte-exact today and live on catair.atwenture.com/simulator.
C_01 full Entry Summary · R20–R90 · byte-exact
C_11 low-value entry · simplified record set
In-bond transportation messages · byte-exact
ABS/Broker Statement records + parser
R20–R90 foundation · PGA hooks ready
Create / Update / Delete importer records
NHTSA vehicle / HS-7 · first PGA module
Census warning message parsing
CBP courtesy-notice records
AD/CVD case lookup + filing records
QP/WP message set · underlies T-1 above
R10/20/30/35/36/45/46 · scoped for ocean-freight phase (Damon: "eBond is for ocean brokers")
all green · first-run · regression-pinned · live in /simulator
You answered the full 14-point pre-meeting checklist — MQ config (QGC1, CBITAMERICA, cbpgw-trade-cert.cbp.dhs.gov:31531), keystore path, retention, Azure posture. Every answer wired into the architecture before this meeting. Below: what you said ↔ where it lives in our code today.
| What you said | Where it lives now | Status |
|---|---|---|
| MQ Series via QGC1 · cbpgw-trade-cert.cbp.dhs.gov:31531 · channel CBITAMERICA | transport/mq_client.py · QGC1 wired, awaiting keystore handoff | stub → 4-6h |
| HTTPS preferred over MQ (newer, simpler to onboard) | transport/https_client.py · dual-transport abstraction · CBIT Swagger v0.1 in hand | scaffolded |
| mTLS with Keystore + CCDT | Keystore loader scaffolded · CCDT env-var path | awaits cert |
| Type 1 · Type 11 · T-1 as priority clearances (eBond is ocean-freight V2) | entry_summary/ · type_01 · type_11 · in_bond QP/WP · all byte-exact | done · 326 tests |
| Option B — we host the runtime | Docker on Hetzner · Azure-replication one config-port away | live |
| Azure-side: unclear, to confirm | Killer #2 tracked · stack already containerized | flagged |
| 99.9% SLA target | Monitoring scaffold + status page on roadmap phase 1 | phase 1 |
| 7-year audit-log retention · test-data only (GDPR + Damon's data-protection agreements) | audit/ · append-only SQLite + JSONL · signed + timestamped · 7y window | done |
| Paper PoA upstream from us | Not blocking filing · handled upstream by broker of record | clear |
Checklist complete. Three operational unknowns remain: filer-code timeline, cert-handoff channel, Azure-vs-Hetzner compliance requirement. Everything else is us executing.
JSON in → byte-exact CATAIR records out → mock CBP MRN. Running now at catair.atwenture.com/simulator?entry_type=01|11|t-1. Paste a JSON payload, hit submit, watch the 80-byte positional records render line-by-line. No vaporware.
MRN · MOCK-01-20260419-0001 · ACCEPTED
MRN · MOCK-11-20260419-0042 · ACCEPTED
MRN · MOCK-T1-20260419-0007 · IN_TRANSIT
Verifiable today: /simulator — live transformer. /process — component-flow map with reject-loop + 7y-retention timeline. /roadmap — five jurisdictions on a premium world map.
Competitors can call Claude too. They can't replicate ten-entity ontology × 100 CBP PDFs × 18,691 typed edges — plus a live byte-exact transformer (/simulator), a component-flow map (/process), and a cross-jurisdiction concept layer spanning US, UK, EU, Mexico (+ China exploratory).
115 modules · 1,897 records · 4,604 fields · 836 code tables · 18,691 typed edges. A structured asset — not a prompt hack.
Verify-Pass found >10,000 UKIMS-authorised traders (vs. ~3,000 in 2024). Green Lane is now the dominant NI flow — V1 scope is H1/H7/I1 + UKIMS, not the full 100–120 doc corpus.
EUCDM 7.0 + WCO DM v4.1 alignment makes the payload mechanically mappable. CBAM (live 2026-01) integrated as cross-cut module from day one.
Live transformation at /simulator. JSON in, byte-exact CATAIR out, mock MRN back. Type 1 · Type 11 · T-1. Verifiable in 10 seconds — not in a sales cycle.
Full flow-map at /process. Bi-directional flows, reject-loop semantics, 7-year-retention timeline. What Mark wanted to see. Rendered, not pitched.
Schema is sticky. CBP revises quarterly — we compound, competitors restart. Every filing pipeline depends on our Pydantic naming, validators, error taxonomy.
Honest framing: dev-time per jurisdiction is days to weeks — the calendar is gated by certification cycles, HMRC approval, CBP sandbox-to-prod promotion, and customer onboarding. If all three killers fire, timeline × 1.6 — still under six months.
This project was impossible 18 months ago. Three pieces landed at once — each necessary, none individually sufficient.
Multimodal OCR preserves CATAIR record layouts byte-exact. Positions, lengths, and codes survive the scan. Legacy PDF-scrapers could not do this.
Million-token context + strict system-prompt enforcement makes "cite or refuse" reliable at production volume. Hallucination on positions = rejection by CBP.
The knowledge base exposes tools; any capable agent becomes a filer-dev overnight. We sell knowledge, not compute.
Checklist: 14/14 answered. Code: 326 tests green across Type 1 · Type 11 · T-1. Live: /simulator + /process + /roadmap. Math: $0.12 × 350k × 10 companies = $5M+ ARR. Three operational answers move us from kickoff to first real sandbox submission.
If reactivatable: 7 days to first sandbox. If new-apply: placeholder mode keeps us moving in parallel. We need the path.
mTLS keystore + CCDT need a secure channel. Whatever your side prefers, we adopt. 1-2h dev once it lands.
Stack is containerized — Azure replication is config-port, not rewrite. But we need the answer to plan phase 0 vs. phase 0 + 2 weeks.
Answer the three — we commit to a first sandbox submission (Type 1 or T-1) within 5-7 working days, conditional on cert-handoff and filer-code arrival.
Live simulator · catair.atwenture.com/simulator
Component flow-map · catair.atwenture.com/process
Full roadmap · catair.atwenture.com/roadmap
Contact · j.wenk@mobilityacademy.de