Master Brain is the template every child brain inherits. It defines how AI knowledge is structured, governed, secured and distributed across every organisation Prosperity Path serves. The venture-specific knowledge lives in the child brain. The standards, skills and governance always come from here.
- ✓ The canonical template that all child brains inherit from
- ✓ The skills library with a full development and security review lifecycle
- ✓ The governance framework: policies, access tiers, audit trail requirements
- ✓ The security infrastructure: content manifest, canary queries, incident response
- ✓ The standards documentation that defines how a brain is built and maintained
- ✓ A deployable framework that organisations adapt to their specific context
- ✗ A knowledge base for venture or client content (that lives in the child brain)
- ✗ A chatbot, AI interface or end-user product
- ✗ A task tracker, CRM or project management system
- ✗ A set-and-forget tool (it requires active governance and maintenance)
- ✗ A black box (every decision, access event and approval is recorded)
- ✗ Shared between clients (each deployment is isolated and independently governed)
quarantine/ first.One Master. Many Deployments.
Master Brain is the template. A child brain is a properly structured repository that inherits the skills, standards and governance from Master Brain, then fills in the knowledge specific to that organisation. The master stays clean. Client knowledge never touches it.
What syncs: base instructions, skills, commands, hooks, documentation templates
What never syncs: brain/ content (venture-specific), CLAUDE.md (venture-specific)
| Layer | Mechanism | What It Prevents |
|---|---|---|
| Content integrity | SHA256 manifest updated on every commit. Verified by audit-brain at Step 0. | Tampered, injected or silently modified brain content |
| Skill safety | Quarantine pipeline and skill-review before any skill reaches production | Malicious, insecure or low-quality skills reaching child brains |
| Access control | Four-tier content tagging with pre-filter enforcement at the database layer | Wrong people receiving wrong content in AI responses |
| Audit trail | Per-query logging to named individual, mandatory source citation on every response | Unattributed AI output, untraceable decisions, APRA CPS 230 non-compliance |
| Incident response | Four documented incident scenarios with detection, response and remediation steps | Uncoordinated or delayed response to knowledge poisoning, exfiltration or injection events |
Full Technical Documentation
The complete Master Brain reference: governance policies, security framework, retrieval layer spec, compliance evidence framework and implementation guides. Requires Prosperity Path Confluence access.