Repository policy
The default-empty config/scoped-admissions.json is a separate operator grant
for DA-WAVE-009. Its exact Desktop descriptor, canonical-policy and immutable
private-shape hashes do not enable another source or grant general private
dependency updates. Every other source keeps ordinary whole-repository holds.
DA-REL-006’s separate artifact capability map defaults to no repositories. A source opt-in cannot enable native projections or alter any existing private, phase, CI, publication or audit hold. This implementation installs no live entry.
DA-PUB-005 registers only Agent UI’s reviewed tagged-workspace publisher and source-byte contract. It changes no repository phase, channel scope, publication floor, signing tool or completion authority.
The reviewed Notes channel cohort follows DA-PUB-003 with exact package, version, integrity and consumer-manifest scopes. It adds no repository entries and changes no phase, schedule or write activation. Profile’s separate reviewed consumer scope is restricted to Server’s root runtime dependencies; other Profile consumer scopes remain forbidden. DA-POL-001 through DA-POL-003 retain their existing authority and excluded hosts.
The November18 Notes refresh changes exactly four package identities to their
verified source538bb469 cohort after same-byte publication recovery. It adds no
consumer scope or repository and retains file-explorer0.2.8 and defaultlatest.
Current-main qualification, source-owned canonical support and upstream floors
remain independent holds; the normalized proof is recorded in
spec/records/2026-11-18-notes-cohort-recovery.md.
The November19 identity-only refresh advances those same four pins to the
current source2838c3dc cohort after exact-source release run44609414345:
API0.6.10, UI0.2.6, Workspace0.4.9 and Profile0.2.7. It changes no consumer
scope, repository phase, write setting, File Explorer pin or defaultlatest
behavior. Exact cryptographic and prospective planning evidence is recorded in
spec/records/2026-11-19-notes-channel-refresh.md; live writes and settlement
remain independently gated.
The subsequent exact Server Profile scope changes only direct channel selection
for its existing public prerequisite, as recorded in
spec/records/2026-11-18-server-profile-scope.md; source compatibility,
publication-floor and production audit holds remain independent.
Server joins the existing ten pilot entries after source103 and exact-main CI/image/Pages/completion qualification. Its measured empty managed note records no npm/private-package release intent; registry prerequisites, source intake, publication and production audit holds remain independent. Eligibility does not complete Server adoption or enable any excluded host.
config/repositories.json is the versioned authority for dependency-update
entries, monitoring additions/exclusions and excluded package names. It is not
a live installation or secret store.
The accepted initial rollout selected Notebook as the first pilot entry.
With the coordinator phase retained at pilot, every full entry remains
observation-only until its own adoption task explicitly promotes that entry.
Existing completion callers remain read/dispatch observers independently of
write activation. Excluded roots remain ineligible. A held full-phase source
may register a separately reviewed metadata-only observer under DA-NOT-004;
its hold and dependency-write ineligibility remain binding.
DA-POL-001 — Explicit dependency scope
Requirement. Dependency discovery and update targets MUST originate from validated repository entries with supported schema, unique identities and explicit rollout phases.
Acceptance details
- Entries MUST identify a supported organization/account repository and
pilotorfullphase. - A supplied hold reason MUST be a non-empty string and MUST prevent that target from entering the write matrix.
- Invalid or duplicate entries MUST fail before reconciliation.
DA-POL-002 — Monitoring authority separation
Requirement. Monitoring additions MUST expand read coverage without granting dependency-update or publication authority.
Acceptance details
- Monitoring scope MUST be the sorted union of update entries and monitoring additions, minus monitoring exclusions.
- Monitoring exclusions MUST win, and malformed or duplicate monitoring identities MUST fail validation.
- Missing optional monitoring fields MUST retain legacy update-entry defaults.
- Monitoring adapters MUST NOT mutate the dependency-write allowlist or remove holds.
DA-POL-003 — Excluded and held scope
Requirement. The rollout MUST preserve explicit repository/package exclusions and portable-leaf boundaries rather than activate parked Deno hosts or held consumers.
Acceptance details
- Community and Nostr repositories MUST remain outside this rollout unless explicitly reauthorized.
- Discovery MUST exclude parked Deno host paths, generated trees and fixtures.
- Excluded package names MUST be ignored by generated Renovate rules.
- An existing portable-leaf entry MUST NOT authorize its excluded service or host; retained excluded Deno roots MUST remain held in every rollout phase while their public metadata MAY remain read-only graph evidence.
Scope interpretation
Monitoring exclusions and update entries deliberately serve different purposes. For example, a repository may retain a portable package consumer entry while its service-oriented root remains excluded from broad monitoring. An explicit hold keeps a repository discoverable for explanation without making it writable.
AI Controller and AI Host retain explicit dependency-write holds in addition to their monitoring exclusions. Their existing entries continue supplying public prerequisite metadata; neither a future full phase nor later successful CI may turn those excluded roots into dependency-update targets.
Public operational coverage
The allowlist does not establish repository visibility. Discovery classifies visibility before collecting source. Public coordinator artifacts/state contain only verified public sources; inaccessible/non-public entries produce opaque coverage holds without widening credentials or revealing source names/bodies.
DA-INV-005 public raw reads use the same reviewed entries and exact source tree. They grant no additional installation, credential, private-source or write scope; unknown visibility and unverified file bytes remain held. DA-INV-006 HTTP diagnostics expose only sanitized failure context, never access tokens or bodies.
Monitoring token detection includes Changesets’ explicit github-token input;
this classification does not expand dependency targets or installation scope.
The separate config/tooling.json contract follows DA-TOOL-001 through
DA-TOOL-003. Its repository-specific cohorts describe tooling rather than
dependency edges or permissions. It cannot add advisory exceptions,
change rollout phases, enable writes or activate excluded hosts.
Expanded tooling records may retain exact source/artifact hashes, resolved versions and historical successful source-CI context under DA-TOOL-004; that metadata never qualifies a whole version recipe or grants dependency writes. Reviewed source workflow/job selectors and package-manager provenance follow DA-TOOL-005/006; evidence refresh preserves existing supported tool ranges and retains undeclared manifests without inventing declarations.
The scheduled single-pilot checkpoint keeps global phase pilot, so only
individually activated entries can enter the writer matrix. Its expected
schedule value does not enable hosted scheduling: actual activation follows
the selected pilot’s candidate/main/replay acceptance. Missing variables retain
the workflow’s default-off gate, independently of checkpoint metadata.
config/operations.json records reviewed template references, single update
class owners, retained exclusions and a dated activation checkpoint, without
granting settings authority. config/advisories.json is the separately reviewed
exact approval authority under DA-OPS-002; its initial list is empty. Source
observations and raw audit findings cannot create approvals.
The initial November 16 operator decision added one exact coordinator deepmerge entry with the reviewed dependency-source/lock binding and November 21 expiry. This changes only advisory admission under DA-OPS-002; repository scope, existing holds, rollout phase and the separate write gate remain unchanged.
After retirement of that LOW decision, the November17 operator explicitly
approves two exact HIGH picomatch runtime paths bound to dependency source
9d657a74 and lock SHA256a3e1f05f. Their exclusive November19,00:00UTC expiry
and earlier known-fix termination are independent of the historical LOW scope.
Only config/advisories.json grants those two tuples; all other findings,
source/lock drift, stale approval cleanup and existing rollout gates still deny
writes. The decision does not activate another repository or consumer exception.
Those two HIGH approvals are now retired after official upstream withdrawal and complete zero-finding audit evidence. Active approvals are empty again. This DA-OPS-002 cleanup neither installs a dependency fix nor grants any new exception; every future finding must pass the unchanged rejection policy.
Hosted activation observations may use the five values supplied by the trusted main audit workflow when its read token cannot query the Variables API. This read-only evidence follows DA-OPS-001; it cannot create defaults, change settings or grant writer authority.
Completion policy binds only existing pilot repository workflow IDs/paths and permitted source events. It adds no dependency write scope, removes no hold, and excludes the notification callback itself and the deferred Nostr publisher. Unknown or recreated workflow identities require explicit source review before notification adoption.
Publication policy reviews source-owned publisher workflow identities and exact verification-tool bytes under DA-PUB-001/002. It adds no update repositories, channel admission, source signing authority or publication permission.
Source-owned canonical intake is an optional preparation capability, not an activation or repository-scope change. Invalid policies fail closed; existing phase, portability, package exclusions and manual-repair holds remain binding.
Notebook is the sole additional pilot update entry for the bounded canonical Core development intake. This changes no global phase, schedule, service scope, package exclusions or held publisher. Source review and actual normal bot regeneration remain separate from source qualification of DA-WAVE-007; the bounded pilot runbook retains acceptance and rollback.
PR34’s explicit operator decision rebinds the single existing coordinator runtime LOW to source9d657a74 and locka3e1f05f…ca61b8b after the required validator update. This replaces the old exact tuple and preserves expiry, known-fix rejection and every other audit failure under DA-OPS-002. No write scope, activation setting, phase, package signing or deployment gate changes.
The five existing pilot tooling cohorts allow exactly spec-validator0.2.0 or the reviewed Deno-free0.2.1 patch. This explicit DA-TOOL-003 policy repair unblocks the source-owned release-intent hook without skipping it or widening other tooling families. Historical source/lock evidence remains unchanged.
The same exact advisory entry is now retired after official upstream withdrawal and complete zero-finding audit evidence. Active approvals are empty. This DA-OPS-002 cleanup neither installs a dependency fix nor grants any new exception; every future finding must pass the unchanged rejection policy.
Docs and Tasks add exact completion observation and one-repository read-only App readiness targets while retaining source phase full until separately reviewed activation. This metadata does not grant writer, publication or audit-exception authority. Their earlier HIGH Changesets finding cleared after upstream advisory withdrawal; only separately qualified source adoption may precede a reviewed phase change.
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 rollout and explicit Deno-package exclusion
The next adoption batches cover existing Node foundations/plugins, native/server packages and applications/registry independently. Only the parent coordinator changes registrations, per-repository activation or durable shared state; source preparation does not enable writes. Notebook, Spec Validator and Visual Delta were the three enabled entries at the start of parallel preparation; subsequent per-entry activation is recorded in the dated sections below.
Agent Redaction publicly exports ./deno and requires pnpm test:deno under its
tracked guide. The operator excludes any Deno package. Its monitoring exclusion,
package ignore and explicit dependency-write hold therefore preserve graph
observation without adopting, porting or activating that source. This excludes
adoption64 rather than claiming successful Node-only acceptance. Community,
Nostr and every prior frozen host exclusion remain unchanged.
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.
The Desktop observer registration names only CI400533153 and Pages403244157,
with their exact paths and original PR/push/manual events. Its explicit
heldObservers opt-in is valid only while the existing private/archive hold and
full phase remain present. It grants no writer admission, publication authority,
private registry access or version recipe; a later promotion must remove this
observer opt-in rather than silently inherit it. Excluded Deno roots cannot use
this registration mechanism. Schedule, preview, trial, health, image publication
and callback self-triggers remain outside the allowed workflow/event pairs.
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.