coreci/orca
3
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 91 Wiki Activity

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

Browse Source 
D-038 HCL config (reuse jobspec dep) | D-039 flag>env>file>default
D-040 pprof opt-in operator addr | D-041 cert registration order
D-042 50% coverage floor, 70% new-code floor

---ci---
project: orca
phase: 0
milestone: v0.7
status: clarify
---/ci---
This commit is contained in:
Jon Chery
2026-08-03 20:28:21 +00:00
parent bd4a34daa2
commit fc034218e3
2 changed files with 15 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.ciagent/CHECKPOINT.json
+2 -2
View File
@@ -1,11 +1,11 @@
{
"phase": 0,
"stage": "specify",
"stage": "clarify",
"milestone": "v0.7",
"milestone_slug": "hardening-completion",
"phase_role": "pre_execution",
"attempts": 0,
"updated_at": "2026-08-03T20:30:00Z",
"updated_at": "2026-08-03T20:35:00Z",
"milestone_complete": false,
"next_milestone": null
}
.ciagent/PROJECT.md
+13
View File
@@ -276,6 +276,19 @@ auto-resolved at full autonomy within the `clarify_budget`:
- **D-037 Ed25519**: `golang.org/x/crypto/ssh` + `golang.org/x/crypto/ed25519`
are in the same module; no additional direct dep beyond D-030.
## v0.7 Clarified Decisions (D-series, full autonomy)
The 5 v0.7 decisions (D-038..D-042) were auto-resolved at full autonomy
within the `clarify_budget` (10):
| ID | Question | Decision | Rationale | Confidence |
|----|----------|----------|-----------|------------|
| D-038 | Config file format — HCL or YAML? | **HCL** | D-009 already specced `config.hcl`. HCL is already a direct dep (hashicorp/hcl/v2 for jobspec). Adding YAML would introduce a second parser dep — violates minimal-deps. Use the existing `hclparse` pkg from jobspec. | 0.93 |
| D-039 | Config precedence order (flag vs env vs file vs default)? | **flag > env > file > default** | Standard layered config: the most explicit (flag) wins, then the runtime (env), then the persisted (file), then the built-in default. Matches cobra/viper convention without the viper dep. | 0.92 |
| D-040 | pprof security — bind to localhost only, or operator-chosen addr? | **Operator-chosen `--pprof <addr>` (default disabled)** | Default disabled keeps the minimalist posture. Operator picks the addr — localhost for dev, unix socket for prod. Separate mux so it never touches the mTLS daemon listener. No auth (pprof is operator-only, addr is the gate). | 0.85 |
| D-041 | cert command registration — where in root command order? | **After `cert` is unreachable today, append after `node` in rootCmd.AddCommand order** | Alphabetical-ish with the existing cluster (audit, daemon, doctor, init, job, node, cert, status, version). No behavior change to existing commands. | 0.88 |
| D-042 | Coverage target — 50% floor or higher? | **50% floor per package, 70% target for new packages** | 50% is achievable for the concurrent packages (engine, transport) without heroic mock effort; 70% is the floor for new code in P02/P04. Avoids a "raise coverage everywhere" rathole. | 0.85 |
## v0.7 Scope Summary — Hardening & Completion
v0.7 is a 4-execution-phase **NFR milestone** that closes out gaps