Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Rollout and remaining work

Single-repository completion

The shared dependency workflow is qualified and enabled for Notebook after its genuine Core0.13.5 development intake, complete candidate/main CI, native auto-merge, Pages and repeated normal reconciliation. Other repositories remain independent adoption work. Notebook, Spec Validator, Visual Delta, Terminal, Registry, Plugins, Agent UI, AI, JJ Store, Notes and Server are source pilot policy entries; the first five have completed their applicable live/replay acceptance. Global phase stays pilot with hourly scheduling enabled. Promoting one reviewed entry from full to pilot enables that repository independently, without a global full rollout.

Server source103 is merged and its exact-main CI, hash-tagged image, Pages and normal completion callbacks pass. Per-entry eligibility retains its measured empty-note convention and all registry/migration/source/audit holds; full normal reconciliation and replay remain pending under adoption58.

Acceptance requires a genuine compatible Core update, shared canonical preparation, current PR and main qualification, source-owned version/release disposition, Pages, automatic completion/catch-up and idempotent repeat runs. A development-only update must retain no publication intent; it cannot stand in for evidence that an npm publication occurred. Existing genuine publication evidence and any unexercised release branch remain explicitly distinguished.

Remaining repository adoption belongs in separate assignable tasks with the same checklist, exact source evidence, repository-specific blockers and activation/rollback steps. Community, Nostr and Deno-only packages stay excluded.

Tracker50 now links sixteen separately assignable adoption tasks. The common adoption runbook defines source inspection, shared pins, independent qualification, per-entry activation, replay and rollback. The tracker records the completed pilot separately from remaining adoption; creating tasks does not enable writers.

The detailed maintenance plan owns delivery steps and dated receipts. This page explains scope without embedding live operational data in the public book.

SliceCurrent boundary
S1 Policy/authenticationShared monitoring, read-only audit/probes and the isolated scheduled profile writer are qualified. All eligible version writers have migrated and passed their main App/Changesets jobs; genuine Plugins and profile candidates also started CI and merged.
S2 Image churnShared signed producer/resolver is qualified in Plugins and Notes, including full warm/repeated-producer acceptance and Notes production deployment. Both obsolete image-pin PRs are closed.
S3 Dependency wavesNotebook proves compatible development intake, native auto-merge, current-main completion and repeat reconciliation; hourly single-pilot scheduling is enabled. Other consumer/release-chain adoption remains independently tracked.
S4 Maintenance integrationThe deployed app reads monitoring policy, waves and open issues and supports confirmed eligible batches. Real report parsing and a disposable live command/preflight test are qualified; visual review remains separate.
S5 Publication recoveryRegistry preparation and publication are separate. Immutable artifact reuse, unchanged replay and rejection before writer minting are hosted-qualified; a genuine three-plugin batch is deployed and its public signatures verified. Package publishers retain source authority.
S6 Tooling/driftNode CLI contracts, initial source cohorts, candidate guards, operational drift reporting and exact advisory admission are deployed. Additional cohorts and consumer whole-recipe guard adoption remain in progress.

No row in this table authorizes additional writes, activates a parked host or waives a product/audit gate. Current source qualification is recorded in the verification matrix; hosted and downstream evidence remains separate.

S6 now has a source implementation for Node-only version preparation, central cohort observations and candidate drift rejection. Hosted qualification and consumer adoption remain separate; existing frozen Deno host sources and all advisory exception rules remain unchanged.

S6b adds production maintenance drift reporting and exact coordinator advisory admission before dependency write planning and App minting. The earlier LOW decision is retired. The separately approved HIGH picomatch decision covered two exact runtime paths/source/lock bindings through November19,00:00UTC or sooner on a known fix; Issue71 owned remediation and retirement, and pilot success could not renew it. Those exact approvals are now retired after upstream withdrawal and zero-finding audit evidence, restoring the empty approval list. Consumer adoption and source-owner treatment of reported unknowns remain separate; a matching static check name is not complete qualification.

