Project
Loading…Commit
—Fleet health
ObservingContext locality
UnmeasuredLocal Fleet Console
+ +Project
Loading…Commit
—Fleet health
ObservingContext locality
Unmeasured${message}
`; +} + +function safe(value) { + const element = document.createElement('span'); + element.textContent = value ?? ''; + return element.innerHTML; +} + +function render(snapshot) { + const project = snapshot.project ?? snapshot.repository; + $('#project-name').textContent = project?.name ?? project?.id ?? 'Not installed'; + $('#project-commit').textContent = snapshot.repository?.head?.slice(0, 9) ?? '—'; + $('#fleet-health').textContent = snapshot.mode === 'installed' + ? (snapshot.doctor?.healthy ? 'Healthy' : 'Needs attention') : 'Not installed'; + $('#context-state').textContent = snapshot.contextLocality?.measured ? 'Measured' : 'Unmeasured'; + + const agents = snapshot.agents ?? []; + $('#agent-count').textContent = `${agents.length} ${agents.length === 1 ? 'identity' : 'identities'}`; + $('#agent-list').innerHTML = agents.length ? agents.map((agent) => ` +${safe(agent.areaId)}${safe(locality?.reason ?? 'Runtime usage reporting is not available.')}
TORCH will compare cache activity with verified outcomes, not token count alone.`; +} + +async function refresh() { + $('#console-error').hidden = true; + try { + const response = await fetch('/api/snapshot', { cache: 'no-store' }); + const snapshot = await response.json(); + if (!response.ok) throw new Error(snapshot.message ?? snapshot.error); + render(snapshot); + } catch (error) { + $('#console-error').textContent = `Snapshot unavailable: ${error.message}`; + $('#console-error').hidden = false; + } +} + +$('#refresh-console')?.addEventListener('click', refresh); +refresh(); diff --git a/site/index.html b/site/index.html new file mode 100644 index 0000000..d2853b1 --- /dev/null +++ b/site/index.html @@ -0,0 +1,133 @@ + + + + + + +Portable fleet alpha
+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.
+ +Request CR-184
+ +Ready at owner request.
+Git required
GitHub optional
Provider independent
Local first
Human approved
+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.
+Architecture, tests, operations, scarce resources, and external Markdown specifications become evidence—not instructions to execute.
+Every domain receives scope, exclusions, owned paths, neighbors, checks, runtime policy, and collision rules.
+Stable identities survive runtime sessions. Durable messages and project state outlive model context.
+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.
+Context savings are a measured hypothesis, not a marketing claim.
+TORCH distinguishes implementation from qualification. Green output without the right scenario, authority, and SHA is not proof.
+Point TORCH at a Git repository, a product specification, or both. Design is read-only; installation waits for your reviewed proposal.
+node bin/torch.mjs design \
+ --repo /path/to/project \
+ --spec /path/to/product-spec.md \
+ --output fleet-proposal.json \
+ --json