Directions
Each study answers part of one of these questions.
Can independent parties act on verifiable commitments instead of requests?
A principal signs what is allowed, a source signs what is true, and one executor makes the effect and answers with a signed outcome. Can anyone holding the records check the action, and what does that add over ordinary integration, a shared topic or a hub?
4 published, 3 re-checked
Who allowed this action, and within what limits?
Grants, approvals and shared limits: can a receiver check that an action falls within a chain of grants back to a principal, and what can a principal not state in a form any node can check?
3 published, 3 re-checked
What does an action rest on?
Every object and field an action uses should come from something its source stated for this principal. What does that rule prevent, what lawful work does it refuse, and should an action have to cite a current requirement?
10 published, 4 re-checked
One effect per intent, and an honest answer
Duplicated delivery is normal in queues and agent teams. When every effect passes one executor that records before it acts, does a duplicate still become a second effect, and what does the requester learn when the answer is lost?
11 published, 7 re-checked; 2 planned
When the basis of an action is withdrawn
A requirement is amended, a grant is revoked, a fact goes stale. Which dependent actions are refused before their effect, which become findings after it, and what do simpler checks already cover?
2 published, 2 re-checked
What the guard costs, and how we measure
Overhead and data footprint of the guard that sits on the delegate's side, checks of its declarations, and the places where our own instruments, oracles and records misled us.
14 published, 3 re-checked