ONI-CADIA Use Case
ONI-CADIA is a concrete public repository built from onizuka-openclaw-autonomous-team-starter.
Why it matters
This starter is meant to be adapted, not only studied. ONI-CADIA shows what that adaptation can look like when the underlying runtime pattern stays the same but the project identity, README flow, and docs surface are republished for a dedicated autonomous-team use case.
What carries over from this starter
- Windows-first operator flow with
uvand PowerShell - One OpenClaw pod per agent, with isolated generated state
- Managed workspace scaffolds such as
SOUL.md,IDENTITY.md,USER.md,HEARTBEAT.md,TOOLS.md, andBOOTSTRAP.md - A local Mattermost communication lab for mentions, smoke tests, and autonomous team chatter
What the downstream project changes
- The public project identity is presented as
ONI-CADIA - The quick-start path is adapted to
D:\Prj\ONI-CADIA - The repository, docs, and release-facing collateral are framed around the downstream project instead of the starter name
When to use it as a reference
Use ONI-CADIA as a reference when you want to fork this starter into a named project and want proof that the runtime glue, persona scaffolds, and communication-lab pattern can be carried forward with only light project-level rewrites.