When a swamp serve daemon runs with a collective API key (SWAMP_API_KEY=[REDACTED-SECRET-1]), every cli_invocation telemetry event it produces is unattributed. The events exist in the pipeline but nobody gets XP for them.

Root cause

The /ingest handler resolves API keys via verifyApiKey(), which only checks the apikey collection (personal keys). Collective keys live in collective_apikey and are resolved by verifyCollectiveApiKey() — but the telemetry service never calls it. So swamp_org_* keys silently fail to resolve, and the event is stored without a username.

Proposed solution

Step 1: Resolve collective API keys at ingest (change)

In services/telemetry/lib/server.ts, the API key resolution currently only calls verifyApiKey(). It needs to also try verifyCollectiveApiKey() when the personal lookup returns null.

When a collective key resolves, override distinct_id to collective:<collectiveId> at ingest time. This naturally separates collective events from individual ones in downstream MVs without requiring schema changes to cli_daily.

Stamp the event with:

username → @<collectiveSlug>
distinct_id → collective:<collectiveId>
collective_token: true in properties
member_user_ids and member_usernames — resolved from the member collection at ingest time (membership snapshot frozen at ingest, matching the extension publish pattern)

verifyCollectiveApiKey is already in shared/auth/api_key.ts — just needs to be imported into the telemetry service's main.ts and wired as a fallback.

Step 2: New activity-distribution projector (new)

Analogous to publish-distribution.sql. Reads directly from swamp.events (not cli_daily — the MV lacks collective_token and member arrays).

Reads cli_invocation events where collective_token = true
Runs activity through the existing diminishing-returns curve first, THEN applies 1.5x multiplier (post-curve, so the ceiling lifts for teams — rewarding collaboration)
Distributes across members via arrayJoin over member_user_ids
Each member gets their own score_grants row with distinct_id = member_id, origin_distinct_id = collective:<id>

No changes needed to the individual activity projector — because distinct_id is overridden to collective:<id> at ingest, these events flow into cli_daily under a synthetic id that no identity_map entry will ever resolve to a real username. The individual projector naturally ignores them.

Step 3: CLI-side audit field (nice-to-have, separate repo)

