The in-flow operating layer
Execution Integrity Infrastructure
Pulse is designed to sit where consequential execution can be evaluated, observed, and, when approved, governed. It does not need to replace the agent, workflow, orchestration layer, or system of record. It adds an independent execution check at the boundary where an action becomes real.
Why the boundary matters
Most systems govern decisions. Pulse governs the commit.
Once execution leaves the original decision, it can pass through APIs, retries, queues, vendors, asynchronous jobs, scripts, and agents. The system may keep performing valid work while the final consequence drifts outside the original authority.
Observe without changing production.
Evaluate actual events and preserve what Pulse would have allowed, escalated, or blocked.
Control before the consequence.
At an approved execution boundary, the same criteria can return ALLOW, ESCALATE, or BLOCK before commit.
Preserve the decision context.
Bind the approved rule/version, authority, inputs, provenance, result, exception path, and committed outcome for replay.
Where Pulse sits
Independent of the system that made the recommendation.
The integration contract must define the event, required fields, provenance, trust boundaries, latency, failure behavior, and how ALLOW, ESCALATE, and BLOCK are handled. Pulse should not claim runtime governance where no definable execution boundary exists.
Runtime outcomes
ALLOW, ESCALATE, and BLOCK are governance outcomes, not generic risk scores.
Required criteria are satisfied.
The supplied context supports execution under the approved standard and authority.
Higher authority or human judgment is required.
A defined condition routes the event into an approved review or exception path.
A mandatory condition failed.
Required authority, evidence, field, version, validation, or governed condition is missing or invalid.
For governed classes, fail-closed behavior must be explicitly designed, documented, and tested. It is not a universal default for every enterprise action.
Evidence at the moment of control
The event should be sufficient for reperformance.
What Pulse determined
Rule/version, authority, required facts and provenance, ALLOW/ESCALATE/BLOCK, overrides, exceptions, and timing.
What the world actually did
The committed action or final state recorded by the operational system, linked back to the same event and evidence population.