First run — set up as Owner
This Hub starts blank. Create the owner account on the server. The password is stored only as a strong hash on the server — it can never be read back.
Your recovery codes — shown once. Keep these off this phone. They prove ownership if you are ever locked out. Using one revokes all sessions; it never revokes ownership.
Log in
Recovery revokes every session and any compromised credential. It never revokes ownership.
Registry counts — tap a count to filter
Backup + restore stamp (hand-entered, OBSERVED)
Green: restore tested within 30 days. Yellow: backup exists, restore untested or older. Red: no backup, or backup older than 30 days. A backup is not recovery until a restore is tested.
Hub cost line (hand-entered, OBSERVED)
Cave Labs Brands preset
The registry is empty. The preset loads the owner's real project rows as a starting offer — it is not a locked default, and loading it is written to the audit trail.
Rooms + later phases
Latest audit entries
Add a registry row
Intake Inbox — quarantine
Nothing enters the Hub untested. Every item moves RECEIVE → IDENTIFY → VALIDATE → QUARANTINE → REVIEW → RELEASE → RECORD, one tap at a time. Nothing executes. RELEASE needs an APPROVE permission — a proposal is never an execution.
Audit trail
What this is
The Cave Labs Brands management hub: one front door, one project registry, one status system. The tools keep their own code and homes — the Hub links and launches them, it does not swallow them. It is not called a collaboration hub until Phase 6 makes that true.
Colour legend: waiting on the owner · in motion / held · live / done · Max is carrying it · parked / later phase.
Roles (Owner / Admin / Member / Client-view) and permissions (VIEW / PROPOSE / EDIT / APPROVE / ADMINISTER) are enforced on the server on every call. This page hiding a button is not the security — the server refusing is.
The Five Security Laws
- 1. Least Authority — no more permission than necessary.
- 2. Trust Boundaries — components do not automatically trust one another.
- 3. Human Authorization — AI may recommend; authority decides execution.
- 4. Recoverable Security — recovery must not restore compromised access.
- 5. Verifiable Integrity — imports, backups and restores must be tested.
- Security fails closed: if authorization cannot be verified, the operation does not proceed. Read-only operation may remain available.
Can't do — Phase 1, said plain
- No collaboration or second-person seats before Phase 6.
- No zip-archive export in Phase 1 — the JSON export and the plain data file are the portable form.
- No payment processing anywhere in the Hub.
- No live AI inside the Hub; no autonomous agents.
- No private material beyond name-only rows; no secrets in any file; no biometric storage or biometric authority.
- A hash does not prove truth. Append-only is not automatically immutable. A backup is not recovery until a restore is tested. A login screen is not complete authorization. A hidden button is not a security control. A checklist is not a completed security audit. Local encryption does not protect a compromised device. AI agreement does not establish fact.
Accounts (ADMINISTER)
Ownership transfer lives with the owner: it needs the owner's live session plus an unused recovery code, and it is written to the audit trail. Ask the owner to run it from their login.
Export
Download the entire Hub data as one JSON file (Owner/Admin, written to the audit trail). Keep it somewhere safe — it is the whole Hub.
Recovery codes
Lost sight of your five codes? A logged-in Owner can retire the old set and issue a fresh five — the old ones stop working the moment the new set is made. Needs your current password. The new set is shown once, on this screen, until you dismiss it.
Your NEW recovery codes — shown once. Keep these off this phone.