Check Action: the engine under Check Write™
Called-gate honesty: production paths must invoke Check Write™. Underneath, Check Action answers: is this agent allowed to perform this specific action, on this specific target, right now, in this context?
Check Write™ is the flagship customer path for mutations of systems of record. Check Action is the underlying authorization engine. Check Write™ routes through Check Action, then applies write-specific policy.
Decision
Every Check Action returns allow, pause, or block, with decision_id, reason_codes, risk_score, and structured checks.
Evaluation pipeline
- Identity — registered agent, optional JWT/JWKS Write Intent Envelope, workflow attestation
- Authority — short-lived scoped authority and approval freshness at action time
- Intent — original vs current goal vs requested action (drift signals)
- Context — environment and upstream injection/risk signals
- Policy — hard rules for system, object, operation, fields
- Delegation — downstream agents cannot expand upstream scope
- Blast radius — volume limits per run / per minute
- Risk — normalized score; hard policies override scoring
Action Request schema
Normalized metadata object (action_request.v1). Default is metadata-only. Schema: /schema/action-request/v1/action-request.v1.json.
API
| Call | Role |
|---|---|
check_write | Customer write wedge. Internally calls Check Action, then write policy. |
check_action | Direct Action Request evaluation (integrators / non-write actions). Body: action=check_action plus Action Request fields; nest the mutation as requested_action (or send full object as action_request) so the API verb does not collide with the action object. |
issue_scoped_authority / revoke_scoped_authority | Short-lived workflow authority. |
list_security_events | Agent security event stream (for SIEM handoff later). |
Typical response shape: decision (allow / pause / block), risk_score, reason_codes, decision_id, message, structured checks.
What we do not claim
- Perfect prompt-injection detection. Upstream signals are inputs; the gate is the final control.
- Silent MITM of Salesforce or any SoR. Called gate only.
- SIEM replacement. TekCapitol emits high-value agent security events; your SOC consumes them.
Also in Docs
- Check Write™ design · emission path and Trace checks
- Write Intent schema · signed envelope
- Security & data handling · JWT/JWKS and registries