docs(P00): clarify v0.5 ambiguities (5 decisions, full autonomy)

D-025: /root/.orca system-level path (mirror of ~/.orca)
D-026: unify on ORCA_HOME as single namespace root + --system flag
D-027: Gitea built-in container registry for docker images
D-028: flip repo visibility to public via tea repos edit
D-029: install.sh defaults to latest release, optional --version pin

---ci---
project: orca
phase: 0
milestone: v0.5
status: clarify
---/ci---
This commit is contained in:
Jon Chery
2026-08-03 17:59:07 +00:00
parent a22c41164f
commit 0f71cf3f36
2 changed files with 15 additions and 2 deletions
+2 -2
View File
@@ -1,10 +1,10 @@
{
"phase": 0,
"stage": "specify",
"stage": "clarify",
"milestone": "v0.5",
"milestone_slug": "distribution",
"phase_role": "pre_execution",
"attempts": 0,
"updated_at": "2026-08-03T18:00:00Z",
"updated_at": "2026-08-03T18:05:00Z",
"milestone_complete": false
}
+13
View File
@@ -170,6 +170,19 @@ The vision ("minimalist, offline-first, CLI-first orchestration
engine") is unchanged. v0.5 is a distribution milestone, not a
direction change.
## v0.5 Clarified Decisions (D-series, full autonomy)
The 5 v0.5 decisions (D-025..D-029) were auto-resolved under full
autonomy during the CLARIFY stage:
| ID | Question | Decision | Rationale | Confidence |
|----|----------|----------|-----------|------------|
| D-025 | System-level namespace path layout? | **`/root/.orca`** (mirror of user-level `~/.orca`) | Consistent shape with user-level; just a different root. Matches the user's "starts at /root" wording. Single dir keeps it simple. | 0.90 |
| D-026 | Namespace override mechanism at runtime? | **Unify on `ORCA_HOME`** as single namespace root for all components (db, certs, init, daemon). Add `--system` flag that sets root to `/root/.orca`. | `ORCA_HOME` already exists for certs; extend to all components. Backward compatible (empty → `~/.orca`). One knob, not many. | 0.92 |
| D-027 | Docker registry target? | **Gitea built-in container registry** (`git.cloudinit.dev/coreci/orca`) | Keeps everything in one forge; uses Gitea's native registry. Consistent with REQ-045 (public repo → public image pulls). | 0.88 |
| D-028 | How to make releases publicly accessible (REQ-045)? | **Flip repo visibility to public** via `tea repos edit coreci/orca --private=false` during P0 ship | Simplest path to anonymous downloads; enables both install.sh pulls and docker pulls. Pre-existing `.env` leak already suppressed via gitleaks baseline + rotate-forward (commit 00127ce). | 0.85 |
| D-029 | install.sh default version? | **Latest release** (query Gitea releases API), optional `--version vX.Y.Z` to pin | Matches typical 1-liner installer UX; users get newest by default, can pin for reproducibility. | 0.92 |
### v0.5 Operational prerequisite (P0 ship)
The Gitea repo `coreci/orca` is currently **private** (returns 404