feat(landing): build interactive landing page with terminal emulator and telemetry comms (#4)

config.toml

@@ -38,6 +38,10 @@ github_org_url = "https://github.com/tars-cloud"
 og_image = "/images/og-banner.png"
 logo_path = "/images/tars-logo.svg"
 status_label = "SYS // NOMINAL"
+hero_badge = "SYS // SOVEREIGN_MULTI_AGENT_RUNTIME // GUARDS_V3.5"
+hero_headline = "Your AI Factory gives you tokens. TARS gives you governed outcomes"
+hero_subtitle = "SOVEREIGN MULTI-AGENT ENGINEERING // GOVERNED BY GUARDS"
+quickstart_cmd = "tars-run-issue --yolo 42"
 
 [[extra.menu_items]]
 name = "Docs"

content/_index.md

@@ -0,0 +1,57 @@
++++
+title = "TARS Cloud // Governed Multi-Agent Engineering"
+description = "Sovereign multi-agent engineering runtime governed by the GUARDS verification lifecycle, adversarial CASE != DOYLE verification, one human gate, and air-gapped zero-registry sovereignty."
+sort_by = "weight"
+template = "index.html"
+
+[extra]
+hero_badge = "SYS // SOVEREIGN_MULTI_AGENT_RUNTIME // GUARDS_V3.5"
+hero_headline = "Your AI Factory gives you tokens. TARS gives you governed outcomes"
+hero_subtitle = "SOVEREIGN MULTI-AGENT ENGINEERING // GOVERNED BY GUARDS"
+hero_summary = "TARS orchestrates specialized engineering spokes inside isolated git worktrees under deterministic verification gates. Builders never grade their own work, human review happens once at specification, and the entire runtime operates air-gapped with zero external registry dependencies."
+cta_primary_label = "[QUICKSTART]"
+cta_primary_url = "#terminal-console"
+cta_secondary_label = "[DOCUMENTATION]"
+cta_secondary_url = "/docs/"
+cta_tertiary_label = "[ACCESS CONSOLE]"
+cta_tertiary_url = "#comms-link"
++++
+
+## Sovereign Multi-Agent Engineering
+
+Unconstrained token factories generate plausible patches without accountability, leaking regressions across branch boundaries and demanding constant human babysitting.
+`TARS` replaces unstructured chat loops with a deterministic **Prime-and-Spokes** engineering runtime.
+`TARS` Prime acts as the state-machine hub, delegating scoped contracts to specialized spokes (`KIPP`, `BRAND`, `ROMILLY`, `CASE`, and `DOYLE`) inside isolated git worktrees where every artifact is bound by SHA-256 digests.
+
+## Three Core Architectural Pillars
+
+### 1. Adversarial Physics (CASE != DOYLE)
+
+In `TARS`, the implementing spoke (`CASE`) is structurally forbidden from grading its own work (`CASE ≠ DOYLE`).
+`CASE` writes code strictly within declared file boundaries inside an isolated worktree and commits a candidate revision.
+An independent verification spoke (`DOYLE`) checks out the candidate revision in a separate verification environment, replays reproduction evidence (`evidence-generation-*.json`), enforces CRAP and coverage thresholds, and either certifies the contract or routes deterministic rework.
+
+### 2. One Human Gate with zero idle compute
+
+Traditional agent harnesses stall repeatedly on interactive tool-approval prompts, burning operator attention while compute sits idle.
+`TARS` concentrates human judgment at a single architectural gate: `Cooper` ratifies the unified `spec.md`, `design.md`, and `structure.md` contract bundle once at the `U -> A` boundary.
+Once ratified, autonomous execution waves (`--yolo`) drive `A.3 -> R.1 -> R.2 -> D.1 -> D.2 -> S.1 -> S.2` to completion with zero idle compute wait states.
+
+### 3. Sovereignty by Construction where air-gap is an empty registry
+
+`TARS` is engineered for sovereign infrastructure from day one, requiring zero mandatory SaaS control planes, zero npm runtime dependencies, and zero outbound telemetry webhooks.
+Build and verification toolchains run locally through reproducible Nix / `devenv` profiles and content-addressed BLAKE3 `casita` repositories.
+Operating inside a classified or disconnected enclave requires no special fork or degraded build flag: in `TARS`, an air-gap is simply an empty upstream registry.
+
+## The GUARDS Verification Lifecycle (`G -> U -> A -> R -> D -> S`)
+
+Every issue progresses through six deterministic stages with cryptographically verifiable contract handoffs:
+
+| Phase | Sub-Phases | Responsible Spoke | Contract Deliverables & Gate Invariants |
+| :--- | :--- | :--- | :--- |
+| **G // Gather** | `G.1`, `G.2` | `TARS` + `KIPP` | Operator context capture (`interview.md`), codebase research (`research.md`), and empirical reproduction receipts (`evidence-generation-*.json`). |
+| **U // Understand** | `U.1` | `BRAND` | Formal specification (`spec.md`), file scope lock declaration, and evidence disposition (`evidence-disposition.json`). |
+| **A // Architect** | `A.1`, `A.2`, `A.3` | `BRAND` + `ROMILLY` | Technical architecture (`design.md`), interface map (`structure.md`), **Cooper Human Gate Ratification**, and step-by-step execution plan (`plan.md`). |
+| **R // Realize** | `R.1`, `R.2` | `CASE` + `DOYLE` | Isolated worktree implementation (`implementation-notes.md`) followed by adversarial `CASE != DOYLE` verification (`verification.md`). |
+| **D // Demonstrate** | `D.1`, `D.2` | `DOYLE` + `KIPP` | End-to-end scenario testing (`test-report.md`) and synchronized architecture/operator documentation (`documentation.md`). |
+| **S // Ship** | `S.1`, `S.2` | `DOYLE` + `KIPP` | Pull request assembly with full SHA-256 artifact lineage (`pr-manifest.md`) and independent spec/standards review (`review.md`). |