Skip to content

Source snapshots and verification limits

Baseline reviewed October 28, 2026 for T-100498; scoped follow-up November 3. Commit-pinned links on each page support the adjacent claim/table/diagram. These are source snapshots, not runtime attestations.

Source register

Repository Reviewed lane Commit
riveroaks/portal main 7f23ffabbf74
riveroaks/portal dev 16bf5ba88b05
riveroaks/portal-api main e3a6ee25be59
riveroaks/portal-api dev 4ede0383c5bd
riveroaks/portal-ios dev 642d022b4f07
riveroaks/infrastructure/lyric-follower main 68d08de85e9d
riveroaks/infrastructure/lyric-follower feat/clearcom-whisper-transcription (feature branch; not a release claim) 23432363e520
riveroaks/infra main bbc67e98e6dc
riveroaks/infrastructure/service-timeline main 834599c55bdf
riveroaks/infrastructure/av-signal-health main 56a14a91ee77
riveroaks/cloudflare-forms main 351d1b1c365c
riveroaks/cloudflare-email main 16e3e0b205be
riveroaks/cloudflare-short-links main 9ef74f212374
riveroaks/cloudflare-mobile-edge main e887dbdc6484
riveroaks/church-app main 280217b61e24
riveroaks/docs main cd0d4f31f8c1
riveroaks/service-monitor main 7c36dc50ae0c

November 3 follow-up

The iOS file links have been refreshed to the reviewed November 3 dev snapshot. Other baseline links retain their original review pins. The follow-up checked current Portal BFF/token/comms interfaces and API catalogs: production API e3a6ee2 remains unchanged; the Portal dev BFF and token/core/comms files are unchanged from the baseline. The added coverage below comes from current implementation, not old task notes. Other repos' snapshots are not a claim that they have stopped evolving.

Repository/lane Follow-up commit Coverage
Portal main f92975cf80cf604316bc3a47e9618d86e03d817a BFF allowlist/core/comms delta; API-token boundary preserved
Portal dev 0a8d4839f76abe9e11019c947b63212f956b27b6 Stable BFF/token boundary; bounded LAN service-alert publisher
Portal API dev e97a23073ea399a96fe6666d966d4a7d996e2fa9 Current contract; prior API/origin relationship preserved
Portal iOS dev 642d022b4f0737c24c584f391ca7ef7240d44652 Managed Q-SYS host/trust, shared packages, Utility target and manual release, LAN alert monitor
Lyric follower main 702b06f57cc49beec3b8088138927bba01937ee3 Default-off hybrid evaluator, native NDI development/activation boundary
Infra main cec9f3f00b76f9e221f57ac97eb56165d7182c64 Source-restricted LAN service-alert alias and current private-docs proxy
Docs main f9ecd275dacf8875405e0aed2fe83cf7d9e68af4 One corpus for both publishing destinations; no folder-level privacy filter

This follow-up performs no Portal promotion, iOS merge, lyric/device activation, SSO, ingress or other infrastructure change. API catalog additions owned by other workstreams are not changed here.

Verification limits

  • File links resolve to the reviewed Git objects. No live account records, credentials, transcripts, recordings or production database contents are needed to verify this document.
  • API production and dev source differ. Consult the matching catalog and deployed release evidence before treating a dev capability as production behavior.
  • The transcription producer is cited from a feature branch. Its source, historical trial installation, merge status and running version must be verified independently.
  • The API operations prose says invocation logging is disabled, while the module declares invocation_logs = true; the implementation is the evidence used here. Likewise the production module reuses the dev-owned VPC Service despite older operations prose describing separate VPC Services.
  • Anonymous private HTTP feeds have source ACLs in nginx. The PHP lyric socket itself only checks the comms opt-in flag; public-edge filtering, WAN reachability and socket confidentiality were not certified by this source audit. Do not expose those feeds through a new public route or port forward.
  • Presence of a systemd unit, container tag, nginx route or protected CI job does not prove it is active. No runtime deployment or core infrastructure change was performed to collect this architecture evidence.
  • External hostname routes, current Access policy rules, publisher commissioning, physical-device permissions and full-service capture acceptance remain operational verification items. The docs publishing result is recorded in T-100498, not inferred from the architecture snapshots; both November 3 publication jobs passed, but the private cluster image requires the separate digest promotion.

Implementation references for those limits: portal-api · src/contract.ts, portal-api · src/contract.ts, portal-api · docs/OPERATIONS.md, portal-api · infra/modules/portal-platform/main.tf, infrastructure/lyric-follower · docs/deployment-pipeline.md, portal · lyrics/server.php, infra · nginx/hosts/rocc-db/sites-enabled/lyrics.riveroaks.cc.conf.