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

Dependency and release waves

DA-WAVE-009 is an inactive, separately granted SDK-only selected view. The artifact-generation opt-in alone does not waive any source admission hold.

DA-PUB-005 may retire an Agent UI publication wait only after exact tagged-cohort verification; its source publisher and main-only completion gates remain distinct.

The schema2 workspace canonical capability applies to ordinary admitted compatible patches across explicitly covered manifests. It verifies source policy bytes, active importer coverage, current locked facts and exact registry targets before writer admission. A wait on the selected dependency remains binding, but a wait on a different dependency MUST NOT contaminate a complete policy-mapped edge merely because both share one manifest; the unrelated wait remains visible and continues to block its own update. Only the existing schema1 development profile retains the broader separately bounded independent-wait behavior.

Wave admission is implemented behind LAPIS_DEPENDENCY_WAVES=true, default off. Hosted pilot qualification and activation remain separate operator decisions.

The reviewed configured Profile publication binding retires only its own genuinely newer, fully verified and currently qualified release. Direct Profile selection is separately restricted to Server’s root runtime dependency scope; that scope cannot bypass source compatibility, dependency floors, channel drift or replay/CAS gates, and does not admit another Profile consumer.

An existing waiting release intent MUST retain an actionable direct runtime or optional-runtime manifest-minimum repair when a compatible simple caret/tilde range still starts below its exact required target, even if an incidental lock refresh already installed that same currently eligible target. Only the same public package/repository/field intent qualifies. Missing or settled intent, private packages, peers, development fields, catalogs, compound/custom ranges, changed targets and newer installed versions MUST NOT create this repair. The ordinary candidate, source/ownership/rollout and newer verified publication-floor gates remain required; no release wait is cleared from a lock update alone. An unobserved admitted operation MUST remain uncertain across unrelated source changes until both its retained minimum and lock target are observed on main; a newer source SHA and matching lock alone MUST NOT assert completion. Independent channel/provenance publication holds MUST remain visible while a retained manifest-minimum repair is actionable; their visibility alone does not authorize a downstream update or suppress an eligible upstream repair.

The exact November18 Notes cohort refresh retires only freshly verified publication/channel waits under the existing scoped contract; current-main CI, upstream dependency floors and source-owned intake remain binding. Origin and recovery attempts retain the same artifact identity, without a new operation or synthetic publication.

The November19 identity refresh advances those same four scoped Notes pins to the exact current publisher source and attempt3-verified artifact. Wave planning may use API0.6.10, UI0.2.6 and Workspace0.4.9 only on their pre-existing paths, and Profile0.2.7 only for Server’s root runtime scope. File Explorer0.2.8, default latest, all scopes and independent waits remain unchanged. A read-only projection may prove Server admission, but only merged-source reconciliation can create its actual operation and writer target.

Canonical schema2 preparation checks target availability through the same exact repository/path/dependency-type reviewed channel projection as wave planning. Raw latest-only availability stays unchanged; valid scoped next patches do not become unsupported solely because they are absent from that raw pool. It may isolate an otherwise complete selected edge from an unrelated package’s same-manifest wait without deleting that wait. A selected-dependency wait, current source qualification and every other admission gate remain binding.

DA-WAVE-001 — Derived admission

Requirement. Wave admission MUST derive update and public release chains from exact manifest, lockfile and registry evidence before selecting consumer targets.

Acceptance details

  • Runtime, optional-runtime and peer changes use the existing release-intent contract; dev-only updates do not create publication waits.
  • Every required publisher must qualify and publish a newer registry version carrying the intended dependency contract before its downstream wave proceeds.
  • Explicit holds, excluded packages, unknown locks, unavailable prerequisites and cyclic release chains remain visible and fail closed.
  • Package/path admission MUST move catalog references jointly while retaining the existing compatible rolling PR and breaking-family drafts.

DA-WAVE-002 — Durable reconciliation

Source-advanced recovery requires an operator-supplied exact current SHA and complete public trees at both immutable revisions. Only regular documentation, workflow, version-guard configuration and test blobs may differ; package, lockfile, workspace, policy and implementation changes reject recovery. Truncation, unavailable trees, duplicate/unsafe paths, changed symlinks and missing source bindings fail closed. Recovery records both revisions and the unchanged projection digest; fresh normal admission still owns target scope. Reports remain ignored artifacts; no live state enters main or public book output.

