ROE, authorities, approval chains, and lifecycle gates are stored data the fabric enforces. Every governed action writes an immutable record, so what was decided, and why it was permitted, is reconstructable.
F2T2EA runs as a gated state machine. Authority is re-validated at the moment of engagement; the two-person rule is a queue, not a promise.
A node that can write its own authority has none. Command authority resolves against a grant signed by a root in your custody, read fresh on every act.
Engagement authority is a named grant in the command relationship, never inferred from a sensor's willingness to share. A shooter without the grant is refused by name.
A signature proves identity. A voucher scopes a relationship. Neither confers. One thing does: a grant attribute on a certificate, consulted at issuance, at lookup, and at every act.
Both nodes record the relationship. Signed vouchers carry its grants one by one: engage, task, re-task, cross-attach, logistics, administration. A grant nobody conferred does not exist.
An administrative delegation can carry logistics and administrative tasking. It can never carry an operational act. No relationship type implies a grant.
An ROE template registry with mission assignment.
Legal and command authorities bounding mission execution.
Configurable multi-step approval workflows, per subject type.
An asynchronous co-sign queue through the unified task queue.
Compartment stamping on missions, entities, playbooks, and workflows.
Envelopes and release decisions for counter-UAS and other time-sensitive engagements.
Audit entries for every authentication, role, and administrative event.
Bring us the mission the seams keep breaking, and we'll show you where the substrate holds. Submissions are validated server-side and routed through INSTOPCO's operational channel.