Randomized routing to judicial panels. Identity-blind decision tier. Adversarial argument cryptographically required for access.
Filed · Patent pending
ABT-W · judicial authorization walkthrough
A federal wiretap nobody can fast-track
A concrete authorization request showing randomized cryptographic routing of judges, adversarial argument as cryptographic precondition to the decision tier, and target identity withheld from the deciding panel.
Variant of ABT · US Provisional Patent 64/056,353 · Filed May 4, 2026
The judges decide the law. They never see who they are deciding about.
AUSA Diaz applies for a wiretap on subject 3kf2
The application is constructed at the prosecutor's endpoint. Target identifying information is encrypted with one tier key. Legal merit content is encrypted with another. The two will travel together but be unsealed separately, by different parties.
AUSA Diaz · prosecutor endpoint
Constructs authorization request
target: subj_3kf2
offense: trafficking conspiracy
probable cause: declaration ¶12–¶47
intercept scope: 90 days, mobile #1
↓ encrypts at endpoint
operational_prosecutor · full record
decision_judicial_panel · target redacted
encrypted application req_8a3c
Process integrity guardian
Receives request, holds for routing
verifies Diaz Ed25519 sig
logs req_8a3c → hash chain
does not decrypt either tier
The same envelope contains two tier-specific projections of the same case. The operational tier holds the full record — target identity, full probable cause, every detail Diaz wrote. The decision tier holds a version of the case with the target identifier authored out before encryption. Same case, two redactions, locked under two different tier keys.
at endpointoperational_prosecutor can be decrypted by Diaz's office, defense counsel once assigned, and the process integrity guardian for routing purposes. decision_judicial_panel can be decrypted only by judges, once assigned, and contains the case with the target identifier removed before encryption.
The registry rolls cryptographic dice to assign judges
The process integrity guardian uses a cryptographically secure random draw against the registered judicial pool. Diaz cannot choose. Defense cannot choose. The draw itself is verifiable later by any registered oversight authority.
draw_seed = HMAC-SHA256(registry_key, req_8a3c) → 0x4f3a91ce82bd...
draw against pool of 47 registered Article III judges
selected: positions [12, 28, 41]
Judge Allen
pool #1
Judge Brennan
pool #2
Judge Carlsen
pool #3
…
pool #4 – #11
Judge Chen
pool #12 · selected
…
pool #13 – #27
Judge Reyes
pool #28 · selected
…
pool #29 – #40
Judge Park
pool #41 · selected
…
pool #42 – #47
Selection is cryptographically committed at draw time. Chen, Reyes, and Park were selected by the deterministic draw against registry_key and req_8a3c. Any oversight authority registered for this tier can reproduce the draw later from the registry's hash-chained log and confirm that selection was not steered.
The registry does the routing. It does not decide. It does not see the case facts — it sees the request identifier and the routing metadata. Diaz, the FBI agent who applied, the President — none of them can substitute Judge Karpinski for Judge Park.
Defense pool member Okonkwo is drawn — must argue before the panel can decide
A second randomized draw assigns the adversarial-argument role to a member of the registered defense pool. The decision tier cannot be constructed for the panel until a signed defense argument has been received at the registry.
Process integrity guardian
Routes to defense pool
second draw against pool of 23
selected: pool #14 · Okonkwo
forwards operational_prosecutor tier
case package for adversarial review
Counsel Okonkwo · defense pool
Constructs adversarial argument
reviews probable cause
drafts objections, alternatives
↓ signs with defense pool key
arg_okonkwo_req8a3c
signed adversarial argument
Process integrity guardian
Verifies, gates decision tier
verifies Okonkwo sig
extends hash chain
unlocks decision tier construction
The defense signature is a cryptographic precondition. The registry will not finalize the decision_judicial_panel tier for transmission to Chen, Reyes, and Park until a valid defense argument has been signed and witnessed. Without it, the panel never sees the case at all.
This is not a "due process" claim wrapped in code. It is structural: the cryptographic envelope encoded as a decision tier accessible to the panel does not exist as decryptable ciphertext until the registry has received and verified the defense argument signature. Skip the defense, and there is no panel envelope to read.
The panel sees the case — without seeing the suspect
Chen, Reyes, and Park receive the decision-tier projection. The target identifier was authored out at encryption time. They have probable cause, prosecution argument, defense argument, statute, and intercept scope. They do not have, and cannot derive, who the application is about.
decision_judicial_panel tier — what Chen, Reyes, Park can see
target_identifier— not included in this projection —
target_address— not included in this projection —
target_employer— not included in this projection —
The judges decide on legal merit alone. The constitutional question — does this probable cause support intercept of this scope under this statute — is the only question they are equipped to answer. The political question — is this the kind of person we like — was never put to them.
The judges' tier-specific keys can decrypt the decision tier and nothing else. They cannot decrypt the operational tier, where the target identity lives. They cannot decrypt other oversight tiers. The cryptographic boundary at the cipher level enforces what discovery rules attempt to enforce by policy in the existing system.
The same architectural pattern applies to regulatory adjudication, professional disciplinary proceedings, and any other authorization in which legal merit ought to be decided independent of who the decision is about.
Three judges decide independently. Two say yes. The authorization issues.
Each judge decrypts the decision tier on their own endpoint, decides, and signs their decision with their persistent tier key. The registry computes majority. The authorization is cryptographically signed and witnessed.
Judge Chen
Decision returned
decrypts decision tier
reviews PC and arguments
decision: grant
signed: dec_chen_8a3c
Judge Reyes
Decision returned
decrypts decision tier
reviews PC and arguments
decision: grant
signed: dec_reyes_8a3c
Judge Park
Decision returned
decrypts decision tier
reviews PC and arguments
decision: deny
signed: dec_park_8a3c
3 signed decisions
Process integrity guardian
Computes majority
2 grant · 1 deny
authorization: issued
witnessed at log_8a3c
Authorization auth_8a3c · issued
request_idreq_8a3c
outcomegranted by 2-judge majority
panelChen, Reyes, Park
defense_argument_presentyes · Okonkwo, signed
scopemobile #1, 90 days, criminal communications
target_identifier— still sealed at this layer —
registry_signaturewitnessed, hash-chained, public
Park's dissent is part of the permanent record. Even when the majority rules to grant, the dissenting decision is signed, witnessed, and entered into the hash-chained log. Future review — by oversight bodies, by subsequent panels, by the bar — can read the dissent without seeing the target.
The executing agent rebinds the target to the authorization — once
The authorization was granted on legal merit alone. To execute it, the FBI field officer combines the registry-witnessed authorization with the operational tier they decrypt at their own endpoint. Identity and authorization come together for the first time at execution, under a fresh registry countersignature.
SA Brooks · executing officer
Combines authorization with target
receives auth_8a3c
decrypts operational_prosecutor
→ subj_3kf2 = Hiroshi Tanaka
→ mobile #1 = +1-415-555-0172
↓ signs execution event
exec_brooks_8a3c
execution event
Process integrity guardian
Countersigns, hash-chain extends
verifies Brooks credentials
links auth_8a3c → exec_brooks_8a3c
logs target binding event
The target's identity met the authorization for the first time at execution, in the field, under a registry countersignature. Chen, Reyes, and Park never knew it was Tanaka. They never can — their tier keys cannot decrypt the operational tier. If the same authorization were ever applied to a different target, the registry would require a fresh execution event, fresh countersignature, fresh hash-chain entry, all publicly auditable.
The 90-day window begins at the execution event. When it expires, the operational tier remains, but the authorization tier's per-event keys cease to be released. Continued execution requires a new application. The structural ratchet — auth must precede execution must precede intercept, each cryptographically witnessed, each non-reversible — is the architecture.
Variant family note. The same mechanism — randomized routing, identity-blind decision tier, adversarial-gating, multi-decision-maker majority — applies to regulatory adjudication, professional disciplinary proceedings, classified committee decisions, treaty ratification panels, and any other authorization where the legal question and the political question must be separated.