diff --git a/docs/TEST_INTEGRITY.md b/docs/TEST_INTEGRITY.md index acbc4cf..afa72ba 100644 --- a/docs/TEST_INTEGRITY.md +++ b/docs/TEST_INTEGRITY.md @@ -1,5 +1,30 @@ # Test Integrity Notes +## 2026-10-01 — Visible source installation instructions + +```yaml +test_integrity_note: + change_type: ["new_tests"] + scenarios: + - id: SCN-site-install + given: "A new visitor has no TORCH CLI and the product is experimental." + when: "They follow the landing page installation entry point." + then: "Visible prerequisites and rewrite-source commands install into an isolated prefix; review and startup remain separate." + observable_outcomes: + - "Installation section and working CLI bin mapping are present." + - "Source/candidate distinction, approval steps and manual pause are explicit." + determinism_controls: + - "Read repository HTML and package metadata; no model or network invocation." + anti_cheat_rationale: + prevents: + - "Assuming torch is already installed" + - "Linking only to a default-branch legacy guide" + - "Hidden automatic startup or global existing-launcher overwrite" + relaxation: + did_relax_any_assertion: false + if_true_explain_spec_basis: "" +``` + ## 2026-09-30 — Bounded routine coordination ```yaml diff --git a/site/index.html b/site/index.html index 9a14d01..40338ec 100644 --- a/site/index.html +++ b/site/index.html @@ -18,7 +18,7 @@ How it works View dashboard demo Evidence - Get started + Install Fleet Console @@ -31,7 +31,7 @@
TORCH studies your repository and goals, then proposes the sessions your work needs. Choose Codex, Claude, Pi, or another local runtime for each role—and keep the team coordinated as the project changes.
Experimental alpha.3. The TORCH-on-TORCH self-host pilot is Codex-run. Built-in Codex, Claude, and Pi adapters exist; live mixed-provider swaps and production use remain unqualified.
@@ -96,7 +96,7 @@The active pilot uses the accepted immutable 0.1.0-alpha.3 artifact from source 28c. Later canonical source at 0c2 is not installed automatically. The user-system schedule timer is installed and running; automatic AI wakes remain paused. Pipeline execution, isolated candidate-executor assurance, and production acceptance remain open.
+The self-host pilot uses the accepted immutable 0.1.0-alpha.3 artifact from source 28c. Later canonical source at 0c2 is not installed automatically. The fleet and its installed user-system schedule timer are manually paused; automatic AI wakes remain paused. Pipeline execution, isolated candidate-executor assurance, and production acceptance remain open.
Experimental source install for developers. You need Git, Node.js 22 or later, and npm. Linux is the current self-host pilot environment; other platforms are not yet qualified.
+Clone the rewrite branch, not the repository’s default branch. This installs the current development source, not the separately accepted pilot artifact. There is no stable release install promised here.
+The isolated prefix below avoids overwriting an existing TORCH installation. The PATH change lasts for this terminal; add it to your shell configuration only if you want to keep using this source install.
+git clone --branch rewrite/portable-agent-fleet \
+ https://github.com/PR0M3TH3AN/TORCH.git
+cd TORCH
+npm ci
+npm install --global --prefix "$HOME/.local/torch-source" .
+export PATH="$HOME/.local/torch-source/bin:$PATH"
+torch --help
+ Review source and dependencies before installing. These commands install the CLI only; they do not create or start a fleet. Already have TORCH? Use your existing installation’s reviewed update flow instead.
+Point TORCH at a Git repository and, if useful, a product specification. It prepares an evidence brief for a fleet proposal; installing or starting the team waits for your review and approval.
After installing the CLI, generate a baseline proposal from your project directory. Review domains, ownership, checks and unresolved gaps. In the proposal, set review.status to approved and record review.reviewedBy and review.reviewedAt only after your review.
The example selects Codex. Install and sign in to your chosen agent CLI separately; model access depends on your account. Each session’s runtime and model can be changed later.
+Preview installation and worktree setup first. Setup creates configuration and worktrees but does not launch agents. Starting agents and installing host schedules are separate approvals.
+Read the full setup, runtime configuration and uninstall guide.
+cd /path/to/project
+torch design --output fleet-proposal.json --json
+# Review and approve fleet-proposal.json before continuing.
+torch install --proposal fleet-proposal.json \
+ --runtime codex --dry-run --json
+torch install --proposal fleet-proposal.json \
+ --runtime codex --yes --json
+torch setup --dry-run --json
+torch setup --yes --json
+torch up --fresh --dry-run --json
+ The last command previews startup only. When you are ready to use your provider account, explicitly run torch up --fresh --yes. Check the plan and required gates first.