Partially absorbed operation reconciliation is a separate manual decision, not source-advanced empty recovery. It requires an exact stored operation and state revision, its completed originating run, qualified advanced public source and proven empty dependency branch, PR and orphan state. The ordinary retained minimum, peer-support and lock predicates MUST divide the old targets into a strict nonempty absorbed subset and a strict nonempty remaining subset. The partition and current source are durable state evidence; fresh ordinary planning alone may admit the remaining targets. None/all partitions, stale state, unqualified source and repair ownership MUST reject without changing state.

Requirement. Versioned wave state MUST reconcile registry observations, source revisions and operation identities independently of notification delivery order.

An unrelated observed PR MUST NOT clear an uncertain operation. Each retained target requires bot-owned branch-family and exact public candidate-head evidence covering its manifest/lock tuple; missing candidate data and empty historic targets remain uncertain until explicit recovery. A later compatible candidate may cover an older target without relaxing minimum or peer-support requirements. Candidate observation MUST evaluate resolved targets through the same exact repository/path/dependency-type reviewed channel projection that admitted the operation. Raw latest availability cannot strand a genuine scoped-channel PR, while stale, forged or out-of-scope channel evidence remains unobserved. A failed candidate may prove that the writer created the owned branch without qualifying that head for merge. The state writer MUST record that exact observation before a new operation may rewrite the rolling dependency PR, so the later head cannot erase evidence for the older operation or resurrect its uncertainty. Ordinary retry, current-head CI and merge gates still apply.

For state written by an older planner that admitted the successor without the new receipt, a different same-repository operation with a strictly later writer run is itself durable proof that the older operation passed observation: the planner cannot assign that later run while an unobserved earlier operation is unresolved. This backfill MUST require both stored run identities, MUST NOT infer from planned or held operations without a writer run, and grants only the same observed-on-branch outcome.

Public reports MAY include a bounded presentation-only attention projection derived from existing holds, waits, qualification and ownership evidence. Each entry retains a stable category, remediation and validated public coordinates without granting command authority or replacing immutable evidence. The projection MUST be derived only after the node’s current status and holds are final, including unresolved-operation detection. A published package awaiting reviewed-channel admission or an unreviewed publisher contract MUST remain distinguishable from a missing publication and MUST NOT instruct an operator to publish the same bytes again.

Acceptance details

  • Registry-verified version/integrity identities coalesce duplicate hints; complete scheduled scans recover missed events without treating payloads as authority.
  • Persistent operations retain exact targets, source/policy revisions, publication baselines and blocked/failed/uncertain outcomes for future operator UI use.
  • State lives only on the dedicated coordinator state branch, with optimistic concurrency and read-back after uncertain writes; conflicting state is never overwritten or blindly retried.
  • Exact manual recovery MAY re-admit only a completed originating run with proven empty branch/PR state and unchanged public source or an explicitly bound current revision with complete immutable-tree proof of unchanged implementation and dependency inputs; separate exact manual operation reconciliation MAY terminally partition only a completed empty admission whose qualified advanced source already satisfies a strict subset of its targets, without classifying changed inputs as unchanged recovery or directly granting the remaining writer operation.

DA-WAVE-003 — Qualification and repair ownership

The accepted initial single-repository pilot selected Notebook in source pilot phase. Other consumers remain observable, including through already deployed verified completion callers, but cannot enter the pilot writer matrix. Enabling the schedule does not promote full entries or bypass candidate/ownership checks.

The next standalone-plugin wave prepares Docs/Tasks completion observation without changing those writer phases. Their source-owned full-audit gates previously reported an unapproved HIGH Changesets/picomatch finding; that advisory was withdrawn upstream and fresh consumer audits are clean. The retired coordinator-only runtime approval never authorized consumer findings.

Requirement. Reconciliation MUST preserve manually repaired branches and require complete current revision qualification before advancing release chains.

