Skip to content

Sith implementation roadmap #39

Description

@gnanirahulnutakki

Sith implementation roadmap

One Go binary, two faces on one shared engine: a day-0 local fleet client (the adoption wedge) and a day-N governed hub (the durable moat). Full plan: reshape PR #17 · docs/SITH-NOTION.md · docs/EPICS.md · docs/ROADMAP.md · docs/BUILD-SEQUENCE.md (PR #40) · docs/research/USE-CASE-AND-SHAPE.md · docs/research/MARKET-RESEARCH-2026-07.md (PR #45).

The reframing: you earn the right to govern a fleet by first being the tool the engineer already uses to see it. Lead with the read wedge; governance is the moat, not the on-ramp.

Sequencing discipline (never violated): local before hub · read before write · PR before mutation · exec never · prod never auto.

The three wedges (market research July 2026): (a) the adoption wedge — "k9s for your whole fleet", an OSS no-account cross-cluster-by-default local client, a slot still empty in OSS (Aptakube closed+paid, k9s declined ×3, Headlamp per-cluster); (b) the durable moat — governed typed-intent action federation with AI as a governed client; (c) newly evidenced inside the moat — a deterministic, offline, rule-based Investigation Brain (E14) occupying the gap between dumb dashboards and non-deterministic LLM SRE-agents.

Milestones → epics

Phase L — local mode (day 0) · adoption wedge — milestone

Delivered as the ordered, always-green slices of docs/BUILD-SEQUENCE.md:

M0 — falsification (PASSED · ADR-0001 Accepted) — milestone

P1 — read federation — milestone

P2 — first governed write — milestone

P3 — policy federation + MCP write — milestone

Fast-follow — milestone

  • E12: Connector framework #30 · E12 — Connector framework — integration waves W1–W4 (W1 daily core = K8s + Argo + GitHub + Prometheus + a log store = the coverage E14's six rules need)
  • E13: Cost read-overlay #31 · E13 — Cost read-overlay (OpenCost rollup + GPU columns)

Standards-alignment gates (market research §5; standards-alignment label)

These are cross-cutting acceptance gates, not a separate epic:

Capability coverage (owner's list → epic)

Falsification gate holds: E1 onward was gated on E0 (now PASSED). Phase L ships day-0 without OCM.

Metadata

Metadata

Assignees

No one assigned

    Labels

    epicEpic tracking issuestandards-alignmentMCP / OTel semconv / SLSA / client-go standards gate

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions