Decision contract
A stable ALLOW, BLOCK, or ESCALATE response with release state, route, reason codes, trace identity, and proof references.
Joint delivery boundary
Implementation partners build the customer route; OntoGuard proves the governed decision
Systems integrators and AI implementation partners own the customer environment, workflow, identity, endpoint integration, operational change, review ownership, and deployment topology. OntoGuard supplies Decision Authorization, semantic admissibility, evidence packaging, review-routing requirements, no-bind proof, and route-evidence design.
Responsibility boundary
| Partner provides | OntoGuard provides |
|---|---|
| Customer environment | Authorization decision |
| Endpoint integration | Evidence and reason codes |
| Identity and access | Decision packet |
| Operational workflow | No-bind and route proof |
| Customer review roles | Reviewer-routing requirements |
| Production enforcement | Proof of the governed decision |
This division prevents a controlled product proof from being mistaken for customer-specific endpoint enforcement.
What OntoGuard contributes to the implementation
Semantic admissibility
BM25 and semantic retrieval can discover candidate evidence; ontology grounding and authority checks determine whether it is relevant to the proposed movement. Retrieval rank alone never authorizes release.
Evidence packaging
Buyer-readable and machine-readable artifacts preserve decision state, evidence posture, uncertainty, route maturity, and no-bind status.
Review routing
The packet states which reviewer role, authority, evidence, and outcome closure are still required.
Route-evidence design
Control points, token checks, refused operations, replay records, fail-closed tests, and downstream closure are made explicit.
Improvement signals
Approved and corrected outcomes may become review-gated candidates without live model-weight mutation in the authorization path.
Sanitized implementation example
An AI-generated workflow movement is escalated before endpoint commit
- Proposed movement
- Send an AI-generated high-consequence recommendation to a customer workflow endpoint.
- OntoGuard decision
- ◆ ESCALATE
- Partner control
- The SI-configured endpoint refuses commit without the required authorization state or reviewer closure.
- Human closure
- An authorized reviewer approves, revises, rejects, or requests evidence; the outcome is written back to the governed record.
- Production evidence
- Route registration, enforcement test, bypass attempt, fail-closed result, replay, and outcome closure.
Pilot deliverables
Route inventory
Identify proposed movements, downstream systems, actors, consequence classes, and control points.
Integration design
Map the Decision Authorization contract to identity, workflow, endpoint, and reviewer systems.
Enforcement tests
Run fail-closed, bypass-attempt, authorization-token, and replay tests on the selected corridor.
Review workflow
Define reviewer role, qualification, delegated authority, decision options, and outcome closure.
Proof review
Inspect packet parity across PDF, JSON, receipt, manifest, trace, and route evidence.
Boundary statement
Separate controlled proof from what the customer integration has actually established in production.
Commercial paths
Partners can begin with a Demo Proof Pack or selected workflow assessment, then move to a Decision Authorization pilot, embedded proof layer, co-sell, OEM, or strategic licensing discussion. Production route completeness is claimed only after the customer route is integrated, tested, replayable, fail-closed, and outcome-accounted.
Shared implementation method
A successful corridor starts with a route inventory rather than a generic model integration. The partner identifies each proposed movement, actor, downstream system, identity boundary, consequence class, reviewer role, and commit point. OntoGuard maps that event to the Decision Authorization contract and the evidence that must accompany ALLOW, BLOCK, or ESCALATE. BM25 may retrieve exact policy or source candidates, while semantic governance connects the candidates to the current workflow and authority state. Retrieval remains evidence discovery, not a release decision.
Control placement
The partner places the authorization call before the protected commit and ensures a missing, invalid, or withheld decision cannot be bypassed by the selected endpoint.
Identity and authority
The customer’s identity system and operating policy establish who may review, override, approve, or close a case. OntoGuard records the resolved or pending state in the packet.
Replay and closure
The integrated route should reproduce the governed event, preserve trace and receipt references, and account for the final operational outcome rather than stopping at queue assignment.
Acceptance evidence for a production corridor
Route registration alone is insufficient. The selected path should be governed, tested, replayable, fail-closed, non-bypassable within the agreed boundary, and outcome-accounted. Evidence should show the attempted operation, authorization-token state, enforcement response, reviewer decision where applicable, downstream commit state, and protected-effect result. Claims remain limited to the routes and endpoints actually integrated and tested.