In the swamp CLI (src/serve/telemetry.ts, src/serve/handlers/*.ts), include initiatedBy in event properties to record which user triggered the serve API call. Audit-only — not used for scoring. The telemetry service doesn't need this to attribute correctly.

Risks to address during implementation

Double-scoring window at deploy — score_grants is append-only. If the distribution projector goes live while events are still being scored individually, scores inflate permanently. Deploy atomically, or gate the projector on a date cutover.
Volume — Serve daemons can generate far more events than human CLI users. Each event carrying a full member array means repeated data. Monitor score_grants row growth after rollout.
cli_daily carries the synthetic collective:<id> distinct_id — these rows are harmless (the activity projector won't resolve them to a username) but they do exist. If cli_daily is ever used for something that should exclude collective activity, this will need attention.

Files to change (swamp-club)

services/telemetry/main.ts — import and wire verifyCollectiveApiKey as fallback resolver
services/telemetry/lib/server.ts — handleIngest: try collective key when personal fails; stamp username, collective_token, members; override distinct_id
services/telemetry/lib/activity-distribution.sql — new projector for collective cli_invocation scoring (post-curve 1.5x, arrayJoin fan-out)

Existing pattern to follow

routes/api/v1/extensions/confirm.ts (emit side) + services/telemetry/lib/publish-distribution.sql (projector side) — this is the proven collective scoring pattern. The new work mirrors it for activity events.

02Bog Flow

Shipped

8/17/2026, 2:45:32 PM

Click a lifecycle step above to view its details.

03Sludge Pulse

stack72 assigned stack728/17/2026, 12:51:50 AM

serve: triggerSource not persisted to workflow run summary

dataOutputOverrides not applied during remote execution — ephemeral resources GC'd before override takes effect

extension rm also deletes the lockfile entry, and install on an empty lockfile is a silent success — rm/install is not a round trip

vault: audit trail should record put, delete, and annotate operations

ExtensionWorkflowRepository scans manifest.yaml as a workflow, emitting 'Unknown key manifestVersion' warning

--max-run-duration only applies to detached runs, not attached runs

Cancel endpoint reports status: cancelled for runs it did not actually cancel

@swamp/git: no way to amend a commit, but push can --force

Installation with new account creation times out

pre-flight checks run on orchestrator, not on worker — breaks remote execution with filesystem-dependent checks

Docs: update cancel endpoint response statuses in REST API reference and workflows page

docs: document --remote-only flag for swamp serve

Swamp serve daemon doesn't run with --hot-reload

serve: include workflowName in HealthSnapshotSchedule

Retyping a model instance strands catalog rows no command can reclaim — prune matches on model_id, delete resolves the current type (follow-up to #1009)

knowledge-base retrieve persists query output into the state resource, with lifetime infinite and the query text in the instance name

Method-name collision between a base model type and an extending extension silently drops the whole extension file — no error, doctor reports pass

Skip 50MB monolithic index rewrite on v2 shard-first path

Share single AwsS3Client instance across lock, sync, and verifier

Double shard assembly per command lifecycle (pull + push both read all shards)

pullChanged never records commitSeq for shard-first (v2) index

localHasAllRemoteEntries() permanently blocks sidecar update on partial caches

serve: workflow.history.get cannot find CLI-created runs or look up by run ID

"TRIAL ENDED" modal shown to team plan user when toggling extension visibility

Concurrent suspended workflow runs can't be disambiguated from 'approvals'; fresh runs should supersede matching-input suspended runs

I _think_ I might like a guard in the trigger yaml

swamp cmds don't realise the user is sshed into the system

serve dashboard: add cluster.instances and serve.config endpoints

CEL expressions have timestamp/duration but no current-time value, so no guard can express "older than N"

Support direct type execution (@type) with --server

access token mint writes to user vault, not serve's _token-secrets control plane in HA mode

Generic OTLP endpoint appends signal path after query or fragment

Issue lifecycle start drops top-level issue comments

serve dashboard: add instanceId, triggerSource, and step progress to WorkflowRunSummary

Document worker affinity (affinity: true) for workflows and jobs

Datastore MongoDB driver leaks connections — 5960 accumulated over 8 days

workflow approvals displays the latest run's prompt for every suspended run

@swamp/git: add a read-only working-tree diff for pre-commit review

docs: document --oauth-client-name flag for swamp serve

Docs: update workflow reference to include trigger in JSON output shapes

@swamp/git branch and push methods fail data naming when branch contains '/'

Docs: update workflow-placement.md for job/workflow-level placement inheritance

feat(serve): use identifiable OAuth client_name instead of random UUID

@swamp/git does not pass AbortSignal to Git subprocesses

Global Secret Manager methods build an invalid regional parent

Document model.method() support in assert expressions

No way to store code-review results — verdicts, findings, and cost are not persisted for any repo

Redaction regex boundary bug: label_base64 secrets with an unrecognized label pass through unredacted (e.g. swamp_ API keys)

User token page (/u/<user>) shows only "swamp_..." for every API key, making leaked-key identification impossible

upstream_state treats sparse-fetch branches as having no upstream

Add native support for the Pi coding harness

Cloud Build create supplies project instead of required projectId path parameter

workflows: support labels/target/platform at job and workflow level

swamp access grant create never registers the grant — a --deny created this way silently fails open

Support credentials in datastore config (vault-resolvable)

swamp serve OOMs on repos with 2000+ model definitions

Serve telemetry attribution for collectives

Extension workflows: no way to override trigger configuration

Add a list/discover method to the generated @swamp/aws types — no way to enumerate resources in a region

Document @vault= prefix for webhook secrets in serve.yaml

swamp access grant create installs an unrelated extension from the registry

docs: document SWAMP_API_KEY headless OAuth bootstrap for swamp serve

workflow-succeeded selects the globally-latest run, so siblings block each other under parallel use

swamp serve: webhook secrets should support @vault= resolution

Misleading collective_not_trusted auto-resolve error when a local source extension transiently fails to index during workflow validate

datastore setup: symlinks not counted in bytesCopied, causing misleading '(0B)' output

vault.get() CEL error embeds raw newline when wrapped by model resolver, producing broken output

Feature: user-configurable redaction rules (.swamp/redaction.yaml)

Fatal JavaScript out of memory: Ineffective mark-compacts near heap limit

Sync every signup to Attio, and backfill the existing population (#809 follow-up)

@swamp/issue-lifecycle probes /api/health, which swamp-club stopped serving when the Fresh scaffold stubs were removed

Lab lifecycle POST rejects any payload string that starts with a dollar sign, not just operator keys

Feed: detect and gracefully handle dead (404) post links (link rot)

/feed: per-post unread indicators and mark-as-read to track reading progress

/feed: filter and search by author, title/text, and topic

Add a :micdrop: emoji / reaction shortcode (swamp-native art included)

Push down the two cheap leaderboard scans: ghost-gate dictionary and eventCounts owner filter

$identify events are never consumed — anonymous web history never binds to the account

Finish the swamp_* attribute set on Attio users, and settle the two unprefixed ones (#809 follow-up)

aria-expanded is a raw boolean in 12 places — collapsed state is unannounced to screen readers