Presence boundary design
Map one consequential workflow, its accountable principal, the physical claim and the action that follows.
4SI PRESENCE / EVIDENCE & DEPLOYMENT
Evidence
before scale.
Presence is evaluated at a real decision boundary: what must be physically verified, which action follows and what evidence an institution needs before it can proceed responsibly.
Start a Presence evaluation ↗Clear about what exists.
Clear about what comes next.
Key and Layer prototypes
Physical forms, integration assumptions and evidence models are moving through controlled technical and institutional review.
Presence Home
A common institutional workspace for relationships between verified people, objects, organizations and permitted actions.
A physical control primitive,
not another connected account.
The public boundary is intentionally precise. Protected mechanism details are not published here.
- Network connectivity
- None. The Key does not connect to the internet, Wi-Fi, cellular networks or Bluetooth.
- Operating life
- At least six months. The sealed unit is designed to be replaced rather than recharged.
- Verification result
- Purpose-limited. Presence answers the defined physical question; it does not become a general identity dossier.
- Decision authority
- Remains with the partner. The integrating institution retains policy, access and final-action control.
One boundary.
Four accountable steps.
- 01BOUNDARY MAP
Map the boundary
Define the person, object or authority claim, the consequential action and the current failure path.
- 02EVALUATION PLAN
Design the evaluation
Set the threat model, success criteria, exception path, data limits and responsible owner before testing begins.
- 03CONTROLLED RECORD
Run under control
Test the verification moment in a bounded environment with explicit stop conditions and retained evidence.
- 04DECISION MEMO
Review, scale or stop
Compare outcomes against the agreed criteria. Scale only where the evidence and operating model support it.
WHAT AN EVALUATION PRODUCES
A decision package,
A decision package,
not a demo.
Authority boundary map
Threat and failure model
Integration contract
Exception and fallback path
Evidence record
Scale-or-stop decision
Put the claim, action
and evidence on the table.
Describe one consequential workflow. 4SI will assess whether Presence is the right control boundary and what a responsible evaluation would require.