`swamp extension pull`'s `installExtension` currently verifies a downloaded artifact against a checksum fetched from the same registry that served the artifact. If there's no server-provided checksum, it proceeds anyway with an "unverified" integrity status. This is same-party trust — the registry is both the thing being trusted and the thing vouching for itself.

This is one candidate idea, not a proposed requirement

Filing to open discussion, not to commit to an implementation. This issue only makes sense to design in detail once #1592 (signing) and #1593 (transparency log) are decided in principle — pull-side verification has nothing meaningful to verify against otherwise. It also depends on unresolved questions about inter-collective trust (see separate issue/discussion to follow) — namely, what counts as a "trusted" signer for a given collective is a prerequisite design question, not something this issue can answer on its own.

Proposed approach (if pursued, and if signing/log land)

Extend pull-time verification to fetch the signature/certificate alongside the existing checksum, verify against the transparency log independently of the registry, and set integrity status based on that rather than registry-issued-checksum-over-TLS.

Open questions (if pursued)

Backward compatibility: extensions published before signing existed have no signature. Does unsigned mean "unverified" (current behavior, preserved) or a harder failure mode? Flag day vs. grace period?
See the (forthcoming) inter-collective trust discussion — this issue is intentionally not resolving identity-to-collective binding, third-party collective onboarding, or multi-maintainer identity rotation.

Alternatives considered

Keep checksum-over-TLS as-is and rely entirely on publish-time audit gates (OSV/npm) to keep bad artifacts out in the first place — simpler, but doesn't protect against a compromised registry serving a tampered artifact with a matching self-issued checksum.

02Bog Flow

Open

8/11/2026, 3:25:43 AM

No activity in this phase yet.

03Sludge Pulse

dailyHistory range pushdown — deferred from #1576, and the measurement says why

score-rollup projector runs N× per cadence — the run gate is per-replica memory, not shared state

Docs: manual never mentions telemetry, and the serve/scheduling pages imply automated runs are visible when they are not

Explore: CLI binary update integrity lacks independent verification

Leaderboard phase 2: take score_grants off the board read path — read today from score_daily

Explore: reconcile quality rubric's dormant provenance factor

Explore: pull-time signature verification for extensions

Explore: transparency-log integration (Rekor) for extension signatures

Explore: publish-time artifact signing for extensions (cosign keyless)

swamp serve is telemetry-dark: scheduled workflow runs never reach /ingest, and the daemon never flushes

Profile day drill-down returns 0 entries at the 5s ClickHouse ceiling for every operative

A ledger read failure still renders as 'no activity': loadProfileScore swallows to an empty standing behind HTTP 200

swamp quest: drop the heartbeat field the server no longer sends

reconcile_from_disk_bench.ts fails deno check (stale DenoRuntime stub)

Improve multi-word search query handling and guidance

Retire the genesis_public flag and delete the dead cutover transcription scaffolding

Leaderboard phase 1: cache the board read and bust it on tier crossings (no schema change)

Catalog backfill deletes rows for any model whose data names are numeric

migrate-index silently drops entries with shallow paths — all of workflows-evaluated/ and any root-level file

Docs: document catalog completeness check and --repair in doctor reference

Catalog backfill reconciles against the local cache, not the datastore

Leaderboard board windows re-anchor on wall-clock while the rest of the view is frozen at asOf

Decision: move per-event grant MVs to day-grain — ledger is on track for ~1.5B score_grants / ~4B quest_grants

Leaderboard phase 5: score-rollup-projector write cost at 10B — ~430M rows scanned per 60s tick

Profile candidateIds prune costs a full ledger scan to build itself — 42.88M rows for one keyed read

Leaderboard phase 3: owner-grain board_totals so a cache miss is survivable at 10B

Epic: /leaderboard and /u/{username} do not survive 10B events — measured audit + phased plan

Add native Bedrock Knowledge Base Retrieve support

Datastore-managed configuration for multi-instance serve deployments

Ghosts on the leaderboard 500

swamp command doesn't check cwd

swamp auth login process fails when run remotely

serve boot OOM: findAllGlobalSince loads all workflow runs as full aggregates during reconciliation

extension search: channel-filtered results carry null version fields, and multiple --channel values collapse instead of unioning

s3-datastore: localHasAllRemoteEntries uses bare rel instead of localRelPath, always returns false in namespaced mode

datastoreSetupExtension migrates .swamp/ to cache root instead of namespace directory

swamp serve writes outputs/ outside the bound namespace — silently never persisted to the remote datastore

s3-datastore: bulk pull writes to cache root instead of the namespace, wedging push and arming a full-datastore delete

git: add pull, fetch --tags, and cherry-pick methods

Workflow runs with wide dataArtifact fan-out (~400/run) OOM both workflow history get and swamp serve boot, crash-looping the scheduler; rollback doesn't help (state-triggered, not release-triggered)

Show user:<name> instead of user:<id> in grant list output

Reusable long-lived invite link: one URL to bring people into the swamp

Exclude swamp internal model types from model list output

Skill docs use invalid two-argument 'vault get' form

access token mint prints an invalid retrieval command (vault get, not vault read-secret)

serve reload and model edit timeout over --server in Kubernetes

swamp auth whoami should report paid tier and trial status

Use whoami entitlement to explain private-extension push refusals

Document --restricted-commands flag for swamp serve

vault put: pass tags through to extension provider CreateSecret/setSecret calls

Docs: update manual for 23 new --server commands

Update VaultProvider interface in @systeminit/swamp-testing to support optional tags in put()

Docs: document --grants-file flag for swamp serve

Docs: document --server support for serve reload

Docs: add --tag flag to vault put reference

Docs: update manual for --detach-runs deprecation and HA auto-detection

Document the Codex plugin in swamp docs

Add --server support to CLI commands missing it

Document the swamp Claude Code plugin in the swamp documentation

Make --server a global CLI option

Add --server support to model cancel (server-side run cancellation)

Load grants from external source on swamp serve startup

swamp vault put should support tags for secret governance

Improve hot reload of the deamon, include extension source/bundle changes

Authenticated users must re-login after swamp serve restart

Add --server support to serve reload

Harden queue claim semantics: atomic claims + status-guarded markDelivered/markFailed across app queues

Auto-detect HA mode and deprecate --detach-runs flag

version-drift check (from #236) is a raw string-inequality, false-positives on multi-model manifests and metadata-only bumps

Resend newsletter audience sync: contacts, segments, backfill, unsubscribe sync-back

Move per-login token secrets from vault to encrypted control-plane store

Docs: document macOS TLS trust limitation and SSL_CERT_FILE workaround

Validate swamp serve deployment stack on startup

Docs: serve config file (.swamp/serve.yaml) and --config flag

Serve config file — read swamp serve configuration from YAML

Deno runtime does not trust ISRG Root YR — extensions fail with valid Let's Encrypt certs

Docs: update hot-reload reference to include trust list refresh

Cross-instance client re-attach for multi-instance swamp serve

vercel codegen: inline rawSyncResult in non-unwrap sync path

vercel codegen: unused listAll import blocks extension publish for 4 models