The user chooses a folder, establishes a baseline and presses ARM. Reloading destroys the in-memory directory handle.
2XBR PROJECTS / WATCH / VISIBLE TABRun when the
Run when the
work changes.
Choose a project, choose a local folder and explicitly arm its WATCH engine. New or modified files run the pinned recipe locally; deletions become evidence. No hidden browser daemon, background presence or invented BRIDGE filesystem capability.
Open project watch →PROJECTPINNED RECIPE→FOLDERUSER PICKER→CHANGEVISIBLE TAB→RUNBOUNDED→EVIDENCEPASS / BLOCK
DISARMEDTAB VISIBLENO FOLDERCHOOSE A PROJECT + FOLDER
Choose the repeatable work.
Create a PROJECT first.
OPEN PROJECTS →Establish a local baseline.
The directory handle stays in this tab memory. Reloading the page requires choosing the folder again.
Arm only when you mean it.
3.5sVISIBLE-TAB POLL / MAX 20 CHANGED FILES PER CYCLE
No service worker, no background daemon, no BRIDGE filesystem capability.
04 / LAST RUN RESULT
No change run yet.
05 / SESSION EVIDENCEMemory-only watch history
No events yet. Establish a baseline and explicitly ARM the watcher.
Polling is scheduled only while the document is visible. WATCH does not register a service worker, background sync or persistent filesystem daemon.
More than twenty runnable changes in one cycle disarm automatic execution and require review instead of silently processing a change storm.
The accepted WEB/BRIDGE contract has no approved filesystem-watch capability. Native background watching requires a separate cross-product ADR and permission model.