Skip to content

Autonomous development for real products. Governed agents build from specs you approve, follow the rules you set, and nothing merges until another agent proves it. Your decisions, judgement and taste are the bar that work must clear. Declare your vision and let agents build it.

feat(merge): a claimed item whose files grow is [C7,N2,H16,B7,B13]

Corey Olsonf7b0ad7d12e5
diff --cc docs/formats.md
index e6cc9422,bca6f86f..075e875f
--- a/docs/formats.md
+++ b/docs/formats.md
@@@ -113,7 -113,7 +113,7 @@@ The board file is in the repository's G
| `row grammar` | `1` | `SPEC_GRAMMAR_VERSION` in `src/spec.js`; optional `<!-- pullboard-grammar N -->` line in either file (absence means the current grammar) | Both files share the version. A declared version must match; an incompatible grammar change requires a coordinated version bump and compatible files. No automatic conversion occurs. |
| `board schema` | `3` | `SCHEMA_VERSION` in `src/board.js`, persisted as `PRAGMA user_version` | On a write open of a board whose version is behind: create missing tables and indexes (version 3 adds the hot-path indexes), add missing columns in place with declared defaults, restore missing or changed triggers, and remove stale machine triggers without replacing rows. Read opens never migrate; a board at the current version whose shape differs is reported once on stderr and left as it is. |
| `event log` | `1` | `EVENT_LOG_VERSION` in `src/board.js`, persisted in `board_meta` as `event_log_version` | Older event-log versions upgrade in place; newer versions are refused with `EVENT_LOG_VERSION`. Preserve event rows when the board schema changes. |
- | `move engine` | `98` | `ENGINE_VERSION` in `src/machine.js`, carried as `engine` in every sealed executable move | Bump when a move's meaning changes, independently of the event log and sealed envelope. A newer engine is refused with `ENGINE_VERSION`, naming both versions and asking you to upgrade Pullboard. |
-| `move engine` | `97` | `ENGINE_VERSION` in `src/machine.js`, carried as `engine` in every sealed executable move | Bump when a move's meaning changes, independently of the event log and sealed envelope. A newer engine is refused with `ENGINE_VERSION`, naming both versions and asking you to upgrade Pullboard. |
++| `move engine` | `99` | `ENGINE_VERSION` in `src/machine.js`, carried as `engine` in every sealed executable move | Bump when a move's meaning changes, independently of the event log and sealed envelope. A newer engine is refused with `ENGINE_VERSION`, naming both versions and asking you to upgrade Pullboard. |
<!-- format-versions:end -->
A builder never picks an engine number (#1101). An item that adds a board move adds its own `src/<name>-engine.js` leaf as `export const NAME_ENGINE = unassignedEngine();` (importing `unassignedEngine` from `./engine-next.js`); on its branch the leaf reads as one above the highest landed engine. The landing merge writes the next number into the leaf, in landing order, inside that item's merge commit, and sets the `move engine` row above to the highest landed number. A landed number never changes, so recorded moves replay as they were written. Moves are recorded under landed numbers only: code with an unnumbered engine is for its branch's own tests, and a move it records on a real board before landing may later read under another item's number, so the item lands before its moves are used.
@@@ -555,63 -541,12 +555,71 @@@ These are recorded inputs only (#1096)
Landing queue grants, first queue entries and releases are shared ordered transitions. New landing-local-heartbeat engine moves leave renewal and repeated-poll events out of history; old engine receipts keep their recorded meaning. `local:landing-lease:<token>` board metadata binds a physical board id, token/generation, process, branch and coordinator lineage to its local deadline. It is excluded from exports, imports and semantic digests and is retained only on the receiving physical board during a same-board relay snapshot restore. A linked foreign holder has no clock-based expiry: release or coordinator takeover fences it; local heartbeat deadlines never authorize another machine to merge.
+
Engine 93 adds item-addressed shouts. A shout move's optional `item` names an existing item; its event belongs to that item and includes the message text. Its canonical `shout_to` is `item:<id>`, read by the item's current builder and reviewer and the coordinator. Inbox, resume and seat watch use the same audience; an explicit seat or lane destination with `--item` still uses the item's audience. An item decision is answerable by its current participants or coordinator; replies stay in its thread and audience. The coordinator can still pass it to the person through the existing decision flow. A registered seat's shout to `all` is accepted and stored at reserved address `coordinator+person`, read only by coordination audiences. The plus sign cannot occur in valid lane names or their derived seat ids. Coordinator and person broadcasts retain `all` and reach everyone; recorded older-engine `all` rows retain their original global meaning without a retrospective sender filter. Main-checkout watch remains the person's board-wide observer. A joined seat's default watch filters shouts to its own address, lane, items and `all`, while ordinary lifecycle events remain visible.
+### Outside intake and sandbox receipts
+
+`pullboard intake <GitHub PR URL> --criterion "behavior" --check "command"`
+reads GitHub metadata and fetches the exact server-owned pull ref. It records an
+outside author (`outside:github:<login>`), commit, tree, source state and maintainer
+reply, and enters `submitted` without claiming that a native builder gated the PR.
+No contributor program is checked out or executed on the host. An issue URL records
+an open local source item; the GitHub issue closing does not accept the local item.
+Repeating intake refreshes source state and replies. A PR head can change only after
+normal return to open; re-intake invalidates its earlier sandbox proof and owner
+approval. Native agents cannot claim or submit an outside PR as their own build.
+
+Public source facts are in `board_meta` under `outside:<item-id>` and appear as
+`outside` on `show` JSON. Ordered `intakeOutside` and `approveOutside` moves retain
+`outside-intake`, `outside-refresh` and `outside-owner-approval` events. Approval is
+person authority bound to the exact commit, not an agent or parent-session claim.
+These facts survive board export and ordered replay. The local container logs are
+beside the board in `outside-check-output/<item-id>/<receipt-id>`; an ordered accept
+must match the executor's exact local receipt and output digests before transport.
+
+Sandbox verification reads operational provider settings from committed trusted
+main, not from the PR's configuration. `sandbox.provider` is `docker`,
+`sandbox.executable` is an absolute Docker-compatible CLI path, `sandbox.endpoint`
+is an explicit Unix daemon socket, and `sandbox.images.minimum` and
+`sandbox.images.current` are immutable `<image>@sha256:<digest>` references selected by trusted main.
+Prebuilt Node+Chrome images are supported for browser gates; outside heads cannot
+choose runtime images, and actual container Node versions must still match both roles. Images
+must already be present; verification uses `--pull never`. The actual container
+must report Linux Node 22.13.x and Node 24.x respectively, the two roles in the
+committed CI matrix; this is not a claim about the latest global Node release.
+Each role executes the trusted full gate and frozen criterion, with the criterion
+also required to fail at the recorded base. Protocol stand-ins in unit tests are
+not evidence of real containment or actual image execution.
+
+Every container has no network, an empty temporary HOME, a read-only root and
+private source export, no added capabilities, and no host credential environment.
+The Docker client has a fresh empty configuration and explicitly constructed
+environment. The source export contains independent exact-commit Git objects and
+files, never an operational checkout, its board database, worktree pointer,
+alternates or credential state. It is copied into a temporary writable container
+work directory. Exports default beside the native board under `sandbox-exports`;
+`sandbox.exportRoot` may name a private absolute directory shared with a VM-backed
+Docker daemon. Only a newly created child is exported and cleaned up. Missing
+runtime, inaccessible export or cleanup failure refuses; no host-process fallback
+is available. Normal physical gate/browser admission still applies.
+
+Owner-sensitive reasons are retained as `outside.sensitivity`, each with `path`,
+`rule` and `detail`; `outside.sensitive` is true when any reason matches. Defaults
+cover relay, sealing/signing/keys, person-move and hook code, hook configuration,
+`bin/`, CI workflows and command-bearing package fields. Trusted main may extend
+this with `intake.sensitivePaths`, relative exact files or trailing-slash prefixes;
+contributions cannot remove the defaults. Newly added process imports/calls or
+shell-runner calls and unreadable changed files also require approval. Renames
+retain both old and new touched paths. Ordinary source is not sensitive merely
+because it is source. The owner runs `pullboard intake approve <id>` through the
+person channel before sensitive work can land. Intake has no autonomous posting
+operation; each future result post still needs the person's separate OK.
++
+ `FILE_GROWTH_NOTICE_ENGINE` adds atomic notices to an ordered brief edit: newly named
+ files on a claimed or submitted item are checked against lease-normalized claimed,
+ submitted and accepted-not-landed work. Each distinct holder receives one system
+ notice per overlapping item, linked to its item thread; the edit remains allowed.
+ Unchanged paths, prose, reordered lists and removals do not resend notices. Older
+ recorded edits retain their silent behavior. The unassigned feature leaf receives
+ its number at landing; no event-log or envelope format changes.
diff --cc src/board.js
index 15c5b46e,24c78f0a..132c0bac
--- a/src/board.js
+++ b/src/board.js
@@@ -1,16 -1,4 +1,17 @@@
+export { lineSettings, setLineSetting } from './line-settings.js';
+
+import {
+ applyOutsideIntake,
+ approveOutside as applyOutsideApproval,
+} from './outside-store.js';
+import {
+ outsideSandboxProblem,
+ outsideBuildProblem,
+ outsideSource,
+ requireOutsideOwner,
+ saveOutsideSource,
+} from './outside-source.js';
+ import { FILE_GROWTH_NOTICE_ENGINE } from './file-growth-notice-engine.js';
import {
recordBarRevision,
barReadyProblem,
@@@ -97,14 -84,14 +98,18 @@@ import
mkdirSync,
} from 'node:fs';
import { dirname } from 'node:path';
--import { sharedSchemaOwner } from './board-schema.js';
--import { expectedBoardSchema } from './board-schema.js';
--import { sharedSchemaDiagnostic } from './board-schema.js';
--import { reportSharedSchema } from './board-schema.js';
++import {
++ sharedSchemaOwner,
++ expectedBoardSchema,
++ sharedSchemaDiagnostic,
++ reportSharedSchema,
++} from './board-schema.js';
import { DatabaseSync } from 'node:sqlite';
--import { boardNotWritable } from './board-access.js';
++import {
++ boardNotWritable,
++ boardBusyError,
++} from './board-access.js';
import { ensureHotIndexes } from './board-hot.js';
--import { boardBusyError } from './board-access.js';
export { boardBusyError } from './board-access.js';
import {
boardStanding,
@@@ -204,17 -192,17 +210,19 @@@ import
landingWaiverKind,
} from './landing-exceptions.js';
import { parseSpec } from './spec.js';
--import { invariantEvidence } from './submit-invariants.js';
++import {
++ invariantEvidence,
++ preserveInvariantEvidence,
++ validateLandingBatch,
++ validateLandingRevision,
++ submissionProof,
++ SUBMISSION_PROOF_ENGINE,
++} from './submit-invariants.js';
import { landingBatches } from './landing-batch-history.js';
import {
NATIVE_FLAKE_ENGINE,
carriesFlakeDiagnostics,
} from './flake-engine.js';
--import { preserveInvariantEvidence } from './submit-invariants.js';
--import { validateLandingBatch } from './submit-invariants.js';
--import { validateLandingRevision } from './submit-invariants.js';
--import { submissionProof } from './submit-invariants.js';
--import { SUBMISSION_PROOF_ENGINE } from './submit-invariants.js';
export { landingFlakes, landingWaiverCovers, landingWaiverKind };
export { landingWaivers, landingWaiverFor, waivedLandingProof } from './landing-waivers.js';
export { acceptCheck } from './check-accept.js';
diff --cc src/file-growth-notice-engine.js
index 00000000,7a485a0f..f8a4ab02
mode 000000,100644..100644
--- a/src/file-growth-notice-engine.js
+++ b/src/file-growth-notice-engine.js
@@@ -1,0 -1,3 +1,2 @@@
+ /** Ordered file-growth notices preserve historical edit replay [N2,B7,B13,H16]. */
-import { unassignedEngine } from './engine-next.js';
-export const FILE_GROWTH_NOTICE_ENGINE = unassignedEngine();
++export const FILE_GROWTH_NOTICE_ENGINE = 99;