Connect the decision to the designated person.
The institution defines which human authority is required. Presence Key helps establish that the expected person participates at the specified boundary.
The physical interface for establishing the human behind a consequential authority.
Presence Key is designed for moments where a digital credential alone is not a sufficient basis for a consequential decision.
The institution defines which human authority is required. Presence Key helps establish that the expected person participates at the specified boundary.
Presence does not need to sit in every interaction. Policy calls for it at selected access, approval, recovery or control events.
The result is constrained to its purpose. It does not expose protected physical data or turn the Key into a general-purpose identity database.
The public sequence explains the control boundary. Protected construction and verification implementation remain confidential.
Specify the person, action, context and assurance policy.
Govern the connection between the expected person and the institutional record.
The designated human presents the Key at the relevant decision boundary.
An authorized point evaluates the expected condition and returns a bounded signal.
The receiving system permits, denies, records or escalates.
The images below depict prototype and design studies showing potential ways Presence Key may be worn, carried or presented. Final deployment form depends on assurance level, validation and operating environment.


Presence Key is most relevant where accepting the wrong human authority produces material, operational or public consequence.
Require the expected accountable officer before treasury release, mandate change, privileged recovery or another unusually consequential action proceeds.
Create an explicit physical checkpoint before an intelligent system executes a high-impact external action under delegated authority.
Add physical participation to selected access, maintenance, administrative or emergency-recovery boundaries.
Strengthen the connection between a designated person, the relevant operating context and a consequential instruction.
Presence Key supports a defined verification question. It does not decide whether an action is lawful, appropriate or safe; it does not replace institutional identity, authorization or accountability systems.
Whether the expected physical participation condition was satisfied at the defined boundary.
Who holds authority, which action is permitted, what exceptions apply and how the event is recorded.
Architecture, construction, validation methods, performance characteristics and adversarial evaluation.
Presence Key is intended to deliver bounded verification outputs to the infrastructure institutions already use.
IAM, physical access and privileged-administration policy.
Approval, recovery, mandate and settlement controls.
Human-in-the-loop and human-on-the-loop execution gates.
Maintenance, handoff, exception and mission workflows.
4SI works with selected institutions to map the authority boundary, threat model, integration path and limits before deployment.