Release the grid without releasing the source
For release cells and coalition operations that today choose between withholding a whole report and retyping one grid reference into a chat window under time pressure.
- Users
- Release cells, liaison officers, coalition HQs
- Problem
- Whole-document decisions at a boundary box
- Products
- Quorum Lace / Release, Sigilcore
The boundary is a box, and the box is a chokepoint
Crores and years
Accredited cross-domain guards are expensive, slow to accredit and become a single point of compromise.
Chokepoint at H-hour
Every release decision passes through one place, at exactly the moment it is busiest.
All or nothing
Whole-document decisions mean reports are withheld, and the real solution becomes a person retyping, slowly and with errors.
The policy travels with every field
- Per-field policy. AND, OR and k-of-n over clearance attributes, matching how release authority works on a staff.
- One artifact, many truths. A coalition cell, brigade HQ and a logistics node open the same bytes and see different, correct subsets.
- Invisible when presence is the secret. A HUMINT field can be indistinguishable from padding, not merely redacted.
- National authority stays national. The attribute authority is held by the customer.
Stated plainly
This construction suits a single national authority and is wrong for genuine multi-authority federation. Partners hold ciphertext of fields they cannot open, so long-horizon fields may need to be omitted from partner copies. And accreditors will rightly ask what replaces a guard's content inspection and one-way flow enforcement. We expect those questions in a pilot, after national user trials.
The binding constraint is a signals regiment willing to run a trial.
Not capital. If you can open that door, or want the architecture note and the runnable prototype to take apart yourself, we would like to hear from you.