Profile
Declare domain, users, devices, hardware, provider, budget, data classes and desired apps—without secrets.
CC10 Distribution Preview
Clone the idea.
Own the outcome.
The vision is simple: describe your needs, give a sanitized CC10 package to your AI, review its plan and create an ecosystem that remains yours. The working reference comes first; reusable automation follows verified evidence.
DescribeSystem profile · people · devices · data · risk
↓
PlanAI reads versioned architecture, IaC and safety gates
↓
ApproveHuman reviews cost, security, migration and rollback
↓
ProveHealth, identity, backup, restore and user workflows
Reference systemLive
Edge + DNS IaCVerified
Reusable packagePreview
Public licencePending decision
The reproducible path
AI can accelerate setup.
Evidence keeps it safe.
This is not a magic prompt that receives root access. It is a staged contract: inspect, model, plan, approve, apply narrowly, verify and record.
Discover
The AI checks actual hosts, DNS, storage, network and existing data before proposing a target.
Plan
Produce topology, cost boundary, threat model, migration stages, rollback and explicit human decisions.
Deploy
Use pinned OpenTofu, Compose, systemd and documented service adapters within approved scope.
Verify
Test identity, role access, app workflows, backups, representative restores, security headers and monitoring.
Operate
Keep Git authoritative, detect drift, rotate credentials, onboard people and repeat acceptance after change.
Reusable layer
More than IaC.
A complete system contract.
Infrastructure alone does not create a usable ecosystem. CC10 also captures product roles, identity, recovery, onboarding and proof.
System profile + architecture
Portable topology, failure domains, app roles, data placement and cost boundaries.
OpenTofu + service bundles
Replaceable public edge, protected DNS, pinned containers and explicit persistent state.
Identity + policy
SSO, passkeys, least privilege, person lifecycle and operator-only surfaces.
AI bootstrap prompt + runbooks
A model-neutral instruction contract with safety gates, assumptions and required evidence.
Onboarding + app map
One clear job per app, thin-client setup, recovery and device replacement workflows.
Acceptance + receipts
Health, access, restore and browser checks recorded after every material deployment.
The AI contract
Useful autonomy.
Bounded authority.
CC10 prefers Codex and OpenAI today, but the package describes interfaces instead of binding the system to one engine. A local or European model can replace the planning layer without replacing the apps.
Current release boundary: the live prototype is real; the public distribution remains a preview. Disaster-recovery evidence is incomplete, hardware discovery is environment-specific and no copying licence has yet been selected.
1
No secrets in prompts or Git
Credentials enter only through protected runtime stores and narrowly scoped installation steps.
2
Inspect before mutation
Observed state, backups and ownership must be established before changing live systems.
3
Plan before apply
Every risky action names impact, rollback and the evidence that will prove success.
4
Typed actions over raw root
Repeatable operations expose narrow contracts, audit records and idempotency where possible.
5
Stop at red gates
No AI convenience overrides an unverified disk, missing restore, unknown host key or absent approval.
Choose your path
Build your own.
Bring help when it matters.
The self-service distribution is being extracted from the working reference. Organisations that need architecture, migration, hardening or ongoing operation can engage Cong directly.