Acceptance details

  • Repair/orphan holds MUST apply to their exact rolling or publisher compatibility family while ambiguous history remains held.
  • Genuine PR creators and every branch commit author MUST establish ownership independently of rerun actors.
  • Auto-merge MUST require complete current workflow/check/status qualification for the exact existing candidate on current source, with default-branch qualification evaluating the latest run for every active push workflow and independent external checks/statuses while manual, scheduled or otherwise non-expected GitHub Actions runs on the same commit remain visible operational evidence without falsely changing that push qualification.
  • Per-consumer failures MUST retain independent progress without weakening product, audit, publication or compatibility gates.

DA-WAVE-004 — Gated workflow integration

Requirement. The production reconcile matrix and generated allowed versions MUST enforce wave admission only under explicit rollout and state-write gates.

Acceptance details

  • Default-off wave mode preserves the existing flat reconciliation rollback path and pending state.
  • Trusted-main state publication uses a separate contents-write job scoped to the coordinator; consumer credentials remain per repository and cross-account installations remain separate.
  • Writable wave reconciliation requires successful durable admission before consumer writes, then fresh per-target source/ownership validation immediately before execution.
  • Hourly/manual/publication reconciliation provides recovery without activating settings, publishing packages or modifying protections.

Public operational storage

Public storage contains only explicitly public repository coordinates. Unavailable or non-public source coverage is held and represented by opaque IDs/counts; public repository artifacts and the state branch are not private storage.

DA-PUB-004 supplies a separate bounded static-plugin batch profile for genuine multi-package publication evidence. The selected package still requires its authenticated provenance, exact artifact digest, signed bundle and published-byte agreement before downstream admission. Archive-size holds remain explicit; the profile does not waive current-source checks, publication prerequisites, channel restrictions, ownership or operation CAS. The full-inventory collector uses the shared 128 MiB/256-request resource gate and observes all current owned versions before other tag/baseline probes. Reject-only claim preflight and the static verifier’s 16 MiB npm cap do not qualify a publisher or alter release floors; incomplete or oversized publication evidence remains held even when its download fits the total budget. The atomic state commit also includes public-safe report.json, consumed by Maintenance through GitHub Contents at the branch’s immutable revision.

DA-WAVE-005 — Completion timing and source isolation

Requirement. Completion-triggered reconciliation MUST settle the exact notifying callback before observing qualification and MUST retain default-branch graph authority.

Acceptance details

  • The receiver MUST validate the public source and callback workflow/run/attempt identity, then wait read-only for successful run and exact check-suite completion with a bounded explicit failure rather than silently accepting pending or unknown evidence.
  • The callback’s own current check MUST remain part of existing qualification; no product, audit, deployment or compatibility lane may be exempted to avoid a notification race.
  • PR-head hints MUST NOT replace the default-branch inventory, select unmerged dependency targets or assert qualification; duplicate and stale arrivals MUST remain ordinary authoritative scans.
  • Manual scans and gated scheduled recovery MUST remain available for missed events or failed callback settlement without changing rollout settings.

DA-WAVE-006 — Compound support ranges

Requirement. Admitted compound runtime ranges MUST preserve their supported release lines while qualifying their exact lockfile update.

Acceptance details

  • Targets already inside a compound support range MUST retain that range and use native update-lockfile rules for the admitted path and dependency type.
  • Targets outside compound support MUST remain held for source-owned compatibility review rather than silently narrowing the public contract.
  • The exact existing candidate MUST resolve the admitted target under the preserved range and pass its own current CI before auto-merge.
  • Earlier compound publication waits MAY be superseded only after qualified current main locks satisfy every target under identical registry-verified published support; a genuinely newer mixed release MAY retain that same compound-lock evidence only when all remaining ordinary/peer publication floors also pass, without claiming a new publication for compound-only retirement.

Publication evidence boundary

DA-PUB-001/002 separate authenticated publication facts from latest-only update eligibility, with only the explicit DA-PUB-003 cohort exception. Waiting releases expose channel-not-admitted/provenance-unknown without relaxing newer-version, compound-support, current-main or CAS rules. Legacy publication records remain readable; fresh receipt/channel evidence owns any new release advancement.

Reviewed channel projections retain default stable availability and apply only to exact active consumer scopes. Release retirement still requires the same newer-version/floor or identical compound-contract proof, current qualification, operation identities and CAS; an approved channel is never a release or CI waiver.

