Files

T

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

1.0 KiB

Raw Blame History

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.

1.0 KiB Raw Blame History