Between AI access and enterprise execution.
TracePoint evaluates the consequential business decision an identified actor proposes, then returns an action bound disposition and connected record. It complements identity, agent runtime, policy, and system of record platforms.
A distinct control boundary, designed to integrate.
IAM controls access. Guardrails constrain behavior. Observability records activity. TracePoint determines whether a specific business action has authority to proceed.
Integration boundary
Integration boundary
ALLOW, DENY, or ESCALATE before execution
Integration boundary
Integration boundary
Horizontal architecture. Vertical proof. Deployment-specific enforcement.
The layers separate reusable decision contracts from operational change policy and the connector that makes authorization enforceable.
Identity · Principal · Authority · Action · Policy · Disposition · Authorization · Receipt
Service · environment · change type · purpose · destination · playbook · scope · rollback
Requires a valid, matching, active, unconsumed Decision Authorization before applying the local change.
One control contract, independent of the business domain.
Core contracts describe identity, authority, action, policy, disposition, authorization, and evidence. A Control Pack adds constraints for a specific enterprise action.
No valid authorization, no execution inside the current connector.
The connector verifies the server controlled authorization identifier, exact action fingerprint, issuer, audience, target, operation, validity, revocation, and consumption state before recording the outcome and returning an Action Receipt.
Proposes an identified action and idempotency key.
Validates input and loads pinned authority and policy.
Returns ALLOW, DENY, or ESCALATE with reason codes.
A named owner may approve or deny an escalated decision.
Binds one authorization to the exact proposed action.
Rejects missing, expired, revoked, consumed, or mismatched authorization.
Connects the resulting state and recovery context.
An external system inherits fail-closed behavior only when it is configured to require valid TracePoint authorization and its connector passes conformance testing. Universal fail-closed behavior is not claimed.
Insert into the stack without pretending to own it.
Identity provider
TracePoint consumes identity references. It does not establish enterprise identities today.
Agent runtime
The runtime proposes actions and supplies context. TracePoint evaluates the decision boundary.
System of record
The target system executes and owns business state. A connector enforces authorization.
Policy and oversight stack
TracePoint can apply relevant policy at decision time without replacing broader oversight systems.
Current local behavior separated from deployment requirements.
The local operational change connector rejects invalid authorization states. External connectors require their own failure, reconciliation, bypass, and recovery verification.
No authorization is issued when evaluation cannot complete. The local connector remains blocked.
An expired authorization is rejected before a local execution record is created.
Revoked authority prevents evaluation; revoked authorization prevents later execution.
A consumed authorization returns AUTHORIZATION_ALREADY_CONSUMED.
A repeated request key returns its original Decision Record without creating another execution.
A changed scope, destination, purpose, playbook, or rollback plan fails action-fingerprint verification.
Review cannot restore authority that expired or was revoked.
The Decision Record retains the exact authority and policy versions evaluated.
External receipt delivery and reconciliation remain connector requirements.
External connectors need idempotency, uncertainty handling, and reconciliation.
The current receipt links a bounded local reversal to the original decision.
Enforcement exists only where the target system requires valid TracePoint authorization.
Server controlled action binding today. Portable verification later.
TracePoint currently creates a stable server controlled authorization fingerprint that binds the approved decision to its execution context. Authorization state is held in isolated process memory. The product does not sign portable artifacts and does not claim cryptographic non repudiation.
Decision contract
Resolve disposition, pin authority and policy versions, and bind one authorization to the exact action.
Identity and access
The enterprise supplies authenticated identities, IAM, SSO, RBAC, separation of duties, and tenant boundaries.
Enforcement and recovery
The target owner makes authorization mandatory and owns authentication, idempotency, receipts, reconciliation, and bypass monitoring.
Portable verification
Signatures, key management, policy digests, cross-system verification, and revocation propagation remain strategic architecture.