# Artifact — the published Field Note (publicly inspectable)

The DO NOT STOP mechanism is not only internal doctrine: it is the subject of a public FoundryOS
Field Note, which anyone can read and check against this package.

## Pointer

- **Title:** FOUNDRYOS FIELD NOTE 01 — *DO NOT STOP!*
- **URL:** <https://foundryos.ca/articles/do-not-stop/>
- **Published:** July 28, 2026
- **Status when this package was built (2026-08-02):** live and publicly reachable (verified by
  fetch during package build).

## What the Field Note asserts (matches the artifacts here)

The Field Note makes the same argument this package evidences: when an agent announces continuation
and then ends the turn, the fault is the **enforcement location**, not the prompt wording. FoundryOS
moves enforcement to a **Stop hook** — a lifecycle boundary in Claude Code — that inspects the final
message for a contradiction between stated continuation and the act of stopping, then blocks the
stop with **exit code 2** and injects a pre-authored decision policy so forks resolve autonomously
rather than interrupting the user. That is exactly the `check-session-stop-contract.mjs` /
`check-audit-loop-terminal.mjs` behaviour excerpted in `enforcement.md`.

## The Field Note's OWN stated limitations (reproduced faithfully, not invented)

The published article states its honesty boundaries plainly. Paraphrased from the live page:

- It is **not a replacement for `/goal`** (Claude Code's native completion-condition tool).
- It makes stopping **"expensive and recorded, not impossible"** — a determined model can still find
  a way to exit. The mechanism is a forcing function, not a proof.
- The **evidence population is small** — on the order of 8 catches across 4 sessions / ~17 hours; it
  is explicitly *not* a controlled benchmark.
- It does **not** establish mechanically-proven task completion, universal zero-human operation,
  perfect premature-stop detection, or that a run will continue indefinitely.
- It does **not** claim universal applicability across all workflows or agents.

These limitations are carried into this package's own `README.md` and `manifest.json` so the
evidence package cannot over-claim relative to the article it links.