Workflow and module wiring
The accepted initial single-repository rollout uses Notebook in the existing
pilot phase; the next qualified source entry is the no-input Spec Validator. config/completions.json also binds its actual CI, Pages and
version workflow IDs; verified observer callbacks from other known non-held
consumers remain accepted without enabling those consumers’ writers. The
coordinator’s hourly schedule is enabled after the Notebook acceptance and
normal replay receipts. The source policy retains global phase pilot, Notebook and only the
separately accepted Spec Validator, Visual Delta, Terminal and Registry entries; the single-pilot record
separates actual candidate/main/callback evidence, timer configuration and the
first unobserved cron event. Sixteen adoption tasks reuse this same flow; no
consumer copies the engine or independently enables another schedule.
reconcile.yml passes optional manual recover-source-revision only to the
inventory recovery boundary. qualifyRecoverySource reads both exact public
trees before recoverEmptyOperation can record a source transition. The
existing exact-state CAS/read-back and consumer revalidation remain required;
ordinary events cannot invoke this recovery path.
reconcile-operation is a separate manual-only inventory boundary: it binds an
exact completed admission and state revision, records only a strict target subset
already qualified on advanced main, and returns the remaining subset to fresh
ordinary planning. It does not use or widen source-recovery projection rules.
This map describes executable entrypoints. It deliberately contains no secret values, live operational reports or copied repository inventories.
DA-WIRE-001 — Explicit workflow graph
Requirement. Each hosted workflow MUST retain an explicit entrypoint, data boundary and authority consistent with its owning canonical chapter.
Acceptance details
- Inventory and audit jobs MUST remain readers; per-target reconciliation, profile publication and the separately gated coordinator state job MUST be the explicit writer boundaries.
- Publication notifications MUST call the registry-verifying notifier after a source-owned verified publication boundary; completion callbacks MUST use the separately verified read-only workflow-run boundary before App minting.
- Documentation delivery MUST upload only the generated specification book.
Hosted entrypoints
| Workflow | Trigger and jobs | Inputs and entrypoints | Outputs and authority |
|---|---|---|---|
check.yml | PR/main checks | Frozen install, pnpm verify | Source/spec qualification; contents read |
reconcile.yml | Publication/completion dispatch, hourly catch-up, manual | inventory → matrix reconcile; exact manual recovery/operation reconciliation → fresh planning; inventory/config scripts → Renovate → prepare-pr.mjs | Ignored report artifacts; dry-run or explicit one-repository App writes |
completion.yml | Reusable trusted source workflow_run call | Exact allowed source run/attempt → read-only verification → existing scoped App | Completion hint; receiver waits for callback completion; no source writes |
notify.yml | Reusable publisher call | Exact coordinator/source revisions → scripts/notify.mjs | Registry-verified dispatch to coordinator; no npm publisher |
maintenance-audit.yml | Daily/manual | Shared monitoring policy → scripts/audit-maintenance.mjs | Read-only partial/complete JSON report, 14-day artifact |
app-readiness.yml | Manual main-only | One of the explicitly reviewed repositories and existing encrypted App credentials | Scope/repository/PR read proof; no target writes |
profile-refresh.yml | Gated hourly/manual | Source generator → same-run artifact → coordinator publish-profile.mjs | Guarded rolling profile PR using scoped App writes |
pages.yml | Main push/manual main | Frozen install and complete verification → generated spec/book | Book-only Pages artifact; isolated Pages deployment authority |
Source flow
policy + GitHub default-branch manifests + npm metadata
-> inventory (owners, consumers, availability, cycles, holds)
-> eligible per-repository matrix
-> generated Renovate rules + target-scoped token
-> exact candidate install + deterministic release intent
-> consumer CI and existing merge rules
-> source-owned versioning / approval / publication
-> verified notification hint or scheduled catch-up
| Boundary | Owning implementation |
|---|---|
| Discovery / registry closure | src/github.mjs, src/policy.mjs, scripts/inventory.mjs |
| Central Renovate rules | src/renovate.mjs, scripts/configure-renovate.mjs, renovate.config.cjs |
| Release intent | src/changesets.mjs, scripts/prepare-pr.mjs |
| Consumer integration | scripts/prepare-consumer.mjs, scripts/onboard-changesets.mjs, src/consumer-ci.mjs, src/docker-context.mjs, templates/ |
| Publication notification | scripts/notify.mjs, notify.yml |
| Monitoring policy / audit | src/maintenance-policy.mjs, scripts/audit-maintenance.mjs |
| Profile validation / writes | src/profile-writer.mjs, scripts/publish-profile.mjs |
| Repository/spec checks | scripts/check.mjs, spec-validator.config.mjs, package scripts |
Workspace canonical preparation uses canonical-workspace-policy.mjs for
source-owned schema/scope, canonical-workspace.mjs for actual facts and lock
validation, and the existing canonical-intake-files.mjs adapter for immutable
source/filesystem checks. canonical-admission.mjs restricts ordinary wave
admission; renovate.mjs binds target integrity and exact output filters before
prepare-pr.mjs invokes the shared preparer. Consumer deployment remains under
DA-REL-005 qualification.
Wave wiring
src/audit-preflight.mjs runs the complete coordinator audit before inventory
can plan writable admissions. scripts/audit-preflight.mjs repeats the real
check before the App-token step. Read-only matrix execution no longer mints a
write-capable App token. The operational maintenance audit resolves local
composites from exact-source tree blobs and reads required-check/activation
metadata without changing settings.
maintenance-audit.yml passes only the five allowlisted activation variables
from GitHub’s vars context. When the Variables API is unavailable, the collector
requires that exact main workflow/repository/ref/event/revision context and
labels the observation source. It retains contents-read authority and adds no
App token, settings permission or write API.
inventory reads state and current evidence, then emits the admitted matrix and
candidate state. wave-state publishes that state only from trusted main with
its separate gate; matrix reconcile requires that publication in writable wave
mode. validate-wave-target.mjs refreshes target revision and branch ownership
before Renovate. src/waves.mjs, src/wave-evidence.mjs and
src/wave-state.mjs own planning, observation and state CAS respectively.
The default-off wave gate leaves the original flat matrix available for rollback.
Completion adoption uses config/completions.json, src/completion.mjs and
scripts/qualify-completion.mjs. The generic publisher notifier rejects
completion calls before App minting. completion.yml checks out only an exact
trusted coordinator revision with credentials disabled, installs frozen
production dependencies without lifecycle scripts, and reads source API metadata.
It revalidates after minting and dispatches no candidate data beyond documented
public coordinates. The callback run/attempt in the hint is settled before
inventory; all existing qualification checks remain observed.
The read-only inventory and source/book verification jobs install the owned
Lapis CI setup-gh action at the reviewed immutable publication-policy pin.
Publication collection verifies its exact binary/runtime/trust bytes before
offline provenance checks; it grants no artifact execution or publication authority.
Trusted-main wave inventory uses its existing contents-read workflow token for public artifact downloads, with no App key, reader mint or permission probe. Discovery and publication collection remain public-only; missing read access keeps the publication unknown. Per-target writers retain their separate App credentials, actual audit preflight and admission gates.
Docs and Tasks register their actual CI/Pages completion identities while remaining outside the writable pilot. The App readiness workflow adds only these exact read-only probe targets; source callback adoption and required consumer audit qualification remain separate gates.
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 preparation shares one coordinator. Exact observer registration for Server/Agent UI/AI/Terminal/jj-store/Registry and owner-mapped read probes add no writer. Source tasks may progress independently; central activation and durable reconciliation stay serialized, with unchanged global pilot settings.
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.
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.