Walkthrough · tool inside your framework
Don't replace your stack.
Call Quadrazene from it.
Your orchestrator already runs the conversation. When a turn needs a real write. SAP, ServiceNow, outbound email - it calls a Quadrazene Skill over REST. The Skill streams progress, pauses for HITL when policy demands it, and returns a hash-chained audit row when it commits.
Walkthrough · 1 of 4
The parent orchestrator decides this turn needs the right kind of write. It picks the Quadrazene tool and calls the Skill over REST.
yourstack.internal/agent-core
quadrazene v0.2.1
Quadrazene
ReactorComposeRecipesInboxGovernanceRecords⌘K
Parent orchestrator · turn 3
User asked: “Open a QM notification for the cracked HT-1000 housings on the recent PO.”
Routing this turn to the quadrazene.action tool. The platform handles SAP writes with HITL + audit.
Routing this turn to the quadrazene.action tool. The platform handles SAP writes with HITL + audit.
POST https://qz.tenant.internal/api/skills/file-quality-notification/run
Authorization: Bearer eyJhbGciOi...
Idempotency-Key: agt-7f912c
Accept: text/event-stream
{
"purchaseOrderRef": "PO-9114",
"material": "MAT-018",
"defect": "cracked HT-1000 housings",
"actor": { "role": "ops-agent" }
}
Authenticated, tenant-scoped, idempotent. Same auth model the Reactor uses. Same Skill, same audit.
Live walkthrough — click a button or use the rail to navigate.
What you just saw
One adoption pattern. Every Engine works this way.
Insights, Governance, Advisory, and Actions are all callable from an external orchestrator. The Reactor is optional. The API spine is the product.