mirror of
https://github.com/PR0M3TH3AN/TORCH.git
synced 2026-10-28 16:31:56 +00:00
134 lines
8.0 KiB
HTML
134 lines
8.0 KiB
HTML
<!doctype html>
|
|
<html lang="en">
|
|
<head>
|
|
<meta charset="utf-8">
|
|
<meta name="viewport" content="width=device-width, initial-scale=1">
|
|
<meta name="description" content="TORCH turns one Git repository into a coordinated team of persistent AI engineering specialists.">
|
|
<title>TORCH — one repository, a coordinated AI engineering team</title>
|
|
<link rel="stylesheet" href="/styles.css">
|
|
<script src="/app.js" defer></script>
|
|
</head>
|
|
<body>
|
|
<a class="skip-link" href="#main">Skip to content</a>
|
|
<header class="masthead">
|
|
<a class="wordmark" href="/" aria-label="TORCH home"><span class="mark">T</span> TORCH</a>
|
|
<nav aria-label="Primary">
|
|
<a href="#system">System</a>
|
|
<a href="#evidence">Evidence</a>
|
|
<a href="#start">Start</a>
|
|
<a href="/console">Fleet Console</a>
|
|
</nav>
|
|
</header>
|
|
|
|
<main id="main">
|
|
<section class="hero" aria-labelledby="hero-title">
|
|
<div class="hero-copy">
|
|
<p class="status-line"><span></span> Portable fleet alpha</p>
|
|
<h1 id="hero-title">One repository.<br>A coordinated AI engineering team.</h1>
|
|
<p class="lede">TORCH studies your code and project specification, proposes durable areas of responsibility, and gives each specialist its own branch, worktree, context, and route back to main.</p>
|
|
<div class="hero-actions">
|
|
<a class="primary-action" href="#start">Design a fleet</a>
|
|
<a class="text-action" href="https://github.com/PR0M3TH3AN/TORCH">Read the source</a>
|
|
</div>
|
|
</div>
|
|
|
|
<div class="dispatch" aria-label="Interactive TORCH routing board">
|
|
<div class="dispatch-head">
|
|
<p>Request CR-184</p>
|
|
<button id="route-toggle" type="button" aria-pressed="false">Run the route</button>
|
|
</div>
|
|
<ol class="route" id="route">
|
|
<li class="route-step is-ready" data-step="0"><span class="node">A</span><div><strong>Owner request</strong><small>Change terrain streaming without weakening frame checks.</small></div></li>
|
|
<li class="route-step" data-step="1"><span class="node">S</span><div><strong>Session Manager</strong><small>Routes ownership and establishes acceptance.</small></div></li>
|
|
<li class="route-step split" data-step="2"><span class="node">T</span><div><strong>Terrain specialist</strong><small>Works in its persistent domain context.</small></div><span class="peer">QA peer</span></li>
|
|
<li class="route-step" data-step="3"><span class="node">✓</span><div><strong>Exact-commit checks</strong><small>Receipts bind evidence to the measured SHA.</small></div></li>
|
|
<li class="route-step" data-step="4"><span class="node">M</span><div><strong>Controlled main</strong><small>Authorized fast-forward after convergence.</small></div></li>
|
|
</ol>
|
|
<p class="route-readout" id="route-readout" aria-live="polite">Ready at owner request.</p>
|
|
</div>
|
|
</section>
|
|
|
|
<section class="principle-strip" aria-label="TORCH principles">
|
|
<p>Git required</p><p>GitHub optional</p><p>Provider independent</p><p>Local first</p><p>Human approved</p>
|
|
</section>
|
|
|
|
<section class="system-section" id="system">
|
|
<div class="section-intro">
|
|
<h2>The project decides the team.</h2>
|
|
<p>TORCH does not install a catalog of generic agents. It reads the repository and the specifications you select, then produces a pending organization for you to split, merge, rename, or reject.</p>
|
|
</div>
|
|
<div class="blueprint">
|
|
<article>
|
|
<span class="blueprint-index">Input</span>
|
|
<h3>Code and intent</h3>
|
|
<p>Architecture, tests, operations, scarce resources, and external Markdown specifications become evidence—not instructions to execute.</p>
|
|
</article>
|
|
<article>
|
|
<span class="blueprint-index">Design</span>
|
|
<h3>Explicit boundaries</h3>
|
|
<p>Every domain receives scope, exclusions, owned paths, neighbors, checks, runtime policy, and collision rules.</p>
|
|
</article>
|
|
<article>
|
|
<span class="blueprint-index">Operate</span>
|
|
<h3>Persistent specialists</h3>
|
|
<p>Stable identities survive runtime sessions. When a durable new boundary emerges, the manager can propose another specialist—but only owner approval wires it into the Fleet.</p>
|
|
</article>
|
|
</div>
|
|
</section>
|
|
|
|
<section class="context-section">
|
|
<div class="context-diagram" aria-hidden="true">
|
|
<div class="wide-context">general session<div class="churn"></div><div class="churn second"></div><div class="churn third"></div></div>
|
|
<div class="versus">versus</div>
|
|
<div class="focused-context"><span>terrain</span><span>runtime</span><span>verification</span></div>
|
|
</div>
|
|
<div>
|
|
<h2>Keep useful context hot.</h2>
|
|
<p>A specialist can retain the working set for one coherent area instead of repeatedly loading unrelated project history. TORCH measures cache reads, cache creation, compactions, resumed prompt size, cost, and verified outcomes before calling that an efficiency win.</p>
|
|
<p class="truth-note">Context savings are a measured hypothesis, not a marketing claim.</p>
|
|
</div>
|
|
</section>
|
|
|
|
<section class="evidence-section" id="evidence">
|
|
<div class="section-intro">
|
|
<h2>Proof has a commit.</h2>
|
|
<p>TORCH distinguishes implementation from qualification. Green output without the right scenario, authority, and SHA is not proof.</p>
|
|
</div>
|
|
<div class="ledger" role="table" aria-label="Current TORCH qualification ledger">
|
|
<div class="ledger-row ledger-head" role="row"><span role="columnheader">Capability</span><span role="columnheader">Current evidence</span><span role="columnheader">State</span></div>
|
|
<div class="ledger-row" role="row"><span>Portable kernel and reversal</span><span>Scenario tested</span><strong class="proven">Proven locally</strong></div>
|
|
<div class="ledger-row" role="row"><span>Durable control plane and backlog</span><span>SQLite + tracked tasks</span><strong class="proven">Proven locally</strong></div>
|
|
<div class="ledger-row" role="row"><span>Checks, resources, integration</span><span>Exact-SHA lifecycle</span><strong class="proven">Proven locally</strong></div>
|
|
<div class="ledger-row" role="row"><span>Claude and Codex coordination</span><span>Virtualized adapters</span><strong class="pending">Live gate open</strong></div>
|
|
<div class="ledger-row" role="row"><span>Self-managed successor</span><span>Atomic candidate mechanics</span><strong class="pending">Stable boot open</strong></div>
|
|
<div class="ledger-row" role="row"><span>COMBATRIG migration</span><span>33 areas, 570 tasks inventoried</span><strong class="pending">Boundaries open</strong></div>
|
|
</div>
|
|
</section>
|
|
|
|
<section class="start-section" id="start">
|
|
<div>
|
|
<h2>Start with the work you actually have.</h2>
|
|
<p>Point TORCH at a Git repository, a product specification, or both. Bootstrap gives your Session Architect AI a bounded evidence brief; installation waits for your reviewed proposal.</p>
|
|
</div>
|
|
<div class="command-panel">
|
|
<div class="command-tabs" role="tablist" aria-label="Startup input">
|
|
<button role="tab" aria-selected="true" data-command="both">Repository + spec</button>
|
|
<button role="tab" aria-selected="false" data-command="repo">Repository only</button>
|
|
</div>
|
|
<pre><code id="start-command">node bin/torch.mjs bootstrap \
|
|
--repo /path/to/project \
|
|
--spec /path/to/product-spec.md \
|
|
--output fleet-design-brief.json \
|
|
--json</code></pre>
|
|
<button class="copy-button" id="copy-command" type="button">Copy command</button>
|
|
</div>
|
|
</section>
|
|
</main>
|
|
|
|
<footer>
|
|
<p><strong>TORCH</strong> is an open, local-first agent fleet for Git projects.</p>
|
|
<div><a href="https://github.com/PR0M3TH3AN/TORCH">GitHub</a><a href="/console">Local console</a><a href="https://github.com/PR0M3TH3AN/TORCH/blob/main/docs/PORTABLE_AGENT_FLEET_SPEC.md">Specification</a></div>
|
|
</footer>
|
|
</body>
|
|
</html>
|