A valid instruction.
An account, an amount and a destination.
Identity & policy4SI for institutions
Digital decisions.
Physical evidence.
A valid instruction does not establish who or what is physically behind it. 4SI is developing an additional evidence layer for consequential actions.
In development. Prototype validation is not production qualification.
The institutional boundary
An additional check.
Not a new authority.
Your identity, policy, approval and audit systems retain their responsibilities.
The expected person.
Physical participation at the point of consequence.
Physical evidencePermit. Deny.
Escalate.
Your policy governs the result. Your institution owns the decision.
Decision & recordIllustrative workflow logic. Not a live verification or evidence of a deployed integration.
What the control contract needs to define +
The claim: what must be physically established, for whom, and at which action boundary.
The result: how your system receives, interprets and records evidence, including missing or uncertain evidence.
The owner: who defines policy, accepts the result and governs failure, revocation and escalation.
Which physical question does your workflow need to answer?
The person
Is the accountable person physically participating in this action?
The object
Is the physical object consistent with the claim being made about it?
The boundary
Is the action taking place under the conditions your institution requires?
The making of trust
Why physical evidence matters.
The making of trustTrust had
Trust had
a texture.
From material knowledge to digital decisions.
Continue to the architectureConnect the digital decision to the physical question.
Explore the three anchorsAbout this illustrated story
An illustrative journey through industrial trust, not a universal chronology. The final scenes describe 4SI’s development direction; product scopes and maturity differ. Object provenance is a separate evaluation area. Institutions retain permissions, operating safeguards and final authority. Current product status follows below.
The Presence architecture
Three anchors.
Different jobs.
Status, without ambiguity
What exists.
What comes next.
A clear distinction between evaluation work, prototype validation and long-term direction.
Presence boundary design
Define the physical claim, the institutional owner and the decision boundary.
Key and Layer prototypes
Prototype evidence is not equivalent to qualified hardware or a production installation.
Presence Home
Governed environments remain a strategic direction, not a current deployment promise.
Application fields
Where trust
has consequences.
Start with one workflow, not a promise to replace your infrastructure.
Controlled evaluation
A decision package.
Not a demonstration.
A bounded evaluation should produce evidence your institution can review.
Define
Name the workflow, accountable owner and physical claim.
Bound
Set the environment, threat model and acceptance criteria.
Evaluate
Observe behavior, failure paths and the resulting evidence.
Decide
Scale, revise or stop against the agreed boundary.
Your reviewable outputs
- Authority boundary map
- Threat and failure model
- Integration contract
- Observed evidence record
- Scale, revise or stop recommendation
4SI Intelligence / Public beta
Read the signals.
Open the sources.
Follow the evidence behind physical-trust risks. Separate reported incidents, analytical scenarios and the limits of what is known.
Explore IntelligenceRisk
Presence Risk Index
EvidenceEvidence Library
ScenariosScenario Lab
Links open the current public Intelligence platform.Long-term thinking
Build the evidence.
Keep the horizon.
Founding Institution Program
Bring one
real question.
Discuss your workflow
Explore the Founding Institution Program A named sponsor.
A defined physical claim.
Explicit acceptance criteria.