Published source evidence and channels
Agent UI’s separate tagged-workspace profile under DA-PUB-005 preserves its existing publisher; it does not relax main-head completion or channel admission.
Publication observations are independent of update eligibility. The latest-only policy remains the default for candidate selection; observing a next-tagged version alone does not admit it or change registry tags.
The exact configured Profile source/integrity binding MAY retire its verified own publication wait. Direct Profile consumption MUST be restricted to Server’s root package.json runtime dependencies; every other repository, manifest path and dependency type remains forbidden. Its exact verified next pin changes no registry tag, release floor, canonical source guard or advisory policy.
The November18 reviewed cohort refresh binds API0.6.9, UI0.2.4, Workspace0.4.8
and Profile0.2.6 to the exact successful Notes538bb469 publication and immutable
artifact. Origin attempt1 and same-byte verification recovery attempt2 remain
distinct; file-explorer0.2.8, all consumer scopes and default latest are unchanged.
The complete measured proof is retained in
spec/records/2026-11-18-notes-cohort-recovery.md.
The November19 refresh advances only those four exact identities to the
current Notes source: API0.6.10, UI0.2.6, Workspace0.4.9 and Profile0.2.7 at
source2838c3dc. Fresh registry signatures, Sigstore provenance, source
contracts, publisher artifact and attempt3 verification agree under the
reviewed Linux x64 Node24.15.0/gh2.102.0 verifier. File Explorer0.2.8,
consumer scopes and default latest remain byte-for-byte unchanged. The
measured read-only proof and prospective Server admission are retained in
spec/records/2026-11-19-notes-channel-refresh.md; hosted merge, writes,
settlement and replay remain separate gates.
DA-PUB-001 — Verified publication identity
Requirement. Published-source acceptance MUST bind package/version/integrity to authenticated provenance, the reviewed public publisher workflow and exact successful source qualification.
Acceptance details
- Registry signatures and Sigstore provenance MUST verify with the reviewed runtime trust material, exact signer identity, issuer, certificate source/invocation and subject digest; gitHead alone MUST NOT qualify publication and the npm publish statement MUST supply consistency only, with structurally inconsistent claims rejected before tarball downloads and preflight never granting verified assurance.
- Exact public source/package contracts and publisher release-manifest/tarball hashes MUST agree; recovery MAY supply successful post-publication verification only for the same source and immutable bytes.
- Complete current source workflow/check/status coverage, exact run attempts and the publisher’s qualification/publication/verification gates MUST remain required; unknown or mismatched evidence MUST remain held.
- Newer-release baselines, required dependency floors, compound-contract rules, current-main acceptance and operation CAS MUST remain unchanged.
DA-PUB-002 — Bounded read-only normalization
Requirement. Publication evidence MUST be normalized independently of version eligibility through bounded read-only observation without executing candidate data.
Acceptance details
- Current public owned versions MUST receive a collection pass before other tag and retained-baseline probes, independently of latest eligibility; channel-not-admitted and provenance-unknown MUST remain explicit independent reasons.
- Exact Node runtime, owned setup action, standard GitHub CLI binary and static public trust-seed bytes MUST match the reviewed contract before verification; missing, changed or unsupported tools MUST fail closed without installing replacements or changing the approved package graph; bundled npm Sigstore JavaScript MUST NOT execute.
- Fetches MUST retain a shared 128 MiB total-byte and 256-request budget plus bounded per-response size, timeouts, redirects and archive inflation; source visibility MUST precede source/artifact reads, existing read-only public-source authority MUST be reused without App minting or added permissions, and no candidate scripts, signing credentials or private API bodies may enter execution or public state.
- Versioned receipts MAY persist only normalized public coordinates/digests and assurance, never raw bundles/artifacts; legacy state remains readable and persisted facts never replace fresh channel/current-head checks and prior verified receipts MUST remain available after unknown fresh observations.
DA-PUB-003 — Reviewed channel cohort
Requirement. Wave mode MAY admit only exact reviewed channel identities within explicit active consumer scopes; default and flat reconciliation MUST remain latest-only.
Acceptance details
- Source policy MUST bind each package, version, integrity, public publisher and attested source; fresh channel, verified publication and exact source-contract evidence MUST agree.
- Direct admission MUST match repository, manifest path and dependency type, with Profile restricted to Server’s root runtime dependencies; consumer prerequisite closure MUST remain rooted in that path’s approved seeds, and public owned publisher retirement MAY use only approved actual runtime/optional/peer fields and their freshly verified cohort prerequisites, with direct scope filters and global eligibility unchanged.
- Unknown policy, missing scope, deprecated or moved channel, incomplete proof and changed identity MUST fail closed; immediate target revalidation MUST refresh registry identities before consumer writes.
- Raw publication channel facts MUST remain unchanged; reports MUST retain remaining channel, source, release-floor, compatibility and ownership holds, with unchanged durable/report schemas and CAS.
DA-PUB-004 — Static plugin publisher proof
Requirement. Plugins static publication MUST use its separate reviewed workflow, environment, job and artifact contract with authenticated npm provenance and exact published-byte agreement.
Acceptance details
- Exact successful public nonfork main workflow/run/attempt and all current source qualification MUST agree with the authenticated certificate, registry signature, subject digest and source package contract.
- The runtime plugin ID/version MUST come from the public source manifest returned as a file at the attested commit, with package directory/release tag and runtime ID/archive coordinates remaining distinct and source/signature-bound.
- The immutable candidate MUST bind package/version, plan, manifest, tarball digest/size and registry bytes within the static profile’s 64 MiB ZIP/aggregate inflation, 16 MiB npm archive, 8 MiB plugin archive/signed file and 32 MiB nested inflation caps, retaining release/path bounds and rejecting ambiguous, expired, mismatched or different-byte skip evidence.
- The reader and cryptographic verifier MUST share the static profile’s 16 MiB npm archive bound only for the reviewed Plugins publisher, reject unreviewed profiles and retain Notes’ existing 8 MiB artifact/4 MiB tarball/32 MiB inflation bounds plus the shared total fetch-byte, request, source and recovery gates without candidate execution, signer access or publisher writes.
DA-PUB-005 — Tagged workspace publisher proof
Requirement. Agent UI publication MUST use a separate reject-by-default tagged-cohort contract for its existing npm publisher, authenticated through the unchanged standard verifier.
Recovery is supported only for the immediately following attempt of the same origin run, after original prepare and both publishes succeeded and actual post-publication verification failed. Fresh latest and exact-attempt responses must bind the same repository, source, tag-push and reviewed workflow. Projected successful prepare/publish jobs must retain original timestamps and step evidence; virtual job IDs alone establish no republish. Repacking, republishing, reused verification, lost origin proof, incomplete coverage, unsupported later attempts and different-run recovery fail closed. Artifact creation remains within original prepare, with origin publication and recovered verification identities distinct.
Acceptance details
- Only repository
lapismd/agent-ui, workflow400453743 at.github/workflows/npm-publish.ymlwith its exact reviewed source-byte hash, tag-push provenance andnpm-productioncertificate environment qualify; the exact stable tag must equal the attested source Agent UI package version, without accepting branch, dispatch or arbitrary tag fallbacks. - Both exact public source packages and unequal versions must match the original three-file artifact schema, SHA256 artifact identity, source-bound manifest, each SHA512 tarball and fresh official registry bytes; missing, extra, duplicate, different-byte or expired evidence fails closed under existing archive bounds.
- Successful original prepare, both version-specific publishes and original or bounded recovered verification MUST remain required with distinct attempt identities, original artifact timing and complete source CI/status coverage, current contract, ancestry and unchanged cryptographic issuer/signer/source/subject/registry checks.
- This profile grants no publication, tag mutation, new key, credential or completion authority; Notes/static profiles, channel floors, budgets and main-head completion remain unchanged, and an unsupported or unexercised publisher cannot become verified by registration alone.