Private code-change application
Step 1
Weaver indexes names and metadata first. File contents are read only when a change-set needs them.
Read-only copies of the four Weaver role prompts for ordinary AI chats: Strategist, Documentarian, Builder, and Validator. Everything is embedded in the application shell — no files are fetched and nothing leaves this device.
Plain-language definitions of the terms used by Weaver and the prompt pack.
Select a folder to validate and apply changes in place. Your browser will ask for permission only after you click.
Use this when direct folder writing is unavailable. Weaver can still simulate, preview, copy, and download results.
Browsers cannot reliably represent a completely empty folder through this fallback.
Directories listed here are not indexed. Changing them after selection requires re-indexing.
Change this list before selecting a project. Reselect the folder after editing it.
Select and index a project to continue.
Direct writing generally requires a Chromium-family browser, HTTPS or localhost, and the File System Access API.
Weaver’s service worker caches only its explicitly declared application shell—never project files, imported JSON, reports, downloads, or snapshots.
Browser filesystem operations are not atomic. Weaver revalidates files and captures rollback data, but an independent backup remains the strongest protection.
Checking install and offline capabilities…
Snapshots remain local and are not removed when you start a new task.
Step 2
Paste JSON, choose a UTF-8 JSON file, or drop one below. Editing it invalidates any prior preflight.
Add JSON to prepare for preflight.
Drop one JSON file here
or
Step 3
Every operation must pass before Weaver permits writing.
Run preflight to determine the next available step.
Step 4
Line numbers are for display only and are never used to apply changes.
Review the resulting files before continuing.
Step 5
Weaver will verify project, policy, JSON provenance, and every affected path before writing.
Browser writes cannot be one atomic transaction. Weaver captures a rollback snapshot and attempts restoration if a write fails.
Apply remains unavailable until all safety checks are current.
Step 6
Copy this report back to the separate AI Builder if diagnosis is needed.
Review and preserve any needed results before starting another task.