OQ6 selects a provider-neutral temporal Bird View inheriting the shipped citation, coverage, pagination, and honest-degradation envelope. OQ5 keeps per-viewer seen state explicitly non-authoritative. These belong in one presentation/query leaf; Task claim remains separate.
This is one fully closeable PR leaf under Epic #15145. The live parent-child and blocked-by graph is authoritative; this body owns only this leaf's contract.
The Problem
A live-query-only explorer is not durable completeness, while a cached narrative or global seen flag can become false authority. Automatic title/body delivery also introduces cross-tenant leakage and prompt-injection exposure.
The Architectural Reality
The provider-neutral query/application surface belongs in Memory Core and injects the GitHub source adapter, following PullRequestHistoryService.mjs plus temporalBirdViewEnvelope.mjs. Prose drill-down reuses source-relative trust from the GitHub reconciliation foundation; the default temporal view is metadata/citations. The operation name cannot encode GitHub.
The Agent OS structure map was run on 2026-07-14. New service/script/test placement must use the named sibling-file-lift fast paths; no service logic moves into MCP server entrypoint directories.
The Fix
Expose a paginated half-open-window community-activity Bird View with manifest/revision identity, coverage/gap fields, citation-backed drill-down handles, explicit notAuthority, and per-viewer idempotent seen markers. Explicit prose drill-down rechecks tenant/source-relative trust and hostile-content projection at read time.
The community substrate is not a mirror of every GitHub repository notification. It separates:
source occurrences needed to reconstruct supported issue, pull-request/review, and Discussion conversation state; and
attention-eligible community items: externally authored, response-bearing occurrences that may need maintainer attention.
Stars/un-stars, forks, watches, and equivalent popularity telemetry are outside the community-event source families and cannot enter Bird View, counts, wake, or Task claim. Internal/rostered actions may update or resolve the state of an existing external item without minting new community attention. First-time versus trusted-repeat external status affects trust/projection, not basic eligibility. Bot eligibility must be an explicit ADR disposition and cannot be inferred from provider actor kind or trust tier.
Attention eligibility remains zero-authority: it does not assign work, enter LifecycleFrontier, or create a Task. Only the explicit canonical claim transition owns that promotion.
Acceptance Criteria
AC1 — The operation name and response schema are provider-neutral while GitHub is the first adapter.
AC2 — Half-open windows, stable pagination, source-manifest identity, coverage, gaps, and degraded reasons are explicit.
AC3 — Every synthesized/drill-down fact is citation-backed and notAuthority remains true.
AC4 — Default results contain metadata and handles, not automatically delivered title/body/excerpt prose.
AC6 — Per-viewer seen writes are idempotent and isolated across viewers/tenants.
AC7 — Seen cannot change unclaimed counts, create/bind Tasks, enter LifecycleFrontier, or rank Golden Path.
AC8 — Deleted/inaccessible/unknown content remains distinguishable without retaining stale prose.
AC9 — MCP/SDK schemas and focused tests cover pagination, coverage, denial, and independent degradation.
AC10 — Default community results contain only attention-eligible external items; internal/rostered occurrences may explain current resolution state but never appear as new attention rows.
AC11 — Star/un-star, fork, watch, and equivalent popularity events are negative fixtures and never appear in results, counts, seen state, or drill-down handles.
Creation duplicate sweep: immediately before filing at 2026-07-14T05:31:17.761Z, checked the latest 20 open issues and last 30 all-state A2A messages. The independent broader audit at 2026-07-14T05:13:00Z covered open and closed issues, pull requests, A2A, ADRs, and code; no equivalent owner or foreign claim existed.
Context
OQ6 selects a provider-neutral temporal Bird View inheriting the shipped citation, coverage, pagination, and honest-degradation envelope. OQ5 keeps per-viewer seen state explicitly non-authoritative. These belong in one presentation/query leaf; Task claim remains separate.
This is one fully closeable PR leaf under Epic #15145. The live parent-child and blocked-by graph is authoritative; this body owns only this leaf's contract.
The Problem
A live-query-only explorer is not durable completeness, while a cached narrative or global seen flag can become false authority. Automatic title/body delivery also introduces cross-tenant leakage and prompt-injection exposure.
The Architectural Reality
The provider-neutral query/application surface belongs in Memory Core and injects the GitHub source adapter, following
PullRequestHistoryService.mjsplustemporalBirdViewEnvelope.mjs. Prose drill-down reuses source-relative trust from the GitHub reconciliation foundation; the default temporal view is metadata/citations. The operation name cannot encode GitHub.The Agent OS structure map was run on 2026-07-14. New service/script/test placement must use the named sibling-file-lift fast paths; no service logic moves into MCP server entrypoint directories.
The Fix
Expose a paginated half-open-window community-activity Bird View with manifest/revision identity, coverage/gap fields, citation-backed drill-down handles, explicit notAuthority, and per-viewer idempotent seen markers. Explicit prose drill-down rechecks tenant/source-relative trust and hostile-content projection at read time.
Contract Ledger Matrix
Decision Record impact
Depends on ADR 0036, admission, and all GitHub reconciliation leaves; composes ADR 0035 without creating ranking or lifecycle authority.
Decision Record
Required: ADR 0036. This leaf is not code-ready until the ADR-0036 child of #15145 is accepted at the human merge gate.
Discussion Criteria Mapping
Source authority: Discussion #15139 body at the version-bound graduation anchor plus Grace's STEP_BACK and GRADUATION_APPROVED.
Operator Scope Clarification — 2026-07-14
The community substrate is not a mirror of every GitHub repository notification. It separates:
Stars/un-stars, forks, watches, and equivalent popularity telemetry are outside the community-event source families and cannot enter Bird View, counts, wake, or Task claim. Internal/rostered actions may update or resolve the state of an existing external item without minting new community attention. First-time versus trusted-repeat external status affects trust/projection, not basic eligibility. Bot eligibility must be an explicit ADR disposition and cannot be inferred from provider actor kind or trust tier.
Attention eligibility remains zero-authority: it does not assign work, enter LifecycleFrontier, or create a Task. Only the explicit canonical claim transition owns that promotion.
Acceptance Criteria
AC1 — The operation name and response schema are provider-neutral while GitHub is the first adapter.
AC2 — Half-open windows, stable pagination, source-manifest identity, coverage, gaps, and degraded reasons are explicit.
AC3 — Every synthesized/drill-down fact is citation-backed and
notAuthorityremains true.AC4 — Default results contain metadata and handles, not automatically delivered title/body/excerpt prose.
AC5 — Explicit prose drill-down revalidates tenant, source, collaborator/trust, and hostile-content projection.
AC6 — Per-viewer seen writes are idempotent and isolated across viewers/tenants.
AC7 — Seen cannot change unclaimed counts, create/bind Tasks, enter LifecycleFrontier, or rank Golden Path.
AC8 — Deleted/inaccessible/unknown content remains distinguishable without retaining stale prose.
AC9 — MCP/SDK schemas and focused tests cover pagination, coverage, denial, and independent degradation.
AC10 — Default community results contain only attention-eligible external items; internal/rostered occurrences may explain current resolution state but never appear as new attention rows.
AC11 — Star/un-star, fork, watch, and equivalent popularity events are negative fixtures and never appear in results, counts, seen state, or drill-down handles.
Out of Scope
Task claim, count/wake projection, Fleet UI, cached Bird-View narratives, ranking, or automatic assignment.
Avoided Traps
Do not name the operation after GitHub, reuse live provider query as completeness, globalize seen, synthesize through gaps, or place prose in hooks.
Related
Origin Session ID: 837ad74b-c2d2-413d-9aab-b7165a93a82a
Handoff Retrieval Hints
provider neutral community Bird View seen non authoritytenant source relative prose drilldown citations coverageCreation Freshness
Creation duplicate sweep: immediately before filing at 2026-07-14T05:31:17.761Z, checked the latest 20 open issues and last 30 all-state A2A messages. The independent broader audit at 2026-07-14T05:13:00Z covered open and closed issues, pull requests, A2A, ADRs, and code; no equivalent owner or foreign claim existed.