The bounded canonical-intake preparer and Notebook source opt-in are hosted qualified through44, including strict native committed-payload and unchanged consumer guard checks. The single-pilot evidence record retains exact source/run/state receipts and distinguishes the correct no-publication outcome from an actual npm release. Source verification still preserves unrelated peer edges and holds ambiguous contexts.

Successful same-source package recovery preserves retained signed artifacts and verifies existing registry bytes before resuming failed qualification. Automatic registry install-metadata readiness remains a concrete S5 maintenance follow-up; manual recovery is not completion of that automation. The bounded Notebook pilot under DA-WAVE-007 retains every unrelated publisher wait while qualifying only its source-authorized development patch. Other source profiles, publisher contracts and unsupported migrations remain independent adoption work.

The next small-repository slice registers Spec Validator’s existing Check workflow and Visual Delta’s existing CI, PR-specification, Pages and version workflows by exact IDs, paths and supported events. The read-only App probe adds only those two exact targets. Tag publishers, native capture, image publishers and callback self-triggers are not completion sources; verified npm notifications remain separate. Registration74 initially retained phase full for both repositories pending merged source acceptance and separate activation/replay, now recorded below. Spec Validator currently consumes no Lapis npm dependency; no synthetic Core pin or version recipe is introduced to create an update. Visual Delta consumes only the Deno-free specification tool in development and retains its existing audit and compare-only browser gates. The operator requests a final merge pass and gives standing approval for per-repository activation after passing source acceptance; advisory exceptions and global full rollout are not implied.

The operator-approved next activation adds only Spec Validator after its source7 mergedf3bab11837648045540bf7ef948503131dcab041 and main Check44174151693 passed. Read-only existing-App probe44173967888 passed. Its normal functional no-Lapis-input contract preserves the current zero-update graph; no Changesets writer, dependency bump, version/tag or publication is invented. Notebook remains the sole exercised dependency-writing consumer; all other entries and existing holds/exclusions remain unchanged, and global phase stays pilot. Actual completion, ordinary no-update settlement and repeat receipts are recorded in the source activation record; source registration alone is not claimed as a new publisher or multi-consumer update proof.

Spec Validator activation75 is deployed at8c71f71d. Exact-main checks, live Pages and completion-driven run44176226486 pass; its current sourcef3bab118 is qualified with no updates, holds or waits. The active no-op operation is unchanged, and durable state matches the hosted candidate. This is producer/ no-input adoption, not an invented dependency update or new package release. The owned source audit follow-up is Spec Validator8, separate from activation.

Ordinary replay44177306438 retains the same unchanged operation after the first post-activation run44176226486. Generations171→172 form the expected durable state chain and both published states match their hosted candidates. No dependency PR or package release is created; Spec Validator adoption62 is complete. Existing development-tool remediation remains separately tracked in Spec Validator8. At that Spec Validator handoff, fifteen repository adoptions remained open; Visual Delta is now completed below and fourteen adoption tasks remain open; this is not global full rollout.

Visual Delta adoption79 and activation77 are deployed after current source acceptance. Ordinary runs44182784733 and44182833366 qualify e755e2a0 with no updates, holds or waits, retain the same unchanged operation and form the verified durable state chain178→179. Exact source, Pages, artifact and state receipts are in the activation record. Notebook, Spec Validator, Visual Delta, Terminal and Registry are the pilot entries; other entries, exclusions, global phase and holds remain unchanged. Visual Delta’s independent guard admits only compatible Node-only validator0.2 development patches. No new dependency update or publisher execution is claimed.

VD-GOV-008 continues to gate audit remediation and package publication. The earlier blanket maintenance hold was too broad; the existing unapproved HIGH remains a publication blocker. This adoption does not change audit collectors, waive a finding, rebind an exception or authorize tags, uploads or baselines.

Visual Delta80 owns its separate publication audit remediation; completed adoption63 does not waive that finding. Docs21 and Tasks31 previously retained required audit failures that cleared after the same upstream advisory withdrawal.

Parallel completion pass

