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.
This commit is contained in:
Jon Chery
2026-06-03 10:59:05 +00:00
commit 97f437f9ef
5 changed files with 67 additions and 0 deletions
+13
View File
@@ -0,0 +1,13 @@
# Architecture: Orchestration Engine
(Initial Draft)
The system will consist of:
1. **CLI Tool**: The primary interface for users and AI agents.
2. **Controller/Server**: A lightweight daemon managing state and scheduling.
3. **Agent/Worker**: A daemon running on each node to execute workloads.
4. **State Store**: A simple, local-first state persistence mechanism.
## Design Pillars
- Security before features.
- Bug fixes before features.
- NFRs before features.
+25
View File
@@ -0,0 +1,25 @@
# Project: Orchestration Engine
## Vision
A minimalist, offline-first, CLI-first orchestration engine inspired by HashiCorp Nomad, prioritizing stability, security, and simplicity over feature richness.
## Objective
Build a lightweight system to manage and execute workloads across a set of nodes, keeping complexity far below that of Kubernetes.
## Requirements
- **CLI First**: Primary interaction through a CLI tool.
- **Offline First**: Functional without constant internet connectivity.
- **AI First**: Designed to be easily discoverable and manageable by AI agents.
- **Stability & Security**: Prioritize security fixes and bug fixes over new features.
- **Language**: Written in Go 1.25+.
- **Simplicity**: Minimalist implementation, avoiding the "K8s complexity trap".
## Constraints
- No web UI as a primary requirement.
- Must not implement K8s-level complexity.
- Feature development must move slowly to ensure stability.
## Out of Scope
- Full-blown Kubernetes-compatible API.
- Complex cloud-provider integrations.
- GUI-based management consoles.
+11
View File
@@ -0,0 +1,11 @@
# Requirements: Orchestration Engine
## Milestone v1.0: Foundation
| ID | Requirement | Priority | Status |
|----|-------------|----------|--------|
| REQ-001 | Go 1.25+ Toolchain Support | High | Pending |
| REQ-002 | CLI-first interface for all operations | High | Pending |
| REQ-003 | Offline-first operational mode | High | Pending |
| REQ-004 | Basic task deployment (single node) | Medium | Pending |
| REQ-005 | Local state storage without external DB | Medium | Pending |
| REQ-006 | Security-first audit logging | High | Pending |
+9
View File
@@ -0,0 +1,9 @@
# Roadmap: Orchestration Engine
## Milestone v1.0: Foundation (Initial)
- [ ] Phase 0: Project Initialization & Specification
- [ ] Phase 1: Core CLI Skeleton & Command Parsing
- [ ] Phase 2: Basic Node Management (Join/Leave)
- [ ] Phase 3: Simple Task Execution Engine
- [ ] Phase 4: Local State Persistence
- [ ] Phase 5: Basic Health Checking
+9
View File
@@ -0,0 +1,9 @@
{
"projects": [
{
"slug": "orch-engine",
"name": "Orchestration Engine"
}
],
"active_project": "orch-engine"
}