DA-WAVE-007 — Independent canonical development intake

Requirement. A source-opted-in compatible development patch MAY advance independently of unrelated publication waits only within its exact canonical preparation contract; every other hold and wait MUST remain binding.

Acceptance details

  • Admission MUST verify immutable source policy bytes/digest and exact existing development, override and lock facts for one policy-named forward patch with no release intent.
  • Missing or changed evidence, additional targets, catalogs, runtime coupling and peers needing changes MUST remain held under ordinary registry/channel eligibility.
  • A wait for the selected dependency MUST still block it while unrelated waits MUST remain visible and block their own updates.
  • Complete current source qualification, rollout scope, ownership, cycles, optimistic concurrency and frozen candidate/canonical-lock validation MUST remain required without widening public contracts or clearing publication evidence.

DA-WAVE-008 — Source preparation before writer admission

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.

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.

Parallel source registration covers six additional existing workflow sets but changes no rollout phase or writer admission. Agent Redaction remains explicitly held and ignored as a Deno package in every phase; all other acceptance, source guard, publication, ownership and state-concurrency requirements remain binding.

Requirement. Opted-in source preparation MUST constrain normal wave admission even after publication waits clear. Unsupported update sets or missing source-policy evidence MUST remain held before consumer writer admission.

Acceptance details

  • The existing bounded profile MUST require its complete source-bound single-development patch facts, not merely a matching package name or a successful upstream release.
  • Mixed or unsupported updates and inconsistent source evidence MUST stay visible, while a mixed node MAY admit only its complete schema2 policy subset; selected edges remain blocked by waits for their own dependency or unscoped waits, but MUST NOT inherit a different package’s same-manifest wait, which remains visible and blocks its own update.
  • Supported source-owned patches and ordinary repositories without an opt-in MUST retain their existing admission paths and every qualification, ownership, registry, rollout and publication gate.
  • Ordinary candidate preparation MUST still validate the complete frozen install and mechanical lock/canonical closure; DA-REL-006’s tooling artifact proof MUST NOT count as full private candidate qualification, which remains required before merge/completion, and pre-admission evidence MUST NOT assert unrun qualification or authorize a product migration.

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. Ordinary live settlement and replay are required after policy deployment.

Held source completion observation

Desktop may explicitly observe its registered successful CI/Pages completions while its private projection write hold and phase full remain intact. DA-NOT-004’s metadata observer is not dependency admission or publication qualification. Existing hold, registry, current-main, ownership and per-entry activation checks remain required; excluded roots cannot opt into this path.

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.

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.

DA-WAVE-009 — Source-bound SDK scope

Requirement. A separate explicit operator grant MAY isolate only Desktop’s root SDK development patch when exact immutable source/private-shape/canonical bindings and complete current-source qualification prove independence from enumerated frozen prerequisites.

Acceptance details

  • Both exact artifact and scope grants MUST bind the descriptor, canonical policy and immutable private shape; the source MUST already be pilot with no explicit operator hold; default-empty policies grant no phase change, audit decision or publication authority.
  • Frozen prerequisite separation MUST use structured exact path/field/name registry findings for runtime AI/Profile and development Tasks; unknown, local-path, coverage, source-CI, identity, audit and selected-SDK constraints MUST remain blocking; matching human text cannot grant authority.
  • Reports MUST retain deferred updates, typed holds and waits while only the selected SDK reaches ordinary canonical preparation and native frozen generation; private source/candidate audit and functional gates remain mandatory; all other dependency writers stay held.
  • Exact scope authority MUST enter operation identity and be rechecked during configuration, generation and copyback; candidate ownership, source/registry integrity, compatibility, fresh target revalidation and durable CAS remain mandatory; unknown or revoked grants MUST fail closed.

Tagged publisher verification recovery

Agent UI DA-PUB-005 verification-only same-run recovery authenticates the original publication independently from the immediately following successful verification. It changes no writer/state gate, channel, release floor, current-source coverage or consumer admission. The actual0.2.9/0.2.7 pair and remaining independent holds are recorded in spec/records/2026-11-18-agent-ui-verification-recovery.md.