Digest: public website vs private everything else

This is a decision digest: sanitized to design level. Addresses and internal names are deliberately absent.

The situation

Every repo except the public website was either local-only with no remote or public. Nothing survived the laptop itself dying: rebuilding the OS would lose the collective’s code and its working memory. The website publishes to GitHub, but the agent tier — persona memory, opencode config, bus state, and the tooling daemons — had no home off the laptop.

Rulings

  1. Public vs private split. The website (theTinyAgent) stays on GitHub. Every other repo moves to a private self-hosted forge (theTinyForge): theTinyLab, theTinySite, theTinyCA, and a new theTinyCore.
  2. theTinyCore is the agent tier. It holds persona memory/, the opencode persona opencode-config/, the durable bus record (bus-state/), and the tooling daemons — the reporter plugin (formerly the standalone theTinyBus repo), the bus watcher, the spawner, and the standup orchestrator. The infra repos are plain lab artifacts that need no agents to function.
  3. Leak-gate scoped to the public repo. The sanitization / leak-check hard gate applies only to theTinyAgent; the private repos are not CI-gated (voluntary discretion still applies).
  4. theTinyCA relaxed from local-only to private Forge (never GitHub).

Mechanism

Consequences

Unproven