ciagent
d10f89d55e
chore(config): add workflow block — 4 standing rules
...
Adds a top-level workflow block to .ciagent/config.json with the four
standing rules for v0.2+ and all future milestones:
1. no_hitl: true — full automation, no human-in-the-loop
2. merge_strategy — fast-forward or rebase-then-fast-forward only;
no merge-commit-no-ff, no squash
3. release_flow_per_phase: true — every phase tag produces a Gitea release
(already in .ciagent/RELEASE_POLICY.md, now
also enforced in config.json)
4. branching — main < milestone/<slug> < phase/<NN>-<slug>
phase branches FF into milestone;
milestone rebases onto main then FF.
---ci---
project: orca
phase: 0
milestone: v0.1
status: execute
---/ci---
2026-06-03 20:20:17 +00:00
ciagent
f1c55ca79b
docs(audit): fix .ciagent/ file discipline issues
...
Audit findings addressed:
- PROJECT.md: add 'What This Is' and 'Key Decisions' sections (per audit Step 2)
- ARCHITECTURE.md: add internal/jobspec (HCL parser) and internal/model (domain types) to system diagram and component details
- PLANS.md: expand REQ coverage lines for Phase 1 and Phase 3 to include all REQ-IDs the work actually delivers (REQ-003 offline-first, REQ-008 slog, REQ-010 --json, REQ-020 hashicorp/hcl)
---ci---
project: orca
phase: 0
milestone: v0.1
status: fix
---/ci---
2026-06-03 20:14:03 +00:00
ciagent
939ce8ba74
docs(P06): add RELEASE_POLICY.md — every phase gets a release
...
Captures the new standing rule: every phase tag MUST produce a Gitea
release (not just a git tag), and milestone tags must use the next
version per the feature-milestone promotion logic.
---ci---
project: orca
phase: 6
milestone: v0.1
status: complete
---/ci---
2026-06-03 19:58:45 +00:00
Jon Chery
d76ff84dfb
docs(milestone): complete v0.1-foundation
...
v0.1 Foundation milestone shipped across 6 phases (P00–P06). All
4-layer verification passed at every stage; audit and review clean.
- 21/24 requirements complete; 3 deferred to v0.2 (mTLS REQ-011/023,
gosec+govulncheck REQ-014, iter.Seq REQ-022) — all paired with
multi-node networking or richer security scanning, explicitly out
of scope for v0.1 minimalism.
- Tagged v0.2.0 per feature-milestone promotion rule (next-minor
after all feature-patches v0.1.1..v0.1.6 ship).
- Per-phase tags v0.1.1..v0.1.6 retained for traceability.
---ci---
project: orca
phase: 0
milestone: v0.1
status: complete
requirements:
covered: [REQ-001, REQ-002, REQ-003, REQ-004, REQ-005, REQ-006, REQ-007, REQ-008, REQ-009, REQ-010, REQ-012, REQ-013, REQ-015, REQ-016, REQ-017, REQ-018, REQ-019, REQ-020, REQ-021, REQ-024]
partial: [REQ-014]
---/ci---
2026-06-03 19:29:59 +00:00
Jon Chery
48cd101ff2
docs(P06): verification - 4 layers pass
...
- Layer 1 build: go build ./... PASS
- Layer 2 vet: go vet ./... PASS
- Layer 3 test: all packages green
- Layer 4 smoke: make build injects version, make changelog regenerates
from commit log, tarball generation works (5.9MB)
REQ-007 (CoreCI release flow) covered; REQ-014 (gosec/govulncheck) deferred
to v0.2 (out of scope for v0.1 minimalism).
---ci---
project: orca
phase: 6
milestone: v0.1
status: verify
requirements:
covered: [REQ-007]
partial: [REQ-014]
---/ci---
2026-06-03 19:28:07 +00:00
Jon Chery
b06458d313
docs(P05): verification - 4 layers pass
...
- Layer 1 build: go build ./... PASS
- Layer 2 vet: go vet ./... PASS
- Layer 3 test: all packages green
- Layer 4 smoke: /healthz, /readyz, /v1/{jobs,nodes,tasks} all 200; SIGTERM clean
REQ-006 (slog audit), REQ-017 (context propagation), REQ-019 (cobra) all covered.
Daemon coverage 67.5%.
---ci---
project: orca
phase: 5
milestone: v0.1
status: verify
requirements:
covered: [REQ-006, REQ-017, REQ-019]
partial: []
---/ci---
2026-06-03 19:24:03 +00:00
Jon Chery
c2038952c7
docs(P00): create 6 phase plans with wave ordering
...
---ci---
project: orca
phase: 0
milestone: v0.1
status: plan
phases_planned: 6
waves: 4
---/ci---
2026-06-03 12:16:08 +00:00
Jon Chery
65eb2e601b
docs(P00): research findings - architecture + personas
...
---ci---
project: orca
phase: 0
milestone: v0.1
status: research
personas_active: 5
personas_deactivated: 2
---/ci---
2026-06-03 12:15:20 +00:00
Jon Chery
6f34f1794b
docs(P00): ideation - 30 ideas accepted (3 tiers)
...
---ci---
project: orca
phase: 0
milestone: v0.1
status: ideate
ideas_accepted: 30
tiers:
mechanical: 10
backend: 10
cross_project: 10
---/ci---
2026-06-03 12:12:55 +00:00
Jon Chery
bc7ce1caf6
docs(P00): clarify ambiguities (full autonomy, 10 decisions)
...
---ci---
project: orca
phase: 0
milestone: v0.1
status: clarify
decisions:
- id: D-001
decision: Single binary distribution
rationale: Simpler distribution; subcommands baked into one orca binary
confidence: 0.95
- id: D-002
decision: modernc/sqlite for state store
rationale: CGO-free, cross-compile friendly, single file
confidence: 0.92
- id: D-003
decision: net/http for inter-node comms
rationale: No external RPC framework for v0.1
confidence: 0.85
- id: D-004
decision: Single-node only for v0.1
rationale: Multi-node scheduling is out of scope
confidence: 0.90
- id: D-005
decision: Human-readable default, --json for machine
rationale: Serves both humans and AI agents
confidence: 0.95
- id: D-006
decision: HCL/YAML job specs
rationale: Familiar to Nomad users, simpler than JSON
confidence: 0.88
- id: D-007
decision: mTLS for v0.1
rationale: Most secure default
confidence: 0.80
- id: D-008
decision: Direct process execution (no containers)
rationale: Avoids Docker dependency
confidence: 0.85
- id: D-009
decision: ~/.orca/config.hcl and /etc/orca/orca.hcl
rationale: XDG-style paths
confidence: 0.90
- id: D-010
decision: Structured JSON via log/slog
rationale: Native Go slog, no external dep
confidence: 0.95
---/ci---
2026-06-03 12:07:28 +00:00
Jon Chery
55aae5347e
chore(P00): rename orch-engine to orca, configure gitea + coreci (v0.1)
...
---ci---
project: orca
phase: 0
milestone: v0.1
status: execute
---/ci---
2026-06-03 11:36:32 +00:00
Jon Chery
0cba1aa5fe
chore(P00): set autonomy level to full
...
---ci---
project: orch-engine
phase: 0
milestone: v1.0
status: execute
---/ci---
2026-06-03 11:18:58 +00:00
Jon Chery
e2e77e79b9
chore(P00): quick task - populate config.json with backlog reference
...
---ci---
project: orch-engine
phase: 0
milestone: v1.0
status: execute
lessons:
- Referenced backlog project's config.json (also Go 1.25+) to establish proper schema including autonomy, personas, parallelization, sessions, ci, repository, and commands sections
---/ci---
2026-06-03 11:15:12 +00:00
Jon Chery
8c086def69
chore(config): populate ciagent config with standard settings
...
---ci---
project: orch-engine
phase: 0
milestone: v1.0
status: execute
---/ci---
2026-06-03 11:08:48 +00:00
Jon Chery
97f437f9ef
docs(init): initialize orch-engine (6 phases)
...
---ci---
project: orch-engine
phase: 0
milestone: v1.0
status: specify
decisions:
- id: D-001
decision: Use single-project mode for initial setup
rationale: Simplified configuration for the initial phase
confidence: 1.0
alternatives: []
---/ci---
Specification: Build an offline/CLI-first orchestration engine.
Requirements: Simplicity, AI-first, Offline-first, CLI-first, prioritize security/bug-fixes over features, Go 1.25+.
Constraints: Simpler than Nomad, far simpler than Kubernetes.
Out of scope: K8s complexity.
2026-06-03 10:59:05 +00:00