Thirteen eligible adoption tasks remain after excluding Agent Redaction64 under the operator’s any-Deno-package boundary. Independent source batches cover foundations/plugins, native/server packages and applications/registry. Docs and Tasks previously retained required Changesets/picomatch audit failures; those consumer findings cleared after upstream advisory withdrawal. The coordinator exception is retired to an empty approval list and cannot authorize consumer gates by inheritance. Only reviewed individual source acceptance permits the subsequent per-entry activation, ordinary settlement and replay.

Terminal and Registry activation

The operator’s standing post-merge approval promotes only Terminal and Registry from full to pilot after their current source/main/callback acceptance. All other phases, global pilot settings, exclusions, source holds and advisory bindings are unchanged. Exact evidence belongs in the activation record.

Terminal source27 merged50d1bb9f with qualified macOS CI, spec Pages and actual false version intent. Its independent Core0.13 development-patch guard qualifies the real released0.13.4→0.13.5 candidate, including the no-note full version recipe; the coordinator’s empty-Changeset flag remains unchanged. Registry source184 merged69d8c063, passes current Checks/signed publication and actual callbacks, and retains its private API0.1/no-version contract. Its upstream API publication wait remains binding; activation does not waive that prerequisite or claim an invented npm release. The live acceptance record now proves Terminal’s genuine Core update, current-main/no-intent completion, durable settlement and unchanged repeat. Registry’s qualified no-update repeat retains its API prerequisite and unexercised dependency-publication branch. These two adoption tasks may close; all other source work remains separate.

Plugins and Agent UI activation

The operator’s standing post-merge approval promotes only Plugins and Agent UI from full to pilot after exact-source, current-main and verified completion acceptance. Their existing empty-Changeset settings stay unchanged: each real version recipe correctly returns false intent without a forced empty note. All other phases, holds, exclusions, global pilot settings and exact advisory bindings remain unchanged. The source activation receipt records their independent evidence. Ordinary live reconciliation and repeat remain required; unavailable upstream publication floors are not waived, and no dependency update, version PR or publication is invented to force activity.

AI and JJ Store activation eligibility

Standing post-merge operator approval promotes only AI and JJ Store from full to pilot after independently green source adoption and whole-recipe acceptance. Both entries add the proven emptyChangeset: true capability: an actual managed empty note lets the source CLI classify supported development intake without inventing version or publication intent. Their real no-note macros alone do not prove the changed-candidate guard succeeds. The bounded activation receipt retains those separate controls and exact current-main observations.

This is eligibility, not a current-main qualification override. Pending or failed current CI, source/audit policy, ownership and publication prerequisites still hold actual writes and release-chain advancement. Existing seven pilot entries, every other empty-note setting, exclusions, holds and global pilot gates remain unchanged. Ordinary live reconciliation, exact settlement and repeat acceptance remain open until their own receipts exist. The user’s unrelated JJ Store main/release repair exclusion does not alter the collector or assert a pass.

Notes activation eligibility

Standing post-merge operator approval promotes only Notes from full to pilot after source155 merged with all required checks passing. Its existing measured emptyChangeset: true flag remains unchanged. Source policy limits supported inputs and preserves frozen hosts; publisher/channel/audit authority stays with the source. The activation record separates source acceptance, current-source release preparation and the live publication attempt. Pending current CI and upstream/publication waits continue to hold writers. Existing nine pilot entries, all other flags/holds/exclusions, empty artifact capabilities and global pilot/schedule settings are unchanged. Actual publication proof, ordinary live settlement and repeat remain required; policy eligibility alone does not complete adoption53.

Mira, Design Core, Tasks and Docs activation

Standing post-merge operator approval promotes only Mira, Design Core, Tasks and Docs from full to pilot after independently green source adoption, current-main checks and verified completion callbacks. Mira retains its existing emptyChangeset: true flag; the other three introduce no forced empty note. Desktop’s private-archive holdReason, every Deno/community/Nostr exclusion, every other phase/flag and global pilot settings remain unchanged. Active advisory approvals stay empty after the picomatch retirement. The source activation receipt records their independent evidence. Ordinary live reconciliation and repeat remain required; retained branch-ownership holds and upstream publication waits are not waived, and no dependency update, version PR or publication is invented to force activity.