operate/audit-logs.mdx diagnoses a missing notification as "a subscription filtered the event out" — subscriptions filter nothing

Found while implementing #132 (whose file surface is content/docs/configure/notifications.mdx only, so this was recorded rather than fixed). Filed unassigned.

content/docs/operate/audit-logs.mdx:100-104:

Because this log sits upstream of routing, a row here with no matching inbox message usually means a subscription or preference filtered the event out — check Notifications when a user reports a missing alert.

The subscription half of that sentence is the same claim #132 corrects on the Notifications page: the subscription→recipient expansion is not wired, so a subscription row cannot filter anything out. This one is worse than a description error because it is diagnostic advice — it sends an admin chasing a missing alert to the Setup "Notification Subscriptions" grid, where nothing they change can affect delivery.

Measured on objectstack origin/main @ 2866d5f97e (the same measurement #132 rests on, re-run):

AudienceSpec (packages/services/service-messaging/src/messaging-service.ts:51) has no 'subscribers' member; EmitInput.audience is required.
RecipientResolver.resolveOne() (recipient-resolver.ts:113-146) branches on user: / role: / team: / owner_of: / email / bare id — no branch reads sys_notification_subscription.
Outside its own declaration, the Setup nav entry and tests, nothing references sys_notification_subscription.
The object's own header carries the upstream ⚠️ [#9807] … NOT WIRED in this repo annotation.

What is true for that sentence: the preference half. MessagingService.emit() calls PreferenceResolver.filter() on the resolved recipients (messaging-service.ts:707) and logs suppressed for all recipients by preference when it empties. So the honest advice is: an event with no inbox message means the producer's audience did not resolve to that user, or their preference muted the topic on that channel.

Scoping, kept the same as the framework's annotation and as #132's wording: this is a statement about the platform notification pipeline (objectstack measured; objectui measured — zero runtime readers, counter-checked against sys_inbox_message; the cloud repo was not measured, recorded as a declared narrowing rather than guessed).

Suggested fix: drop "a subscription or" from that sentence and let it name the two real causes (audience did not include the user; preference muted it). One-line edit, but on a page outside #132's surface and inside no other card's completion scope, hence a separate issue.

Related: #132, objectstack-ai/objectstack#9807 (ruling), objectstack-ai/objectstack#10027 (the landed annotation).

Triage: pm:queue, Bug (diagnostic advice sends an admin to a grid that filters nothing). One-line fix per the card: drop "a subscription or" and name the two real causes (audience did not resolve to the user; preference muted the topic/channel). The cloud-repo leg stays a declared narrowing, as measured.

Generated by Claude Code

Claim: PM loop round 1
Session: session_016TUrhcggSFrYctvp5dsV1A
Branch: claude/issue-146-audit-logs-subscription-claim
Worktree: objectos-issue-146
Domain: n/a — objectos is a single-lane repo and carries no domain:* labels
File surface: content/docs/operate/audit-logs.mdx (stop on breach; explain in the report)
Container & model: S mechanical, mode:subagent, model: sonnet — node scripts/pm/dispatch-gates.mjs --tier content/docs/operate/audit-logs.mdx run this dispatch: no path-derived mandate (the path is absent from the objectstack tree the tool derives from, which it reports as "not evidence either way"), so the tier is this seat's per-card call. Floor, because triage adjudicated both the deletion and the replacement content — the writing judgment left is one sentence.
Clause-②: no
Serial constraints cleared: nothing in flight in this lane (zero pm:dispatched cards at round open, zero dev PRs open). operate/audit-logs.mdx is touched by no other queued card and by nothing merged since 514527b. Sibling dispatches this round are #148 (build/index.mdx, build/automation/flows.mdx) and #150 (reference/cli.mdx) — disjoint surfaces, and no read-coupling: none of the three pins an assertion about behaviour another is changing.

Premise re-check, run at dispatch rather than quoted forward

This card was measured at 514527b; main is now 09a0dd9, ~30 commits later. Re-measured just now on origin/main:

content/docs/operate/audit-logs.mdx:102 still reads a row here with no matching inbox message usually means a subscription or — intact, same line number.
Nothing has touched this file since 514527b.

The upstream measurements the card rests on (AudienceSpec has no subscribers member; RecipientResolver.resolveOne() has no branch reading sys_notification_subscription; PreferenceResolver.filter() is the one real filter) were taken at objectstack 2866d5f97e and are not re-verified by me. Re-verify them yourself before writing — they are the whole basis of the replacement text, and objectstack main has moved a long way since.

Adjudication (not re-litigable)

Triage, 2026-08-23: "pm:queue, Bug (diagnostic advice sends an admin to a grid that filters nothing). One-line fix per the card: drop "a subscription or" and name the two real causes (audience did not resolve to the user; preference muted the topic/channel). The cloud-repo leg stays a declared narrowing, as measured."

That settles both the direction and the replacement's content. Do not reopen whether the sentence should instead be softened or footnoted.

PM mechanism assumptions (test these; falsifying one is a good outcome)

I assume the sentence is still reachable from the rendered page and is not inside a block that some later change made conditional or dead. Cheap to check while you are in the file.
I assume operate/audit-logs.mdx has no locale siblings needing anything from you. Translations are never a dev agent's output in this repo — locale siblings go stale by design and are the translation pass's input. If you find yourself editing a .de.mdx/.zh-Hans.mdx file, stop.

Scope, held tight

One sentence on one page. The card's own measurement narrows what you may claim: the preference half of that sentence is true and stays. Only the subscription half is false.

⛔ Do not fix the same claim wherever else it appears. If you find it on another page, report it — it is a card, not a rider. configure/notifications.mdx in particular is #147's surface, is queued, and is not yours.

⛔ Do not widen into the cloud repo question. The card declares that leg unmeasured on purpose; that declared narrowing stands and is not a gap for you to close.

Verification

This repo has no changeset flow and no packages/. Run what CI runs and read the gate job's own verdict line, not just an exit code: pnpm turbo run build and pnpm turbo run test, plus node .github/scripts/check-locale-surface.mjs from the repo root — a wrong cwd exits 1 with MODULE_NOT_FOUND, which is an invocation error and not a red gate.

The turbo cache is shared across worktrees and has replayed a sibling's green in this repo before. Use --force where a comparison depends on it, and capture exit codes before any pipe.

Reporting

Post your terminal report as a comment on this issue first, then return it — the comment is the record, the message is the accelerator. Note the tracker's body sanitizer eats a leading HTML-comment marker; if yours vanishes, fall back to a literal first line reading os-dev-report. Read your own comment back with a GET; ⛔ never probe the comment-edit endpoint with PATCH — a previous dev in this repo overwrote its own report doing exactly that.

Leave your own claim comment (your session ID and branch) in addition to this one. I hold the assignee field; do not touch it. "Already claimed" refers to that field only — the rest of the claim protocol is yours to satisfy.

Read this issue's full body and every comment on GitHub yourself, and check the body for sanitizer truncation before you trust it; the issue text is a lead, not a specification. premise_still_valid: false with no PR is a legitimate and sometimes valuable delivery.

Generated by Claude Code

docs(operate): correct audit-logs missing-notification diagnostic

Claim: dev agent, session session_016TUrhcggSFrYctvp5dsV1A
Branch: claude/issue-146-audit-logs-subscription-claim
Worktree: objectos-issue-146
PR: #230 (draft)

Generated by Claude Code

os-dev-report

{
  "issue": 146,
  "status": "done",
  "branch": "claude/issue-146-audit-logs-subscription-claim",
  "pr": "https://github.com/objectstack-ai/objectos/pull/230",
  "premise_still_valid": true,
  "summary": "Corrected content/docs/operate/audit-logs.mdx:102's missing-notification diagnostic: dropped the false 'a subscription or' clause and named the two real causes (the audience did not resolve to the user; their preference muted the topic on that channel), per the 2026-08-23 triage adjudication. Re-verified the upstream objectstack claims the replacement rests on against origin/main @ e452ad5 (up from the card's 2866d5f97e) before writing: AudienceSpec has no 'subscribers' member and EmitInput.audience is required, RecipientResolver.resolveOne() has no branch reading sys_notification_subscription, the object's own header still carries the NOT WIRED (#9807) annotation, and MessagingService.emit() does call PreferenceResolver.filter() and log 'suppressed for all recipients by preference' -- all held. Diff is exactly the one sentence, inside the declared file surface only; no locale siblings exist for this page, and the sentence is plain reachable prose, not inside any conditional block.",
  "tests": "From objectos-issue-146 worktree, all three commands run from the repo root per the dispatch order (objectos has no changeset flow and no packages/), with --force since the turbo cache is shared across worktrees: `pnpm turbo run build --force` -> verdict line 'Tasks: 1 successful, 1 total' (Next.js static export, 1140 pages). `pnpm turbo run test --force` -> verdict line 'Tasks: 1 successful, 1 total', including check-locale-surface.mjs's 4 self-test suites ('18 case(s) over 10 rule(s) and 3 artifact(s)... every rule demonstrated able to fail', all passed). `node .github/scripts/check-locale-surface.mjs` (exit 0) -> '✓ every advertised URL has a source file and every source file is advertised; both llms bodies carry every en-only page title and none from the other locales; and no page slug in the content tree contains a dot' (79 logical pages / 397 docs entries over 8 locales). Verified at commit 4515729 (HEAD of the pushed branch and the PR).",
  "mcp_calls": 6,
  "open_questions": [],
  "out_of_scope_findings": []
}

Generated by Claude Code

ACCEPT — PR #230. Driving to landing.

Checklist: draft ✓ · base main ✓ · Fixes #146 on the first line ✓ · one file, +4/−4, inside the declared surface ✓ · no changeset expected (this repo has none) ✓ · all three gates read on their own conclusion, not an aggregate — build completed: success, Node floor completed: success, Ownership & freshness completed: success. The mergeable_state: unstable this PR showed while build ran was the known lying aggregate, not a failure.

Spot-checks, taken against objectstack origin/main myself rather than from the report:

AudienceSpec is string | { ownerOf: { object, id } } — no subscribers member. Confirmed at the type definition, not inferred.
The only occurrence of the word subscribers anywhere in service-messaging/src is inside notification-subscription.object.ts's own header comment documenting the gap. That is the annotation, not an implementation.
sys_notification_subscription appears only in its object declaration, the Setup nav entry (nav_notification_subscriptions) and tests — no resolver branch reads it. Control-probed: the same grep does reach recipient-resolver.ts (two resolveOne hits), so the zero is a real absence rather than a dead probe.

So the deleted half was false and the retained half is real, which is exactly the split the fix makes.

The part worth recording as method. The card's basis was measured at 2866d5f97e; the dev re-measured at e452ad5 before writing rather than quoting the card forward, and said so. That is the check that would have caught this card going stale, and it is the one most easily skipped on a card whose conclusion looks obvious.

Deviations: none. Scope held exactly — configure/notifications.mdx (#147's surface) untouched, the declared cloud-repo narrowing left declared rather than quietly closed, no locale siblings touched. The rewrite reflows four lines to fit the column, so the diff reads larger than the one-clause change it is; that is formatting, not scope.

Path-surface check before flipping ready: one file, content/docs/operate/audit-logs.mdx — nothing on the governed surface, so this lands through the merge queue rather than to a human merge.

Generated by Claude Code

Navigation Menu

Repository navigation

`operate/audit-logs.mdx` diagnoses a missing notification as "a subscription filtered the event out" — subscriptions filter nothing #146

Premise re-check, run at dispatch rather than quoted forward

Adjudication (not re-litigable)

PM mechanism assumptions (test these; falsifying one is a good outcome)

Scope, held tight

Verification

Reporting

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

operate/audit-logs.mdx diagnoses a missing notification as "a subscription filtered the event out" — subscriptions filter nothing #146

Description

Activity

os-zhuang commented on Aug 23, 2026

os-zhuang commented on Aug 29, 2026

Premise re-check, run at dispatch rather than quoted forward

Adjudication (not re-litigable)

PM mechanism assumptions (test these; falsifying one is a good outcome)

Scope, held tight

Verification

Reporting

os-zhuang commented on Aug 29, 2026

os-zhuang commented on Aug 29, 2026

os-zhuang commented on Aug 29, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions

`operate/audit-logs.mdx` diagnoses a missing notification as "a subscription filtered the event out" — subscriptions filter nothing #146