OmniRoids Studio

What it is

OmniRoids Studio is the commercial catalogue, private capability projection, and governed authoring boundary around the OmniRoids core. It turns reviewed capabilities and automations into explicit, versioned release candidates without making Studio a second source of truth.

The problem and business value

Reusable AI capability is difficult to commercialize when permissions, evidence, release state, and private implementation details are mixed together. Studio separates those concerns so a team can discover approved capabilities, plan an automation, pass it through review, and prepare a release that can be independently verified by the Core system.

The business value is controlled reuse: capability catalogues and automation workflows can become reviewable products while the private corpus, credentials, and release authority stay behind explicit boundaries.

What it does today

• Builds a public-safe catalogue and graph projection from reviewed source data.
• Maintains a private, digest-verified vault for capability and artifact metadata outside public/.
• Exposes permission-checked catalog, graph, vault, relation, and automation surfaces through the local server and protected API routes.
• Validates automation manifests, routes required skills from policy, plans workflows, and checks the exact lifecycle required for publication.
• Produces signed, immutable release envelopes and a Core-targeted outbox. The Studio adapter does not write the Core repository or invoke the Core publication RPC directly.

Integrations and data flow

OmniRoids Core remains authoritative for identity, membership, permissions, private capability publication, and runtime state. Studio consumes a short-lived signed Core access assertion and a versioned capability projection. The private vault is paginated, digest-checked, and served only after the requested permission is verified.

Automation source lives under the Studio repository. The source digest, evidence digests, routed skills, lifecycle receipts, and signed bundle are checked before a release can be prepared for the Core bridge. The public projection contains only approved catalogue and graph information.

AI or automation workflow

Studio is an orchestration and governance surface, not an autonomous agent. Its automation flow routes capabilities, validates inputs and lifecycle receipts, and prepares a release for review. Human owners or authorized capability architects remain responsible for approval, signing material, production transport, and any external side effect.

Security and privacy boundaries

The public bundle excludes the private vault, release envelopes, lifecycle receipts, Core credentials, environment files, and private artifact bodies. Every protected surface checks the required permission on the server, and missing, stale, revoked, expired, or unverified assertions deny access. Digest validation, path checks, secret-pattern checks, replay protection, and immutable release directories provide additional fail-closed controls.

What is coming next

The next work is operational: verify hosted authorization, transport credentials, deployment and rollback evidence, and any provider-backed delivery boundary before describing those integrations as live. The catalogue can then grow through reviewed automation packages without weakening the Core- to-Studio ownership boundary.

Current activity or evidence from the project

Recent repository work rebranded Studio as OmniRoids Studio, exposed the complete automation workflow surfaces, and added the private Full Graph and vault projections. The repository contains local validation, lifecycle, graph, mirror, and vault checks. These checks support the documented contracts; they do not claim hosted provider authorization, customer adoption, revenue, or production delivery.