A consequential action reaches a defined threshold.
Policy requests the designated person—not merely a valid account—before the action may continue.
InputA pending action
PolicyExpected human required
OwnerThe institution
Presence / 01 · Human authority
Presence
Presence
Key.
Confirm the expected person before money moves, access is granted or a consequential system acts.
Final form may differ
One physical check.
One bounded result.
The institution defines the authority. Presence Key establishes whether the expected human participates at that specific decision boundary.
The expected human brings the Key to the boundary.
Physical participation is requested only where higher assurance matters. The public interface reveals no protected construction or verification data.
ConditionPhysical presence
ContextOne defined event
DataPurpose-limited
An authorized point evaluates the expected condition.
The protected mechanism remains confidential. The receiving system gets only the bounded result required by policy.
QuestionExpected person present?
ResultSatisfied · not satisfied
ProtectedCore implementation
Permit, deny, record or escalate.
Presence Key informs the decision. The institution retains authority over identity, policy, exceptions and the final action.
SignalBounded verification
ActionInstitutional policy
RecordMinimum evidence
The same boundary.
Different consequences.
Choose a scenario to see how Key fits into an existing institutional workflow without replacing the system that owns the decision.
AI execution gate
Human authority before an agent acts.
An intelligent system reaches a high-impact external action. Key adds an explicit physical checkpoint for the accountable human.
- Before
- Agent requests authority
- Presence
- Expected person participates
- After
- Policy permits or escalates
Exceptional transaction
The accountable officer before release.
A treasury or mandate event crosses a defined threshold. Key establishes physical participation before the existing financial system decides.
- Before
- Exceptional transaction pending
- Presence
- Designated officer participates
- After
- Release, deny or review
Privileged control
The expected human before sensitive access.
Selected administrative, facility or recovery paths request Key before the existing access system grants or escalates the event.
- Before
- Sensitive access requested
- Presence
- Expected operator participates
- After
- Grant, deny or escalate
Prototype studies. Moving toward controlled pilot engagements.
The images show potential forms, not announced production hardware. Timing, final form and availability remain subject to technical, security and deployment validation.
The decision boundaryPresence informs.
Presence informs.
Institutions decide.
Key answers one narrow physical question. It does not decide whether an action is lawful, appropriate or safe.
Whether the expected physical participation condition was satisfied at the defined boundary.
Identity, authority, policy, exceptions, accountability and the final action.
Construction, architecture, validation methods, performance and adversarial evaluation.
Start with the action that
cannot accept the wrong person.
4SI works with selected institutions to map the authority boundary, threat model, integration path and explicit limits before deployment.
Presence / 01 · Human authority
Presence
Key.
The physical interface for establishing the human behind a consequential authority.
01 / FROM IDENTITY TO AUTHORITY
Authentication can identify an operator.
Authority is a separate question.
A physical checkpoint for
human participation.
Presence Key is designed for moments where a digital credential alone is not a sufficient basis for a consequential decision.
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.
Verify only where higher assurance matters.
Presence does not need to sit in every interaction. Policy calls for it at selected access, approval, recovery or control events.
Return the minimum signal the decision requires.
The result is constrained to its purpose. It does not expose protected physical data or turn the Key into a general-purpose identity database.
From institutional policy
to accountable action.
The public sequence explains the control boundary. Protected construction and verification implementation remain confidential.
Set the authority.
Specify the person, action, context and assurance policy.
Establish the relationship.
Govern the connection between the expected person and the institutional record.
Bring physical presence.
The designated human presents the Key at the relevant decision boundary.
Return a narrow result.
An authorized point evaluates the expected condition and returns a bounded signal.
Let policy act.
The receiving system permits, denies, records or escalates.
Designed to be present.
Not performative.
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.
One boundary.
Different consequences.
Presence Key is most relevant where accepting the wrong human authority produces material, operational or public consequence.
Exceptional transactions.
Require the expected accountable officer before treasury release, mandate change, privileged recovery or another unusually consequential action proceeds.
Human authority before autonomous action.
Create an explicit physical checkpoint before an intelligent system executes a high-impact external action under delegated authority.
Sensitive environments and control paths.
Add physical participation to selected access, maintenance, administrative or emergency-recovery boundaries.
Accountable command and handoff.
Strengthen the connection between a designated person, the relevant operating context and a consequential instruction.
06 / EXPLICIT BOUNDARIESStrong claims require
Strong claims require
narrow claims.
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.
PRESENCE KEY CAN INFORM
Whether the expected physical participation condition was satisfied at the defined boundary.
THE INSTITUTION STILL DECIDES
Who holds authority, which action is permitted, what exceptions apply and how the event is recorded.
CONTROLLED UNDER NDA
Architecture, construction, validation methods, performance characteristics and adversarial evaluation.
Inform existing systems.
Do not create another silo.
Presence Key is intended to deliver bounded verification outputs to the infrastructure institutions already use.
Identity and access
IAM, physical access and privileged-administration policy.
Transactions
Approval, recovery, mandate and settlement controls.
AI control
Human-in-the-loop and human-on-the-loop execution gates.
Operations
Maintenance, handoff, exception and mission workflows.
Start with the decision
that cannot accept the wrong person.
4SI works with selected institutions to map the authority boundary, threat model, integration path and limits before deployment.