RaiCentral

docs / pilot-onboarding

Pilot onboarding

Page summary

Stand up Community Edition, register a system, issue a key, prove DENY and ALLOW.

Goal: one consequential workflow under governance for a scoped alpha pilot. Book a demo on this site if you want a guided evaluation with ZTechnium.

Prerequisites: Docker (or your preferred deploy path from the raicentral repository), ability to reach the console and /sdk/v1 from your application environment.

Bootstrap: follow the public raicentral README to start the stack. Sign in with the bootstrap admin account and change default secrets before sharing the environment.

Provision: register an AI system → agent/version with an owner → create a runtime identity → issue an agent key (store securely) → create an SDK integration with integration_id and fail_closed: true.

First governed call: from Python or TypeScript, heartbeat → session → authorize a safe test tool. Prove DENY does not invoke the downstream tool. Prove ALLOW path executes then report_execution.

Pilot checklist: health OK; heartbeat OK; agent key not in git; deny path verified; allow + report path verified; named owner for the workflow; demo/pilot terms agreed if working with ZTechnium.

Repository: https://github.com/ztechnium/raicentral

Tags:pilotops