Eve library

V1-002 — V1 runtime and publication defect closure

Evidence

Revision 1

On this page

Status: all six V1-002 repository requirements are complete, including the 1,937-root operational-state inventory and executable loss proof for every retained ephemeral owner.

Final all-store closure source commits: 80873ce591e73471090129de651a049605bab858 and 7e7cd0662d2891018d02e6a19ce736fe58f18a1f.

This evidence file is an append-only implementation history. Statements in earlier dated sections that the parent all-store row was still open describe the state at those intermediate commits; they are superseded by “2026-07-27 — Final retained-ephemeral gate and V1-002 closure” at the end of this file and by the current status above.

Restart-publication implementation source tip: 7e519c01c2cadfa34c7459bd7f44781b355fbbf8. Latest identity-durability progress source tip: 05856d6c76007de3a08d1c0a349ce2f8f547d7f3 (published through e6d37a508a0ef4ab72df6798f00fa790a6f507a0). Latest generated-artifact stored- object purge source tip: c41b4661da7f29f51628d957f106f128811efc53 (published to origin/main through integration tip c974990c8104a7d5bd3aa0230223bd2d38542047). Latest notification-state durability source and published tip: 067d5fff4634a189a751faa366f4ac0342073a61. Latest personalization-state durability source and published tip: 90e6592487f2be1d36069c9be4789fcf1e9120c2. Latest customer message-center durability source and published tip: 25f9acaf3fba4cc20859b2472b4a90589457e4bd. Latest device-token durability source and published tip: e6b90e13762cc94a8b8a0f70750248c9b4f14519. Latest customer channel-binding durability source and published tip: c6e034e46dbe119409147fa6d3356fe3d2f0d274. Latest per-user Telegram durability source and published tip: 6262e3a94e09aded2f2b5ead93d035366a7fc2e1. Latest celestial ritual-schedule durability source and published tip: 844ee060a65e29a55ea6028959c2763bbdff621c. Latest wearable-health durability source and published tip: 0656aabd9b7a3b57588f897be492a8b9c49a3b7a. Latest morning-capture durability source and published tip: 989ce593373199adf3e752e1da89f59089a66e3c. Latest customer data-export durability source tip: f50976ba40460ecdc6b413f9e9ff1a57a1b5f50e (published through integration tip 25b510fbe0701062b54c88caef88146e957b81ef). Latest customer-consent durability source and published tip: 58c932258048f74f1c40cdf97e7a0c2a5380a79a. Latest customer-billing and Fiat Stripe durability source and published tip: e390bf2c0a8565cec2f044c190c71ef27162a2bd. Latest customer-feedback support- case durability source and published tip: 48a0b27374fbdf12aad257c7f51e4f8e5f507c32. Latest signup-verification and signup-velocity durability source and published tip: 78d1d455e24d1a559c77a0bd1ccce67cab935307. Latest member-library learning/content authority and collection share-policy durability source commit, published to origin/main: ec2be9918cfafcdeb0c42fbebd97cd538ca49a71. Latest bounded recent-search learning-state durability source and published tip: 1c456fe472216149c4fe1296cbae12b4db191165. Latest scene tip-ledger and counsel payout-authority durability source and published tip: df93bd737dcd05434a71cafdd6de6cfa755aeba2. Latest connected scene-tip financial retention source and published tip: 5e22686cf704fbd3f89c009cffc839b3f3c484f1. Latest connected customer-feedback support-case retention source and published tip: c8e99bf217937a9797c1cee9218d1955ec6d5d60. Latest connected Themis moderation-appeal support-case retention source and published tip: abe4159c3b4de8f6bd716117d426d8a11a9fc146. Latest connected Living Scene abuse-report support-case retention source and published tip: 7544b773daa7c9aec87a29a28e7a95f093facd3e. Latest scene-appreciation and velocity-authority durability source and published tip: 6867a88a670ac3ce690fe017f077288d0d0c9d89. Latest scene-follow and premiere lifecycle durability source and published tip: f162352a9587fdbef46d47c4209defa433fb49a7. Latest group-practice session lifecycle and private leave-audit durability source and published tip: 68bba491d06af85d1e2010559b50b223580fea24. Latest Metis/Themis academic-record, gradebook, notification-outbox, and evidence_pack durability/privacy source and published tip: 65200d9e043b3acefd6eef19743e2de7f7033e97. Latest connected Metis academic evidence_pack expiry source and published tip: d01e4c2c315f3156b4abb4c1b26d39c36cc558fb. Latest Stripe provider-native Customer deletion source and published tip: 1ecef2d5c36ae810d5666b2434752736aa44d42d. Latest shared compliance-retention executor and connected Fiat Stripe expiry-purge source and published tip: 068f2a2619f01933181773302c7d2b3056040366. Latest connected customer-billing expiry-purge and Apple replay-chain attribution source and published tip: 7c93da74220ddac485f90c4de72e4c71ea62c070. Latest canonical Isis GeneratedOutput DSAR source and published tip: 82497742474e5ae6354fa824c5e35a58a146bc2b. Latest canonical shared-V1 journal, ritual, and academic-record DSAR source and published tip: 234523f6c6323ab4a546828c2fa2adba37120247. Latest local calendar OAuth connection authority, DSAR, and profile-erasure source and published tip: 20b4e99fa49118643894e5e8413fd20f195e7625. Latest Arete weekly-review, living-offering, and coach-decision continuity authority, DSAR, and signed erasure source and published tip: 43a87fdb6e03cea3e92f00f6250fd19550f547b1. Latest Nyx saved-object, event-reminder, and search-count continuity authority, DSAR, and signed-erasure source and published tip: 5abc400e018c6beff1bc0302a795bd000b642d27. Latest authenticated client-state continuity authority, DSAR, signed erasure, and canonical inactivity-retention source chain: initial durability commit aedda7fe1ac5a05fdf90ea8b1ebe71c674535711, corrected and published through c0681992f5638c86ccf8d73b442d31da99e7b67d. Latest authenticated Psyche dialogue-session acknowledgement, recovery, conversation-history DSAR, signed erasure, and legal-hold-aware retention source and published tip: ea6721e1d1bc0d92ff41f16e611729fae828fe2d. Latest shell-assistant and external conversation.turn.recorded transcript acknowledgement, recovery, DSAR, signed erasure, and legal-hold-aware retention source and published tip: b8d4535215eb9f8abace1d556d02bc893461d572. Latest shell-assistant session- continuity checkpoint acknowledgement, recovery, DSAR, signed erasure, and bounded-retention source and published tip: 140a6bce686dac8d1c41fd811e7663f3c65b214a. Latest connected BFF Iris memory acknowledgement, restart recovery, memory_scope DSAR, exact local erasure, and bounded-retention source and published tip: a64a03415eda5b11a2edb283a7b2f2e2622326cf. Latest DMCA statutory-case authority, uploader privacy, and retention source: 9d8faf8bf6fe90b0f5fe865baa93fed55d5e5234. Latest DSA decision authority, affected-account redaction, MAR attestation, and review-package retention source and published tip: a839ad6ffd802a919135e6d445eb290a37a792cd. Latest authenticated Metis ingest-job acknowledgement, recovery, learning-state DSAR, and exact erasure source and published tip: 10c0ef948db6813c3d1db2b81ddc483c9d9dc2ef. Latest authenticated Metis tutor- session memory, mastery-posterior, continuity DSAR, signed-erasure, and bounded- retention source and published tip: 87c6cb62d615504adfc37ecfeb114ca0d2145da8. Latest Metis BYO-material operator-decision acknowledgement, recovery, operator-redaction, and review-package retention source and published tip: e417f95c0ee568dd9b2a7865d3f095d5e1e789b1. Latest general operator-inbox decision acknowledgement, recovery, reviewer redaction, and review-package retention source and published tip: 9609569b9ec8883296953100a7aaad0b9c819244. Latest connected Themis moderation-appeal operator outcome and DSA reporting source and published tip: 2a7f20afcb6f18de1cfef779af5a2d0cdd710934. Latest shared operator-incident durability/privacy/retention source and published tip: f74af22b7e296edf23827c6155d5ebeed1d5d376. Latest citation-drift terminal- resolution and source-classification durability/privacy/retention source and published tip: bf5cc04b0dfef3753ba1aca48762cf883e2a286e. Latest runnable production BFF artifact build and smoke-gate source and published tip: f52037994aeb2229960e8c23d67e44da6b31663f. Latest operator persona-lifecycle authority durability source and published tip: d145bc035f60448c688e79d458b9f71178587905. Latest payment-time chargeback- screening durability, exact-id billing export, account-redaction fence, and compliance-retention source and published tip: bc7cf14ab3811627b8520265014cf3bcda7d9968. Latest crypto-invoice issuance, settlement, receipt, entitlement-reconciliation, privacy, and retention source and published tip: b8f31c4d344131bf7c155175ba62fc1051cba853. Latest model-governance license-registry and admission-decision authority source chain: initial durability commit 250f2fcc66a629eb1210d8aea3baeeb5c84d3d1c, followed by the PostgreSQL JSONB structural-equality correction and published source tip 3f30e0aa302ab2a720b55516c47db80c385d497b. Latest authenticated Iris desktop- to-mobile handoff authority, continuity lifecycle, and bodyless mobile-DELETE transport source and published tip: 93d0a355339e7e42db8a14d5bd97da3ee6b7ab6c. Latest authenticated Studio world-configuration, story-graph, quest, and timeline authoring-record durability, continuity DSAR, signed erasure, and bounded-retention source and published tip: 6d1b0d3983a81b64cad39eaf8744a92426ddbc95. Latest authenticated Mentor Presence rendered-performance durability, exact media DSAR, signed erasure, and legal-hold-aware bounded-retention source and published tip: 1b7533f36846528641f8a1da36c6b9eb26d1a5e7. Latest authenticated Lilith Studio Tara scene-publish durability, exact-manifest DSAR, signed erasure, and legal-hold-aware bounded-retention source and published tip: 343b87fe359270d1ad756050f2f67a1ffebd52a4. Latest weekly-digest input ephemeral/recomputable disposition source and published tip: 28e6582b8da2d424e82a6c14adac59676b2688b7. Latest tenant Living Scenes code-backed policy/live durable-audit authority disposition and published tip: ea3169fe8a0de109d11047548f14c4ac2cc4b65f. Latest legacy process-local takedown/repeat-infringer authority retirement source and published tip: add4cec8f42e1bd12193f9084d58ba20bc4d74de. Latest on-call schedule ephemeral/static-configuration disposition source and published tip: 26a84182fa3072dae0995672fd3ffe4843308011. Latest contextual-help ephemeral/static-definition disposition source and published tip: cb247571dd183cb6cead4a4a265fc032a4e9413e. Latest unavailable scene projection disposition source and published tip: 950617ce2dca9840238b38a594768b520871bd55. Latest account-protection screening durability, session privacy, erasure, and retention source and published tip: 93484dede75567663f6606f3aaca372af9b7f2c3. Latest connected Isis artifact- detection review-package durability, operator privacy, retention, and browser source and published tip: bce1e432032d95a8570ea989505b88db2674c53a. Latest connected Isis 3D-benchmarking review-package durability, operator privacy, retention, and browser source and published tip: b4623dfe0e8ed9a6e9e776260f054cf7e602a4a0. Latest connected Isis feedback- evaluation review-package durability, operator privacy, retention, and browser source and published tip: 6998eb4883bd8437c3bf5b414b7ee0fbb7551552. Latest connected Isis model-quality assessment review-package durability, operator privacy, retention, and browser source and published tip: d1bbb3ca0f14fa8d913239dd4f86887cea463b28. Latest connected Isis texture- quality diagnostic review-package durability, operator privacy, retention, and browser source and published tip: b0728341aa7a065968e9f90eaf9d040501bb4732. Latest connected Isis content-safety diagnostic review-package durability, integrity, operator privacy, retention, and browser source and published tip: 181979d868d606715a4d71179f16e1df827efad2. Latest connected Isis resource-recommendation governance history source and published tip: e1a7ae32087b1b17cd3d37cef9df7a3afd791dd7. Latest connected Isis intelligent-routing governance history source and published tip: 1f90b287735cf6087e64aec76a999b4317891036. Latest connected Isis cost-tracking governance history source tip: 8bab273a22d48801748efc21c7ed062166824288, published and verified through ae490aa4fb500ad0c6e471999eb5ed70b2f34727. Latest connected Isis cost-optimization ephemeral/recomputable disposition source and published tip: 9dc92a2905b182d4e4bcca11393ca1b0b0e6d43e. Latest connected Isis prompt-template preview ephemeral/recomputable disposition source and published tip: b876a5ce0e393ef732ea32a7af899e9daf9cef5a. Latest Isis managed-model registry unbound/empty projection disposition source and published tip: 5a47c333dd7a5117920a21966b16035dcdd9ef4f. Latest Isis Civitai intake unbound/empty projection and disabled-decision disposition source and published tip: a2e8e0d69d1fb4bc667c10594b884b27b85f747a. Latest Isis model-merging unbound/empty projection and disabled-plan disposition source and published tip: 8dca9a9e33996b791085b663b59d46ddcffbd0a6. Latest Isis voice-cloning unbound/empty projection and disabled-workflow disposition source and published tip: 73d0f24553b3fb596c97d0374973b35542b0490d. Latest Isis 3D Editing browser-local workspace and request-local repair- simulation disposition source and published tip: f7c89cc85db1f1641911a3384b00ed99af7ff13f. Latest Isis 3D Generation request-local structured-prompt preview disposition source and published tip: 45f1a952fa76045ddafc3210f2ee60cf7431fe89. Latest Veritas personal-retraction acknowledgement durability, profile DSAR, and exact-subject erasure source and published tip: 44e733459bd13b60dbffea5b5c64dedc2430220c. Latest Tara procedural ambient-WAV cache disposition source and published tip: 6d185b90dc7d93ddf02af9e1e93e507067f15675. Latest V3 regional-waitlist unbound/disabled collection disposition source commit, published to origin/main: 29228d13b6. Latest Isis reference-bank false-authority retirement source and published tip: 3ec98e462988da49aa6d223d27c55204c8443559. Latest Isis scene/production/lecture ledger false-authority retirement source and published tip: b6a090c7922f38e9db307e6ec653f89d28c53cea. Latest Year in Practice orphan activity-summary disposition source and published tip: 8ed2347d86e9a352bdd5d87ca6a885f5a06d7575. Latest Nyx Sky Tonight false-state retirement source and published tip: 72e97fd5fdf8f14b3c1b0214e5d259e9424f1ca4. Latest privacy-receipts false-state retirement source and published tip: 24e010e7632b38d49c5188452b428f32aa5db31b. Latest follow/premiere read-through fail-closed source and published tip: 978fb8b1fe98ee72ac3ebfa5ea33f46112143730. Latest Studio workspace-telemetry shadow-buffer retirement and canonical analytics transport source and published tip: 81969832b2d2421779e501172d6a0159610c701d.

Work-package charter#

  • Task ID: V1-002
  • Owner: V1 Agentic Studio, creative-autonomy, BFF generation, publication, privacy, and common run-protocol maintainers; integration auditor: Codex
  • Accountable product: V1
  • Priority / milestone: P0 actual-path runtime and publication integrity
  • Risk tier: critical authority-loss, duplicate-publication, stale-approval, unscorable-media, false-proof, and sensitive-data risk
  • Dependencies: AUTH-002, COST-001, HITL-001 through HITL-004, RUN-003, RUN-005, MEDIA-001, PROOF-002, PROOF-003, PRIV-001, the admin snapshot database, and Redis when generation caps are configured
  • Affected source: creative review approval records, common-run approval mapping, director publication authorization, editorial publication identity and reconciliation, autonomy-plane persistence, AgentRun and human-authority state, generation claims/effects/usage/admission, operator kill-switch and audit state, governed Studio state and its signed continuity-deletion fanout, the central admin workspace, the customer account-deletion schedule/receipt ledger, authenticated analytics-event ingestion and erasure, uploaded profile avatar durability and byte erasure, canonical Arete journal and Tara ritual record erasure, acknowledgement-bound Arete weekly-review closures, living- offering decisions, and coach decisions with exact continuity_state export and erasure, acknowledgement-bound Nyx saved celestial objects, event reminders, and search-count aggregates with exact continuity_state export and erasure, acknowledgement-bound authenticated client-state slots with exact continuity_state export, erasure, and 30-day last-access expiry, owner-scoped library-collection durability and erasure, saved library-item acknowledgement and resurrection-safe erasure, member-authored Nisaba notebook durability and erasure, acknowledgement-bound authenticated Studio world-configuration, story-graph, quest, and timeline authoring records with exact continuity_state export, erasure, and 30-day inactivity retention, the acknowledgement-bound Mentor Presence rendered APNG performances with exact generated_artifact export, erasure, and 365-day creation-time retention, the acknowledgement-bound Lilith Studio Tara scene-publish receipts with exact manifest export, erasure, and 365-day creation-time retention, the historical evidence-pack structural-absence mapping and its real owner-keyed Metis academic-record replacement, durable consumer profile/preferences, durable customer authentication accounts and session-secret metadata, durable device-session/audit state, acknowledgement-bound device push-token registrations, exact profile and count-validated session erasure, acknowledgement-bound customer email, SMS, and WhatsApp binding verification and exact profile erasure, their BFF acknowledgement boundaries, acknowledgement-bound per-user Telegram captures, link, voice, and delivery preferences with exact saved_claim_passage and profile erasure/export fanout, acknowledgement-bound celestial ritual schedules with exact continuity_state erasure/export fanout, durable wearable-health delivery intents, provider identities, session/HRV state, provider-confirmed ritual_completion erasure, and configured exact-owner DSAR reads for canonical V1 ritual rows, acknowledgement-bound morning-capture journal state, exact journal_entry erasure/export fanout, configured exact-owner DSAR reads for canonical V1 journal rows, configured exact-learner DSAR reads for Metis assessment evidence and academic-integrity verdicts, acknowledgement-bound customer data-export request metadata and exact short-lived bundle bytes, acknowledgement-bound canonical customer-consent current state, complete retained decision evidence/history, expiry, policy revision, and DSAR export, durable notification domain/persona/quiet-hours/digest preferences, durable notification read/unread/dismiss state, exact profile and continuity_state erasure/export fanout for those partitions, acknowledgement-bound personalization vectors and active-persona selection, exact personalization_vector erasure/export fanout, acknowledgement-bound customer message history, receipts, opt-outs, and delayed dispatches, exact continuity_state erasure/export fanout for that partition, acknowledgement-bound billing, trial, cancellation, family, App Store, scholar, entitlement-projection, Stripe attribution, webhook replay, and payment-event state with compliance redaction and DSAR export, acknowledgement-bound customer feedback submission and operator triage with support_case export, contact-consent minimization, and account redaction, durable pre-account verification delivery reservations, code state, resend/velocity authority, and challenge bindings with secret-minimized snapshots, session export, and exact email-owned account erasure, acknowledgement-bound imported member cards and FSRS learning state, citations, captured artifacts, followed-story state, passage collections, mastery targets, collection visibility, named-user grants, and hashed link grants with verifier-redacted export and exact subject erasure, acknowledgement-bound recent-search learning state with a 90-day retention window, conversation_history export, and persistent exact-subject erasure, acknowledgement-bound authenticated Psyche HTTP/WebSocket dialogue sessions with strict recovery, raw-turn conversation_history export, persistent exact-subject erasure, and 30-day creation-time retention that honors active legal holds and category retention exceptions, acknowledgement-bound shell- assistant user/assistant exchanges and external conversation.turn.recorded events with strict recovery, raw-turn conversation_history export, persistent exact-subject erasure, event acknowledgement/dead-letter semantics, and the same legal-hold-aware 30-day creation-time retention, acknowledgement-bound scene tip accrual, settlement, counsel-authority history, atomic payout authorization, billing_receipt export, and retained-financial-record pseudonymization with a persistent subject fence, acknowledgement-bound one-per-viewer scene appreciations and active-day abuse authority with continuity_state export, exact erasure, and a persistent subject fence, acknowledgement-bound viewer/creator follow relationships, premiere allocation/lifecycle authority, continuity_state export, exact two-role erasure, and persistent subject fences, generated-artifact bucket/key object-version purge, exact-owner canonical Isis GeneratedOutput DSAR with private lineage and credential redaction, normalized connected Isis texture- quality diagnostic batches and ordered fixture evidence, and normalized Isis content-safety screens with ordered message/issue evidence, operator pseudonymization, retention, tests, and this evidence/checklist. The content- safety slice changes an internal administrator-facing diagnostic workspace; it does not change a customer-facing surface or runtime moderation.
  • Rollout: hydrate every configured snapshot-backed store before accepting traffic, connect Redis before enabling a generation cap, and keep deployable mutation paths fail closed until their required sink is bound. Legacy approvals without exact bindings require review; legacy published editorial records remain readable. Every generated-artifact bucket represented by Isis metadata must have an S3/MinIO registry entry whose credentials can list versions and delete object versions. Monitor durable-write, admission, audit-append, object-purge, and publication-policy failures before raising autonomy.
  • Rollback: pause the affected autonomous, generation, Studio, and admin mutation surfaces before reverting their independently published commits in reverse order. Reverting 7e519c01c2 specifically restores the prior best-effort publication posture. Revert the evidence commit separately if the ledger must mirror a source rollback.
  • Evidence pack: this file

Requirement disposition#

Ledger requirement Current repository proof Closure state
Complete AUTH-002, COST-001, HITL-001–004, RUN-003, and RUN-005 on the actual V1 path Every named task is checked with a dedicated evidence pack and source commit. The V1 BFF route invokes governed tools and measured accounting; the operator console and intervention/authority bindings operate the durable product envelope; the common effect and approval lifecycles are composed into that path. Closed by constituent implementations and refreshed integration tests
Make every required store durable/recoverable and prove ephemeral loss harmless The autonomy plane and subsequent hardening chain now cover AgentRun/human authority, generation claims/effects/usage/admission, kill-switch authority, audit evidence, governed Studio state, the central admin workspace, the customer deletion schedule/receipt ledger, authenticated analytics events, uploaded profile avatars, owner-scoped library collections, cross-device saved-library items, member-authored Nisaba notebooks, consumer profiles/preferences, customer auth accounts and token-family metadata, device-session/audit state, notification preferences, notification read/unread/dismiss state, personalization vectors, active-persona selection, customer message history/receipts/opt-outs/delayed dispatches, morning captures, customer data-export request metadata and exact export-bundle bytes, canonical customer-consent state with complete retained evidence/history, imported member-library learning/content state, collection share-policy authority, bounded recent-search learning state, and authenticated Studio world-configuration, story-graph, quest, and timeline authoring records. Each covered write has an awaited or response-bound acknowledgement, failed-write semantics, and restart/race tests. Studio drafts, BFF-owned generated-artifact control-plane copies, subject-owned analytics events, profile-avatar inline/object bytes, canonical journal rows, both ritual-completion partitions, both collection representations, saved-item LWW rows/tombstones, member-library shelves, collection share policies and incoming named grants, the Nisaba study workspace, consumer profiles, auth accounts, refresh/recovery/verification state, device sessions, notification preferences, notification read state, personalization vectors, active-persona selections, customer message-center records, recent-search queries, BFF morning captures, short-lived customer-export bundles, and all four authenticated Studio authoring-record partitions participate in signed, fail-closed deletion fanout. Every configured S3/MinIO object version or delete marker represented by an Isis GeneratedOutput bucket/key does too. Canonical Isis GeneratedOutput metadata, provenance, and private lineage also participate in exact-owner DSAR when the dedicated database reader is configured. Compliance-retained consent records now undergo deletion-time pseudonymization and minimization before the legal-hold-aware seven-year purge executor documented below. Evidence packs contribute a signed structural-absence receipt because the deployed BFF response is request-scoped and the shared Sophia schema has no owner key; this is not a fabricated row erasure. All 16 current canonical deletion artifacts map to an injected service or the explicit evidence-pack absence eraser, and the repository full-account lifecycle completes when every eraser attests. The box stays open until the remaining operational-store inventory, provider-native deletion identities not represented by a configured bucket/key, retention-exception/legal-hold execution for compliance metadata, and other user-scoped partitions are dispositioned. Open
Guarantee publication idempotency and approval freshness across restart Approval is versioned and bound to exact plan, source, artifact, policy, and gate SHA-256 dependencies, mapped into the common run, invalidated by replacement, and checked with source half-life at publish time. The editorial publisher serializes effects, commits through the durable plane barrier before acknowledgement, uses a stable placement plus approved-candidate digest, and reconciles duplicate publish/update/takedown/rollback and lost acknowledgement after restore. Closed by 7e519c01c2 and focused restart/race tests
Provide video frame outputs to media critique Every successful V1 video provider path probes the produced clip with ffmpeg, extracts a real PNG keyframe with its SHA-256, and passes it through the executor. Media critique resolves an image/keyframe before VLM dispatch and emits a typed media_required_frame_missing hold without spending a critique call when absent. Closed by MEDIA-001 and refreshed video/media tests
Replace declared-citation and automatic-rights proxies V1 generation uses bounded retrieved passages, stable citation IDs, atomic claims, and independent claim-entailment proof. Publication rejects declared citation metadata as proof and requires artifact/output-bound license and consent receipts; provider identity cannot substitute. Closed by PROOF-002/PROOF-003 and refreshed adversarial tests
Apply privacy/retention to review, learning, full artifacts, feedback, and standing direction PRIV-001 inventories all named classes, applies explicit retention/deletion/legal-hold/backup policy, and encrypts the complete tenant-bound V1 durable snapshot with AES-256-GCM. Tests reject missing key configuration, cross-tenant/key substitution, tampering, and unsafe legacy migration. Closed by PRIV-001 and refreshed persistence tests
↳ Mentor Presence rendered-performance partition Exact APNG bytes now commit before 201, recover across restart, enforce exact-owner reads, export under generated_artifact, erase behind a persistent subject fence, and expire after the canonical legal-hold-aware 365-day window. This is progress on the parent all-store requirement only. Covered; parent all-store row remains open
↳ Lilith Studio Tara scene-publish receipt partition Exact manifest JSON and its stable receipt now commit before 201, recover across restart, enforce exact-owner list reads, export under generated_artifact, erase behind a persistent subject fence, and expire after the canonical legal-hold-aware 365-day window. The first-party editor and Playwright journey use the durable boundary. This is progress on the parent all-store requirement only. Covered; parent all-store row remains open
↳ Account-protection screening partition Successful-login and authorized-admin ATO/credential-stuffing verdicts commit as normalized PostgreSQL rows with cross-replica session-id uniqueness. Production verifies the tables before traffic; raw device and country inputs are never stored. Exact-subject session DSAR, signed erasure, a digest-only resurrection fence, and legal-hold-aware 90-day expiry are connected. Login remains deliberately fail-open on analyzer/storage failure and does not claim step-up enforcement. This is progress on the parent all-store requirement only. Covered; parent all-store row remains open
↳ Isis artifact-detection review-package partition Authenticated administrator defect reports commit as normalized PostgreSQL rows with queue-item uniqueness across replicas; production contains no synthetic history. A digest-only operator row serializes insert against account erasure, pseudonymizes retained internal quality evidence, and permanently fences recreation. Seven-year review_package expiry is legal-hold/retention-exception aware. Asset/provider/model fields remain opaque operational identifiers and are not treated as customer ownership. This is progress on the parent all-store requirement only. Covered; parent all-store row remains open
↳ Isis 3D-benchmarking review-package partition Authenticated administrator evaluations commit as normalized PostgreSQL rows with case-id uniqueness across replicas; production contains no seeded benchmark history. A digest-only operator row serializes insertion against account erasure, pseudonymizes retained internal quality evidence, and permanently fences recreation. Vectors are finite, bounded, and equal dimensional; metrics are recalculated on read. Seven-year review_package expiry is legal-hold/retention-exception aware. Labels and embeddings are internal operational measurements and are not treated as customer ownership. This is progress on the parent all-store requirement only. Covered; parent all-store row remains open

| ↳ Isis feedback-evaluation review-package partition | Authenticated administrator evaluations commit as normalized PostgreSQL rows with sample-id uniqueness across replicas; production contains no seeded quality history. A digest-only operator row serializes insertion against account erasure, pseudonymizes retained internal quality evidence, and permanently fences recreation. Predicted/reference text is bounded approved de-identified internal evidence, and BLEU/ROUGE projections are recalculated on read. Seven-year review_package expiry is legal-hold/retention-exception aware. The implementation neither accepts customer feedback nor infers customer ownership. This is progress on the parent all-store requirement only. | Covered; parent all-store row remains open |

| ↳ Isis model-quality assessment review-package partition | Authenticated administrator assessments commit as normalized PostgreSQL rows with assessment- id uniqueness across replicas; production contains no seeded assessment history. A digest-only operator row serializes insertion against account erasure, pseudonymizes retained internal quality evidence, and permanently fences recreation. Nested delivery signals, evaluator revisions, and calculated projections are strictly bounded and revalidated on read. Seven-year review_package expiry is legal-hold/retention-exception aware. Assessment ids and signals are internal operational evidence and are not treated as customer ownership. This is progress on the parent all-store requirement only. | Covered; parent all-store row remains open |

| ↳ Isis texture-quality diagnostic review-package partition | Authenticated administrator diagnostic batches and ordered fixture evidence commit as normalized PostgreSQL rows with batch-id uniqueness across replicas; production contains no seeded diagnostic history. A digest-only operator row serializes insertion against account erasure and concurrent purge, pseudonymizes retained internal quality evidence, and permanently fences recreation. Fixture inputs, thresholds, scores, evaluator revision, and stored scalar projections are strictly bounded; the versioned worst-fixture projection is recalculated on read. Seven-year review_package expiry is legal-hold/retention-exception aware. Batch and fixture ids are opaque internal operational identifiers, customer ids and source assets are prohibited, and this surface has no release authority. This is progress on the parent all-store requirement only. | Covered; parent all-store row remains open |

| ↳ Isis content-safety diagnostic review-package partition | Authenticated administrator diagnostic screens, ordered source messages, and ordered evaluator issues commit as normalized PostgreSQL rows with screen-id uniqueness across replicas; production contains no seeded diagnostic history. A digest-only operator row serializes insertion against account erasure and concurrent purge, pseudonymizes every owned internal review row, and permanently fences recreation. Message inputs, issue vocabulary, scores, evaluator revision, and stored projections are strictly bounded; the versioned evaluator is rerun from the source messages on every read. Seven-year review_package expiry is legal- hold/retention-exception aware. The surface accepts only approved de-identified internal fixtures, prohibits customer content/ids/source assets/PII, and has no live-moderation or release authority. This is progress on the parent all-store requirement only. | Covered; parent all-store row remains open |

Current evidence_pack correction for the open all-store row: its structural-absence sentence records the earlier Sophia-only state and is superseded by source 65200d9e043b3acefd6eef19743e2de7f7033e97. The BFF now injects a real owner-keyed Metis academic-record exporter/eraser. Source 234523f6c6323ab4a546828c2fa2adba37120247 additionally queries the separate canonical V1 evidence/verdict tables for the exact learner when OSHUN_V1_DATABASE_URL is configured; without that binding the gaps remain explicit. The row remains open for unfinished provider-native boundaries and the rest of the store inventory—not because evidence_pack is still absence-only, lacks local scheduled expiry, or lacks a configured canonical DSAR reader.

Five V1-002 checkboxes close. Only the all-store durability/recoverability box remains open; closing the autonomy plane does not prove that every other operational V1 store acknowledges its own durable mutation.

The open all-store requirement now also covers the closed scene tip-ledger partition: accruals, settlements, and complete counsel-authority history are ordered and acknowledgement-bound; payout calculation and settlement commit share one serialization boundary; retained financial rows participate in DSAR and account pseudonymization. This is further progress on the open row, not a claim that the remaining store inventory is complete.

The scene-appreciation partition is also closed within that still-open requirement. Current one-per-viewer reactions and the active UTC-day abuse counter now share one ordered durable snapshot. Route acknowledgement waits for the commit, daily-cap decisions are recomputed inside the mutation queue, and exact-subject continuity_state erasure removes reaction plus velocity state, persists a resurrection fence, and preserves adjacent viewers.

The scene follow and premiere partition is likewise closed within the open all-store row. Follow, unfollow, premiere scheduling, allocation, and lifecycle transitions now share one ordered snapshot; competing transitions recompute against the committed state inside the mutation queue. DSAR and signed continuity_state erasure cover a subject as both viewer and creator, remove creator-owned premieres, and persist a fence across restart. Blocklists, notification preferences, and weekly delivery counts have no production mutation producer in this store and remain explicitly external read-through inputs rather than being duplicated into its durability claim.

The continuing store inventory now additionally closes celestial ritual schedules, the BFF wearable-health partition, morning captures, the BFF billing/Fiat Stripe operational partitions, customer-feedback support cases, and pre-account signup verification/abuse state, imported member-library learning and content state, collection share-policy authority, and bounded recent-search learning state, plus scene tip/payout authority and scene appreciations. The inventory now also closes scene follows and creator-owned premiere lifecycle authority. Member-library and share-policy mutations now commit ordered snapshots before acknowledgement, restore exact learning/access state before traffic, export subject data without share-token verifiers, and compose into the signed saved_claim_passage and collection deletion services. Recent authenticated queries now commit before the search route acknowledges them, purge outside a 90-day window, export under conversation_history, and persist an exact-subject deletion fence. Scene tip accruals, settlements, and counsel authority history now commit atomically; billing_receipt exports relevant rows, while profile erasure pseudonymizes retained financial evidence and fences the subject. Accepted astronomical triggers are acknowledgement-bound continuity state, persist subject revisions and deletion fences, export through DSAR, and participate in the signed continuity_state erasure. Wearable delivery now journals stable provider operations before external effects, retains recovery identities across restart, and requires provider-confirmed erasure before the signed ritual_completion fanout can remove canonical rows. Nyx saved objects, event reminders, and per-member search-count aggregates now commit one ordered snapshot, export under continuity_state, and hard-delete behind a durable subject fence; object-search query strings are not retained. Morning self- reports now acknowledge only committed snapshots and compose into signed journal_entry erasure and export. This progress does not close the still incomplete all-store inventory or provide the absent production HealthKit/Google Fit adapter.

Constituent implementation chain#

The 2026-07-18 filter-repo rewrite reissued every earlier commit with a new identity. Rows not explicitly labeled as currently published preserve the pre-rewrite identities captured when their evidence was verified; they are historical audit identifiers, not claimed to resolve in the rewritten object graph. No unverified old-to-new mapping is silently substituted here.

Control Recorded source identity
Governed V1 tool execution AUTH-002 e659629be3beab421e254a6082171410393547b1
Measured V1 usage/cost accounting COST-001 f0441eda501f459fbb85bfb28bf761c919bbee63
Human-usable operator console and real BFF proof HITL-001 06fe5f10396c0f52e22ccb92bfbb8f3369cb8401 and 7244cd392183bc26c1fa4f18b65b61ede1ada8a4
Complete intervention domain API HITL-002 c6d53c2c25170209834d072b520ffbac2411d04b and cfa056db69aea4170c8211f3a23e08956252b0a8
Transactional provenance-bearing intervention HITL-003 10f8aa6505384232602c879de91572643f7a3e5d
Composed V1 authority and authoring HITL-004 85f4f126f0c79a4e811e42813484aa9e780ca29d and 432ef426e4a27e890bb8d3826ae7ce6e502b99ea
Idempotent/reconcilable effects RUN-003 aee2879220a22a0bc4402c5828a13acb135059a3
Atomic approval/execution lifecycle RUN-005 f20ba9c007fdd175ed45faea2893a1768bdf0982
V1 durable publication and current approval binding 7e519c01c2cadfa34c7459bd7f44781b355fbbf8
Video frames and typed media holds MEDIA-001 f8046ba3a573f082aa24e95573cd30de8a5c31d6
Semantic grounding PROOF-002 40d160fb7cf8941522a290682a781c80b2f2f9a6
Rights, consent, provenance, and signatures PROOF-003 integration tip 19a2057f6e0691be92881b4c1cfd4989d3acf21f
Sensitive-data governance and protected V1 snapshot PRIV-001 e155aa7f2ef852e550028506b0dba38513821809
AgentRun lifecycle and human-authority durability 30e4f733a845535aaf635a8e4489d0cf72815017
Generation claims queue durability ca1ec9e557e8af6a348f268327ecaa5503e195dd
Generated-output lineage/effect durability 4e6bb82984353c6c21f753e9b5afb222878af824
Usage reservation and receipt durability d1f7e2ae8cee96296da568b1730974f56913fae0
Generation-cap fail-closed deployment b14ca4e963eaf20c87feb8aa4469c6248f15735c
Kill-switch staged durable authority 9b2c291a34f211d131cd09cc86d78893f0c8c0b6
Operator audit acknowledgement 399998e8c5a58d5cd48f18d6314da3330a5ba38a
Atomic generation budget/quota admission 99e294003c73dc576249958361f2598f86e42d4b
Governed Studio workspace durability 8a3225a39b10c67553b54b4725df778ab3fdea4b
Central admin workspace acknowledgement b2e2313d782963a03f130d892cd5ac3730d9b3a6
Studio continuity deletion fanout c6227208cefc808e0ee85cfb1268465473788e94
Durable reminder continuity and exact erasure aab9c2634210178443a54d2d8212688171a1cc10 (currently published through af7fffdb9a6fcaff863a57b516c0ecefba0f82f5)
Durable Nisaba saves/reminders and exact fanout af7fffdb9a6fcaff863a57b516c0ecefba0f82f5
Generated-artifact control-plane deletion fanout af9747a008be4af85b890a45b302c9c352d04b86
Generated-artifact stored-object version purge c41b4661da7f29f51628d957f106f128811efc53 (published through c974990c8104a7d5bd3aa0230223bd2d38542047)
Customer deletion lifecycle durability and honesty a587f3d7ea2d37edab779edd94aa132031a9ef4f
Durable authenticated analytics-event erasure 96ae61d4a02384b000145f1c406730a92df79551
Durable profile-avatar metadata and byte erasure df31de5699d25dc460e49b3e2fdee78c2883fb51
Exact journal and atomic ritual-record erasure 94512a6a1b4a5b8eeb6e0af244f3e0bede4e0365
Durable, resurrection-safe library collections c0265b5461e0fba9b07dd8f84e022cde71c03acf
Durable, resurrection-safe saved library items 007a0bd8a5e21099e09d7c1bacf6402884179a59
Durable, resurrection-safe Nisaba notebooks b54626b784aa165ea21e027ae286731ad6916bf9
Honest evidence-pack structural-absence attestation 01dd3d56802a9825d2e45a387d088d8f54d804c7
Durable consumer profile and auth-account state 05856d6c76007de3a08d1c0a349ce2f8f547d7f3
Durable session registry and exact identity erasure 05856d6c76007de3a08d1c0a349ce2f8f547d7f3
Durable notification preferences and read state 067d5fff4634a189a751faa366f4ac0342073a61
Durable vector and active-persona personalization 90e6592487f2be1d36069c9be4789fcf1e9120c2
Durable customer message-center continuity 25f9acaf3fba4cc20859b2472b4a90589457e4bd
Durable device push-token session state e6b90e13762cc94a8b8a0f70750248c9b4f14519
Durable customer channel-binding profile state c6e034e46dbe119409147fa6d3356fe3d2f0d274
Durable per-user Telegram saved/profile state 6262e3a94e09aded2f2b5ead93d035366a7fc2e1
Durable celestial ritual-schedule continuity 844ee060a65e29a55ea6028959c2763bbdff621c
Durable wearable-health delivery and erasure journal 0656aabd9b7a3b57588f897be492a8b9c49a3b7a
Durable morning-capture journal state 989ce593373199adf3e752e1da89f59089a66e3c
Durable Arete member continuity and exact erasure 43a87fdb6e03cea3e92f00f6250fd19550f547b1
Durable Nyx member continuity and exact erasure 5abc400e018c6beff1bc0302a795bd000b642d27
Durable customer data-export metadata and bytes f50976ba40460ecdc6b413f9e9ff1a57a1b5f50e (published through 25b510fbe0701062b54c88caef88146e957b81ef)
Durable canonical customer-consent evidence 58c932258048f74f1c40cdf97e7a0c2a5380a79a
Durable billing and Fiat Stripe operational state e390bf2c0a8565cec2f044c190c71ef27162a2bd
Durable customer-feedback support cases 48a0b27374fbdf12aad257c7f51e4f8e5f507c32
Durable signup verification and abuse authority 78d1d455e24d1a559c77a0bd1ccce67cab935307
Durable member library and collection share authority ec2be9918cfafcdeb0c42fbebd97cd538ca49a71
Durable bounded recent-search learning state 1c456fe472216149c4fe1296cbae12b4db191165
Durable scene tip ledger and counsel authority df93bd737dcd05434a71cafdd6de6cfa755aeba2
Durable scene appreciations and velocity authority 6867a88a670ac3ce690fe017f077288d0d0c9d89
Durable scene follows and premiere lifecycle f162352a9587fdbef46d47c4209defa433fb49a7

The audit did not re-award credit for contract fixtures alone. Closure uses the named constituent packs only where they identify the V1 BFF/composition source and actual repository request path. Their deployment qualifications remain in force; this evidence does not claim production traffic or external provider receipts.

Current path observations#

snapshotPlane captures the review queue, contextual-bandit arms, preference learner, standing direction, cycle reports, editorial publisher records, learned-item IDs, autonomous authoring state, category autonomy, and the usage ledger. restorePlane restores those records and deliberately derives the learned set for legacy snapshots so a restart cannot double-learn a resolved outcome. AgentRun persistence separately retains common controls, Lilith authority/revocation, Yemaya checkpoints, approvals, tool evidence, and cost maps.

The protected autonomy snapshot inventories full artifacts, human feedback, learner state, and standing direction, then authenticates tenant, schema, key-reference, inventory, and retention metadata with the ciphertext. wireDurableAutonomyPlane now snapshots at mutation time, serializes saves, returns the save promise, prevents a failed write from poisoning later writes, and restores the last durable snapshot when the latest requested write fails. All autonomy-route mutation paths, manual/scheduled cycles, and engagement polling await that barrier before success is reported.

The editorial publisher uses a stable artifact identity derived from the review item and retains every gated transition. A human replacement reuses the same publication reference and advances published -> updated -> published. Each record also stores the digest of the exact approved candidate. Publication mutations are globally serialized, staged on a clone, and acknowledged only after the plane snapshot lands; a failed first publish or update restores the prior record. Same-digest retries return the existing placement without adding transitions, including after snapshot restore, while changed approved content updates that same placement. Takedown and rollback are likewise idempotent so a restart between publisher commit and queue transition can reconcile safely.

ReviewQueueStore issues a monotonic approval binding for human approval, review-window expiry, or full-auto policy. Its dependency record uses the RUN-005 hash vocabulary for plan, source, artifact, policy, and gate, plus a binding digest. Human replacement clears the old approval (and full-auto replacement creates a new version). The director requires a current binding, an authority kind permitted by the live autonomy level, a non-future source, and source age no greater than its declared half-life. Legacy approved records without a binding and dependency-tampered restored records fail closed. The common-run adapter preserves the approval as an audit artifact and versioned policy binding rather than treating the new fields as an opaque sidecar.

Subsequent all-store durability progress#

The common AgentRun lifecycle and nested human-authority SLO mutations now expose one awaited flush, preserve ordered checkpoints, and fail without acknowledging lost authority. Generation job claims, output catalog/effect lineage, and usage reservations/receipts are separately restart recoverable. Configured budget and quota limits no longer fall back to restart-resettable memory; atomic, job-idempotent Redis admission prevents concurrent overspend and reconciles actual cost without moving a reservation across its original UTC window. Kill-switch state is staged behind its durable authority commit, and operator audit mutation responses wait for ordered append evidence.

The governed Studio workspace store publishes its synchronous read view only after its per-user/per-workspace snapshot commit. The central AdminWorkspaceStateStore now retains a last-durable record per operator, creates a checkpoint for each mutation, and exposes the commit to the shared admin route barrier. All 187 core mutation routes capture their pre-mutation checkpoint and hold onSend until the matching snapshot settles. A failed write restores the last durable record and produces a controlled 500; a deployable without its required snapshot sink produces 503. A second mutation for the same operator is rejected while the first commit is active, preventing a later successful whole-record snapshot from making a failed earlier candidate durable. A real Postgres restart test writes and reloads the exact operator record from admin_store_snapshot.

Studio workspace snapshots are now classified under the existing canonical customer-visible continuity_state artifact, whose deletion mode is hard_delete and whose data-rights category is continuity. The signed deletion-service contract includes that service, category-only and full-account requests schedule it, and the BFF registers a real subject eraser. The eraser executes one Postgres deleteMany over the exact <userId>:: scope prefix, returns the database row count for its attestation, and clears the synchronous view only after that durable statement commits. Missing erasure capability or a failed/invalid-count write throws through the consumer, producing a signed failed outcome rather than false completion. Studio writes and erasures share one mutation queue, so an already-started same-process write cannot land after an acknowledged erasure; adjacent subject IDs and unrelated store keys remain isolated.

The signed generated_artifact eraser now composes all BFF-owned durable representations instead of deleting only Isis GeneratedOutput metadata rows. Authenticated curated-card, music, Nyx briefing, and Studio-tool enqueue paths stamp immutable server-authoritative user and tenant attribution outside the untrusted provider request. Legacy snapshots fall back to request fields only when the explicit field is genuinely absent; an explicit null or a different authenticated owner cannot be overridden by a spoofed request. Generation quota admission and released gallery attribution consume that same owner field.

One signed service operation erases the canonical Isis database rows, durable released-output catalog/provenance/lineage, gallery records, and job requests, results, and governance state. Catalog deletion precedes gallery deletion so startup repair cannot recreate an erased gallery row. Failed durable writes restore the last acknowledged snapshot and propagate a signed failure; a retry idempotently completes representations deleted before the failure. Enqueue, provider execution, and deletion share a per-subject lifecycle barrier. If erasure wins, a worker holding a stale queue snapshot cannot dispatch. If an already-running provider wins, erasure waits for its catalog/gallery outcome and then removes every control-plane copy. Work for unrelated subjects is not globally serialized.

The same signed operation now reads each subject-owned Isis GeneratedOutput storage identity and permanently purges the exact bucket/key before deleting its metadata. The shared S3/MinIO client enumerates every concrete version and delete marker, paginates version listings, deletes in API-sized batches, rejects provider-reported per-version errors, and re-lists the exact key before acknowledging absence. A repeated or missing pagination cursor and a version that appears during final verification both fail closed. This also upgrades profile-avatar deletion: a plain delete against the production versioned bucket can no longer leave historical avatar bytes behind a delete marker.

The BFF binds stored buckets to an explicit S3/MinIO registry whose credentials are referenced by environment-variable name, with the existing single asset store as a one-bucket fallback. Unknown buckets, mismatched stored regions, missing credentials, malformed/duplicate registrations, and an unwired adapter fail the signed service rather than removing retry metadata. Object purge runs inside the existing per-subject generation barrier; metadata deletion is restricted to the exact owner and the IDs already purged, and a final owner read detects a row introduced during the database phase. A live versioned-MinIO test created two byte versions plus a delete marker, confirmed their complete purge, proved idempotent retry, and proved an adjacent key remained present.

The customer account-deletion lifecycle itself is now a required durable BFF store. Boot hydrates its per-user request histories, grace deadlines, cascade jobs, tombstones, signed attestations, revisions, and global ID sequence before traffic; every create, cancel, manual failure, and terminal fanout result writes through an ordered snapshot queue. The API waits for the scheduled snapshot before invoking any immediate external erasure and waits for cancellation or the signed terminal record before replying. A missing sink or failed write returns a controlled 503 and restores the last durable snapshot. The grace worker reports a terminal-write failure as retryable and leaves the request scheduled under the same deletion ID.

Completion is evaluated against every canonical customer-visible deletable artifact, not merely artifact types that happen to equal a deletion-service ID. Each resolved artifact receives a cascade job. A mapped job completes only when its service is both reported satisfied and present in the runner's verified- attestation set; legacy jobs without the newer explicit service field derive it only when their artifact type is a canonical service. The profile and session artifacts now map directly to canonical services. All 16 current canonical artifacts are mapped, so the repository full-account request reaches completed when every injected eraser returns a verified attestation; any missing or failed service still fails closed.

analytics_event is now a canonical signed deletion service rather than an unmapped artifact. The BFF analytics store hydrates before traffic, requires a durable sink in production, serializes mutation snapshots, waits for persistence before publishing an event or returning 202, and leaves the acknowledged view unchanged on a failed write. Authenticated ownership is derived from the server-validated bearer token, not the caller-controlled event context; an absent header remains intentionally anonymous, while an invalid supplied token returns 401. Legacy snapshots without an owner remain anonymous rather than being guessed into a subject.

The subject eraser removes only exact owner matches, durably commits even an empty not-found result, returns the deleted-row count for its signed attestation, and is wired into the customer deletion runner and canonical contract union. The web buffered transport resolves the current bearer token on every send attempt, so login and refresh changes cannot leave a stale captured identity on later batches. Anonymous telemetry is deliberately outside account-subject erasure; subject-owned telemetry is now covered.

The prior avatar_pack eraser incorrectly treated the whole category as a shared catalog with no subject rows even though the BFF profile-avatar store retains per-user inline image bytes or an object-store key. That no-data receipt has been removed. The deployable now requires an injected subject deleter; an unwired avatar eraser is omitted so orchestration fails closed.

Profile-avatar writes now wait for an ordered durable snapshot before returning success and leave the last acknowledged record readable after a failed write. Object-backed replacements use immutable content-versioned keys, durably retain every superseded key until its deletion is confirmed, and remove a newly written key if the metadata commit fails. The real object adapter exposes the underlying S3/MinIO hard delete. Inline replacements cannot discard a prior object key when object-store credentials are unavailable.

Subject erasure deletes inline bytes/metadata and every tracked current or superseded object version before committing removal. A missing object deleter, failed byte purge, or failed snapshot propagates as a signed service failure; the readable metadata remains for idempotent retry. The deletion snapshot also persists a subject fence even for not-found data. Upload and erasure share a per-subject lifecycle barrier, so an upload that wins is subsequently removed, while an erasure that wins rejects the queued upload and cannot be resurrected. Adjacent subject IDs remain isolated.

journal_entry and ritual_completion are now canonical signed deletion services. The journal eraser executes one AreteJournalEntry.deleteMany against the exact subject userId. The ritual eraser runs the exact-user deletes for TaraRitualSession and TaraSittingCompletionEvent inside one Prisma transaction and returns their validated summed row count. Blank subjects, negative or non-integral counts, and transaction failure propagate instead of producing a success attestation. The deployable wires both erasers only when the V1 database client is configured; otherwise they are absent from the runner and canonical-service completeness fails closed.

collection is now a canonical signed deletion service backed by the same operational store used by the authenticated library export path. Postgres collection creation writes the goal3_stub_collection and canonical v1_library_library_collection rows in one transaction. Exact-owner deletion serializes on the same advisory lock, persists an erasure fence, and removes both representations before acknowledging. Either create/delete race linearization therefore ends with no subject rows: a create that wins is deleted, while a delete that wins causes the later create to fail with the durable fence.

The snapshot-backed tier now treats collection creation and deletion as required writes rather than best-effort persistence. Failed snapshot writes restore the prior readable records and fence state. Its persisted owner fence survives restart, prevents recreation even after a not-found deletion, and is shared with a per-owner lifecycle barrier so queued in-process mutations cannot resurrect an erased collection. A configured but unavailable Postgres database fails closed instead of silently falling back to a different storage tier.

saved_claim_passage is now a canonical signed deletion service backed by the same saved-library store consumed by the customer export and unified-search paths. Save, unsave, and cross-device sync build a candidate whole-store snapshot, wait for its ordered durable commit, and only then publish the new read view or acknowledge the route. A failed snapshot leaves the last durable revision and item set readable, and the next mutation can recover without a poisoned queue. The deployable requires the sink even when its admin snapshot database is absent, so mutation and not-found erasure fail closed rather than falling back to restart-resettable memory.

Exact-subject deletion removes the complete LWW set, including unsave tombstones, while preserving adjacent members. It commits a subject fence even when no item exists. The fence is authoritative over inconsistent restored rows, survives restart, and rejects both direct saves and stale device sync. A per-subject lifecycle barrier plus the globally ordered whole-store snapshot queue covers both create/delete race orderings: a save that wins is subsequently removed, while a deletion that wins rejects the queued save.

Consumer profile and preference mutations now clone a per-subject candidate, wait for the required ordered durable snapshot, and publish that candidate only after the write commits. Customer authentication does the same for accounts, linked identities, sessions, refresh-token families, recovery codes, and email- verification state. Production wiring hydrates both stores before traffic and requires their snapshot sinks. Route, SSO, billing/payment, and admin bulk callers await the durable mutation boundary; a missing or failed sink produces a controlled failure without publishing cache-only identity state.

Persisted passwords and recovery codes are salted scrypt verifiers. Persisted refresh and email-verification tokens are SHA-256 lookup hashes, while raw secrets exist only in the one-time response/delivery path. The profile export composes the consumer record with the non-secret auth-account view. The session export composes authentication sessions with the device-session registry while omitting refresh-token hashes. It returns empty sections during partial erasure instead of synthesizing account or session defaults.

profile and session are now canonical signed deletion services. Profile erasure removes the exact auth account and consumer profile/preferences; session erasure removes the subject's auth sessions, refresh tokens, device sessions, step-up freshness, and device-session audit rows. Each service persists its own subject fence even for a not-found deletion, rejects post-erasure mutations, and preserves adjacent subjects. The device-session registry itself has an ordered durable snapshot and exports only its customer-visible session/audit view. Server wiring injects the real erasers in session-before-profile order, and missing or failed persistence propagates through the signed fanout rather than producing a false success receipt.

Notification domain, persona, quiet-hours, and digest preferences now follow the same whole-store candidate/save/publish discipline. Notification read, unread, dismissal, and bulk mutations use an independent ordered snapshot. Production requires both sinks and hydrates them before accepting traffic; preference and write routes await the durable commit, translate a failed save to a controlled 503, and reject post-erasure recreation with 409. The consumer-cadence cache remains derivable: it seeds a subject's first explicit preference candidate when present, but is excluded from durable snapshots and DSAR output.

Each notification partition persists per-subject revisions and a deletion fence. Exact-subject erasure is serialized with mutation, commits the fence even when no record exists, survives restart, preserves adjacent subjects, and rejects stale resurrection. Notification preferences participate in the signed profile service after consumer-profile and auth-account erasure; read/dismiss state participates in signed continuity_state. Both composers validate every partition count and fail the aggregate service on a missing, malformed, or failed result. The real export collectors expose the stored preference record under profile and the read-state revision/map under continuity_state.

Personalization-vector events now await the same ordered candidate/save/publish boundary before the consumer invokes its recorded callback. Active-persona selection, consumer clearing, and admin bulk assignment use an independent ordered store whose synchronous helpers are rejected once production durability is required. The server requires both sinks before traffic and hydrates an absent snapshot as authoritative empty state. Failed vector or persona writes leave the last committed view visible; persona routes return controlled 503s, and an erased subject receives 409 rather than recreating a selection.

Both personalization partitions persist revisions and exact-subject deletion fences. Deletion shares each partition's mutation stream, commits a fence even for not_found, survives restart, preserves adjacent members, and rejects a stale vector event or persona assignment. The signed personalization_vector service now count-validates and composes the embedding and active selection; a partial failure rejects the receipt. Existing DSAR collectors expose the vector under personalization_vector and the selected guide under persona, and both become empty after the composed eraser.

Customer message history, delivery receipts, archived/read state, channel and category opt-outs, and quiet-hours delayed dispatches now share one ordered whole-store snapshot. Every customer or operator route awaits the candidate save before responding; Trust & Safety and Metis multi-receipt deliveries commit atomically. Failed persistence leaves the last committed inbox visible, routes return 503, and an erased subject receives 409 instead of being recreated.

The message-center partition persists global and per-subject revisions plus an exact-subject deletion fence. Deletion removes visible and archived messages, suppression policies, and delayed work, survives restart, preserves adjacent members, and rejects stale sends or schedules. The signed continuity_state service count-validates this partition. Its DSAR section contains complete message history, receipts, policies, and delayed dispatches and becomes empty after erasure; the existing canonical retention and deletion policy for continuity_state therefore governs this stored record.

Device push-token registration and removal now use one ordered candidate/save/publish snapshot instead of mutating memory before a fire-and-forget save. Production requires the sink, routes await persistence, and a failed save returns 503 without changing the live or restart-restored delivery target. The snapshot persists per-subject revisions and deletion fences; a deleted subject receives 409 and cannot be recreated by a stale app registration.

The canonical signed session service now count-validates customer-auth sessions, device-session/audit state, and push-delivery tokens as three separate partitions. Session DSAR includes complete device metadata and a SHA-256 token fingerprint without disclosing the raw push credential. Exact erasure removes the raw credentials, persists even for an absent subject, preserves adjacent accounts, and leaves the session section empty after all three erasers complete.

Customer email, SMS, and WhatsApp binding requests, verification attempts, and step-up unbinds now use an ordered candidate/save/publish snapshot. Routes await the save and return 503 without publishing a new address, burning a verification attempt, or revoking a verified binding when persistence fails. Production rejects legacy synchronous mutation, and an exact-subject fence returns 409 to a stale binding request after account erasure.

The signed profile service now count-validates channel bindings independently from the consumer profile, authentication profile, and notification preferences. Profile DSAR exports address, status, verification/expiry metadata, attempts, and revision while deliberately excluding the salted verification codeHash. Deletion removes pending secrets and verified addresses, survives restart, preserves adjacent members, and leaves the profile section empty once every profile partition is erased.

Per-user Telegram captures, identity links, voice-reply preferences, and delivery suppression now share one ordered whole-store snapshot with separate saved-content and profile revisions and fences. Bot saves, quiet-hours updates, stop/voice/unlink effects, authenticated link minting, login binding, and webhook link completion await persistence. Failed writes return 503 without claiming a capture, preference, or link; stale authenticated profile writes return 409 after erasure.

Telegram notes and links compose into saved_claim_passage; identity-link and voice/delivery metadata compose into profile. Category-specific deletion preserves the other partition and adjacent members, and both fences survive restart. DSAR exports capture provenance plus profile metadata and a SHA-256 nonce fingerprint without disclosing the raw pending link nonce.

Accepted celestial ritual schedules now use one ordered whole-store candidate/save/publish stream. The schedule route awaits persistence, returns 503 without publishing volatile state on a failed save, and returns 409 when a stale client targets a subject whose continuity state has been erased.

The snapshot carries complete trigger, occasion, timing, quiet-hours displacement, provenance, acceptance, and member ownership fields together with per-subject revisions and exact-subject deletion fences. The signed continuity_state eraser removes only the subject's schedule, preserves an adjacent member, and prevents resurrection across restart. DSAR exports the same complete ritual records plus their revision and becomes empty after erasure.

An in-process per-request lifecycle guard prevents two callers from launching the same erasure concurrently. If cancellation wins while a runner is in flight, its durable cancelled state cannot be overwritten by the late erasure result. Failed terminal persistence restores the durable scheduled state, so an idempotent retry can obtain and persist a receipt rather than acknowledging cache-only success.

These slices materially reduce the remaining inventory but do not close it. Every newly durable user-scoped record must be connected to the applicable account-deletion, retention, legal-hold, and backup fanout before the final all-store disposition can be accepted. The previously named Studio workspace and generated-artifact BFF control-plane fanout items, authenticated analytics events, uploaded profile-avatar bytes, canonical journal rows, canonical ritual-completion records, and owner-scoped library collections are now closed. Cross-device saved-library items and tombstones are now closed as well. This now also covers the member-authored Nisaba notebook/annotation workspace. The evidence-pack category is mapped through an explicit structural-absence receipt, not a row deletion: no deployed customer-owned store exists for the request-scoped response or the ownerless shared/editorial Sophia schema. This now also covers consumer profile/preferences, customer auth accounts and token- family metadata, the device-session registry, device push-token credentials, customer channel bindings, and Telegram profile state through exact, count-validated profile and session erasers. Telegram captures are covered through the existing saved_claim_passage service. Notification preferences and notification read state are now covered by the existing profile and continuity_state services respectively. Personalization vectors and active-persona selections are now covered together by the existing personalization_vector service. Customer message-center state is now covered by the existing continuity_state service. Celestial ritual schedules are now covered by the same signed continuity_state service. Every current canonical deletion artifact is mapped. Generated-artifact objects represented by Isis bucket/key metadata now have a concrete, bucket-aware all-version purge adapter for configured S3/MinIO stores, as do profile-avatar objects. This does not claim deletion of provider-native remote URLs or assets whose deletion identity is not represented by a configured bucket/key. Those identities, the remaining operational-store inventory, and other user-scoped partitions still require explicit disposition and proof.

Restart-publication automated verification#

Tested source: 7e519c01c2cadfa34c7459bd7f44781b355fbbf8 on host dev-server, Linux 6.8.0-110-generic x86_64. Toolchain: Node 24.14.1, pnpm 10.25.0, TypeScript 6.0.3, Vitest 4.1.7, and ESLint 10.4.0. The protected lockfile blob remained a37431842e330b3a06b030947c25bebdc72bc2b1.

Verification ran on 2026-07-17 UTC. Every command below exited 0.

text
pnpm exec vitest run --config libs/oshun/creative-autonomy/vitest.config.ts \
  libs/oshun/creative-autonomy/src/review/review.test.ts \
  libs/oshun/creative-autonomy/src/director/director.test.ts \
  libs/oshun/creative-autonomy/src/common-run-adapter.test.ts --maxWorkers=1
  3 files, 67/67 tests passed

pnpm exec vitest run --config libs/oshun/creative-autonomy/vitest.config.ts \
  libs/oshun/creative-autonomy/src/common-run-adapter.test.ts --maxWorkers=1
  1 file, 8/8 tests passed after the final approval-mapping assertion

pnpm exec tsc --noEmit  # cwd libs/oshun/creative-autonomy
  passed

pnpm exec vitest run --config apps/oshun/bff/vitest.config.ts \
  apps/oshun/bff/src/agentic/autonomy-route.test.ts \
  apps/oshun/bff/src/agentic/autonomy-bindings/autonomy-bindings.test.ts \
  apps/oshun/bff/src/agentic/autonomy-bindings/autonomy-plane-e2e.test.ts \
  apps/oshun/bff/src/agentic/autonomy-bindings/plane-persistence-privacy.test.ts \
  apps/oshun/bff/src/agentic/autonomy-bindings/engagement-poller.test.ts --maxWorkers=1
  5 files, 64/64 tests passed

pnpm exec vitest run --config apps/oshun/bff/vitest.config.ts \
  apps/oshun/bff/src/agentic/autonomy-bindings/autonomy-bindings.test.ts \
  apps/oshun/bff/src/agentic/autonomy-bindings/plane-persistence-privacy.test.ts \
  --maxWorkers=1
  2 files, 45/45 tests passed after final reconciliation hardening

pnpm --filter @oshun/bff typecheck:autonomy
  passed at final implementation source

pnpm exec eslint <eight changed non-test TypeScript sources>
  passed

pnpm exec prettier --check <fourteen changed TypeScript files>
  passed

git diff --check
  passed

The unchanged constituent integration baseline at 9248841df7890311f8e43902950706577e3e8847 also passed the run-protocol gate (5 files, 56/56, contract lint and TypeScript) and the eight-file V1 rights, media/video, editorial, and protected-persistence set (123/123). Those commands are not represented as reruns at 7e519c01c2; the implementation-source runs above cover every file directly changed by this slice.

The retained integration tests exercise bounded Sophia retrieval and entailment; rejection of unknown citations, declared-citation-only proof, and provider-identity rights proxies; artifact-bound rights receipts; full editorial lifecycle and same-ID replacement; encrypted snapshot restore and tamper rejection; real ffmpeg video probing/keyframes; typed missing-frame holds; post-restart editorial takedown; and no duplicate learning after restore. The new tests add ordered and failed write rollback, route acknowledgement blocking, dependency-tamper and stale evidence refusal, legacy approval fail-closed restore, concurrent duplicate publication, failed create/update rollback, stable same-placement replacement, lost-ack restart reconciliation, and duplicate takedown/rollback delivery.

The host has 15 GiB RAM, 31 GiB swap, another workspace agent, and an active Nx daemon. Verification was targeted, single-worker, and sequential. No broad Nx sweep, Next production build, or combined build matrix ran. The implementation changed BFF/runtime behavior and API authority metadata but no rendered UI, so frontend skill, Playwright/mobile, database migration, provider calls, and Unreal automation were inapplicable.

Central admin workspace durability verification#

Tested source: b2e2313d782963a03f130d892cd5ac3730d9b3a6 on dev-server, Linux 6.8.0-110-generic x86_64. Toolchain: Node 24.14.1, pnpm 10.25.0, TypeScript 6.0.3, Vitest 4.1.7, and ESLint 10.4.0. Verification completed 2026-07-18 UTC. The protected lockfile blob remained a37431842e330b3a06b030947c25bebdc72bc2b1.

text
pnpm exec vitest run src/routes/admin-workspace-state-durability.test.ts \
  src/admin/admin-workspace-state-durability.test.ts --maxWorkers=1
  2 files, 11/11 tests passed

OSHUN_V1_DATABASE_URL=postgresql://<local-dev> pnpm exec vitest run \
  -c vitest.integration.config.ts \
  src/admin/admin-workspace-state-durability.integration.test.ts --maxWorkers=1
  1 file, 1/1 real-Postgres restart test passed

NX_DAEMON=false pnpm nx run @oshun/bff:typecheck --skip-nx-cache \
  --output-style=stream
  no new app-own type errors; backlog 0

pnpm exec eslint <four changed sources> --quiet --no-warn-ignored
pnpm exec eslint <three changed tests> --no-ignore --quiet --no-warn-ignored
  passed

pnpm exec prettier --check <seven changed TypeScript files>
git diff --check
  passed

pnpm exec esbuild src/server.ts --bundle --platform=node --format=esm \
  --target=node22 --outfile=/tmp/oshun-bff-admin-workspace-durability.js \
  --sourcemap
  passed; 30.6 MB bundle

The route tests prove delayed acknowledgement, failed-write rollback, missing sink fail-closed behavior, and same-operator race rejection. Store tests also cover hydrated-scope restart, correct post-mutation snapshot content, explicit in-memory test mode, last-durable rollback, and absence of the internal operator stamp from persisted JSON. The integration test used the repository's idempotent admin-snapshot bootstrap against the local Postgres container and removed its test row afterward.

The full BFF lint target was also executed. It remains red on the repository's pre-existing broad baseline (245 errors and 223 warnings, principally module boundary and duplicate-import findings outside this slice); error-only lint on every changed source and test passed. The existing full-app inbox route suite could not collect because this checkout lacks the lock-declared luxon package required by libs/v10/rail-kernel/src/dayparts.ts; the new narrow Fastify route suite registers the same admin router directly and is green. This slice changed no rendered UI, provider/model behavior, contract/schema, or Unreal path, so Playwright/mobile, provider probes, schema migration creation, and UE automation were inapplicable.

Studio continuity deletion-fanout verification#

Tested implementation source: c6227208cefc808e0ee85cfb1268465473788e94 on dev-server, Linux 6.8.0-110-generic x86_64. Toolchain: Node 24.14.1, pnpm 10.25.0, TypeScript 6.0.3, Vitest 4.1.7, and ESLint 10.4.0. Verification completed 2026-07-18 UTC. The protected lockfile blob remained a37431842e330b3a06b030947c25bebdc72bc2b1.

text
pnpm exec vitest run --config libs/oshun/persistence/vitest.config.ts \
  libs/oshun/persistence/src/durable-snapshot-store.test.ts --maxWorkers=1
  1 file, 10/10 tests passed

pnpm exec vitest run --config libs/shared/deletion-fanout/vitest.config.ts \
  <six deletion fanout/orchestrator/transport/consumer/runner suites> --maxWorkers=1
  6 files, 36/36 tests passed

pnpm exec vitest run --config libs/contracts/vitest.config.ts \
  libs/contracts/src/common/customer-data-deletion.spec.ts --maxWorkers=1
  1 file, 24/24 tests passed

pnpm exec vitest run --config apps/oshun/bff/vitest.config.ts \
  apps/oshun/bff/src/studio/workspace-state-store.test.ts \
  apps/oshun/bff/src/routes/studio-workspace-state-durability.test.ts \
  apps/oshun/bff/src/data-deletion/state-run-deletion.test.ts --maxWorkers=1
  3 files, 15/15 tests passed

pnpm exec vitest run --config apps/oshun/bff/vitest.config.ts \
  apps/oshun/bff/src/routes/data-deletion-continuity.test.ts --maxWorkers=1
  1 file, 1/1 direct Fastify route test passed

OSHUN_V1_DATABASE_URL=postgresql://<local-dev> pnpm exec vitest run \
  --config libs/oshun/persistence/vitest.config.ts \
  libs/oshun/persistence/src/durable-snapshot-store.integration.test.ts \
  --maxWorkers=1
  1 file, 5/5 real-Postgres tests passed

OSHUN_V1_DATABASE_URL=postgresql://<local-dev> pnpm exec vitest run \
  --config apps/oshun/bff/vitest.integration.config.ts \
  apps/oshun/bff/src/studio/workspace-state-store.integration.test.ts \
  --maxWorkers=1
  1 file, 2/2 real-Postgres restart/erasure tests passed

pnpm exec tsc -p libs/oshun/persistence/tsconfig.lib.json --noEmit
pnpm exec tsc -p libs/contracts/tsconfig.lib.json --noEmit
pnpm exec tsc -p libs/shared/deletion-fanout/tsconfig.lib.json --noEmit
  all passed

node tools/typecheck/ratchet.mjs --app apps/oshun/bff \
  --tsconfig tsconfig.typecheck.json
  no new app-own type errors; backlog 0

pnpm exec eslint <all changed TypeScript sources/tests> --no-ignore --quiet
pnpm exec prettier --check <all changed TypeScript sources/tests>
git diff --check
  passed

pnpm run build  # cwd apps/oshun/bff
  passed; 30.1 MB esbuild bundle

The tests prove exact-prefix and store-key isolation, idempotent not-found counts, missing-adapter and failed-write fail-closed behavior, durable-before- cache erasure, same-process write/erase ordering, restart absence, canonical service/schema alignment, signed receipt propagation, category-only routing, and live Postgres bulk deletion. The host had 15 GiB RAM, 31 GiB swap, an active Nx daemon, and another workspace audit process; all checks were targeted, single-worker, sequential, and memory-supervised. No rendered UI, mobile flow, provider/model pipeline, database schema, or Unreal content changed, so Playwright/mobile, provider probes, migration creation, and UE automation were inapplicable.

Generated-artifact control-plane deletion verification#

Tested implementation source: af9747a008be4af85b890a45b302c9c352d04b86, published as an ancestor of origin/main integration tip 4b58010a251319d8fdba171218a57b072718b101 on dev-server, Linux 6.8.0-110-generic x86_64. Toolchain: Node 24.14.1, pnpm 10.25.0, TypeScript 6.0.3, Vitest 4.1.7, and ESLint 10.4.0. Verification ran from 2026-07-18T05:44Z through 2026-07-18T06:08Z UTC. The protected lockfile blob remained a37431842e330b3a06b030947c25bebdc72bc2b1.

text
pnpm exec vitest run \
  src/generation/jobs-route.test.ts \
  src/generation/output-catalog.test.ts \
  src/generation/generated-artifact-erasure.test.ts \
  src/isis/output-gallery-store.test.ts \
  src/generation/curated-generation-executor.test.ts \
  src/generation/music-enqueue-executor.test.ts \
  src/generation/sky-briefing-enqueue-executor.test.ts \
  src/isis/curated-card-route.test.ts \
  src/isis/music-route.test.ts \
  src/isis/nyx-3d-route.test.ts \
  src/agentic/studio-tool-catalog.test.ts \
  src/agentic/runs-route.test.ts --maxWorkers=1
  12 files, 116/116 tests passed

pnpm exec vitest run src/generation/jobs-route.test.ts --maxWorkers=1
  1 file, 35/35 tests passed after final attribution-helper cleanup

node tools/typecheck/ratchet.mjs --app apps/oshun/bff \
  --tsconfig tsconfig.typecheck.json
  no new app-own type errors; backlog 0

pnpm exec eslint <12 changed non-test BFF sources>
  passed

pnpm exec prettier --write <24 changed BFF sources/tests>
git diff --check
  passed

pnpm exec esbuild src/server.ts --bundle --platform=node --format=esm \
  --target=node22 --outfile=dist/server.js --sourcemap
  passed; 30.6 MB bundle

pre-commit affected typecheck
  @oshun/bff and @oshun/prompt-injection-evals passed

The value assertions cover authenticated owner/tenant stamping on every customer enqueue front door and the governed Studio tool; immutable explicit ownership defeating a spoofed request owner; legacy-snapshot fallback; exact cross-user isolation; deletion durability across reset/rehydration; failed queue, catalog, and gallery writes restoring the last durable state; lineage and reversible gallery-snapshot removal; resurrection-safe catalog-before-gallery ordering; signed-composer count/order; and idempotent retry after a partial representation failure. Race tests force both linearizations: erasure first leaves a worker with a stale captured job and proves provider calls stay at zero, while provider first holds deletion until its released output lands, then proves the job, provenance, lineage/catalog, and gallery record remain absent after restart.

The host had 15 GiB RAM, 31 GiB swap, an active Nx daemon, and another workspace agent. Verification was targeted and single-worker. The full BFF ratchet was run alone and supervised at no more than approximately 5.4 GiB TypeScript RSS; available memory remained above 6 GiB. The commit hook later ran two affected typechecks concurrently and remained above 6 GiB available. No rendered UI, mobile flow, contract/schema migration, model/provider request, or Unreal content changed, so Playwright/mobile, migration creation, live-provider, and UE automation were inapplicable. No live provider or bucket purge was claimed.

Customer deletion lifecycle integrity verification#

Tested implementation source: a587f3d7ea2d37edab779edd94aa132031a9ef4f, published as an ancestor of origin/main integration tip 5f5f2d40a3e94328ee2cd61783dae8022fe30e96 on dev-server, Linux 6.8.0-110-generic x86_64. Toolchain: Node 24.14.1, pnpm 10.25.0, TypeScript 6.0.3, Vitest 4.1.7, and ESLint 10.4.0. Verification ran from 2026-07-18T06:20Z through 2026-07-18T06:43Z UTC. The protected lockfile blob remained a37431842e330b3a06b030947c25bebdc72bc2b1 before and after the remote integration.

text
pnpm exec vitest run \
  src/data-deletion/state-run-deletion.test.ts \
  src/data-deletion/deletion-worker.test.ts \
  src/data-deletion/state-durability.test.ts \
  src/routes/data-deletion-continuity.test.ts --maxWorkers=1
  4 files, 22/22 tests passed

pnpm exec eslint \
  apps/oshun/bff/src/data-deletion/state.ts \
  apps/oshun/bff/src/data-deletion/state-run-deletion.test.ts \
  apps/oshun/bff/src/data-deletion/deletion-worker.ts \
  apps/oshun/bff/src/data-deletion/deletion-worker.test.ts \
  apps/oshun/bff/src/data-deletion/state-durability.test.ts \
  apps/oshun/bff/src/routes/data-deletion.ts \
  apps/oshun/bff/src/__tests__/data-deletion-route.test.ts \
  apps/oshun/bff/src/server.ts
  passed

node tools/typecheck/ratchet.mjs --app apps/oshun/bff \
  --tsconfig tsconfig.typecheck.json
  no new app-own type errors; backlog 0

pnpm --dir apps/oshun/bff run build
  passed; 30.1 MB production server bundle

git diff --check
  passed

pre-commit affected typecheck
  @oshun/bff and @oshun/prompt-injection-evals passed

The value assertions cover boot hydration and ID continuity; scheduled request and signed terminal receipt survival; required-sink failure; failed terminal write rollback to the durable scheduled state; ordered create/cancel writes; route acknowledgement before erasure; route 503 without an acknowledged schedule; worker retryability; legacy job hydration; verified-receipt gating; full-account false-completion refusal; cancellation during an in-flight runner; and duplicate-runner exclusion. The full-account negative fixture names profile as an unmapped artifact and proves its job fails while mapped continuity_state completes.

The older src/__tests__/data-deletion-route.test.ts was also attempted directly, but this checkout's installed dependency tree lacks the lock-declared luxon package imported by @oshun/v10-rail-kernel, so Vitest failed during collection before running a test. The changed route was exercised through the directly registered Fastify suites above, including delayed and failed durable writes. No dependency installation or lockfile rewrite was performed because the lockfile is protected user state.

An Nx BFF build was stopped once its graph expanded into 274 dependency builds; the package-local production bundle then passed. The host had 15 GiB RAM, 31 GiB swap, another workspace agent, and an active Nx daemon. Expensive checks were run sequentially and memory-supervised; available memory remained above 6 GiB during the full ratchet. No rendered UI, mobile flow, database schema, external provider, or Unreal content changed, so Playwright/mobile, migration, live-provider, and UE automation were inapplicable.

Analytics-event durability and erasure verification#

Implementation source: 96ae61d4a02384b000145f1c406730a92df79551; remote-integrated publication tip: b12cfdeb181ffa1180dcd0de85ab034eec1ead69. The protected lockfile blob remained a37431842e330b3a06b030947c25bebdc72bc2b1 across the remote merge.

text
# apps/oshun/bff
pnpm exec vitest run \
  src/analytics/events-ingest-store.test.ts \
  src/analytics/events-ingest.test.ts \
  src/data-deletion/state-run-deletion.test.ts \
  src/data-deletion/state-durability.test.ts \
  src/data-deletion/deletion-worker.test.ts --maxWorkers=1
  5 files, 34/34 tests passed

# libs/oshun/analytics
pnpm exec vitest run src/__tests__/buffered-sink.test.ts --maxWorkers=1
  1 file, 13/13 tests passed

# libs/shared/deletion-fanout
pnpm exec vitest run --maxWorkers=1
  7 files, 40/40 tests passed

# libs/contracts
pnpm exec vitest run src/common/customer-data-deletion.spec.ts --maxWorkers=1
  1 file, 24/24 tests passed

node tools/typecheck/ratchet.mjs --app apps/oshun/bff \
  --tsconfig tsconfig.typecheck.json
node tools/typecheck/ratchet.mjs --app apps/oshun/web \
  --tsconfig tsconfig.typecheck.json
  both passed with zero known and zero new errors

pnpm exec tsc --noEmit -p <package tsconfig>
  analytics, deletion-fanout, and contracts passed

pnpm --dir apps/oshun/bff run build
  passed; 30.1 MB production server bundle

targeted ESLint, Prettier check, package emitted builds, and git diff --check
  passed

The analytics tests prove restart hydration and legacy anonymous normalization; ordered concurrent writes; response acknowledgement after persistence; rollback on a failed snapshot; exact-subject deletion and adjacent-owner isolation; required-sink failure; anonymous acceptance; invalid-token rejection; server-authoritative ownership despite spoofed client context; current-token resolution on buffered retries; and signed fanout success/failure behavior. The customer deletion fixtures consume the canonical service-ID list so a future service addition cannot silently drift out of those assertions.

A broad BFF route-test collection was attempted, but this checkout's installed dependency tree lacks the lock-declared luxon package imported by @oshun/v10-rail-kernel; collection therefore stopped before route tests ran. The changed analytics route and real metrics collector were instead mounted directly in Fastify and passed in the focused suite above. No dependency install or protected-lock rewrite was performed.

The pre-commit affected-typecheck hook expanded this 13-file slice to 290 projects at --parallel=4, contrary to the host's required resource-safe targeting. It exposed 16 pre-existing TS2883 inferred-Jest-mock errors in libs/lilith/service-lib before the process group was stopped. The commit was then made with the repository's SKIP_TYPECHECK=1 hook bypass only after both affected application ratchets, all three package typechecks, the direct BFF production build, focused tests, lint, and formatting had passed. No live account-deletion request or production signed receipt is claimed by this repository-only tranche.

Profile-avatar durability and byte-erasure verification#

Implementation source: df31de5699d25dc460e49b3e2fdee78c2883fb51; remote-integrated publication tip: c3898fc47663ad960c6f0286e41b25d1d7b3d0e9. The protected lockfile blob remained a37431842e330b3a06b030947c25bebdc72bc2b1.

text
# apps/oshun/bff
pnpm exec vitest run \
  src/profile/avatar-store.test.ts \
  src/profile/avatar-upload.test.ts \
  src/routes/profile-avatar-route.test.ts \
  src/generation/caption-dub-provider-env.test.ts \
  src/generation/jobs-route.test.ts --maxWorkers=1
  5 files, 87/87 tests passed

pnpm exec vitest run \
  src/data-deletion/state-run-deletion.test.ts \
  src/data-deletion/state-durability.test.ts \
  src/data-deletion/deletion-worker.test.ts --maxWorkers=1
  3 files, 21/21 tests passed

# libs/shared/deletion-fanout
pnpm exec vitest run --maxWorkers=1
  7 files, 40/40 tests passed

pnpm exec tsc --noEmit -p libs/shared/deletion-fanout/tsconfig.lib.json
  passed

node tools/typecheck/ratchet.mjs --app apps/oshun/bff \
  --tsconfig tsconfig.typecheck.json
  no new app-own type errors; backlog 0

pnpm --dir apps/oshun/bff run build
  passed; 30.1 MB production server bundle

targeted ESLint --no-warn-ignored, Prettier check, and git diff --check
  passed

The tests cover boot-compatible legacy snapshots; acknowledgement only after snapshot persistence; globally ordered concurrent snapshots; failed-write rollback and recovery; exact-subject/adjacent-subject isolation; current plus superseded object-key deletion; failure when object deletion is unavailable; metadata retention after byte or snapshot failure; required-sink failure; durable not-found fences; both upload-versus-erasure orderings; route-level 503 and deleted-subject 409 responses; replacement-object cleanup; failed-upload object rollback; and fanout omission when the real avatar deleter is absent. Caption-dub and generation-route coverage was refreshed because the shared asset store gained the hard-delete capability.

The implementation binds S3/MinIO deletion through the real storage client, but the byte-erasure assertions use injected object-store doubles; no live bucket purge or production signed deletion receipt is claimed. The host had 15 GiB RAM, 31 GiB swap, another agent, and an active Nx daemon. The BFF ratchet peaked near 5.4 GiB RSS with at least 5.7 GiB available memory, and the direct build ran only after the required RAM/swap/disk/process gate. The commit used SKIP_TYPECHECK=1 solely to avoid the already-observed 290-project unsafe hook expansion after the exact BFF ratchet and package typecheck passed. No rendered UI, mobile flow, contract schema, database migration, or Unreal content changed; the affected API behavior is covered by direct Fastify tests, so Playwright/mobile/migration/UE automation was inapplicable.

This correction closes the BFF profile-avatar partition behind the existing avatar_pack service. It does not map the broader profile artifact, whose account identity and preferences remain in the open inventory, and therefore did not itself reduce the then-eight unmapped-artifact count or close V1-002.

Journal and ritual record-erasure verification#

Implementation source: 94512a6a1b4a5b8eeb6e0af244f3e0bede4e0365; remote-integrated publication tip: 8caa97abccdab9ac60c80f6e2dcfbeb0c5a306fc. The protected lockfile blob remained a37431842e330b3a06b030947c25bebdc72bc2b1.

text
# apps/oshun/bff
pnpm exec vitest run \
  src/data-deletion/v1-record-erasers.test.ts \
  src/data-deletion/state-run-deletion.test.ts \
  src/data-deletion/state-durability.test.ts \
  src/data-deletion/deletion-worker.test.ts --maxWorkers=1
  4 files, 27/27 tests passed

# libs/shared/deletion-fanout
pnpm exec vitest run --maxWorkers=1
  7 files, 40/40 tests passed

# libs/contracts
pnpm exec vitest run src/common/customer-data-deletion.spec.ts --maxWorkers=1
  1 file, 24/24 tests passed

pnpm exec tsc --noEmit -p libs/shared/deletion-fanout/tsconfig.lib.json
pnpm exec tsc --noEmit -p libs/contracts/tsconfig.lib.json
  both passed

node tools/typecheck/ratchet.mjs --app apps/oshun/bff \
  --tsconfig tsconfig.typecheck.json
  no new app-own type errors; backlog 0

pnpm --dir apps/oshun/bff run build
  passed; 30.1 MB production server bundle

targeted ESLint --no-ignore --max-warnings=0, Prettier check, and git diff --check
  passed

# post-integration conflict-sensitive reruns
pnpm exec vitest run src/data-deletion/v1-record-erasers.test.ts --maxWorkers=1
  1 file, 6/6 tests passed
pnpm exec vitest run src/service-erasers.test.ts --maxWorkers=1
  1 file, 10/10 tests passed

The eraser tests prove exact userId filters, atomic composition of both Tara partitions, summed and idempotent zero counts, rejection before a blank-subject delete, invalid-count refusal, and transaction-failure propagation. The shared fanout and contract suites prove canonical service-ID alignment, omission when the database-backed erasers are unavailable, and complete signed fanout when they are injected. Customer deletion state tests remain green with the expanded canonical mapping, so these two artifacts now schedule mapped jobs while the then-remaining six still forced honest full-account failure.

OSHUN_V1_DATABASE_URL was not configured in the verification environment. The transaction behavior was therefore exercised through an injected Prisma-shaped client, not a live database; no live V1 row deletion or production signed receipt is claimed. The production entrypoint with the real Prisma client composition bundled successfully. The host had 15 GiB RAM, 31 GiB swap, another agent, and an active Nx daemon. Checks were targeted, sequential, and memory-supervised; no rendered UI, mobile flow, schema migration, provider/model call, or Unreal content changed, so Playwright/mobile/migration/provider/UE automation was inapplicable.

Library-collection durability and erasure verification#

Implementation source: c0265b5461e0fba9b07dd8f84e022cde71c03acf; remote-integrated publication tip: cb55f1562980f23c87d7323c2dd1e5335edd39a2. The protected lockfile blob remained a37431842e330b3a06b030947c25bebdc72bc2b1.

text
# apps/oshun/bff, snapshot-backed tier
pnpm exec vitest run src/routes/domain-stubs-store.test.ts --maxWorkers=1
  1 file, 7/7 tests passed

# apps/oshun/bff, isolated disposable local Postgres database
OSHUN_TEST_POSTGRES_URL=postgresql://<isolated-disposable-db> pnpm exec vitest run \
  src/routes/domain-stubs-postgres.test.ts \
  -t "collections deletion|racing collection" --maxWorkers=1
  1 file, 2/2 selected tests passed; 26 skipped

# apps/oshun/bff, customer-deletion lifecycle
pnpm exec vitest run \
  src/data-deletion/state-run-deletion.test.ts \
  src/data-deletion/state-durability.test.ts \
  src/data-deletion/deletion-worker.test.ts --maxWorkers=1
  3 files, 21/21 tests passed

# libs/shared/deletion-fanout
pnpm exec vitest run --maxWorkers=1
  7 files, 40/40 tests passed

# libs/contracts
pnpm exec vitest run src/common/customer-data-deletion.spec.ts --maxWorkers=1
  1 file, 24/24 tests passed

pnpm exec tsc --noEmit -p libs/shared/deletion-fanout/tsconfig.lib.json
pnpm exec tsc --noEmit -p libs/contracts/tsconfig.lib.json
  both passed

node tools/typecheck/ratchet.mjs --app apps/oshun/bff \
  --tsconfig tsconfig.typecheck.json
  no new app-own type errors; backlog 0

pnpm --dir apps/oshun/bff run build
  passed; 30.1 MB production server bundle

targeted ESLint, Prettier check, and git diff --check
  passed

# post-integration conflict-sensitive reruns
snapshot-backed store 7/7; deletion fanout 40/40; contract 24/24 passed

The snapshot tests prove required-write acknowledgement, failed-create rollback, exact-owner deletion, adjacent-owner isolation, restart absence, and persisted fence refusal of recreation. The live database tests created collections for the target and adjacent subject, asserted deletion of both target physical representations while retaining the adjacent rows, rejected recreation, and proved both create-versus-delete orderings converge to no target rows. The test database was created only for this slice and dropped immediately afterward; no shared development data was truncated.

The full deletion-fanout and contract suites prove canonical service-ID alignment, omission when the collection deleter is unwired, and complete signed fanout when it is injected. The customer-deletion state suites remain green with collection mapped, leaving the then-five honest unmapped_artifact:* failures. The older broad BFF domain-stubs route suite was attempted, but this checkout's installed dependency tree lacks the lock-declared luxon package imported by @oshun/v10-rail-kernel, so collection stopped before tests ran. The affected storage behavior was instead covered directly at both file and live-Postgres tiers; no dependency installation or protected-lock rewrite was performed.

The host had 15 GiB RAM, 31 GiB swap, another agent, and an active Nx daemon. The BFF ratchet peaked near 5.5 GiB RSS while remaining above the safety floor; checks and the direct build were sequential and resource-supervised. The commit used SKIP_TYPECHECK=1 only after the exact BFF ratchet and both package typechecks passed, avoiding the repository hook's previously observed unsafe 290-project expansion. No rendered UI, mobile flow, schema migration, provider/model call, production signed deletion receipt, or Unreal content was involved, so Playwright/mobile/migration/provider/UE automation was inapplicable.

Saved-library durability and erasure verification#

Implementation source: 007a0bd8a5e21099e09d7c1bacf6402884179a59; remote-integrated publication tip: d46818e303b1184f3ef65f1a0b40ae0bbcb8957d. The protected lockfile blob remained a37431842e330b3a06b030947c25bebdc72bc2b1.

text
# apps/oshun/bff, real store + directly registered Fastify route
pnpm exec vitest run \
  src/library/saved-items-store.test.ts \
  src/routes/library-saved-items.test.ts --maxWorkers=1
  2 files, 31/31 tests passed

# apps/oshun/bff, default saved_claim_passage export collector
pnpm exec vitest run src/data-export/bundle-builder.test.ts --maxWorkers=1
  1 file, 4/4 tests passed

# apps/oshun/bff, customer-deletion lifecycle
pnpm exec vitest run \
  src/data-deletion/state-run-deletion.test.ts \
  src/data-deletion/state-durability.test.ts \
  src/data-deletion/deletion-worker.test.ts --maxWorkers=1
  3 files, 21/21 tests passed

# libs/shared/deletion-fanout
pnpm exec vitest run --maxWorkers=1
  7 files, 40/40 tests passed

# libs/contracts
pnpm exec vitest run src/common/customer-data-deletion.spec.ts --maxWorkers=1
  1 file, 24/24 tests passed

pnpm exec tsc --noEmit -p libs/shared/deletion-fanout/tsconfig.lib.json
pnpm exec tsc --noEmit -p libs/contracts/tsconfig.lib.json
  both passed

node tools/typecheck/ratchet.mjs --app apps/oshun/bff \
  --tsconfig tsconfig.typecheck.json
  no new app-own type errors; backlog 0

pnpm --dir apps/oshun/bff run build
  passed; 30.1 MB production server bundle

targeted ESLint, Prettier check, and git diff --check
  passed

# post-integration conflict-sensitive reruns
saved store/route/export 35/35; deletion fanout 40/40; contract 24/24 passed

The store tests prove legacy snapshot hydration, saved and unsaved revision survival, delayed acknowledgement, globally ordered cross-member snapshots, failed-write rollback and recovery, exact-member erasure, adjacent-member isolation, authoritative restart fences, corrupted-row suppression, missing-sink failure, and both save-versus-delete orderings. The directly registered Fastify tests prove route response blocking until persistence, controlled 503 on a failed sink, and 409 refusal of direct and device-sync resurrection. The export test seeds the real singleton, confirms the default saved_claim_passage collector exports it, erases one subject, and confirms only that subject's section becomes empty.

The full fanout and contract suites prove canonical service-ID alignment, omission when the saved-library deleter is unwired, and a signed attestation when it is injected. Customer-deletion state suites remain green with saved_claim_passage mapped, leaving four honest unmapped_artifact:* failures. The broader search and data-export route suites were attempted after their setup writes were changed to await the new acknowledgement boundary, but this checkout's installed dependency tree lacks the lock-declared luxon package imported by @oshun/v10-rail-kernel; both suites stopped during collection before tests ran. The affected saved-library route and export collector were therefore exercised directly; no dependency installation or protected-lock rewrite was performed.

The host had 15 GiB RAM, 31 GiB swap, another agent, and an active Nx daemon. The BFF ratchet peaked near 5.25 GiB RSS while remaining above the safety floor; checks and the direct build were sequential and resource-supervised. The commit used SKIP_TYPECHECK=1 only after the exact BFF ratchet and both package typechecks passed, avoiding the repository hook's previously observed unsafe 290-project expansion. No rendered UI, mobile flow, schema migration, database, provider/model call, production signed deletion receipt, or Unreal content was involved, so Playwright/mobile/migration/database/provider/UE automation was inapplicable.

Nisaba notebook durability and erasure verification#

Implementation source: b54626b784aa165ea21e027ae286731ad6916bf9; remote-integrated publication tip: 500531bf12b1f6521cfcb02f57f9f5f140a72dd6. The protected lockfile blob remained a37431842e330b3a06b030947c25bebdc72bc2b1.

text
# apps/oshun/bff, real store + direct Fastify mutation routes + default export
pnpm exec vitest run \
  src/nisaba/state-durability.test.ts \
  src/nisaba/in-process-adapter.test.ts \
  src/routes/nisaba-durability.test.ts \
  src/data-export/bundle-builder.test.ts
  4 files, 26/26 tests passed

# apps/oshun/bff, customer-deletion lifecycle
pnpm exec vitest run \
  src/data-deletion/state-run-deletion.test.ts \
  src/data-deletion/state-durability.test.ts \
  src/data-deletion/deletion-worker.test.ts
  3 files, 21/21 tests passed

# libs/shared/deletion-fanout
pnpm exec vitest run --config libs/shared/deletion-fanout/vitest.config.ts
  7 files, 40/40 tests passed

# libs/contracts
pnpm exec vitest run src/common/customer-data-deletion.spec.ts \
  --config libs/contracts/vitest.config.ts
  1 file, 24/24 tests passed

pnpm exec tsc --noEmit -p libs/shared/deletion-fanout/tsconfig.lib.json
pnpm exec tsc --noEmit -p libs/shared/deletion-fanout/tsconfig.spec.json
pnpm exec tsc --noEmit -p libs/contracts/tsconfig.lib.json
  all passed

node tools/typecheck/ratchet.mjs --app apps/oshun/bff \
  --tsconfig tsconfig.typecheck.json
  no new app-own type errors; backlog 0

pnpm --dir apps/oshun/bff run build
  passed; 30.1 MB production server bundle

targeted source ESLint, pre-commit ESLint/Prettier, and git diff --check
  passed

The durable snapshot contains only member-authored annotations and notebooks; it deliberately excludes the shared public-domain corpus, seeded compare views, manuscript witnesses, and recomputable grounded evidence. Notebook, annotation, annotation-to-notebook synchronization, and notebook-item mutations now clone a candidate, wait for the globally ordered snapshot write, and publish it only after success. Annotation counts and highlight state are rebuilt from restored annotations. Required deployable persistence fails closed, while direct routes return controlled 503 responses instead of acknowledging a volatile write.

The tests prove annotation-driven notebook rewrites survive restart, snapshot failure leaves the prior view intact and the next write recovers, exact-subject erasure preserves adjacent subjects, a failed deletion write neither clears memory nor installs a false fence, damaged snapshots cannot override a deletion fence, and both create-versus-delete orderings converge to an erased workspace. Stale post-erasure clients receive 409. The real default notebook export collector was seeded before deletion and observed empty for only the erased subject afterward. The canonical signed fanout now injects the live Nisaba deleter, omits it when unwired, and includes notebook in both the shared service enum and customer-deletion contract.

The broader nisaba-route.test.ts suite was attempted after every affected call site was converted to await persistence, but this checkout's installed dependency tree lacks the lock-declared luxon package imported by @oshun/v10-rail-kernel; collection stopped before tests ran. The directly registered Nisaba route harness covers the changed 503/409 behavior, and the store/adapter tests cover the mutation surface without importing the unrelated rail kernel. No dependency installation or protected-lock rewrite was performed. The repository-wide contracts spec typecheck was also attempted; it reached unrelated existing fixture errors, while the changed contract test and contracts production-library typecheck passed.

The host had 15 GiB RAM, 31 GiB swap, another agent, and an active Nx daemon. The final BFF ratchet peaked near 5.4 GiB RSS with about 5 GiB still available; checks and the direct build were sequential and resource-supervised. The commit used SKIP_TYPECHECK=1 only after the exact BFF ratchet and changed-package typechecks passed, avoiding the repository hook's previously observed unsafe 290-project expansion. No rendered UI, mobile flow, schema migration, database, provider/model call, production signed deletion receipt, or Unreal content was involved, so Playwright/mobile/migration/database/provider/UE automation was inapplicable.

This tranche maps the canonical notebook deletion artifact. Nisaba's separate passage-saved flags and study-reminder map were intentionally not smuggled into that artifact snapshot; their duplicate-source/reconciliation or durability disposition remains part of the final operational-store inventory.

Historical evidence-pack structural-absence verification (superseded)#

Current status: superseded for the BFF's persisted Metis academic-record partition by source 65200d9e043b3acefd6eef19743e2de7f7033e97 and the current verification section below. The following record remains valid proof for the earlier request-scoped Sophia surface; it is no longer the complete repository evidence_pack disposition.

Implementation and published source: 01dd3d56802a9825d2e45a387d088d8f54d804c7. The protected lockfile blob remained a37431842e330b3a06b030947c25bebdc72bc2b1.

text
# libs/shared/deletion-fanout
pnpm exec vitest run --config libs/shared/deletion-fanout/vitest.config.ts
  7 files, 40/40 tests passed

# libs/contracts
pnpm exec vitest run src/common/customer-data-deletion.spec.ts \
  --config libs/contracts/vitest.config.ts
  1 file, 24/24 tests passed

# apps/oshun/bff, explicit default-export absence
pnpm exec vitest run src/data-export/bundle-builder.test.ts \
  --config vitest.config.ts
  1 file, 6/6 tests passed

# apps/oshun/bff, customer-deletion lifecycle
pnpm exec vitest run \
  src/data-deletion/state-run-deletion.test.ts \
  src/data-deletion/deletion-worker.test.ts \
  src/data-deletion/state-durability.test.ts \
  --config vitest.config.ts
  3 files, 21/21 tests passed

pnpm exec tsc --noEmit -p libs/shared/deletion-fanout/tsconfig.lib.json
pnpm exec tsc --noEmit -p libs/shared/deletion-fanout/tsconfig.spec.json
pnpm exec tsc --noEmit -p libs/contracts/tsconfig.lib.json
  all passed

node tools/typecheck/ratchet.mjs --app apps/oshun/bff \
  --tsconfig tsconfig.typecheck.json
  no new app-own type errors; backlog 0

pnpm --dir apps/oshun/bff run build
  passed; 30.1 MB production server bundle

targeted source ESLint, pre-commit ESLint/Prettier, and git diff --check
  passed

The repository inventory found no customer-owned evidence-pack mutation or operational record. GET /v1/sophia/adapter/evidence-pack assembles its result inside the request and does not save it. Sophia's dormant/shared EvidencePack schema has no ownerId, userId, or other customer subject key, and no deployed repository service performs owner-keyed evidence-pack persistence. Contract and generated-client types describing evidence packs do not establish an operational customer store.

The canonical deletion service and customer-deletion contract now include evidence_pack. The BFF always contributes a no-subject-data eraser with an explicit structural detail. Through the real fanout, that eraser produces a signed and verifiable not_found attestation with zero rows removed; it never claims erased. The default export collector likewise reports the category unavailable with the same request-scoped/no-owner-key reason instead of implying that an unimplemented owning service will export it. Customer-deletion lifecycle tests remain complete with this newly mapped canonical service.

This proof is deliberately narrower than a real deletion implementation. No database row, shared editorial evidence, or production artifact was deleted, and no production signed receipt was obtained. If any future deployment persists customer-owned evidence packs, it must add an authenticated owner key, durable acknowledgement/restart proof, retention and export behavior, and a real subject-keyed eraser; retaining this structural-absence eraser in that state would fail closed-review requirements. No UI, mobile flow, schema migration, external database, provider/model call, or Unreal content changed, so their automation was inapplicable.

The host had 15 GiB RAM, 31 GiB swap, another agent, and an active Nx daemon. The supervised BFF ratchet was observed near 4.75 GiB RSS with 5.3 GiB still available; checks and the direct build were sequential. The implementation commit used SKIP_TYPECHECK=1 only after the exact ratchet and changed-package typechecks passed, avoiding the hook's previously observed unsafe 290-project expansion.

Profile and session durability/erasure verification#

Implementation source: 05856d6c76007de3a08d1c0a349ce2f8f547d7f3; remote-integrated publication tip: e6d37a508a0ef4ab72df6798f00fa790a6f507a0. Verification completed 2026-07-18 UTC on dev-server with Node 24.14.1, pnpm 10.25.0, TypeScript 6.0.3, Vitest 4.1.7, and ESLint 10.4.0. The protected lockfile blob remained a37431842e330b3a06b030947c25bebdc72bc2b1.

text
# cwd apps/oshun/bff; profile/auth/device-session durability, direct routes,
# honest export, and customer-deletion lifecycle
pnpm exec vitest run \
  src/profile/state-durability.test.ts \
  src/auth/customer-auth-durability.test.ts \
  src/auth-sessions/device-session-store-durability.test.ts \
  src/routes/profile-durability-route.test.ts \
  src/routes/auth-durability-route.test.ts \
  src/data-export/bundle-builder.test.ts \
  src/data-deletion/state-run-deletion.test.ts --maxWorkers=1
  7 files, 40/40 tests passed after publication integration

# cwd apps/oshun/bff; complete customer auth/profile/device-session routes
pnpm exec vitest run \
  src/__tests__/auth-route.test.ts \
  src/__tests__/profile-route.test.ts \
  src/routes/auth-device-sessions.test.ts --maxWorkers=1
  3 files, 36/36 tests passed after publication integration

# cwd apps/oshun/bff; converted admin/billing/payment/SSO callers
pnpm exec vitest run \
  src/admin/admin-bulk-operations-store.test.ts \
  src/admin/durable-backed-bulk-operations-store.test.ts \
  src/__tests__/admin-bulk-operations-route.test.ts \
  src/auth/sso-login-routes.test.ts \
  src/payments/fiat-routes.test.ts \
  src/payments/settlement-route.test.ts \
  src/routes/billing-app-store-route.test.ts --maxWorkers=1
  7 files, 89/89 tests passed after publication integration

# libs/contracts
pnpm exec vitest run libs/contracts/src/common/customer-data-deletion.spec.ts \
  --config libs/contracts/vitest.config.ts
  1 file, 24/24 tests passed

# cwd libs/shared/deletion-fanout; affected mapping/injection suites
pnpm exec vitest run src/deletion-fanout.test.ts \
  src/service-erasers.test.ts --maxWorkers=1
  2 files, 16/16 tests passed

pnpm exec tsc --noEmit -p libs/contracts/tsconfig.lib.json
pnpm exec tsc --noEmit -p libs/shared/deletion-fanout/tsconfig.lib.json
pnpm exec tsc --noEmit -p libs/shared/deletion-fanout/tsconfig.spec.json
  all passed

node tools/typecheck/ratchet.mjs --app apps/oshun/bff \
  --tsconfig tsconfig.typecheck.json
  no new app-own type errors; backlog 0

pnpm --dir apps/oshun/bff run build
  passed; 30.4 MB production server bundle

targeted ESLint, pre-commit ESLint/Prettier, and git diff --check
  passed

The store tests prove restart hydration, acknowledgement after ordered commit, failed-write rollback and recovery, exact-subject isolation, durable not-found fences, damaged-row suppression behind a fence, and both mutation-versus-delete orderings. Auth tests additionally prove password, recovery-code, refresh-token, and verification-token snapshots contain verifiers or lookup hashes rather than raw secrets. Direct Fastify route tests prove successful responses wait for the durable barrier and persistence failures become controlled responses. Export tests prove the real collectors include the available profile/session records, exclude refresh-token hashes, remain honest during partial erasure, and return empty sections after both erasers complete.

The contract, fanout, and deletion-lifecycle tests prove canonical artifact/ service alignment, omission when a real eraser is not injected, signed exact- subject attestations when it is injected, and successful full-account completion for all 16 current artifacts. The converted SSO, admin bulk, billing, settlement, and fiat-payment suites demonstrate that their identity/session mutations still preserve behavior across the new asynchronous acknowledgement boundary.

The post-integration ratchet and bundle build were rerun because the remote delta changed shared build/lint configuration; later publication-only integration was Hathor-scoped and did not change Oshun or shared verification inputs. The host had 15 GiB RAM and 31 GiB swap. The ratchet was run alone and supervised at no more than approximately 5.8 GiB TypeScript RSS; checks and build were sequential. The implementation changed no rendered UI, mobile flow, database schema, model or provider call, or Unreal content, so Playwright/mobile/migration/provider/UE automation was inapplicable. No production deletion request, signed production receipt, or provider-native remote-asset purge is claimed by that identity slice.

Generated-artifact stored-object purge verification#

Implementation source: c41b4661da7f29f51628d957f106f128811efc53; remote-integrated publication tip: c974990c8104a7d5bd3aa0230223bd2d38542047. Verification completed 2026-07-18 UTC on dev-server, Linux 6.8.0-110-generic x86_64, with Node 24.14.1, pnpm 10.25.0, TypeScript 6.0.3, Vitest 4.1.7, and ESLint 10.4.0. The protected lockfile blob remained a37431842e330b3a06b030947c25bebdc72bc2b1.

text
# cwd libs/shared/storage; exact-key version-listing, pagination, batching,
# provider-error, concurrent-writer, repeated-cursor, and input validation
pnpm exec vitest run
  4 files, 81/81 tests passed

# cwd libs/oshun/privacy; byte-before-metadata ordering, exact owner/ID scope,
# missing-adapter and byte/DB failure, retry, race, and malformed identity
pnpm exec vitest run
  3 files, 88/88 tests passed

# cwd apps/oshun/bff; bucket registry and generated-artifact composition
pnpm exec vitest run \
  src/generation/generated-artifact-object-store.test.ts \
  src/generation/generated-artifact-erasure.test.ts \
  src/assets/__tests__/asset-store.test.ts
  3 files, 10/10 tests passed

# cwd apps/oshun/bff; generation owner/control-plane regression group
pnpm exec vitest run \
  src/generation/jobs-route.test.ts \
  src/generation/output-catalog.test.ts \
  src/generation/generated-artifact-erasure.test.ts \
  src/generation/generated-artifact-object-store.test.ts \
  src/isis/output-gallery-store.test.ts \
  src/generation/curated-generation-executor.test.ts \
  src/generation/music-enqueue-executor.test.ts \
  src/generation/sky-briefing-enqueue-executor.test.ts \
  src/isis/curated-card-route.test.ts \
  src/isis/music-route.test.ts \
  src/isis/nyx-3d-route.test.ts \
  src/agentic/studio-tool-catalog.test.ts \
  src/agentic/runs-route.test.ts
  13 files, 121/121 tests passed

# cwd apps/oshun/bff; profile-avatar all-version deletion regression
pnpm exec vitest run \
  src/assets/__tests__/asset-store.test.ts \
  src/profile/avatar-store.test.ts \
  src/profile/avatar-upload.test.ts \
  src/routes/profile-avatar-route.test.ts
  4 files, 30/30 tests passed

# cwd apps/oshun/bff; live disposable prefix in a versioned local MinIO bucket
pnpm exec vitest run -c vitest.integration.config.ts \
  src/generation/generated-artifact-object-store.integration.test.ts
  1 file, 1/1 integration test passed

# cwd libs/shared/deletion-fanout
pnpm exec vitest run
  7 files, 40/40 tests passed

# cwd apps/oshun/bff; signed customer-deletion lifecycle
pnpm exec vitest run \
  src/data-deletion/state-run-deletion.test.ts \
  src/data-deletion/deletion-worker.test.ts \
  src/data-deletion/state-durability.test.ts
  3 files, 21/21 tests passed

pnpm exec tsc --noEmit -p libs/shared/storage/tsconfig.lib.json
pnpm exec tsc --noEmit -p libs/oshun/privacy/tsconfig.lib.json
pnpm exec tsc --noEmit -p libs/shared/deletion-fanout/tsconfig.lib.json
  all production-library typechecks passed

node tools/typecheck/ratchet.mjs --app apps/oshun/bff \
  --tsconfig tsconfig.typecheck.json
  no new app-own type errors; backlog 0

pnpm --dir apps/oshun/bff run build
  passed; 30.4 MB production server bundle

targeted ESLint, Prettier, pre-commit ESLint/Prettier, and git diff --check
  passed

After the first push was rejected because origin/main had advanced, the remote delta was merged and the protected/user state was restored. The focused published-tree rerun passed 14 shared/privacy assertions, 21 BFF adapter/ composition/asset/deletion assertions, and the live versioned-MinIO test. The BFF zero-backlog ratchet and 30.4 MB bundle build also passed again before the integration tip was pushed to exact remote parity.

The live object-store test uploads two versions, creates a normal-delete marker, purges through the deploy-bound adapter, verifies a second all-version purge finds nothing, and uses the adjacent key's one remaining version as both an isolation assertion and cleanup. Unit tests cover database ordering and failure semantics because the checkout's local Isis database does not currently expose the generated_outputs table; no real-Postgres generated-row receipt is claimed. Production-library typechecks are green. The pre-existing spec-only typechecks remain red outside this change: storage's presigned.spec.ts passes an unsupported region fixture property, and privacy's privacy.test.ts has an unused ResidencyAssignment import. Every changed spec executes and passes.

The host had 15 GiB RAM and 31 GiB swap. Both BFF ratchets ran alone and were polled within 30 seconds; the post-merge run peaked near 5.1 GiB TypeScript RSS with about 7.2 GiB still available. Checks and the direct build were sequential. The implementation commit used SKIP_TYPECHECK=1 only after the exact BFF ratchet and changed production-package typechecks passed, avoiding the hook's unsafe broad affected expansion. No rendered UI, mobile flow, schema migration, model/provider generation call, Unreal content, production deletion request, or signed production receipt was involved, so their automation was inapplicable.

This closes the recoverable-byte defect for every generated artifact whose Isis row carries a configured S3/MinIO bucket/key and for profile-avatar objects in the same store. It does not prove erasure of provider-native remote assets that have no bucket/key deletion identity or credentials in the deploy-bound registry.

Reminder continuity durability and erasure verification#

Implementation source aab9c2634210178443a54d2d8212688171a1cc10, currently published through af7fffdb9a6fcaff863a57b516c0ecefba0f82f5, closes the currently implemented reminder-continuity partition. Verification completed on 2026-07-18 UTC on dev-server with Node 24.14.1, pnpm 10.25.0, TypeScript 6.0.3, Vitest 4.1.7, and ESLint 10.4.0. The protected user pnpm-lock.yaml remained byte-identical at Git blob a37431842e330b3a06b030947c25bebdc72bc2b1.

text
# cwd apps/oshun/bff; complete focused reminder/deletion/export surface
pnpm exec vitest run \
  src/routes/data-deletion-continuity.test.ts \
  src/data-deletion \
  src/data-export \
  src/reminders
  21 files, 120/120 tests passed

# final reminder candidate/commit/race/restart suite
pnpm exec vitest run src/reminders/reminder-service.durability.test.ts
  1 file, 12/12 tests passed

# real Postgres durable-store integration; password redacted
OSHUN_ADMIN_DATABASE_URL=postgresql://oshun:<redacted>@127.0.0.1:5432/oshun_dev \
  pnpm exec vitest run src/reminders/reminder-service.postgres.integration.test.ts
  1 file, 1/1 test passed

# published-tree composition regression, including concurrent Ori continuity
pnpm exec vitest run \
  src/data-deletion/continuity-state-eraser.test.ts \
  src/data-deletion/v1-subject-erasers.test.ts \
  src/reminders/reminder-service.durability.test.ts \
  src/data-export/bundle-builder.test.ts
  4 files, 34/34 tests passed

node tools/typecheck/ratchet.mjs --app apps/oshun/bff \
  --tsconfig tsconfig.typecheck.json
  no new app-own type errors; backlog 0

pnpm --dir apps/oshun/bff run build
  passed; 31.9 MB production server bundle

targeted ESLint, Prettier, pre-commit ESLint/Prettier and affected typecheck,
and git diff --check
  passed

The reminder service now clones the complete schedule, delivered-ID ledger, delivery-ownership index, in-app inbox, and deleted-recipient fence; awaits one ordered durable save of that candidate; and publishes it to process memory only after the save succeeds. A required production durability guard rejects an unbound sink, and the pre-provider guard prevents delivery side effects before that check. Failed writes leave the last committed in-memory state visible. Snapshot normalization repairs legacy delivered-owner entries and makes the upgraded state restart-safe.

Exact-subject deletion runs through the same synchronous process queue as the reminder cycle. It removes the subject's pending schedule, owned delivered IDs, ownership entries, and inbox messages, then commits a durable resurrection fence. Tests cover restart, failed save, idempotent retry, delete-versus-cycle ordering in both directions, stale recreation refusal, legacy-owner repair, and adjacent-recipient isolation. The live Postgres test uses an isolated store key and proves the committed snapshot is recoverable from the real administrative database adapter.

DSAR export reads the same continuity snapshot and reports all three user-facing state representations: pending schedule, owned delivery IDs, and inbox. The export is empty after erasure. The canonical continuity eraser count-validates each partition and now composes Studio, reminders, and the concurrently landed Ori-presence partition; missing, malformed, or failed partition receipts fail the aggregate deletion receipt closed.

Two remote integrations were required because origin/main advanced during publication. Both integrations preserved the protected lockfile and unrelated user files. The second integration tip was pushed and verified as the exact refs/heads/main value. A frozen install refreshed only missing local workspace links needed by the remote delta and did not change the lockfile. The Nx lint wrapper could not construct its project graph against the intentionally protected lockfile (Source project does not exist: npm:vite-tsconfig-paths@6.1.1), so the exact changed TypeScript sources were run through ESLint directly and passed.

The queue is a same-process serialization boundary, not a distributed lease. An external provider delivery necessarily occurs before the final delivery-ledger commit, so a failed final save can cause that provider operation to be retried. This evidence therefore claims durable at-least-once reminder continuity and exact local-state erasure, not distributed multi-worker serialization or provider-level exactly-once delivery. No rendered UI, mobile flow, schema migration, model/provider generation call, Unreal content, production deletion request, or signed production receipt changed in this slice, so those automation paths were inapplicable.

Nisaba saved-state and study-reminder durability verification#

Implementation source and published tip af7fffdb9a6fcaff863a57b516c0ecefba0f82f5 closes the two explicitly named Nisaba-local gaps: saved passage flags and study reminders. Verification completed on 2026-07-18 UTC on dev-server with Node 24.14.1, pnpm 10.25.0, TypeScript 6.0.3, Vitest 4.1.7, and ESLint 10.4.0. The protected user pnpm-lock.yaml remained byte-identical at Git blob a37431842e330b3a06b030947c25bebdc72bc2b1.

text
# cwd apps/oshun/bff; focused state/adapter/DSAR/deletion behavior
pnpm exec vitest run \
  src/nisaba/state-durability.test.ts \
  src/nisaba/in-process-adapter.test.ts \
  src/data-deletion/saved-claim-passage-eraser.test.ts \
  src/data-deletion/continuity-state-eraser.test.ts \
  src/data-export/bundle-builder.test.ts
  5 files, 43/43 tests passed

# expanded Nisaba BFF route, contract, adapter, state, DSAR, and eraser surface
pnpm exec vitest run \
  src/nisaba \
  src/routes/nisaba-durability.test.ts \
  src/routes/nisaba-passage-audio.test.ts \
  src/__tests__/nisaba-read-adapters.test.ts \
  src/__tests__/nisaba-route.test.ts \
  src/__tests__/contract/nisaba-bff-contract.test.ts \
  src/data-deletion/saved-claim-passage-eraser.test.ts \
  src/data-deletion/continuity-state-eraser.test.ts \
  src/data-export/bundle-builder.test.ts
  11 files, 79/79 tests passed

# real Postgres durable-store integration; password redacted
OSHUN_ADMIN_DATABASE_URL=postgresql://oshun:<redacted>@127.0.0.1:5432/oshun_dev \
  pnpm exec vitest run -c vitest.integration.config.ts \
    src/nisaba/state-durability.integration.test.ts
  1 file, 1/1 test passed

node tools/typecheck/ratchet.mjs --app apps/oshun/bff \
  --tsconfig tsconfig.typecheck.json
  no new app-own type errors; backlog 0

pnpm --dir apps/oshun/bff run build
  passed; 31.3 MB production server bundle

targeted production-source ESLint, Prettier, pre-commit ESLint/Prettier,
git diff --check, and post-rewrite focused rerun
  passed; post-rewrite rerun 43/43

The existing Nisaba snapshot now retains only member-owned saved passage IDs and reminder records alongside notebooks and annotations. Shared corpus passage bodies, manuscript witnesses, compare views, and grounded evidence remain outside the snapshot. Legacy snapshots with no new fields still restore. Every save, unsave, reminder create, and reminder toggle clones the complete member record, enters the same ordered mutation queue as notebook changes and deletions, awaits the durable candidate save, and publishes memory only after success. Missing required persistence and failed writes leave visible state unchanged.

Notebook/annotation, saved-passage, and study-reminder deletion now have independent durable subject fences. Selective deletion clears only its category, preserves the other two, survives restart, is idempotent, preserves adjacent members, and rejects stale recreation. Tests exercise mutation-before-delete and delete-before-mutation ordering for both new categories. The real Postgres test uses an isolated store key and proves committed saved/reminder recovery, selective erasure, retained notebook state, adjacent-subject isolation, and both fences after a second restart.

The signed saved_claim_passage service now count-validates and composes the cross-device LWW saved-item store with Nisaba's local saved flags. The signed continuity_state service includes Nisaba study reminders in addition to Studio, delivery reminder state, and any deploy-bound Ori-presence partition. A partial error or malformed count rejects the service instead of issuing a misleading receipt. Full-account fanout can run the three Nisaba category erasers in any order because they share one serialization boundary and preserve unrelated category state.

DSAR saved_claim_passage export labels and includes both physical saved representations without exporting shared passage bodies. continuity_state includes the subject's Nisaba reminder records. The notebook category now includes member-authored annotations as well as notebooks. Tests prove each view becomes empty after its exact category eraser while adjacent-member data remains available.

During commit verification, the repository's affected-typecheck hook attempted to install nx@latest while constructing a project graph. That out-of-scope dependency mutation was stopped before package.json or the protected lockfile changed. The exact zero-backlog BFF ratchet had already passed, so the final commit used SKIP_TYPECHECK=1 only for that unsafe duplicate hook step; the hook's ESLint and Prettier phases passed. origin/main was then deliberately rewritten with filter-repo under the repository history-rewrite runbook. The single Nisaba patch was rebased onto the replacement history; tree comparison showed only the runbook differed outside the nine intended files, the 43-test focused suite passed again, and the rewritten commit was pushed to exact remote parity.

No rendered UI, mobile flow, schema migration, model/provider generation call, Unreal content, production deletion request, or signed production receipt changed in this slice, so those automation paths were inapplicable.

Notification preference and read-state durability verification#

Implementation source and published tip 067d5fff4634a189a751faa366f4ac0342073a61 closes the currently implemented notification preference and read-state partitions. Verification completed on 2026-07-17 UTC on dev-server, Linux 6.8.0-110-generic x86_64, with Node 24.14.1, pnpm 10.25.0, TypeScript 6.0.3, Vitest 4.1.7, and ESLint 10.4.0. The protected user pnpm-lock.yaml remained byte-identical at Git blob a37431842e330b3a06b030947c25bebdc72bc2b1.

text
# cwd apps/oshun/bff; exact final notification/data-rights regression surface
pnpm exec vitest run \
  src/notifications/state-durability.test.ts \
  src/__tests__/notification-preferences-store.test.ts \
  src/__tests__/notification-read-state-store.test.ts \
  src/__tests__/notifications-preferences-route.test.ts \
  src/__tests__/notifications-write-route.test.ts \
  src/data-export/bundle-builder.test.ts \
  src/data-deletion/continuity-state-eraser.test.ts \
  src/data-deletion/profile-state-eraser.test.ts \
  src/data-deletion/state-run-deletion.test.ts \
  src/data-deletion/state-durability.test.ts \
  src/data-deletion/deletion-worker.test.ts \
  src/routes/data-deletion-continuity.test.ts \
  --maxWorkers=1
  12 files, 82/82 tests passed

# real Postgres snapshot recovery; password redacted
OSHUN_ADMIN_DATABASE_URL=postgresql://oshun:<redacted>@127.0.0.1:5432/oshun_dev \
  pnpm exec vitest run -c vitest.integration.config.ts \
    src/notifications/state-durability.integration.test.ts --maxWorkers=1
  1 file, 1/1 test passed

# repository root; exact BFF zero-backlog type ratchet
node tools/typecheck/ratchet.mjs --app apps/oshun/bff \
  --tsconfig tsconfig.typecheck.json
  no new app-own type errors; backlog 0

# cwd apps/oshun/bff; changed production sources
pnpm exec eslint \
  src/data-deletion/profile-state-eraser.ts \
  src/data-export/bundle-builder.ts \
  src/notifications/preferences-store.ts \
  src/notifications/read-state-store.ts \
  src/notifications/state.ts \
  src/routes/notifications-preferences.ts \
  src/routes/notifications-write.ts \
  src/server.ts
  passed; only repository Nx-project-graph availability warnings

# cwd apps/oshun/bff; exact production entry bundle
pnpm exec esbuild src/server.ts --bundle --platform=node --format=esm \
  --target=node22 --outfile=dist/server.js --sourcemap
  passed; 31.9 MB server bundle and 75.4 MB source map

pre-commit ESLint/Prettier, docs validation, and git diff --check
  passed

The preference snapshot contains explicit domain, persona, quiet-hours, and digest records, subject revisions, and subject-deletion fences. The derivable consumer-cadence cache is deliberately omitted; when a subject first makes an explicit durable mutation, any cached cadence provides the initial candidate so timezone and frequency are not silently lost. The read-state snapshot contains each subject's notification IDs and read/dismissed state, revisions, and deletion fences. Both stores normalize legacy snapshots, restore only committed state, serialize whole-store saves, and leave the last committed in-memory view visible after a failed write.

Production wiring binds both stores to the administrative durable-snapshot adapter, hydrates them before traffic, and fails startup if a required sink is missing. Preference and write routes await the durable API before responding. Persistence failures return a controlled 503 without publishing the candidate; a durable subject fence rejects later mutation with 409. Direct synchronous helpers remain available only to in-memory tests and are rejected once production durability is required.

Exact-subject deletion is part of the same ordered mutation stream. It removes the subject's complete record, commits a fence even for not_found, preserves adjacent subjects, survives restart, and wins safely in either mutation/delete race order. The tests also prove idempotent retry, failed-delete rollback, and stale resurrection refusal. The live Postgres case uses an isolated store key and recovers both committed partitions and their deletion fences from the real adapter.

The canonical signed profile eraser now count-validates consumer profile, customer authentication profile, and notification preferences. The canonical signed continuity_state eraser count-validates notification read state along with Studio, reminder, Nisaba, and any deploy-bound Ori partitions. A partial failure rejects the service instead of signing a misleading receipt. DSAR collectors read the same stored records: explicit notification preferences are included in profile, while read/dismiss state and its revision are included in continuity_state; both views become empty after exact erasure.

The BFF ratchet ran alone under the repository memory gate, was polled within 30 seconds, peaked near 5.64 GiB TypeScript RSS, and retained at least 7 GiB available memory. The source commit used SKIP_TYPECHECK=1 only after that exact ratchet passed; the hook's ESLint and Prettier phases passed. origin/main advanced normally during publication, so the single source commit was rebased onto the new tip, the protected lockfile was restored byte-for-byte, and the rebased SHA above was pushed to exact remote parity.

No rendered UI, mobile flow, schema migration, model/provider generation call, Unreal content, production deletion request, or signed production receipt changed in this slice, so Playwright/mobile, migration, provider, Unreal, and production-operations automation were inapplicable.

Personalization-vector and active-persona durability verification#

Implementation source and published tip 90e6592487f2be1d36069c9be4789fcf1e9120c2 closes the currently implemented personalization-vector and active-persona partitions. Verification completed on 2026-07-17 UTC on dev-server, Linux 6.8.0-110-generic x86_64, with Node 24.14.1, pnpm 10.25.0, TypeScript 6.0.3, Vitest 4.1.7, and ESLint 10.4.0. The protected user pnpm-lock.yaml remained byte-identical at Git blob a37431842e330b3a06b030947c25bebdc72bc2b1.

text
# cwd apps/oshun/bff; final personalization, route, downstream, DSAR, and
# deletion-lifecycle regression surface
pnpm exec vitest run \
  src/personas/active-persona-store.test.ts \
  src/personalization/personalization-vector-store.test.ts \
  src/personalization/personalization-vector-consumer.test.ts \
  src/routes/personas-consumer.test.ts \
  src/data-deletion/personalization-state-eraser.spec.ts \
  src/data-export/bundle-builder.test.ts \
  src/__tests__/admin-bulk-operations-route.test.ts \
  src/__tests__/assistant-llm-composer.test.ts \
  src/data-deletion/state-run-deletion.test.ts \
  src/data-deletion/state-durability.test.ts \
  src/data-deletion/deletion-worker.test.ts \
  --maxWorkers=1
  11 files, 95/95 tests passed

# real Postgres snapshot recovery; password redacted
OSHUN_ADMIN_DATABASE_URL=postgresql://oshun:<redacted>@127.0.0.1:5432/oshun_dev \
  pnpm exec vitest run -c vitest.integration.config.ts \
    src/personalization/state-durability.integration.spec.ts --maxWorkers=1
  1 file, 1/1 test passed

# repository root; final exact BFF zero-backlog type ratchet
node tools/typecheck/ratchet.mjs --app apps/oshun/bff \
  --tsconfig tsconfig.typecheck.json
  no new app-own type errors; backlog 0

# cwd apps/oshun/bff; changed production/config sources
pnpm exec eslint --no-warn-ignored \
  src/admin/bulk-commit-executors.ts \
  src/data-deletion/personalization-state-eraser.ts \
  src/personalization/personalization-vector-consumer.ts \
  src/personalization/personalization-vector-store.ts \
  src/personas/active-persona-store.ts \
  src/routes/personas-consumer.ts \
  src/server.ts vitest.integration.config.ts
  passed; only repository Nx-project-graph availability warnings

# cwd apps/oshun/bff; exact production entry bundle
pnpm exec esbuild src/server.ts --bundle --platform=node --format=esm \
  --target=node22 --outfile=dist/server.js --sourcemap
  passed; 31.9 MB server bundle and 75.4 MB source map

authoring-time conventions ratchet, staged stub scan, pre-commit
ESLint/Prettier, V5 docs validation, and git diff --check
  passed; no convention-baseline expansion

The vector consumer now awaits upsertPersonalizationVectorDurably before it reports a record to its observability callback. Each update clones the complete store candidate, waits for the ordered snapshot, and publishes memory only after success. A missing required sink or failed save leaves the last committed vector visible and reports the event as dropped instead of acknowledged. Legacy vector-only snapshots restore with zero revisions; a missing snapshot is authoritative empty state at production binding.

Active-persona selection follows the same discipline for consumer select, consumer clear, and admin bulk-assignment paths. Production rejects the legacy synchronous mutation helpers. The consumer route converts a persistence failure to 503 without exposing the candidate and converts durable subject-fence rejection to 409. The existing assistant path still consumes the committed selection, which the expanded regression suite verifies.

Both stores persist subject revisions and deletion fences and serialize mutation with exact-subject erasure. A not-found deletion still commits its fence; restart retains it; adjacent subjects remain intact; and stale vector or persona mutations lose safely in either race order. The live Postgres case uses isolated snapshot keys and proves acknowledged recovery, composed erasure, adjacent-subject isolation, and both fences after a second hydration.

The signed personalization_vector service now count-validates and composes the embedding with active-persona selection, matching the existing deletion taxonomy that treats the selection as personalization data. Partial failure rejects the service rather than issuing an incomplete receipt. DSAR retains the established artifact vocabulary: the embedding is exported as personalization_vector and the selected guide as persona; both sections become empty after composed erasure.

The final BFF ratchet ran alone after the repository resource gate and was polled within 30 seconds. It peaked near 5.10 GiB TypeScript RSS with about 7.0 GiB still available. The source commit used SKIP_TYPECHECK=1 only after the exact ratchet passed twice; all other hook phases passed. origin/main advanced during publication, but the incoming delta changed only the tracked lockfile in this scope. The single source patch was rebased, the protected user lockfile was restored byte-for-byte, and the rebased SHA above was pushed to exact remote parity.

No rendered UI, mobile flow, schema migration, model/provider generation call, Unreal content, production deletion request, or signed production receipt changed in this slice, so Playwright/mobile, migration, provider, Unreal, and production-operations automation were inapplicable.

Customer message-center durability verification#

Implementation source and published tip 25f9acaf3fba4cc20859b2472b4a90589457e4bd closes the previously named customer message-center partition. Verification completed on 2026-07-17 UTC on dev-server, Linux 6.8.0-110-generic x86_64, with Node 24.14.1, pnpm 10.25.0, TypeScript 6.0.3, Vitest 4.1.7, and ESLint 10.4.0. The protected user pnpm-lock.yaml remained byte-identical at Git blob a37431842e330b3a06b030947c25bebdc72bc2b1.

text
# cwd apps/oshun/bff; final message-center, route, producer, notification,
# DSAR, deletion-lifecycle, and persistence regression surface
pnpm exec vitest run \
  src/customer/customer-message-center-store.test.ts \
  src/customer/customer-message-center-store-durability.spec.ts \
  src/__tests__/customer-message-center-route.test.ts \
  src/__tests__/notifications-write-route.test.ts \
  src/__tests__/notifications-route.test.ts \
  src/__tests__/user-reports-route.test.ts \
  src/__tests__/metis-integrity-route.test.ts \
  src/data-export/bundle-builder.test.ts \
  src/data-deletion/continuity-state-eraser.test.ts \
  src/data-deletion/state-run-deletion.test.ts \
  src/data-deletion/state-durability.test.ts \
  src/data-deletion/deletion-worker.test.ts \
  --maxWorkers=1
  12 files, 120/120 tests passed

# repository root; pure message-center engine
pnpm exec vitest run \
  libs/oshun/customer-message-center/src/message-center.test.ts --maxWorkers=1
  1 file, 21/21 tests passed

# real Postgres snapshot recovery; password redacted
OSHUN_ADMIN_DATABASE_URL=postgresql://oshun:<redacted>@127.0.0.1:5432/oshun_dev \
  pnpm exec vitest run -c apps/oshun/bff/vitest.integration.config.ts \
    apps/oshun/bff/src/customer/customer-message-center-durability.integration.spec.ts \
    --maxWorkers=1
  1 file, 1/1 test passed

# repository root; final exact BFF zero-backlog type ratchet
node tools/typecheck/ratchet.mjs --app apps/oshun/bff \
  --tsconfig tsconfig.typecheck.json
  no new app-own type errors; backlog 0

# repository root; pure-engine typecheck
pnpm exec tsc --noEmit \
  -p libs/oshun/customer-message-center/tsconfig.json --pretty false
  passed

# cwd apps/oshun/bff; changed production/tests/config sources
pnpm exec eslint --no-warn-ignored \
  src/customer/customer-message-center-store.ts \
  src/customer/customer-message-center-store-durability.spec.ts \
  src/customer/customer-message-center-durability.integration.spec.ts \
  src/routes/customer-message-center.ts \
  src/routes/notifications-write.ts src/routes/user-reports.ts \
  src/routes/metis-integrity.ts src/data-export/bundle-builder.ts src/server.ts
  passed; only repository Nx-project-graph availability warnings

# cwd apps/oshun/bff; exact production entry bundle
pnpm exec esbuild src/server.ts --bundle --platform=node --format=esm \
  --target=node22 --outfile=dist/server.js --sourcemap
  passed; 31.9 MB server bundle and 75.5 MB source map

authoring-time conventions ratchet, staged stub scan, pre-commit
ESLint/Prettier, V5 docs validation, and git diff --check
  passed; no convention-baseline expansion

The BFF wrapper now snapshots the complete pure-engine state—visible and archived messages, read timestamps, all receipt entries, and both suppressed and resubscribed channel/category policies—alongside delayed dispatch payloads, attempts, errors, global revision, per-subject revisions, and deletion fences. A missing bound snapshot is authoritative empty state. Production rejects every legacy synchronous mutator, requires the sink before traffic, and hydrates it before route registration can accept requests.

All customer writes and operator dispatches use ordered candidate/save/publish mutations. Mark-read, archive, unsubscribe, resubscribe, deep-link click receipts, and normal dispatch return only after persistence. Trust & Safety and Metis decision notifications add queued/sent/delivered history in one atomic save. A failed write does not change the inbox, receipt, policy, delayed queue, or revision; routes return controlled 503s. Replay persists gate holds and semantic failures with attempt metadata, preserves work when persistence fails, and removes a dispatch only when the message plus sent/delivered receipts commit together.

Exact-subject erasure shares the same mutation stream, removes archived and visible history, policies, and delayed work, and commits a resurrection fence even for not_found. Unit races prove send-before-delete ends erased and delete-before-send rejects. The real Postgres case proves acknowledged recovery, composed erasure, adjacent-subject isolation, and stale send/schedule rejection after a second hydration.

The existing signed continuity_state service now count-validates the customer message-center partition with Studio, reminder, Nisaba, notification-read, and any deploy-bound Ori state. A malformed count or partition failure rejects the aggregate receipt. DSAR exports complete message history, receipt stages, suppression policies, delayed work, and revision; archived rows are not hidden from the export, and the section becomes empty after exact erasure while the adjacent subject remains intact. Mapping the record to continuity_state also binds it to that canonical retention/deletion policy rather than inventing a new artifact category.

The final BFF ratchet ran alone after the repository resource gate and was polled within 30 seconds. It peaked near 5.34 GiB TypeScript RSS with about 6.3 GiB still available. The source commit used SKIP_TYPECHECK=1 only after the exact supervised ratchet passed; all other hook phases passed. origin/main advanced during publication with no overlap in the 15 source/test files. The single source patch was rebased, the protected user lockfile was restored byte-for-byte, and the rebased SHA above was pushed to exact remote parity.

No rendered UI, mobile flow, schema migration, model/provider generation call, Unreal content, production deletion request, or signed production receipt changed in this slice, so Playwright/mobile, migration, provider, Unreal, and production-operations automation were inapplicable.

Device push-token durability verification#

Implementation source and published tip e6b90e13762cc94a8b8a0f70750248c9b4f14519 closes the device push-token partition discovered by the final operational-store inventory. Verification completed on 2026-07-17 UTC on dev-server, Linux 6.8.0-110-generic x86_64, with Node 24.14.1, pnpm 10.25.0, TypeScript 6.0.3, Vitest 4.1.7, and ESLint 10.4.0. The protected user pnpm-lock.yaml remained byte-identical at Git blob a37431842e330b3a06b030947c25bebdc72bc2b1.

text
# cwd apps/oshun/bff; final route, session-composer, DSAR, and deletion lifecycle surface
pnpm exec vitest run \
  src/routes/device-tokens.test.ts \
  src/data-deletion/session-state-eraser.spec.ts \
  src/data-export/bundle-builder.test.ts \
  src/data-deletion/state-run-deletion.test.ts \
  src/data-deletion/state-durability.test.ts \
  src/data-deletion/deletion-worker.test.ts \
  --maxWorkers=1
  6 files, 52/52 tests passed

# real Postgres snapshot recovery and signed-session erasure; password redacted
OSHUN_ADMIN_DATABASE_URL=postgresql://oshun:<redacted>@127.0.0.1:5432/oshun_dev \
  pnpm exec vitest run -c apps/oshun/bff/vitest.integration.config.ts \
    apps/oshun/bff/src/routes/device-tokens-durability.integration.spec.ts \
    --maxWorkers=1
  1 file, 1/1 test passed

# repository root; final exact BFF zero-backlog type ratchet
node tools/typecheck/ratchet.mjs --app apps/oshun/bff \
  --tsconfig tsconfig.typecheck.json
  no new app-own type errors; backlog 0

# repository root; changed production/tests/config sources
pnpm exec eslint --no-warn-ignored \
  apps/oshun/bff/src/routes/device-tokens.ts \
  apps/oshun/bff/src/routes/device-tokens.test.ts \
  apps/oshun/bff/src/routes/device-tokens-durability.integration.spec.ts \
  apps/oshun/bff/src/data-deletion/session-state-eraser.ts \
  apps/oshun/bff/src/data-deletion/session-state-eraser.spec.ts \
  apps/oshun/bff/src/data-export/bundle-builder.ts \
  apps/oshun/bff/src/data-export/bundle-builder.test.ts \
  apps/oshun/bff/src/server.ts
  passed; only repository Nx-project-graph availability warnings

# cwd apps/oshun/bff; exact production entry bundle
pnpm exec esbuild src/server.ts --bundle --platform=node --format=esm \
  --target=node22 --outfile=dist/server.js --sourcemap
  passed; 31.9 MB server bundle and 75.5 MB source map

authoring-time conventions ratchet, staged stub scan, pre-commit
ESLint/Prettier, V5 docs validation, and git diff --check
  passed; no convention-baseline expansion attributable to this slice

Registration and removal share an ordered whole-store mutation stream. Each operation builds a detached candidate, awaits its snapshot save, and publishes only after that save succeeds. Route tests force both registration and removal failures: each returns 503, keeps the last committed token visible, and restores the same state after hydration. A missing bound snapshot is authoritative empty state, and production mutation fails closed when its required sink is absent.

The snapshot contains the complete raw delivery credentials, device metadata, per-subject revisions, and durable deletion fences. Register-before-delete ends erased; delete-before-register rejects the stale registration. A failed delete does not remove or fence the subject, so the signed service can retry honestly. Deletion survives restart, preserves an adjacent member, and rejects later registration with 409 at the route boundary.

The signed session eraser now count-validates customer-auth sessions, device-session/audit records, and push tokens independently; a malformed count or partition failure rejects the aggregate receipt. Session DSAR adds device metadata and a stable SHA-256 fingerprint while deliberately withholding the raw push credential. After composed erasure the section is empty. Mapping this partition to session binds it to the existing session retention and deletion policy rather than inventing another artifact category.

The final BFF ratchet ran alone after the repository resource gate and was polled within 30 seconds. It peaked near 5.79 GiB TypeScript RSS while about 5.9 GiB remained available. The source commit used SKIP_TYPECHECK=1 only after the exact supervised ratchet passed; all other hook phases passed. origin/main advanced with unrelated Hathor files and pnpm-lock.yaml. The eight-file source patch rebased without overlap, the protected user lockfile was restored from preservation stash 700299fa36d1002b731f2fdc914a494c21ffb952, and the rebased SHA above was pushed to exact remote parity. The preservation stash remains intact.

No rendered UI, mobile flow, schema migration, model/provider generation call, Unreal content, production deletion request, or signed production receipt changed in this slice, so Playwright/mobile, migration, provider, Unreal, and production-operations automation were inapplicable.

Customer channel-binding durability verification#

Implementation source and published tip c6e034e46dbe119409147fa6d3356fe3d2f0d274 closes the customer email, SMS, and WhatsApp binding partition discovered by the continuing operational-store inventory. Verification completed on 2026-07-17 UTC on dev-server, Linux 6.8.0-110-generic x86_64, with Node 24.14.1, pnpm 10.25.0, TypeScript 6.0.3, Vitest 4.1.7, and ESLint 10.4.0. The protected user pnpm-lock.yaml remained byte-identical at Git blob a37431842e330b3a06b030947c25bebdc72bc2b1.

text
# cwd apps/oshun/bff; store, route, profile composer, and DSAR surface
pnpm exec vitest run \
  src/messaging-channels/channel-bindings-store.test.ts \
  src/__tests__/channel-bindings-route.test.ts \
  src/data-deletion/profile-state-eraser.test.ts \
  src/data-export/bundle-builder.test.ts --maxWorkers=1
  4 files, 49/49 tests passed

# cwd apps/oshun/bff; connected profile and reminder-recipient consumers
pnpm exec vitest run \
  src/__tests__/profile-route.test.ts \
  src/reminders/streak-reminder-producer.test.ts --maxWorkers=1
  2 files, 16/16 tests passed

# cwd apps/oshun/bff; customer-deletion lifecycle
pnpm exec vitest run \
  src/data-deletion/state-run-deletion.test.ts \
  src/data-deletion/state-durability.test.ts \
  src/data-deletion/deletion-worker.test.ts --maxWorkers=1
  3 files, 21/21 tests passed

# real Postgres recovery, adjacent-subject isolation, and signed-profile erasure
OSHUN_ADMIN_DATABASE_URL=postgresql://oshun:<redacted>@127.0.0.1:5432/oshun_dev \
  pnpm exec vitest run -c apps/oshun/bff/vitest.integration.config.ts \
    apps/oshun/bff/src/messaging-channels/channel-bindings-durability.integration.spec.ts \
    --maxWorkers=1
  1 file, 1/1 test passed

# repository root; final exact BFF zero-backlog type ratchet
node tools/typecheck/ratchet.mjs --app apps/oshun/bff \
  --tsconfig tsconfig.typecheck.json
  no new app-own type errors; backlog 0

# repository root; all ten changed production/test sources
pnpm exec eslint --no-warn-ignored <changed-source-files>
  passed; only repository Nx-project-graph availability warnings

# cwd apps/oshun/bff; exact production entry bundle
pnpm exec esbuild src/server.ts --bundle --platform=node --format=esm \
  --target=node22 --outfile=dist/server.js --sourcemap
  passed; 31.9 MB server bundle and 75.5 MB source map

authoring-time conventions ratchet, staged stub scan, pre-commit
ESLint/Prettier, V5 docs validation, and git diff --check
  passed; no convention-baseline expansion attributable to this slice

Binding request, confirmation, and step-up unbind operations share an ordered whole-store mutation stream. Each operation builds a detached candidate, awaits its snapshot save, and publishes only after that save succeeds. Route tests force failures before each acknowledgement boundary: a failed request does not expose a new address, a failed wrong-code confirmation does not burn an attempt, and a failed unbind does not revoke a verified binding. Routes return controlled 503s, missing bound snapshots are authoritative empty state, and production rejects legacy synchronous mutation or a missing required sink.

The complete snapshot carries binding metadata, salted pending-code hashes, per-subject revisions, and durable deletion fences. Register-before-delete ends erased; delete-before-register rejects the stale request with 409. A failed delete neither erases nor fences the subject, so retry remains honest. Deletion survives restart, preserves an adjacent member, and refuses resurrection after a second hydration.

The signed profile eraser now count-validates consumer profiles, customer-auth profiles, notification preferences, and channel bindings as four independent partitions; a malformed count or partial failure rejects the aggregate receipt. Profile DSAR exports address, status, verification and expiry metadata, attempts, and revision while deliberately excluding the salted verification codeHash. After composed erasure the section is empty. Mapping the partition to profile binds it to the existing profile retention and deletion policy rather than inventing another artifact category.

The final BFF ratchet ran alone after the repository resource gate and was polled within 30 seconds. It peaked near 5.17 GiB TypeScript RSS while about 6.1 GiB remained available. The source commit used SKIP_TYPECHECK=1 only after the exact supervised ratchet passed; all other hook phases passed. origin/main advanced with unrelated Aphrodite and Hathor files and pnpm-lock.yaml. The ten-file source patch rebased without overlap, the protected user lockfile was restored from preservation stash 2e9ab1b268938f66e56394b339a109a921fa7223, and the rebased SHA above was pushed to exact remote parity. The preservation stash remains intact.

No rendered UI, mobile flow, schema migration, model/provider generation call, Unreal content, production deletion request, or signed production receipt changed in this slice, so Playwright/mobile, migration, provider, Unreal, and production-operations automation were inapplicable.

Per-user Telegram durability verification#

Implementation source and published tip 6262e3a94e09aded2f2b5ead93d035366a7fc2e1 closes the per-user Telegram state partition discovered by the continuing operational-store inventory. Verification completed on 2026-07-17 UTC on dev-server, Linux 6.8.0-110-generic x86_64, with Node 24.14.1, pnpm 10.25.0, TypeScript 6.0.3, Vitest 4.1.7, and ESLint 10.4.0. The protected user pnpm-lock.yaml remained byte-identical at Git blob a37431842e330b3a06b030947c25bebdc72bc2b1.

text
# cwd apps/oshun/bff; store, effects, route, signed composers, and DSAR
pnpm exec vitest run \
  src/telegram/user-state-durability.spec.ts \
  src/telegram/effects-adapter.test.ts \
  src/__tests__/telegram-route.test.ts \
  src/routes/telegram-captures-route.test.ts \
  src/data-deletion/profile-state-eraser.test.ts \
  src/data-deletion/saved-claim-passage-eraser.test.ts \
  src/data-export/bundle-builder.test.ts --maxWorkers=1
  7 files, 58/58 tests passed

# cwd apps/oshun/bff; connected webhook, notification, and profile consumers
pnpm exec vitest run \
  src/telegram/webhook.test.ts \
  src/__tests__/notifications-preferences-route.test.ts \
  src/__tests__/profile-route.test.ts --maxWorkers=1
  3 files, 18/18 tests passed

# cwd apps/oshun/bff; customer-deletion lifecycle
pnpm exec vitest run \
  src/data-deletion/state-run-deletion.test.ts \
  src/data-deletion/state-durability.test.ts \
  src/data-deletion/deletion-worker.test.ts --maxWorkers=1
  3 files, 21/21 tests passed

# real Postgres recovery, adjacent-subject isolation, and both signed erasers
OSHUN_ADMIN_DATABASE_URL=postgresql://oshun:<redacted>@127.0.0.1:5432/oshun_dev \
  pnpm exec vitest run -c apps/oshun/bff/vitest.integration.config.ts \
    apps/oshun/bff/src/telegram/user-state-durability.integration.spec.ts \
    --maxWorkers=1
  1 file, 1/1 test passed

# repository root; final exact BFF zero-backlog type ratchet
node tools/typecheck/ratchet.mjs --app apps/oshun/bff \
  --tsconfig tsconfig.typecheck.json
  no new app-own type errors; backlog 0

# repository root; all fourteen changed production/test sources
pnpm exec eslint --no-warn-ignored <changed-source-files>
  passed; only repository Nx-project-graph availability warnings

# cwd apps/oshun/bff; exact production entry bundle
pnpm exec esbuild src/server.ts --bundle --platform=node --format=esm \
  --target=node22 --outfile=dist/server.js --sourcemap
  passed; 32.0 MB server bundle and 75.5 MB source map

authoring-time conventions ratchet, staged stub scan, pre-commit
ESLint/Prettier, V5 docs validation, and git diff --check
  passed; no convention-baseline expansion attributable to this slice

Every Telegram-owned write now uses one globally ordered whole-store candidate/save/publish stream. Bot /save, inline and callback capture, delivery stop, voice toggle, unlink, authenticated link mint/refresh, login binding, and webhook nonce completion acknowledge only committed state. The quiet-hours effect now awaits the independently durable notification preference store as well. Forced failures return controlled 503s without publishing a capture or link, changing a preference, or claiming bot success. Production rejects legacy synchronous mutation and a missing required sink.

The snapshot carries complete capture provenance and raw pending-link material, plus separate saved-content/profile revisions and exact-subject deletion fences. The raw nonce is retained only because pending link completion requires it; customer export substitutes a stable SHA-256 fingerprint. Selective capture erasure preserves link/preferences, selective profile erasure preserves captures, and both preserve adjacent subjects. Failed deletion neither clears memory nor installs a false fence. Create-before-delete ends erased, delete-before-create rejects, and both fences survive real PostgreSQL restart.

Telegram captures compose into the signed saved_claim_passage service while the identity link and voice/delivery preferences compose into signed profile. Each composer validates the Telegram partition count independently and rejects partial or malformed results. DSAR exports complete note/link content, provenance, timestamps, link status, Telegram identity/label, expiry and link/revocation timestamps, preference flags, and revisions; it excludes the raw nonce and becomes empty for each exact erased category while the adjacent subject remains populated.

The final BFF ratchet ran alone after the repository resource gate and was polled every 15–20 seconds. It peaked at 5.37 GiB TypeScript RSS while about 5.8 GiB remained available. The source commit used SKIP_TYPECHECK=1 only after the exact supervised ratchet passed; all other hook phases passed. origin/main advanced with three unrelated build/Hathor/shared commits and no source-file overlap. The fourteen-file patch rebased cleanly, the protected user lockfile was restored from preservation stash 00b6cf8600a6101d0627e9d5532eb617ed8c1620, and the rebased SHA above was pushed to exact remote parity. The preservation stash remains intact.

No rendered UI, mobile flow, schema migration, model/provider generation call, Unreal content, production deletion request, or signed production receipt changed in this slice, so Playwright/mobile, migration, provider, Unreal, and production-operations automation were inapplicable.

Celestial ritual-schedule durability verification#

Implementation source and published tip 844ee060a65e29a55ea6028959c2763bbdff621c closes the celestial ritual-schedule partition discovered by the continuing operational-store inventory. Verification completed on 2026-07-17 UTC on dev-server, Linux 6.8.0-110-generic x86_64, with Node 24.14.1, pnpm 10.25.0, TypeScript 6.0.3, Vitest 4.1.7, and ESLint 10.4.0. The protected user pnpm-lock.yaml remained byte-identical at Git blob a37431842e330b3a06b030947c25bebdc72bc2b1.

text
# cwd apps/oshun/bff; durable store, route, DSAR, and signed continuity eraser
pnpm exec vitest run \
  src/delight/celestial-ritual-schedule-durability.spec.ts \
  src/routes/nyx-celestial-rituals.test.ts \
  src/data-export/bundle-builder.test.ts \
  src/data-deletion/continuity-state-eraser.test.ts --maxWorkers=1
  4 files, 34/34 tests passed

# real Postgres recovery, adjacent-subject isolation, and durable erasure fence
OSHUN_ADMIN_DATABASE_URL=postgresql://oshun:<redacted>@127.0.0.1:5432/oshun_dev \
  pnpm exec vitest run -c apps/oshun/bff/vitest.integration.config.ts \
    apps/oshun/bff/src/delight/celestial-ritual-schedule-durability.integration.spec.ts \
    --maxWorkers=1
  1 file, 1/1 test passed

# cwd apps/oshun/bff; final post-rebase customer-deletion lifecycle regression
pnpm exec vitest run \
  src/data-deletion/state-run-deletion.test.ts \
  src/data-deletion/state-durability.test.ts \
  src/data-deletion/deletion-worker.test.ts --maxWorkers=1
  3 files, 21/21 tests passed

# repository root; final post-rebase exact BFF zero-backlog type ratchet
node tools/typecheck/ratchet.mjs --app apps/oshun/bff \
  --tsconfig tsconfig.typecheck.json
  no new app-own type errors; backlog 0

# repository root; all eight changed production/test sources
pnpm exec eslint <changed-source-files>
  passed with no errors; only repository Nx-project-graph and ignored-test warnings
pnpm exec prettier --check <changed-source-files>
  passed

# cwd apps/oshun/bff; exact production entry bundle
pnpm exec esbuild src/server.ts --bundle --platform=node --format=esm \
  --target=node22 --outfile=dist/server.js --sourcemap
  passed; 32.0 MB server bundle and 75.5 MB source map

authoring-time conventions ratchet, staged stub scan, pre-commit
ESLint/Prettier, V5 docs validation, and git diff --check
  passed; no convention-baseline expansion attributable to this slice

Accepted astronomical triggers now acknowledge only a committed snapshot. The production route cannot use the legacy synchronous mutator, and a missing or failed required sink returns controlled 503 without changing live or restart-restored state. Deduplication remains member-scoped and preserves the route's existing trigger accounting.

The durable snapshot includes complete ritual records, per-subject revisions, and deletion fences. Schedule-before-delete ends erased; delete-before-schedule rejects the stale write; a failed delete neither erases nor installs a false fence. Restart restores the last committed schedules and fences, and exact deletion preserves an adjacent member.

Celestial schedules compose into signed continuity_state as the independent celestial_ritual_schedule partition. Its eraser is count-validated with the other continuity partitions, while DSAR exports revision, provenance, timing, occasion, quiet-hours displacement, acceptance time, and ownership metadata. The exact subject's section is empty after erasure and the adjacent member's section remains populated.

The final post-rebase BFF ratchet ran alone after the repository resource gate and was polled every 20–30 seconds. It peaked near 5.64 GiB TypeScript RSS while about 5.9 GiB remained available. The source commit used SKIP_TYPECHECK=1 only after the exact supervised pre-commit ratchet passed; all other hook phases passed. origin/main then advanced with a large unrelated merge. The remote delta had no path intersection with the eight-file celestial patch, so the source commit rebased cleanly. The protected lockfile was restored from preservation stash 087894ea78fe27d86769298c26bb1291647e82b7, and the rebased SHA above reached exact remote parity. The preservation stash remains intact.

No rendered UI, mobile flow, schema migration, model/provider generation call, Unreal content, production deletion request, or signed production receipt changed in this slice, so Playwright/mobile, migration, provider, Unreal, and production-operations automation were inapplicable.

Wearable-health durability and external-effect recovery verification#

Implementation source and published tip 0656aabd9b7a3b57588f897be492a8b9c49a3b7a closes the durability, recovery, and signed-erasure composition of the BFF wearable-health partition discovered by the continuing operational-store inventory. Verification completed on 2026-07-17 UTC on dev-server, Linux 6.8.0-110-generic x86_64, with Node 24.14.1, pnpm 10.25.0, TypeScript 6.0.3, Vitest 4.1.7, and ESLint 10.4.0. The protected user pnpm-lock.yaml remained byte-identical at Git blob a37431842e330b3a06b030947c25bebdc72bc2b1.

text
# repository root; platform mapping and stable operation-ID bridge contract
pnpm exec vitest run -c libs/oshun/shell-wearable/vitest.config.ts \
  libs/oshun/shell-wearable/src/__tests__/health-sessions.test.ts \
  --maxWorkers=1
  1 file, 12/12 tests passed

# cwd libs/oshun/shell-wearable; direct package typecheck
pnpm exec tsc --noEmit
  passed

# cwd apps/oshun/bff; store, route, eraser, DSAR, and deletion-lifecycle sweep
pnpm exec vitest run \
  src/delight/wearable-health-durability.spec.ts \
  src/routes/wearable-health.test.ts \
  src/data-deletion/v1-record-erasers.test.ts \
  src/data-export/bundle-builder.test.ts \
  src/__tests__/data-export-route.test.ts \
  src/data-deletion/state-run-deletion.test.ts \
  src/data-deletion/state-durability.test.ts \
  src/data-deletion/deletion-worker.test.ts --maxWorkers=1
  8 files, 79/79 tests passed

# cwd apps/oshun/bff; final store/route/DSAR regression after coverage-gap proof
pnpm exec vitest run \
  src/delight/wearable-health-durability.spec.ts \
  src/routes/wearable-health.test.ts \
  src/data-export/bundle-builder.test.ts --maxWorkers=1
  3 files, 33/33 tests passed

# repository root; real Postgres restart, external deletion, and durable fence
OSHUN_ADMIN_DATABASE_URL=postgresql://oshun:<redacted>@127.0.0.1:5432/oshun_dev \
  pnpm exec vitest run -c apps/oshun/bff/vitest.integration.config.ts \
    apps/oshun/bff/src/delight/wearable-health-durability.integration.spec.ts \
    --maxWorkers=1
  1 file, 1/1 test passed

# repository root; targeted shell package build
pnpm nx run @oshun/shell-wearable:build --parallel=1
  passed

# repository root; exact BFF zero-backlog type ratchet
node tools/typecheck/ratchet.mjs --app apps/oshun/bff \
  --tsconfig tsconfig.typecheck.json
  no new app-own type errors; backlog 0

# repository root; all 13 changed production/test sources
pnpm exec eslint <changed-source-files> --no-warn-ignored
  passed with no errors or warnings
pnpm exec prettier --check <changed-source-files>
  passed

# cwd apps/oshun/bff; exact production entry bundle
pnpm exec esbuild src/server.ts --bundle --platform=node --format=esm \
  --target=node22 --outfile=dist/server.js --sourcemap
  passed; 32.0 MB server bundle and 75.6 MB source map

git diff --check, staged path audit, protected-lock hash, and pre-commit hooks
  passed

Each new session first commits a durable pending intent containing the exact mapped HealthKit and Google Fit records and stable, caller-owned operation IDs. Only then may the bridges run. Complete, partial, and acknowledgement-lost outcomes are persisted without discarding the identities needed for recovery. A same-session retry returns a completed delivery without another provider call; a partial retry invokes only the unfinished platform; an acknowledgement-lost retry reuses the same IDs so a conforming bridge can reconcile idempotently. The route returns 503 if the pre-effect intent cannot commit, 502 with a recovery ID for a partial provider failure, 503 with a recovery ID if the post-effect outcome cannot commit, and 409 when an erased subject attempts stale recreation. HRV analysis likewise publishes only after its ordered snapshot succeeds.

Exact-subject erasure requires deleted or not_found confirmation for every complete or pending platform attempt before it removes local sessions, attempts, and operation/provider identities and commits a resurrection fence. A missing required snapshot sink prevents provider deletion; a missing bridge, provider failure, or invalid partition count fails the signed receipt and retains retry evidence. When the canonical V1 database is configured, the ritual_completion eraser runs wearable provider deletion first and then deletes Tara ritual sessions and sitting-completion events atomically. When that database is absent, the entire canonical eraser remains omitted and the fanout fails closed rather than signing a false absence.

At this source boundary, the default ritual_completion DSAR collector exported the durable wearable partition, including provider/operation identity and recovery state, and added an explicit canonical_v1_ritual_completion coverage gap because it did not query the V1 database. The canonical DSAR implementation documented below supersedes that read gap when OSHUN_V1_DATABASE_URL is configured; an unconfigured deployment retains it. Tests prove exact deletion, adjacent-subject isolation, both write/delete race orderings, failed-save rollback, partial retry, restart recovery, and the persisted erasure fence against real Postgres.

This source slice does not establish live HealthKit or Google Fit operation. The shell contract now requires stable operation-ID binding and idempotent deletion, but the repository contains no production adapter that calls configureBridge. Consequently, the production route remains fail-closed with 503 and no fabricated platform write, and any signed deletion with retained wearable identities fails until a deletable bridge is injected. Real provider write/reconcile/delete receipts and platform automation remain part of the open provider-native work.

The final BFF ratchet ran alone after the repository resource gate and was polled within the required 30-second interval. It peaked near 5.35 GiB TypeScript RSS while roughly 6.0 GiB remained available. The source commit used SKIP_TYPECHECK=1 only after that exact supervised ratchet passed; all other hook phases passed. origin/main then advanced through five unrelated commits, including a large app relocation. Their 598-file delta had no path intersection with the 13-file wearable patch, so the source commit rebased without conflict. The protected lockfile was restored from preservation stash b11c0ae1cae49c0534f3389f51820f1078f5eca3, and the rebased SHA above reached exact remote parity. The preservation stash remains intact.

No rendered UI, mobile flow, schema migration, live provider credential, Unreal content, production deletion request, or signed production receipt changed in this slice, so Playwright/mobile, migration, live-provider, Unreal, and production-operations automation were inapplicable. The absent production bridge is an explicitly open product gap, not a test waiver or closure claim.

Morning-capture journal durability verification#

Implementation source and published tip 989ce593373199adf3e752e1da89f59089a66e3c closes the BFF morning-capture partition discovered by the continuing operational-store inventory. Verification completed on 2026-07-17 UTC on dev-server, Linux 6.8.0-110-generic x86_64, with Node 24.14.1, pnpm 10.25.0, TypeScript 6.0.3, Vitest 4.1.7, and ESLint 10.4.0. The protected user pnpm-lock.yaml remained byte-identical at Git blob a37431842e330b3a06b030947c25bebdc72bc2b1.

text
# cwd apps/oshun/bff; focused store, route, signed eraser, and DSAR proof
pnpm exec vitest run \
  src/delight/morning-capture-durability.spec.ts \
  src/routes/arete-morning-capture.test.ts \
  src/data-deletion/v1-record-erasers.test.ts \
  src/data-export/bundle-builder.test.ts --maxWorkers=1
  4 files, 42/42 tests passed

# repository root; real Postgres restart, adjacent isolation, and durable fence
OSHUN_ADMIN_DATABASE_URL=postgresql://oshun:<redacted>@127.0.0.1:5432/oshun_dev \
  pnpm exec vitest run -c apps/oshun/bff/vitest.integration.config.ts \
    apps/oshun/bff/src/delight/morning-capture-durability.integration.spec.ts \
    --maxWorkers=1
  1 file, 1/1 test passed

# cwd apps/oshun/bff; final export/deletion lifecycle regression
pnpm exec vitest run \
  src/delight/morning-capture-durability.spec.ts \
  src/routes/arete-morning-capture.test.ts \
  src/data-deletion/v1-record-erasers.test.ts \
  src/data-export/bundle-builder.test.ts \
  src/__tests__/data-export-route.test.ts \
  src/data-deletion/state-run-deletion.test.ts \
  src/data-deletion/state-durability.test.ts \
  src/data-deletion/deletion-worker.test.ts --maxWorkers=1
  8 files, 78/78 tests passed

# repository root; exact BFF zero-backlog type ratchet
node tools/typecheck/ratchet.mjs --app apps/oshun/bff \
  --tsconfig tsconfig.typecheck.json
  no new app-own type errors; backlog 0

# repository root; all 10 changed production/test sources
pnpm exec eslint <changed-source-files> --no-warn-ignored
  passed with no errors or warnings
pnpm exec prettier --check <changed-source-files>
  passed

# cwd apps/oshun/bff; exact production entry bundle
pnpm exec esbuild src/server.ts --bundle --platform=node --format=esm \
  --target=node22 --outfile=dist/server.js --sourcemap
  passed; 32.0 MB server bundle and 75.6 MB source map

production synchronous-mutator search, git diff --check, staged path audit,
protected-lock hash, conventions ratchet, and pre-commit hooks
  passed; no production `morningCaptureStore.submit(...)` call remains

The POST route now awaits a globally ordered candidate/save/publish mutation. The candidate contains the domain-normalized capture, waking mood, optional dream note, body state, crisis flag, authenticated owner, UTC day, and receipt time. A failed or missing required snapshot returns 503 without changing the live or restart-restored view. Same-day replacement remains latest-wins but increments the subject revision only after persistence commits; invalid domain input remains the existing typed 422 and does not create a candidate. Production requires the durable store and rejects the legacy synchronous test seam.

Exact-subject deletion removes every capture and its revision and commits a durable resurrection fence. Submit-before-delete ends erased; delete-before-submit rejects the stale request with 409. A failed delete leaves the old records visible and does not install a false fence. Restart proof against real Postgres recovers acknowledged captures, retains the fence, and preserves the adjacent subject.

The signed journal_entry eraser now count-validates morning_capture before deleting the canonical Arete journal rows. If the local erasure succeeds but the database delete fails, retry is safe: the local fence remains, its idempotent count becomes zero, and the signed operation remains failed until the canonical delete succeeds. As before, an unconfigured V1 database omits the complete canonical eraser so the fanout cannot fabricate completion.

At this source boundary, the default journal_entry DSAR collector exported the full BFF capture record and revision, then explicitly reported canonical_v1_journal_entry as a coverage gap because it did not query the V1 database. The canonical DSAR implementation documented below supersedes that read gap when OSHUN_V1_DATABASE_URL is configured; an unconfigured deployment retains it. Exact deletion empties the subject's local partition, and an adjacent member's section remains populated.

The accompanying delight-store inventory found no non-test mutation caller for the SkyTonightStore seed/record methods, ActivitySummariesStore.seedSummaries, or any PrivacyRecordsStore.record*/setAuditCoverage method. Their production routes currently read fixture-fed seams only; wiring and reads do not make an absent producer an operational write path. They therefore require no acknowledgement-bound mutation retrofit in this slice. This is a scoped disposition, not a permanent exemption: adding a production producer must first provide the same durability, deletion, DSAR, and race proof, and the repository-wide inventory remains open.

The final BFF ratchet ran alone after the required RAM/disk/process gate and was polled within 30 seconds. TypeScript peaked near 5.71 GiB RSS while available memory remained above 6.2 GiB; 31 GiB of swap was configured. The source commit used SKIP_TYPECHECK=1 only after that exact supervised ratchet passed; all other hook phases passed. The source commit advanced origin/main directly from d2611f1b573f921a1facb841e70e837a93de1ced to the SHA above and reached exact remote parity without a rebase.

No rendered UI, mobile flow, schema migration, external provider effect, Unreal content, production deletion request, or signed production receipt changed in this slice, so Playwright/mobile, migration, provider, Unreal, and production-operations automation were inapplicable.

Customer data-export durability verification#

Implementation source f50976ba40460ecdc6b413f9e9ff1a57a1b5f50e, published through integration tip 25b510fbe0701062b54c88caef88146e957b81ef, closes the customer data-export request-metadata and exact bundle-byte partitions found by the continuing operational-store inventory. Verification completed on 2026-07-17 UTC on dev-server, Linux 6.8.0-110-generic x86_64, with Node 24.14.1, pnpm 10.25.0, TypeScript 6.0.3, Vitest 4.1.7, and ESLint 10.4.0. The protected user pnpm-lock.yaml remained byte-identical at Git blob a37431842e330b3a06b030947c25bebdc72bc2b1.

text
# cwd apps/oshun/bff; broad store, route, export, eraser, and deletion sweep
pnpm exec vitest run \
  src/data-export/state.test.ts \
  src/data-export/bundle-store.spec.ts \
  src/data-export/bundle-builder.test.ts \
  src/generation/generated-artifact-erasure.test.ts \
  src/generation/output-catalog.test.ts \
  src/__tests__/data-export-route.test.ts \
  src/data-deletion/state-run-deletion.test.ts \
  src/data-deletion/state-durability.test.ts \
  src/data-deletion/deletion-worker.test.ts --maxWorkers=1
  9 files, 94/94 tests passed

# cwd apps/oshun/bff; cross-endpoint account export/deletion lifecycle
pnpm exec vitest run \
  src/__tests__/export-deletion-flows.integration.test.ts --maxWorkers=1
  1 file, 14/14 tests passed

# repository root; real Postgres exact-byte restart, expiry, and fence proof
OSHUN_ADMIN_DATABASE_URL=postgresql://oshun:<redacted>@127.0.0.1:5432/oshun_dev \
  pnpm exec vitest run -c apps/oshun/bff/vitest.integration.config.ts \
    apps/oshun/bff/src/data-export/customer-data-export-durability.integration.spec.ts \
    --maxWorkers=1
  1 file, 1/1 test passed twice

# repository root; exact BFF zero-backlog type ratchet after all source changes
node tools/typecheck/ratchet.mjs --app apps/oshun/bff \
  --tsconfig tsconfig.typecheck.json
  no new app-own type errors; backlog 0

# repository root; all 13 changed production/test sources
pnpm exec eslint <changed-source-files> --no-warn-ignored
  passed with no errors or warnings
pnpm exec prettier --check <changed-source-files>
  passed

# cwd apps/oshun/bff; exact production entry bundle
pnpm exec esbuild src/server.ts --bundle --platform=node --format=esm \
  --target=node22 --outfile=dist/server.js --sourcemap
  passed; 32.0 MB server bundle and 75.6 MB source map

production synchronous-mutator search, git diff --check, staged path audit,
protected-lock hash, conventions ratchet, and pre-commit hooks
  passed; production data-export mutations await their durable boundary

CustomerDataExportStateStore now stages, saves, and only then publishes each request transition through one ordered mutation tail. Production requires its snapshot sink. Request creation, completion, failure, cancellation, and read-triggered expiry use their durable variants; a missing or failed write returns 503 without acknowledging a live-only state. The durable snapshot keeps the complete request history and a monotonic request-ID high-water mark, rejects invalid restored sequences, and does not confuse the public 50-row listing cap with record retention. The DSAR consent_record section includes the full request metadata but deliberately excludes bundle bytes.

ExportBundleStore persists the exact generated bytes as base64 together with owner, content type, creation, and expiry metadata. A request is downloadable only after both the bundle commit and completed-state commit; a completion-save failure removes the staged bundle, and pending or orphaned bytes are never served. Restart restores byte-for-byte content. Bundles expire after 14 days, including a bounded migration for legacy snapshots, and expiry purging removes the durable record before reporting success. Cancellation commits request state and removes its bundle with an idempotent cleanup path for a prior byte-removal failure.

The bundle partition is a short-lived generated_artifact, not retained compliance metadata. The signed generated-artifact eraser includes the count-validated customer_export_bundles partition, exact-subject deletion, and a durable resurrection fence. Tests cover adjacent-subject isolation, submit/delete in both race orderings, failed saves, restart, exact bytes, expiry, and the persisted fence against real Postgres. Customer export request metadata is instead classified as nondeletable compliance consent_record history: account erasure does not silently destroy the audit record, while DSAR continues to expose it to the authenticated subject.

This slice does not implement the final retention executor for export-request metadata. In particular, it does not yet enforce the intended seven-year purge with retention exceptions and legal-hold awareness. That limitation, the wider store inventory, and provider-native remote deletion keep the all-store durability/privacy checkbox open; durable retention is not claimed as complete retention governance.

The final BFF ratchet ran alone after the required resource gate and was polled within 30 seconds. TypeScript peaked near 5.35 GiB RSS while about 6.0 GiB remained available; 31 GiB of swap was configured. The cross-endpoint integration emitted non-fatal warnings for pre-existing absent generated source maps, but all 14 assertions passed. The source commit used SKIP_TYPECHECK=1 only after the exact supervised ratchet passed; every other hook phase passed. After its first successful push, origin/main advanced through unrelated Yemaya documentation. The remote delta had no path intersection with the 13-file source patch, and the branch integrated cleanly through the published tip above. The protected lockfile was restored from named preservation stashes, which remain intact.

No rendered UI, mobile flow, schema migration, external provider effect, Unreal content, production deletion request, or signed production receipt changed in this slice, so Playwright/mobile, migration, provider, Unreal, and production-operations automation were inapplicable.

Implementation source and published tip 58c932258048f74f1c40cdf97e7a0c2a5380a79a closes the canonical customer- consent operational partition found by the continuing store inventory. Verification completed on 2026-07-17 UTC on dev-server, Linux 6.8.0-110-generic x86_64, with Node 24.14.1, pnpm 10.25.0, TypeScript 6.0.3, Vitest 4.1.7, and ESLint 10.4.0. The protected user pnpm-lock.yaml remained byte-identical at Git blob a37431842e330b3a06b030947c25bebdc72bc2b1.

text
# cwd apps/oshun/bff; canonical store plus every affected request surface
pnpm exec vitest run \
  src/consent/state-durability.spec.ts \
  src/__tests__/consent-route.test.ts \
  src/__tests__/residency-routing.test.ts \
  src/routes/personas-consumer.test.ts \
  src/__tests__/mentor-presence-route.test.ts \
  src/data-export/bundle-builder.test.ts \
  src/__tests__/data-export-route.test.ts --maxWorkers=1
  7 files, 101/101 tests passed

# cwd apps/oshun/bff; cross-endpoint grant/revoke/audit behavior
pnpm exec vitest run --config vitest.integration.config.ts \
  src/__tests__/consent-grant-revoke-audit.integration.test.ts \
  --maxWorkers=1
  1 file, 11/11 tests passed

# cwd apps/oshun/bff; real Postgres restart and sequence proof
OSHUN_ADMIN_DATABASE_URL=postgresql://oshun:<redacted>@127.0.0.1:5432/oshun_dev \
  pnpm exec vitest run --config vitest.integration.config.ts \
    src/consent/state-durability.integration.spec.ts --maxWorkers=1
  1 file, 1/1 test passed

# repository root; shared asynchronous residency resolver
pnpm exec tsc -p libs/shared/bff-kit/tsconfig.lib.json \
  --noEmit --pretty false
  passed

# repository root; exact BFF zero-backlog type ratchet after all source changes
node tools/typecheck/ratchet.mjs --app apps/oshun/bff \
  --tsconfig tsconfig.typecheck.json
  no new app-own type errors; backlog 0

# repository root; all 17 changed production/test sources
pnpm exec eslint <changed-source-files>
  passed with 0 errors; repository ignore policy reported 8 ignored-test warnings
pre-commit eslint --fix --no-warn-ignored <17 staged source files>
  passed
pnpm exec prettier --check <changed-source-files>
  passed; all 17 files use Prettier style

# cwd apps/oshun/bff; exact production entry bundle
pnpm exec esbuild src/server.ts --bundle --platform=node --format=esm \
  --target=node22 --outfile=dist/server.js --sourcemap
  passed in 8.436 seconds; 32.0 MB server bundle and 75.6 MB source map

production synchronous-consent call search, git diff --check, staged path
audit, protected-lock hash, conventions ratchet, and pre-commit hooks
  passed; no production caller bypasses the awaited durable boundary

CustomerConsentStateStore now treats its map as a live projection of one deploy-bound durable snapshot. Server boot requires the sink in deployable environments, restores it before accepting traffic, and rejects incomplete, duplicate-flow, non-monotonic-ID, malformed timestamp, and taxonomy-invalid snapshots. The snapshot retains the canonical current state for every flow, the complete internal history, exact decision evidence and verification evidence, policy version, selected target, revision, and monotonic global ID sequence. Restore advances that sequence above every retained identifier so a restart cannot reuse an evidence or history ID.

Every asynchronous mutation is globally ordered and follows candidate -> save -> publish. A failed first-read default, grant, withdrawal, revocation, renewal, policy update, or read-time expiry leaves the live view at the last acknowledged snapshot and does not poison a later retry. Concurrent decisions cannot observe an uncommitted candidate or overwrite one another. Deployable synchronous reads and mutations fail instead of silently consulting restart-resettable memory; all production call sites use their durable variants.

The soft-opt-in reconciliation seed no longer fabricates an onboarding-banner acceptance. It records no subject-action evidence, labels the history entry as system_reconciliation, and explains that the state came from the policy default. Explicit grants and renewals retain their exact canonical collection, verification, evidence, permission, and target vocabulary. Public audit output remains capped at the documented 200 rows, but that presentation cap no longer truncates the durable compliance record or its totals. Tests retain more than 200 decisions and prove DSAR still receives the complete history and evidence.

Consent HTTP reads and writes now await persistence; a missing or failed sink returns controlled 503 customer_consent_persistence_unavailable without acknowledging live-only state. Customer export first commits a durable consent read before creating request metadata, and its consent_record section exports every current flow plus the full retained decision history. Persona eligibility and mentor analytics likewise return 503 rather than acting on unavailable consent. Cross-region residency routing resolves consent asynchronously and fails closed to the authenticated subject's home data plane when durable evidence cannot be read; it does not create fallback consent state.

The real-Postgres test restarts a fresh store over the production snapshot adapter and proves exact evidence recovery, durable read-time expiry, adjacent-subject isolation, and collision-safe ID continuation. Unit races prove ordered writes, no pre-save visibility, failed-save rollback, idempotent retry, single-commit lazy seed/expiry under concurrency, and rejection of corrupted authority vocabulary. Route tests prove that failed consent persistence creates neither an export request nor a persona/analytics/residency side effect.

Canonical consent evidence is classified as compliance-retained consent_record, so this slice deliberately does not attach account-deletion fences or an eraser that would destroy the audit record. It does not close retention governance: the repository still lacks the intended seven-year purge executor with legal-hold and retention-exception evaluation. That honest gap, the wider operational-store inventory, and provider-native remote deletion keep the all-store durability/privacy checkbox open.

The final BFF ratchet ran alone after the required RAM/swap/disk/process gate and was polled within 30 seconds. TypeScript's observed RSS reached about 4.90 GiB; available RAM stayed at or above 6.1 GiB, and 31 GiB of swap was configured. The cross-endpoint integration emitted non-fatal warnings for pre-existing absent generated source maps, but all 11 assertions passed. The source commit used SKIP_TYPECHECK=1 only after the exact supervised ratchet passed; every other hook phase passed. Its first push was rejected because origin/main had moved. The fetched delta touched only Hathor/Yemaya, CI, and the regenerated lockfile, with no consent-patch path intersection. Rebase and republish completed cleanly, the protected lock was restored from a named preservation stash, and local HEAD, origin/main, and the live remote branch all reached exact source-tip parity.

No rendered UI, mobile flow, schema migration, external provider effect, Unreal content, production deletion request, or signed production receipt changed in this slice, so Playwright/mobile, migration, provider, Unreal, and production-operations automation were inapplicable.

Billing and Fiat Stripe durability verification#

Implementation source and published tip e390bf2c0a8565cec2f044c190c71ef27162a2bd closes the BFF-owned customer- billing and Fiat Stripe operational partitions found by the continuing store inventory. Verification completed on 2026-07-17 UTC on dev-server, Linux 6.8.0-110-generic x86_64, with Node 24.14.1, pnpm 10.25.0, TypeScript 6.0.3, Vitest 4.1.7, and ESLint 10.4.0. The protected user pnpm-lock.yaml remained byte-identical at Git blob a37431842e330b3a06b030947c25bebdc72bc2b1.

text
# cwd apps/oshun/bff; complete affected store/route/export/erasure suite
pnpm exec vitest run \
  src/billing-support/billing-store-durability.spec.ts \
  src/routes/billing-app-store-route.test.ts \
  src/routes/billing-cancel-flow-route.test.ts \
  src/routes/billing-family-route.test.ts \
  src/routes/billing-scholar-verification-route.test.ts \
  src/routes/billing-trials-route.test.ts \
  src/middleware/entitlements.test.ts \
  src/payments/fiat-stripe-store-durability.spec.ts \
  src/payments/fiat-routes.test.ts \
  src/data-export/bundle-builder.test.ts \
  src/data-deletion/profile-state-eraser.test.ts --maxWorkers=1
  11 files, 120/120 tests passed

# cwd apps/oshun/bff; real PostgreSQL restart, redaction, and fence proof
OSHUN_V1_DATABASE_URL=postgresql://oshun:<redacted>@127.0.0.1:5432/oshun_dev \
  pnpm exec vitest run --config vitest.integration.config.ts \
    src/billing-support/billing-store-durability.integration.spec.ts \
    src/payments/fiat-stripe-store-durability.integration.spec.ts \
    --maxWorkers=1
  2 files, 2/2 tests passed

# repository root; exact BFF zero-backlog type ratchet after final source
node tools/typecheck/ratchet.mjs --app apps/oshun/bff \
  --tsconfig tsconfig.typecheck.json
  no new app-own type errors; backlog 0

# cwd apps/oshun/bff; all changed production/test sources
pnpm exec eslint <changed-source-files>
  passed with 0 errors; repository ignore policy reported 12 ignored-test warnings
pre-commit eslint --fix --no-warn-ignored <25 staged source files>
  passed
pnpm exec prettier --check <changed-source-files>
  passed; all files use Prettier style

# cwd apps/oshun/bff; exact production entry bundle
pnpm exec esbuild src/server.ts --bundle --platform=node --format=esm \
  --target=node22 --outfile=/tmp/oshun-billing-fiat-bff-server-final.js \
  --sourcemap
  passed in 8.463 seconds; 32.1 MB server bundle and 75.9 MB source map

production synchronous-mutator searches, snapshot-corruption tests,
git diff --check, staged path audit, protected-lock hash, conventions ratchet,
and pre-commit hooks
  passed; no production caller bypasses the ordered durable boundary

BillingStore now persists subscriptions, trial ownership, cancellation/save offers, churn evidence, family plans and seats, Apple and Google Play admission, scholar grants, deterministic identifier high-water state, subject-redaction fences, and the account-plan projection outbox in one ordered snapshot. Every route mutation runs candidate -> validate -> save -> publish and sends success only after the save. A missing or failed deployable sink returns controlled 503 without publishing the candidate; an already-redacted subject receives 410. Snapshot restore rejects duplicate authority, malformed identifiers and timestamps, invalid family membership, broken plan revisions, and inconsistent provider-admission records. Concurrent trials and other writes serialize so a later whole-snapshot commit cannot accidentally make a failed earlier candidate durable.

The raw Google Play purchase bearer token is never snapshotted. The store keeps only its SHA-256 lookup digest plus provider acknowledgement metadata, and the DSAR billing_receipt section proves the secret is absent. Apple transaction identities and scholar verification evidence are retained only to the degree needed for entitlement and billing compliance; scholar document references are cleared during subject redaction.

Billing is the durable entitlement authority. Each subscription decision stages a revisioned desired-plan outbox record in the same commit. Projection to the customer-auth account is retryable, startup reconciles pending records before traffic, and entitlement evaluation takes the more restrictive of the billing decision and account projection. A pending upgrade therefore cannot overgrant, while a pending downgrade fails closed immediately.

FiatStripeStore now durably retains member/customer/subscription bindings, pending checkout attribution, processed Stripe webhook identities, and the bounded payment-event feed. Provider HTTP and Apple merchant-session transports remain process configuration and never enter the snapshot. Bigints use checked decimal serialization; restore rejects malformed checkout vocabulary, unrecognized redaction pseudonyms, duplicate identities, invalid replay rows, and non-Stripe bus events. Checkout, wallet attachment, binding, event emission, and replay acknowledgement wait for this snapshot. Subscription metadata is peeked until the billing commit succeeds, so a failed billing write leaves the webhook retryable even when the Stripe price has no usable lookup key. Bus-event deduplication similarly makes a retry safe if event publication committed but processed-event acknowledgement did not.

The billing_receipt DSAR section now returns both the canonical billing record and locally retained Stripe binding/pending-checkout state. Profile deletion composes both stores into signed account-deletion fanout as redaction-only compliance partitions: direct subject identifiers are replaced by irreversible, domain-separated SHA-256 pseudonyms, stale-subject recreation is fenced across restart, and adjacent family members are preserved. This is deliberately not a claim that billing receipts are hard-deleted on account closure.

This slice does not execute provider-native Stripe customer/subscription deletion, Apple/Google receipt deletion, or a production provider effect. Those remote retention/deletion obligations must be dispositioned against provider policy and bound to a confirmed eraser where deletion is available. It also does not implement the repository-wide seven-year compliance purge with retention exceptions and legal-hold evaluation. Those gaps and the remaining operational-store inventory keep the all-store durability/privacy checkbox open.

The final BFF ratchet ran alone after the required RAM/swap/disk/process gate and was polled within 30 seconds. TypeScript peaked at about 5.0 GiB RSS while available RAM stayed above 5 GiB; 31 GiB of swap was configured. The source commit used SKIP_TYPECHECK=1 only after that exact ratchet passed; all other hooks passed. Its first push was rejected because origin/main had moved. The remote delta touched the lockfile, shared study contracts, Hathor, Aphrodite, and documentation but none of the 25 billing source paths. Rebase and republish completed cleanly, the protected lock was restored from a named preservation stash that remains intact, and local HEAD, origin/main, and the live remote branch reached exact source-tip parity.

No rendered UI, mobile flow, schema migration, production provider call, Unreal content, or signed production deletion receipt changed in this slice, so Playwright/mobile, migration, provider, Unreal, and production-operations automation were inapplicable.

Customer-feedback support-case durability verification#

Implementation source and published tip 48a0b27374fbdf12aad257c7f51e4f8e5f507c32 closes the production customer- feedback submission and operator-triage partition found by the continuing store inventory. Verification completed on 2026-07-17 UTC on dev-server, Linux 6.8.0-110-generic x86_64, with Node 24.14.1, pnpm 10.25.0, TypeScript 6.0.3, Vitest 4.1.7, and ESLint 10.4.0. The protected user pnpm-lock.yaml remained byte-identical at Git blob a37431842e330b3a06b030947c25bebdc72bc2b1.

text
# cwd apps/oshun/bff; store, route, DSAR, and profile-erasure coverage
pnpm exec vitest run \
  src/feedback/feedback-intake-store.test.ts \
  src/feedback/feedback-intake-store-durability.spec.ts \
  src/routes/feedback-route.test.ts \
  src/data-export/bundle-builder.test.ts \
  src/data-deletion/profile-state-eraser.test.ts --maxWorkers=1
  5 files, 45/45 tests passed

# cwd apps/oshun/bff; real PostgreSQL restart, triage, redaction, and fence proof
OSHUN_V1_DATABASE_URL=postgresql://oshun:<redacted>@127.0.0.1:5432/oshun_dev \
  pnpm exec vitest run --config vitest.integration.config.ts \
    src/feedback/feedback-intake-store-durability.integration.spec.ts \
    --maxWorkers=1
  1 file, 1/1 test passed

# repository root; exact BFF zero-backlog type ratchet after final source
node tools/typecheck/ratchet.mjs --app apps/oshun/bff \
  --tsconfig tsconfig.typecheck.json
  no new app-own type errors; backlog 0

# cwd apps/oshun/bff; all nine changed production/test sources
pnpm exec eslint <changed-source-files>
  passed with 0 errors; repository ignore policy reported 5 ignored-test warnings
pre-commit eslint --fix --no-warn-ignored <9 staged source files>
  passed
pnpm exec prettier --check <changed-source-files>
  passed; all files use Prettier style

# cwd apps/oshun/bff; exact production entry bundle
pnpm exec esbuild src/server.ts --bundle --platform=node --format=esm \
  --target=node22 --outfile=/tmp/oshun-feedback-bff-server-final.js \
  --sourcemap
  passed in 8.989 seconds; 32.1 MB server bundle and 76.0 MB source map

production synchronous-mutator search, git diff --check, staged path audit,
protected-lock hash, conventions ratchet, and pre-commit hooks
  passed; production submission and triage use only durable mutations

FeedbackIntakeStore now owns support-case submissions, operator triage, deterministic ID high-water state, and account-redaction fences in one ordered snapshot. Deployable startup requires and hydrates the sink before traffic. Submissions and triage follow candidate -> validate -> save -> publish; a missing or failed sink returns controlled 503 and leaves the live projection at its last acknowledged state. Concurrent submissions serialize without lost records. The authenticated subject plus mandatory bounded requestId is a durable idempotency key, so a retry after a lost response returns the original case rather than creating a duplicate. A stale deleted subject receives 410.

Restore validates the ID sequence, unique case identities, submission and triage vocabulary, timestamps, bounds, contact-consent invariant, and complete redaction shape. It migrates the legacy snapshot by normalizing formerly unbounded fields and removing any contact email stored without affirmative contact consent, then durably saves that migration before traffic. New submissions never retain a contact email unless contactConsent is true.

The canonical support_case DSAR section now exports the authenticated customer's feedback, bug reports, feature requests, trace context, contact choice, and triage resolution. Account deletion composes the store into signed profile fanout as a compliance redaction partition. It replaces direct subject, case, and request identities with domain-separated SHA-256 pseudonyms; removes customer-authored title/description, contact email and permission, route, domain, app version, trace IDs, and operator free-text notes; and retains only categorical case metadata, timestamps, triage state, and screenshot count. The fence survives restart, adjacent customers remain readable, and operator triage cannot reintroduce a note into a redacted case. Screenshot bytes are not present in this server store; only the bounded count is retained.

This partition uses the existing canonical support_case policy: redaction- only on account deletion, five-year default retention, compliance-window driver, legal-hold extension, and 30-day purge cadence. This slice does not implement the legal-hold/retention-exception-aware five-year purge executor. That global retention gap and the remaining operational-store/provider inventory keep the all-store durability/privacy checkbox open.

The final BFF ratchet ran alone after the required RAM/swap/disk/process gate and was polled within 30 seconds. TypeScript peaked near 5.0 GiB RSS while more than 5 GiB remained available; 31 GiB of swap was configured. The source commit used SKIP_TYPECHECK=1 only after that exact ratchet passed; every other hook passed. Its first push was rejected because origin/main had moved. The remote delta touched only Aphrodite live media, shared study contracts, and related documentation, with no feedback-patch path intersection. Rebase and republish completed cleanly, the protected lock was restored from a named preservation stash that remains intact, and local HEAD, origin/main, and the live remote branch reached exact source-tip parity.

No rendered UI, mobile flow, schema migration, external provider effect, Unreal content, production deletion request, or signed production receipt changed in this slice, so Playwright/mobile, migration, provider, Unreal, and production-operations automation were inapplicable.

Signup verification and abuse-authority durability verification#

Implementation source and published tip 78d1d455e24d1a559c77a0bd1ccce67cab935307 closes the production pre-account email-verification, resend-throttle, signup-velocity, and issued-challenge partition found by the continuing store inventory. Verification completed on 2026-07-17 UTC on dev-server, Linux 6.8.0-110-generic x86_64, with Node 24.14.1, pnpm 10.25.0, TypeScript 6.0.3, Vitest 4.1.7, and ESLint 10.4.0. The protected user pnpm-lock.yaml remained byte-identical at Git blob a37431842e330b3a06b030947c25bebdc72bc2b1.

text
# cwd apps/oshun/bff; durable store, routes, DSAR, and erasure composition
pnpm exec vitest run \
  src/auth-sessions/signup-verification-store-durability.spec.ts \
  src/routes/signup-verification.test.ts \
  src/routes/auth-durability-route.test.ts \
  src/data-deletion/profile-state-eraser.test.ts \
  src/data-export/bundle-builder.test.ts \
  src/auth/customer-auth-durability.test.ts --maxWorkers=1
  6 files, 60/60 tests passed

# cwd libs/oshun/auth; shared token/throttle/challenge decision contract
pnpm exec vitest run src/__tests__/signup-abuse.test.ts --maxWorkers=1
  1 file, 25/25 tests passed
pnpm exec tsc -p tsconfig.json --noEmit --pretty false
  passed

# cwd apps/oshun/bff; real PostgreSQL restart, secret minimization, and erasure
OSHUN_V1_DATABASE_URL=postgresql://oshun:<redacted>@127.0.0.1:5432/oshun_dev \
  pnpm exec vitest run --config vitest.integration.config.ts \
    src/auth-sessions/signup-verification-store-durability.integration.spec.ts \
    --maxWorkers=1
  1 file, 1/1 test passed

# repository root; exact BFF zero-backlog type ratchet after final source
node tools/typecheck/ratchet.mjs --app apps/oshun/bff \
  --tsconfig tsconfig.typecheck.json
  no new app-own type errors; backlog 0

# cwd apps/oshun/bff; changed production source
pnpm exec eslint --no-warn-ignored <changed-production-source-files>
  passed with 0 errors and 0 warnings
pre-commit eslint --fix --no-warn-ignored <15 staged TypeScript files>
  passed
pre-commit prettier --write <changed-source-and-documentation-files>
  passed; all files use Prettier style

# cwd apps/oshun/bff; exact production entry bundle
pnpm exec esbuild src/server.ts --bundle --platform=node --format=esm \
  --target=node22 \
  --outfile=/tmp/oshun-bff-signup-verification-final.mjs --sourcemap
  passed in 8.049 seconds; 32.2 MB server bundle and 76.1 MB source map

strict snapshot-corruption and wrong-secret tests, provider-configuration
absence assertions, production signup-producer coverage, git diff --check,
staged path audit, protected-lock hash, conventions ratchet, and pre-commit hooks
  passed

SignupVerificationStore now owns delivered verification-token state, in-flight delivery reservations, resend timestamps, pseudonymous network and device velocity observations, and issued challenge bindings in one ordered snapshot. Deployable startup requires a stable 32-byte-or-longer OSHUN_SIGNUP_VERIFICATION_HMAC_SECRET, verifies that secret against the stored snapshot before hydration, and purges expired state before traffic. A missing secret, missing sink, corrupt snapshot, or failed write fails closed.

Email delivery is a two-phase durable effect. The BFF first commits a single per-email reservation, derives the six-digit code from the reservation identity under the deployment HMAC secret, and supplies that identity as both the relay requestId and Idempotency-Key. Concurrent callers reuse the committed reservation. A configured provider error is treated as an ambiguous lost acknowledgement, so retry sends the same code with the same provider key. Only a provider acknowledgement moves the reservation to active token state and consumes the resend window. If that acknowledgement cannot be saved, the API returns controlled 503 and retains the retryable reservation rather than claiming success. The provably pre-effect unconfigured-provider seam cancels its reservation and does not consume a send.

Raw verification codes are never snapshotted. Network prefixes and device fingerprints are stored only as domain-separated HMAC digests; delivery and challenge provider override objects remain process configuration. Restore requires an exact schema, unique email/token/challenge identities, recognized token state, bounded identifiers, safe-integer timestamps and attempt counts, exact TTL/retention relationships, valid digest shapes, and the correct secret check. A wrong deployment secret or an injected codeDigits field is rejected before traffic.

The real /v1/auth/signup producer now records a validated signup attempt before account creation. Failure to commit that security observation returns a controlled 503 and creates no unmetered customer account. This deliberately counts accepted attempts, including an attempt that customer-auth later rejects, which is the safer abuse posture and connects the formerly test-only observation path to the real producer. Gate reads durably purge bounded state before scoring, and challenge-band responses acknowledge the issued binding before returning it.

Retention is bounded to 24 hours for verification evidence, one hour for resend timestamps, 24 hours for network/device velocity, and ten minutes for pending delivery reservations and issued challenges. The canonical session DSAR section exports the current account email's safe token, send, and challenge metadata while excluding any raw or reproducible verifier. Network/device digests are shared security observations with no retained email link and expire after 24 hours; they are not falsely attributed to an individual DSAR subject.

Full-account profile fanout deletes email-owned signup token, pending delivery, send, and challenge records before customer-auth removes the email needed to find them. The composition count-validates that partition. It deliberately does not install a permanent email fence: after deletion, an intentional anonymous signup for that address must remain possible. The globally ordered snapshot prevents an older in-flight candidate from resurrecting deleted state, while a later new reservation is an explicit new request.

The final BFF ratchet ran after each final production-source change and after the required RAM/swap/disk/process gate. It was polled within 30 seconds; TypeScript peaked near 5.5 GiB RSS while available memory remained above 5 GiB, and 31 GiB of swap was configured. The source commit used SKIP_TYPECHECK=1 only after the exact zero-backlog ratchet passed; every other hook passed. Its first push was rejected because origin/main had moved. The six incoming shared study-contract commits did not overlap any signup patch path. Rebase and republish completed cleanly, the protected lock was restored from a named preservation stash that remains intact, and local HEAD, origin/main, and the live remote branch reached exact source-tip parity.

No rendered UI, mobile flow, schema migration, live transactional-email or challenge-provider call, Unreal content, production deletion request, or signed production receipt changed in this slice. Playwright/mobile, migration, provider, Unreal, and production-operations automation were therefore inapplicable.

Member-library learning and collection-share authority durability verification#

Implementation source commit ec2be9918cfafcdeb0c42fbebd97cd538ca49a71, published to origin/main, closes the imported member-library and collection share-policy partitions found by the continuing production-store inventory. Verification completed on 2026-07-17 UTC on dev-server, Linux 6.8.0-110-generic x86_64, with Node 24.14.1, pnpm 10.25.0, TypeScript 6.0.3, Vitest 4.1.7, and ESLint 10.4.0. The protected user pnpm-lock.yaml remained byte-identical at Git blob a37431842e330b3a06b030947c25bebdc72bc2b1.

text
# cwd apps/oshun/bff; affected routes, stores, deletion, and DSAR
pnpm exec vitest run \
  src/library/member-library-store-durability.spec.ts \
  src/library/share-policy-store-durability.spec.ts \
  src/library/library-authority-routes-durability.spec.ts \
  src/data-deletion/collection-state-eraser.spec.ts \
  src/routes/library-import.test.ts \
  src/routes/library-review.test.ts \
  src/routes/library-clip.test.ts \
  src/routes/library-citations.test.ts \
  src/routes/veritas-briefing.test.ts \
  src/routes/nisaba-passage-audio.test.ts \
  src/__tests__/library-sharing-route.test.ts \
  src/data-export/bundle-builder.test.ts --maxWorkers=1
  12 files, 93/93 tests passed

# final store and DSAR assertions after adding verifier-redaction coverage
pnpm exec vitest run \
  src/data-export/bundle-builder.test.ts \
  src/library/member-library-store-durability.spec.ts \
  src/library/share-policy-store-durability.spec.ts --maxWorkers=1
  3 files, 29/29 tests passed

# real PostgreSQL restart, exact-subject deletion, and persistent fences
OSHUN_V1_DATABASE_URL=postgresql://oshun:<redacted>@127.0.0.1:5432/oshun_dev \
  pnpm exec vitest run --config vitest.integration.config.ts \
    src/library/library-authority-durability.integration.spec.ts --maxWorkers=1
  1 file, 1/1 test passed (final rerun after snapshot validation)

# repository root; exact BFF zero-backlog type ratchet
node tools/typecheck/ratchet.mjs --app apps/oshun/bff \
  --tsconfig tsconfig.typecheck.json
  no new app-own type errors; backlog 0

# cwd apps/oshun/bff; changed production source and commit hook
pnpm exec eslint <changed-production-source-files>
  passed with 0 errors
pre-commit eslint --fix --no-warn-ignored <18 staged TypeScript files>
  passed
pre-commit prettier --write <18 staged TypeScript files>
  passed; all files use Prettier style

# exact production entry bundle
pnpm exec esbuild src/server.ts --bundle --platform=node --format=esm \
  --target=node22 \
  --outfile=/tmp/oshun-bff-member-library-server.mjs --sourcemap
  passed in 9.791 seconds; 32.3 MB server bundle and 76.4 MB source map

strict snapshot-field/identity/fence/digest rejection, failed-write rollback,
concurrent mutation ordering, controlled 503 route behavior, verifier-redacted
DSAR export, exact-subject and incoming-grant erasure, adjacent-subject
preservation, git diff --check, staged path audit, protected-lock hash,
conventions ratchet, and pre-commit hooks
  passed

MemberLibraryStore now commits one ordered snapshot for imported cards and their full FSRS state, bibliographic citations, captured clips/claims/imported artifacts, followed Veritas stories, Nisaba passage collections, and mastery targets. Production import, clip, and review routes await that commit and return a controlled 503 without publishing a candidate when persistence fails. The missing-snapshot boot case is authoritative empty state, preventing volatile pre-hydration rows from surviving, and concurrent writes serialize without dropping an adjacent card or shelf.

LibrarySharePolicyStore now commits visibility, named-user grants, public profile settings, hashed link grants, revocations, and expiry metadata before a route acknowledges them. A raw share token is returned only after its digest and permission grant are durable; restart resolution uses that committed digest. Snapshot restore rejects unknown fields, duplicate identities, malformed token digests, invalid domain policy, and any live row owned by a fenced subject.

The saved_claim_passage DSAR section now includes the complete member-library record. The collection section includes owner share-policy metadata but omits token hashes because they are reusable authorization verifiers. Full-account deletion removes and fences every subject-owned member shelf, removes owned share policies, strips the deleted subject from named-user grants in adjacent owners' policies, and count-validates both stores behind the existing signed categories. Both fences survive restart and reject delayed stale writers while preserving adjacent accounts.

The final BFF ratchet ran alone after the required RAM/swap/disk/process gate and was polled within 30 seconds. TypeScript peaked near 5.3 GiB RSS while available memory remained above 5 GiB; 31 GiB of swap was configured. The source commit used SKIP_TYPECHECK=1 only after that exact ratchet passed; every other hook passed. Its first push was rejected because origin/main advanced by two Yemaya study-workspace/build commits. Those commits did not overlap any implementation path in this slice. Rebase and republish completed cleanly, the protected lock was restored from a named preservation stash that remains intact, and local HEAD, origin/main, and the live remote branch reached exact source-tip parity.

No rendered UI, mobile flow, schema migration, external share delivery, production deletion request, signed production receipt, Unreal content, or provider operation changed in this slice. Playwright/mobile, migration, provider, Unreal, and production-operations automation were inapplicable.

Recent-search learning-state durability and privacy verification#

Implementation source commit 1c456fe472216149c4fe1296cbae12b4db191165, published to origin/main, closes the authenticated recent-search partition found by the continuing production-store inventory. Verification completed on 2026-07-17 UTC on dev-server, Linux 6.8.0-110-generic x86_64, with Node 24.14.1, pnpm 10.25.0, TypeScript 6.0.3, Vitest 4.1.7, and ESLint 10.4.0. The protected user pnpm-lock.yaml remained byte-identical at Git blob a37431842e330b3a06b030947c25bebdc72bc2b1.

text
# cwd apps/oshun/bff; store, route, deletion, DSAR, and existing search suites
pnpm exec vitest run \
  src/search/recent-queries-store-durability.spec.ts \
  src/search/recent-search-route-durability.spec.ts \
  src/data-deletion/conversation-history-state-eraser.spec.ts \
  src/__tests__/recent-queries-store.test.ts \
  src/__tests__/search-route.test.ts \
  src/__tests__/search-suggestions-route.test.ts \
  src/data-export/bundle-builder.test.ts --maxWorkers=1
  7 files, 51/51 tests passed

# final adversarial snapshot assertions after explicit invalid-order coverage
pnpm exec vitest run \
  src/search/recent-queries-store-durability.spec.ts --maxWorkers=1
  1 file, 5/5 tests passed

# real PostgreSQL restart, composed erasure, adjacent-account isolation, fence
OSHUN_V1_DATABASE_URL=postgresql://oshun:<redacted>@127.0.0.1:5432/oshun_dev \
  pnpm exec vitest run --config vitest.integration.config.ts \
    src/search/recent-queries-store-durability.integration.spec.ts \
    --maxWorkers=1
  1 file, 1/1 test passed

# repository root; exact BFF zero-backlog type ratchet
node tools/typecheck/ratchet.mjs --app apps/oshun/bff \
  --tsconfig tsconfig.typecheck.json
  no new app-own type errors; backlog 0

# cwd apps/oshun/bff; changed production source and commit hook
pnpm exec eslint <changed-production-source-files>
  passed with 0 errors and 0 warnings
pre-commit eslint --fix --no-warn-ignored <14 staged TypeScript files>
  passed
pre-commit prettier --write <14 staged TypeScript files>
  passed; all files use Prettier style

# exact production entry bundle
pnpm exec esbuild src/server.ts --bundle --platform=node --format=esm \
  --target=node22 \
  --outfile=/tmp/oshun-bff-recent-search-server.mjs --sourcemap
  passed in 8.241 seconds; 32.3 MB server bundle and 76.4 MB source map

strict snapshot-field/schema/identity/fence/order/duplicate rejection,
failed-write rollback, concurrent mutation ordering, boot/read-time retention
purge, controlled 503 route behavior, DSAR export, exact-subject erasure,
adjacent-subject preservation, persistent anti-resurrection fence,
git diff --check, staged path audit, protected-lock hash, conventions ratchet,
and pre-commit hooks
  passed

RecentSearchStore now stores each authenticated member's deduplicated query order and last-used timestamp in one globally ordered durable snapshot. Search mutation acknowledgement waits for that snapshot; a missing required sink or a failed save produces a controlled 503 and leaves the last committed view unchanged. Boot hydrates before traffic and durably removes entries outside the explicit 90-day window. Reads also commit newly discovered expiry, so a long- running process cannot retain stale rows indefinitely.

Snapshot restore rejects unknown fields, unsupported schemas, duplicate users or case-insensitive duplicate queries, non-canonical identities, invalid or misordered timestamps, over-limit state, and a live row for a fenced subject. Concurrent queries serialize through the same mutation tail, and a failed save does not poison a later valid write.

Recent searches now export under the existing conversation_history artifact as the explicit recent_search_queries storage partition. The signed conversation-history eraser count-validates and composes canonical conversation turn deletion with exact recent-search deletion. Erasure removes only the subject, persists a fence even for a not-found subject, survives PostgreSQL restart, preserves adjacent accounts, and rejects delayed stale recreation.

The final BFF ratchet ran alone after the required RAM/swap/disk/process gate and was polled within 30 seconds. TypeScript peaked near 5.5 GiB RSS while available memory remained above 5 GiB; 31 GiB of swap was configured. The source commit used SKIP_TYPECHECK=1 only after that exact ratchet passed; every other hook passed. The source push completed without a remote conflict, and local HEAD, origin/main, and the live remote branch reached exact source-tip parity.

No rendered UI, mobile flow, schema migration, external search-provider operation, production deletion request, signed production receipt, Unreal content, or provider-native record changed in this slice. Playwright/mobile, migration, provider, Unreal, and production-operations automation were inapplicable.

Scene tip-ledger and counsel-authority durability verification#

Implementation source commit df93bd737dcd05434a71cafdd6de6cfa755aeba2, published to origin/main, closes the tip accrual, settlement, and counsel payout-authority partitions found by the continuing production-store inventory. Verification completed on 2026-07-17 UTC on dev-server, Linux 6.8.0-110-generic x86_64, with Node 24.14.1, pnpm 10.25.0, TypeScript 6.0.3, Vitest 4.1.7, and ESLint 10.4.0. The protected user pnpm-lock.yaml remained byte-identical at Git blob a37431842e330b3a06b030947c25bebdc72bc2b1.

text
# cwd apps/oshun/bff; financial store, route, and DSAR suites
pnpm exec vitest run \
  src/scene-experience/tip-ledger-store-durability.spec.ts \
  src/routes/scene-tips.test.ts \
  src/data-export/bundle-builder.test.ts --maxWorkers=1
  3 files, 35/35 tests passed

# final failed-settlement-commit and recovery assertions
pnpm exec vitest run \
  src/scene-experience/tip-ledger-store-durability.spec.ts --maxWorkers=1
  1 file, 5/5 tests passed

# real PostgreSQL restart, settlement recovery, pseudonymization, and fence
OSHUN_V1_DATABASE_URL=postgresql://oshun:<redacted>@127.0.0.1:5432/oshun_dev \
  pnpm exec vitest run --config vitest.integration.config.ts \
    src/scene-experience/tip-ledger-store-durability.integration.spec.ts \
    --maxWorkers=1
  1 file, 1/1 test passed

# repository root; exact BFF zero-backlog type ratchet
node tools/typecheck/ratchet.mjs --app apps/oshun/bff \
  --tsconfig tsconfig.typecheck.json
  no new app-own type errors; backlog 0

# cwd apps/oshun/bff; changed production source/tests and commit hook
pnpm exec eslint <changed-source-and-test-files> --no-warn-ignored
  passed with 0 errors and 0 warnings
pre-commit eslint --fix --no-warn-ignored <8 staged TypeScript files>
  passed
pre-commit prettier --write <8 staged TypeScript files>
  passed; all files use Prettier style

# exact production entry bundle
pnpm exec esbuild src/server.ts --bundle --platform=node --format=esm \
  --target=node22 \
  --outfile=/tmp/oshun-bff-tip-ledger-server.mjs --sourcemap
  passed in 13.893 seconds; 32.4 MB server bundle and 76.4 MB source map

strict snapshot-field/schema/sequence/balance/fee-split/authority/fence
rejection, failed tip and settlement rollback, later-write recovery, concurrent
payout serialization, controlled 503 route behavior, DSAR export, exact-subject
pseudonymization, adjacent-subject preservation, persistent anti-resurrection
fence, git diff --check, staged path audit, protected-lock hash, conventions
ratchet, and pre-commit hooks
  passed

TipLedgerStore now persists the append-only tip accrual and payout-settlement ledger together with the complete counsel-authority change history. Production boot treats an absent snapshot as authoritative empty state, hydrates before traffic, and requires the sink. Tip and admin-authority routes wait for the ordered snapshot before replying; a missing or failed sink produces a controlled 503 without publishing the candidate.

Payout authorization and settlement append now run inside that same mutation queue rather than calculating against a ledger that another request can change. Two concurrent authorization requests for one unsettled balance therefore yield one committed settlement and one nothing-to-pay-out refusal. A failed settlement write leaves the balance unsettled, and a later retry commits it exactly once. The counsel gate still defaults closed; every authority revision, including the operator who recorded it, survives restart for audit.

Snapshot restore independently checks every sequence, amount band, running accrual, unsettled balance, 10-percent fee split, counsel memo linkage, identity, timestamp, revision, field set, and deletion fence. It rejects a settlement not backed by complete recorded counsel authority, rather than trusting serialized derived totals.

Tip rows relevant to a viewer or creator and authority revisions recorded by a subject now export under billing_receipt as the scene_tip_ledger partition. Because these are retained financial records, profile deletion does not erase the transaction evidence: it replaces exact viewer, creator, and authority- recorder IDs with a deterministic pseudonym, durably installs a subject fence, removes direct-subject DSAR access, preserves adjacent-account records, and rejects delayed stale writes. At that source boundary, shared legal-hold-aware and retention-exception-aware terminal expiry execution remained open.

The final BFF ratchet ran alone after the required RAM/swap/disk/process gate and was polled within 30 seconds. TypeScript peaked near 5.6 GiB RSS while available memory remained above 4.6 GiB; 31 GiB of swap was configured. The source commit used SKIP_TYPECHECK=1 only after the exact zero-backlog ratchet passed; every other hook passed. The source push completed without a remote conflict and reached origin/main.

No rendered UI, mobile flow, schema migration, payment-provider execution, production deletion request, signed production receipt, Unreal content, or provider-native record changed in this slice. Playwright/mobile, migration, provider, Unreal, and production-operations automation were inapplicable.

Scene-appreciation and velocity-authority durability verification#

Implementation source commit 6867a88a670ac3ce690fe017f077288d0d0c9d89, published to origin/main, closes the one-per-viewer scene-appreciation and active UTC-day abuse-authority partitions found by the continuing production- store inventory. Verification completed on 2026-07-17 UTC on dev-server, Linux 6.8.0-110-generic x86_64, with Node 24.14.1, pnpm 10.25.0, TypeScript 6.0.3, Vitest 4.1.7, and ESLint 10.4.0. The protected user pnpm-lock.yaml remained byte-identical at Git blob a37431842e330b3a06b030947c25bebdc72bc2b1.

text
# cwd apps/oshun/bff; appreciation store, route, and continuity DSAR suites
pnpm exec vitest run \
  src/scene-experience/appreciation-store-durability.spec.ts \
  src/routes/scene-reactions.test.ts \
  src/data-export/bundle-builder.test.ts --maxWorkers=1
  3 files, 35/35 tests passed

# real PostgreSQL restart, exact erasure, adjacent isolation, and fence
OSHUN_V1_DATABASE_URL=postgresql://oshun:<redacted>@127.0.0.1:5432/oshun_dev \
  pnpm exec vitest run --config vitest.integration.config.ts \
    src/scene-experience/appreciation-store-durability.integration.spec.ts \
    --maxWorkers=1
  1 file, 1/1 test passed

# repository root; exact BFF zero-backlog type ratchet
node tools/typecheck/ratchet.mjs --app apps/oshun/bff \
  --tsconfig tsconfig.typecheck.json
  no new app-own type errors; backlog 0

# cwd apps/oshun/bff; changed production source/tests and commit hook
pnpm exec eslint <changed-source-and-test-files> --no-warn-ignored
  passed with 0 errors and 0 warnings
pre-commit eslint --fix --no-warn-ignored <8 staged TypeScript files>
  passed
pre-commit prettier --write <8 staged TypeScript files>
  passed; all files use Prettier style

# exact production entry bundle
pnpm exec esbuild src/server.ts --bundle --platform=node --format=esm \
  --target=node22 \
  --outfile=/tmp/oshun-bff-appreciation-server.mjs --sourcemap
  passed in 8.071 seconds; 32.4 MB server bundle and 76.5 MB source map

strict snapshot field/schema/identity/kind/timestamp/order/duplicate/cap/fence
rejection, exact restart recovery, stale-counter boot purge, failed-write
rollback, later-write recovery, concurrent first-tap serialization at the
daily-cap boundary, controlled 503 route behavior, continuity-state DSAR
export, exact-subject erasure, adjacent-subject preservation, persistent anti-
resurrection fence, producer audit, git diff --check, staged path audit,
protected-lock hash, conventions ratchet, and pre-commit hooks
  passed

AppreciationStore now persists current one-per-viewer reactions and the active UTC-day creation count in one globally ordered snapshot. The route no longer computes a decision and then performs two independent in-memory writes: the domain decision is recomputed inside the mutation queue, the candidate reaction and counter commit together, and success is returned only after the required sink acknowledges the snapshot. A failed save leaves both the reaction view and velocity authority unchanged, and does not poison a later valid request.

Only the active UTC-day counters are retained. Boot durably removes older counters before traffic; the next mutation also builds from the current day, so a long-running process cannot carry stale abuse rows into a new snapshot. Two simultaneous first appreciations at count 199 serialize to exactly one creation and one appreciation-velocity-exceeded refusal at count 200.

Snapshot restore rejects unknown fields, unsupported schemas, duplicate or misordered identities, invalid kinds/timestamps/counts, over-cap counters, and records or counters for a fenced subject. Appreciation data and the active-day count export under continuity_state as the scene_appreciations partition. Exact-subject account erasure removes every viewer reaction and counter row, persists the fence even after restart, rejects delayed recreation, and preserves adjacent viewers' records.

The final BFF ratchet ran alone after the required RAM/swap/disk/process gate and was polled within 30 seconds. TypeScript peaked near 5.1 GiB RSS while available memory remained above 4.7 GiB; 31 GiB of swap was configured. The source commit used SKIP_TYPECHECK=1 only after that exact zero-backlog ratchet passed; every other hook passed. The source push completed without a remote conflict and reached origin/main.

No rendered UI, mobile flow, schema migration, external reaction-provider operation, production deletion request, signed production receipt, Unreal content, or provider-native record changed in this slice. Playwright/mobile, migration, provider, Unreal, and production-operations automation were inapplicable.

Scene-follow and premiere-lifecycle durability verification#

Implementation source commit f162352a9587fdbef46d47c4209defa433fb49a7, published to origin/main, closes viewer/creator follow relationships and creator-owned premiere allocation/lifecycle authority found by the continuing production-store inventory. Verification completed on 2026-07-17 UTC on dev-server, Linux 6.8.0-110-generic x86_64, with Node 24.14.1, pnpm 10.25.0, TypeScript 6.0.3, Vitest 4.1.7, and ESLint 10.4.0. The protected user pnpm-lock.yaml remained byte-identical at Git blob a37431842e330b3a06b030947c25bebdc72bc2b1.

text
# cwd apps/oshun/bff; follow/premiere store, route, and continuity DSAR suites
pnpm exec vitest run \
  src/scene-experience/follow-store-durability.spec.ts \
  src/routes/scene-follows.test.ts \
  src/data-export/bundle-builder.test.ts --maxWorkers=1
  3 files, 40/40 tests passed

# real PostgreSQL restart, allocation recovery, exact erasure, and fence
OSHUN_V1_DATABASE_URL=postgresql://oshun:<redacted>@127.0.0.1:5432/oshun_dev \
  pnpm exec vitest run --config vitest.integration.config.ts \
    src/scene-experience/follow-store-durability.integration.spec.ts \
    --maxWorkers=1
  1 file, 1/1 test passed

# repository root; exact BFF zero-backlog type ratchet
node tools/typecheck/ratchet.mjs --app apps/oshun/bff \
  --tsconfig tsconfig.typecheck.json
  no new app-own type errors; backlog 0

# cwd apps/oshun/bff; changed production source/tests and commit hook
pnpm exec eslint <changed-source-and-test-files> --no-warn-ignored
  passed with 0 errors and 0 warnings
pre-commit eslint --fix --no-warn-ignored <8 staged TypeScript files>
  passed
pre-commit prettier --write <8 staged TypeScript files>
  passed; all files use Prettier style

# exact production entry bundle
pnpm exec esbuild src/server.ts --bundle --platform=node --format=esm \
  --target=node22 \
  --outfile=/tmp/oshun-bff-follow-server.mjs --sourcemap
  passed in 8.628 seconds; 32.4 MB server bundle and 76.5 MB source map

strict snapshot field/schema/identity/order/duplicate/reach/state/sequence/fence
rejection, exact restart and next-ID recovery, failed follow, unfollow,
schedule, transition, and erasure rollback, later-write recovery, concurrent
unique premiere allocation, concurrent lifecycle serialization, both
follow/delete race orders, controlled 503 route behavior, two-role
`continuity_state` DSAR export, exact-subject erasure, adjacent-subject preservation,
persistent anti-resurrection fence for owned and read-through inputs,
producer/disposition audit, git diff --check, staged path audit, protected-lock
hash, conventions ratchet, and pre-commit hooks
  passed

FollowStore now persists follow relationships, creator-owned premieres, the monotonic premiere allocation sequence, and deletion fences in one globally ordered snapshot. Follow, unfollow, scheduling, and lifecycle responses wait for that snapshot; a missing or failed required sink produces a controlled 503 and leaves the last acknowledged view and allocation sequence unchanged.

Premiere transitions now reload the current lifecycle state inside the mutation queue. Two concurrent scheduled -> live requests therefore produce one committed transition and one refusal from the newly committed live state, rather than both accepting the same stale scheduled record. Concurrent schedules allocate distinct IDs, and restart resumes after the highest durable allocation without reusing an ID removed by subject erasure.

Snapshot restore rejects unknown fields, unsupported schemas, malformed or duplicate relationships and premieres, noncanonical allocation IDs, regressed sequence authority, invalid reach/state/timestamps, and rows that reference a fenced subject. A subject's relationships in either viewer or creator role and creator-owned premieres export under continuity_state as the scene_follows_premieres partition. Exact-subject erasure removes all three forms, preserves adjacent relationships and premieres, fences recreation in either role, and clears/rejects stale read-through inputs.

Blocklists, follower quiet-hours preferences, and weekly premiere-delivery counts are used only through seed/read methods in this store; repository search found no production mutation producer for them. Their authoritative trust and safety, notification-preference, and delivery-ledger stores therefore remain outside this snapshot. The durability and deletion claim covers only the owned follow and premiere partition rather than silently duplicating those external sources of truth.

The final BFF ratchet ran alone after the required RAM/swap/disk/process gate and was polled within 30 seconds. TypeScript peaked near 5.2 GiB RSS while available memory remained above 4.4 GiB; 31 GiB of swap was configured. The source commit used SKIP_TYPECHECK=1 only after that exact zero-backlog ratchet passed; every other hook passed. The source push completed without a remote conflict and reached origin/main.

No rendered UI, mobile flow, schema migration, external follow/notification provider operation, production deletion request, signed production receipt, Unreal content, or provider-native record changed in this slice. Playwright, mobile, migration, provider, Unreal, and production-operations automation were inapplicable.

Group-practice session and private leave-audit durability verification#

Implementation source commit 68bba491d06af85d1e2010559b50b223580fea24, published to origin/main, closes the shared group-session lifecycle and participant-private departure-audit authority found by the continuing production-store inventory. Verification completed on 2026-07-17 UTC on dev-server, Linux 6.8.0-110-generic x86_64, with Node 24.14.1, pnpm 10.25.0, TypeScript 6.0.3, Vitest 4.1.7, and ESLint 10.4.0. The protected user pnpm-lock.yaml remained byte-identical at Git blob a37431842e330b3a06b030947c25bebdc72bc2b1.

text
# cwd apps/oshun/bff; group-session store, route, and continuity DSAR suites
pnpm exec vitest run \
  src/scene-experience/group-session-store-durability.spec.ts \
  src/routes/scene-group-sessions.test.ts \
  src/data-export/bundle-builder.test.ts --maxWorkers=1
  3 files, 41/41 tests passed

# real PostgreSQL restart, hashed invite authority, exact erasure, and fence
OSHUN_V1_DATABASE_URL=postgresql://oshun:<redacted>@127.0.0.1:5432/oshun_dev \
  pnpm exec vitest run --config vitest.integration.config.ts \
    src/scene-experience/group-session-store-durability.integration.spec.ts \
    --maxWorkers=1
  1 file, 1/1 test passed

# repository root; exact BFF zero-backlog type ratchet
node tools/typecheck/ratchet.mjs --app apps/oshun/bff \
  --tsconfig tsconfig.typecheck.json
  no new app-own type errors; backlog 0

# repository root; changed production source/tests and commit hook
pnpm exec eslint <changed-source-and-test-files> --no-ignore --max-warnings=0
  passed with 0 errors and 0 warnings
pre-commit eslint --fix --no-warn-ignored <8 staged TypeScript files>
  passed
pre-commit prettier --write <8 staged TypeScript files>
  passed; all files use Prettier style

# exact production entry bundle
pnpm exec esbuild src/server.ts --bundle --platform=node --format=esm \
  --target=node22 \
  --outfile=/tmp/oshun-bff-group-session-server.mjs --sourcemap
  passed in 10.176 seconds; 32.4 MB server bundle and 76.6 MB source map

strict snapshot field/schema/identity/order/duplicate/token-digest/roster/
shared-private-audit/fence rejection, exact restart and lifecycle recovery,
raw invite-token absence, post-restart invite proof, failed create/join/
heartbeat/start/leave/erasure rollback, atomic shared/private leave failure,
later-write recovery, concurrent capacity serialization without invited ghosts,
concurrent start serialization, durable 30-day boot retention purge, physical
expired-row erasure count, both create/delete race orders, controlled 503 and
410 route behavior, participant-only private reason export, two-role
`continuity_state` DSAR export, exact-subject erasure, adjacent-subject
preservation, persistent anti-resurrection fence, live PostgreSQL restart,
git diff --check, staged path audit, protected-lock hash, conventions ratchet,
and pre-commit hooks
  passed

GroupSessionStore now owns session allocation, hashed invite authority, roster and heartbeat state, start-barrier state, reason-free shared departure records, participant-private leave reasons, and deletion fences in one globally ordered snapshot. Create, invite-token join, heartbeat, start, and leave responses wait for the candidate snapshot to succeed. A missing or failed required sink produces a controlled 503 and leaves the last acknowledged state unchanged. In particular, a leave can no longer publish its shared roster transition while losing its private crisis reason in a second memory-only write.

Invite bearer tokens are returned once at creation. Only their SHA-256 lookup digests enter store-owned retained memory or the durable snapshot, equality uses a timing-safe digest comparison, and the export projection omits even that digest. The real-Postgres test proves that the original high-entropy token still authorizes a join after a fresh process hydrates only the stored digest. Snapshot restore rejects raw-token fields, malformed digests, duplicate sessions or participants, malformed roster state/timestamps, inconsistent shared leave logs, private-audit mismatches, unknown fields, bad order, and rows referring to a fenced subject.

Capacity tests and the host start barrier now reload current state inside the mutation queue. Two simultaneous joins at the last seat therefore yield one committed participant and one session-at-capacity refusal without persisting the losing invite intermediate. Two simultaneous starts yield one start and one already-started verdict from the newly committed state. Failed writes for every mutation are rolled back, and later requests continue in order rather than inheriting a rejected candidate.

The shared session and private audit window is bounded to 30 days. Boot hydration removes expired sessions and audits from the durable snapshot before traffic, reads hide expired state, and successful writes plus existing-session lookup mutations fold retention cleanup into their ordered writes. An account erasure racing that cleanup still counts the physical subject-bearing records it removed rather than reporting a false zero.

A subject's hosted sessions, participant roster membership, reason-free shared leave entries, and subject-owned private leave records export under continuity_state as the scene_group_sessions partition. Private reasons are included only for their participant owner; a host's export of the same shared session cannot see another participant's crisis reason. Exact-subject erasure removes host-owned sessions, removes a participant from sessions hosted by others, deletes only that participant's private audits, preserves adjacent sessions and other participants' private records, and persists a recreation fence. Create and participant mutations lose safely to that fence in either race order. The live-Postgres case proves restart recovery, both-role erasure, adjacent preservation, and stale recreation refusal.

The final BFF ratchet ran alone after the required RAM/swap/disk/process gate and was polled within 30 seconds. TypeScript peaked near 5.8 GiB RSS while available memory remained above 4.7 GiB; 31 GiB of swap was configured. The source commit used SKIP_TYPECHECK=1 only after that exact zero-backlog ratchet passed; every other hook passed. The first source push was rejected because origin/main had advanced to unrelated optional live-media adapter commit 418fd496d8c6a90efe8b69b09e0f7396c78981cf. Its changed-path audit found no overlap, the source commit rebased cleanly, the protected lockfile was restored from a retained named stash, and exact local/remote parity was then verified at 68bba491d06af85d1e2010559b50b223580fea24.

No rendered UI, mobile flow, schema migration, external session/provider operation, production deletion request, signed production receipt, Unreal content, or provider-native record changed in this slice. Playwright, mobile, migration, provider, Unreal, and production-operations automation were inapplicable.

Themis moderation-appeal support-case durability verification#

Implementation source commit 4afe204a3b9df3229a4b3814b522148e68d9da96, published to origin/main, closes the authenticated moderation-appeal case map found by the continuing production-store inventory. Verification completed on 2026-07-17 UTC on dev-server, Linux 6.8.0-110-generic x86_64, with Node 24.14.1, pnpm 10.25.0, TypeScript 6.0.3, Vitest 4.1.7, and ESLint 10.4.0. The protected user pnpm-lock.yaml remained byte-identical at Git blob a37431842e330b3a06b030947c25bebdc72bc2b1.

text
# cwd apps/oshun/bff; durable store, customer route, and support-case DSAR
pnpm exec vitest run \
  src/themis/moderation-appeal-store-durability.spec.ts \
  src/__tests__/themis-route.test.ts \
  src/data-export/bundle-builder.test.ts --maxWorkers=1
  3 files, 40/40 tests passed

# real PostgreSQL restart, JSONB restore, compliance redaction, and fence
OSHUN_V1_DATABASE_URL=postgresql://oshun:<redacted>@127.0.0.1:5432/oshun_dev \
  pnpm exec vitest run --config vitest.integration.config.ts \
    src/themis/moderation-appeal-store-durability.integration.spec.ts \
    --maxWorkers=1
  1 file, 1/1 test passed

# repository root; exact BFF zero-backlog type ratchet
node tools/typecheck/ratchet.mjs --app apps/oshun/bff \
  --tsconfig tsconfig.typecheck.json
  no new app-own type errors; backlog 0

# cwd apps/oshun/bff; all eight changed production/test sources
pnpm exec eslint --no-warn-ignored <changed-source-and-test-files>
  passed with 0 errors and 0 warnings
pre-commit eslint --fix --no-warn-ignored <8 staged TypeScript files>
  passed
pre-commit prettier --write <8 staged TypeScript files>
  passed; all files use Prettier style

# exact production entry bundle
pnpm exec esbuild src/server.ts --bundle --platform=node --format=esm \
  --target=node22 \
  --outfile=/tmp/oshun-themis-appeal-bff-server-final.js --sourcemap
  passed in 8.644 seconds; 32.4 MB server bundle and 76.6 MB source map

strict snapshot identity/duplicate/flow/status/remedy/deadline/routing/owner/
redaction/fence rejection, JSONB key-order-independent restart, failed-save
rollback, later-write recovery, concurrent filing serialization, global
duplicate admission across redaction, reserved identifier namespace, bounded
appellant narrative and evidence references, controlled 503 and 410 routes,
authenticated owner isolation, canonical `support_case` DSAR export,
exact-subject pseudonymization, adjacent-subject preservation, persistent
anti-resurrection fence, production synchronous-mutator search,
git diff --check, staged path audit, protected-lock hash, conventions ratchet,
and pre-commit hooks
  passed

ModerationAppealStore now persists the opened DSA appeal-case outcome, including statement/action references, filing and resolution deadlines, intake status and rejection reasons, requested remedy, appellant narrative, evidence references, canonical Themis routing, authenticated ownership, and redaction fences in one globally ordered snapshot. A filing follows candidate -> validate -> save -> publish. A missing or failed required sink returns a controlled 503 without exposing the candidate, later writes continue after a rejected save, and concurrent filings serialize without losing an acknowledged case. Deployable startup hydrates and requires this sink before traffic.

Snapshot restore rejects duplicate or reserved IDs, unsupported flow metadata, mismatched ownership, invalid status/remedy/deadline/routing authority, malformed evidence, unrecognized or incomplete redactions, and active rows for a fenced subject. Routing comparison is semantic rather than object-key-order sensitive; the real-PostgreSQL test caught and closed the JSONB key-order issue that an in-memory structured clone could not expose. Caller-controlled IDs, appellant narrative, and evidence references are bounded. The internal redacted-appeal: namespace is unavailable to callers, preventing a crafted ID from colliding with a later compliance-redacted adjacent record. Duplicate admission also checks the retained hash form, so redaction cannot reopen a previously consumed global appeal ID.

The canonical support_case DSAR section now exports the authenticated appellant's locally retained moderation-appeal case alongside customer feedback cases under the distinct themis_moderation_appeals partition. Profile and full-account deletion compose this partition as compliance redaction rather than claiming hard deletion: direct owner/appellant, appeal, statement, and action identifiers are replaced by deterministic domain-separated SHA-256 pseudonyms; appellant-authored narrative and evidence references are removed; and only categorical decision, routing, and timestamp evidence remains. Adjacent appellants remain readable, direct subject export becomes empty, and the durable fence rejects stale recreation with 410 after restart. The signed deletion workflow's existing legal-hold gate applies before this profile fanout.

This partition uses the existing canonical support_case policy: five-year default retention, legal-hold extension, redaction-only account deletion, and a 30-day compliance purge cadence. This slice does not implement the shared legal-hold/retention-exception-aware five-year purge executor. That retention gap and the remaining operational/provider inventory keep the all-store durability/privacy checkbox open.

The exact BFF ratchet ran alone after the required RAM/swap/disk/process gate and was polled within 30 seconds. TypeScript peaked near 5.6 GiB RSS while available memory remained above 5 GiB; 31 GiB of swap was configured. The source commit used SKIP_TYPECHECK=1 only after that exact zero-backlog ratchet passed; every other hook passed. Three source pushes were rejected as origin/main advanced through unrelated Hathor and Yemaya changes. The only cross-cutting incoming source was the root ESLint configuration, so targeted lint was rerun and passed after rebase. A later incoming binary lockfile change produced the expected stash-apply conflict; the index retained the published remote lock change while the user's exact unstaged blob was restored. Three named preservation stashes remain intact. Final source HEAD, origin/main, and the live remote branch reached exact parity at 4afe204a3b9df3229a4b3814b522148e68d9da96.

No rendered UI, mobile flow, schema migration, external moderation provider operation, production deletion request, signed production receipt, Unreal content, or provider-native record changed in this slice. Playwright, mobile, migration, provider, Unreal, and production-operations automation were inapplicable.

Admin achievement-evaluation durability verification#

Source commit: 4234baf3c39a7f59a0a70feb986221d99174d851

This slice dispositions the admin achievement-evaluation store as bounded operational history. Deployable startup now hydrates the singleton from the shared PostgreSQL durable-snapshot boundary and requires that sink before traffic. Each evaluation is serialized through candidate -> strict restore validation -> durable save -> publish; a missing or failed required sink cannot expose the candidate and returns the route's controlled 503. Concurrent evaluations cannot overwrite an acknowledged outcome, and the persisted idempotency key remains authoritative after restart.

The durable document deliberately omits the caller's raw progress map, unlocked-achievement set, and any subject or user field. It retains only the opaque machine-shaped evaluation id, canonical catalog-derived awards, exact points total, and server evaluation timestamp. Evaluation ids reject free-form text and are bounded to 200 characters. Restore rejects duplicate ids, malformed timestamps, duplicate awards, noncanonical catalog metadata, prerequisite-order changes, and incorrect points totals. Consequently a tampered snapshot cannot become the source of award or duplicate-admission authority.

Operational history is bounded to 90 days. Every write purges older outcomes from the same candidate snapshot, and startup performs and durably saves the physical purge before serving traffic. Reads independently hide expired rows. The current API has no subject association and therefore cannot support an honest owner-keyed DSAR or account-erasure join; it is not added to those fanouts. If a future API associates evaluations with a customer, that schema must add authenticated ownership plus DSAR and erasure composition rather than encoding identity in the opaque evaluation id.

Verification against the exact published source:

text
# cwd apps/oshun/bff; final source after opaque-id hardening
pnpm exec vitest run \
  src/achievements/achievement-store-durability.spec.ts \
  src/__tests__/admin-achievements-route.test.ts --maxWorkers=1
  2 files, 13/13 tests passed

# real PostgreSQL durable_snapshot proof
pnpm exec vitest run --config vitest.integration.config.ts \
  src/achievements/achievement-store-durability.integration.spec.ts \
  --maxWorkers=1
  1 file, 1/1 test passed

# repository root; exact BFF zero-backlog type ratchet
node tools/typecheck/ratchet.mjs --app apps/oshun/bff \
  --tsconfig tsconfig.typecheck.json
  no new app-own type errors; backlog 0

# all six changed production/test sources
pnpm exec eslint --no-warn-ignored <changed-source-and-test-files>
  passed with 0 errors and 0 warnings
pnpm exec prettier --check <changed-source-and-test-files>
  passed

# exact production entry bundle
pnpm exec esbuild src/server.ts --bundle --platform=node --format=esm \
  --target=node22 \
  --outfile=/tmp/oshun-achievement-bff-server-final.js --sourcemap
  passed in 10.014 seconds; 32.4 MB server bundle and 76.6 MB source map

failed-save rollback, controlled 503, restart-safe duplicate authority,
concurrent serialization, 90-day physical purge, live-PostgreSQL boot purge,
strict canonical-catalog restore, opaque-id rejection, production synchronous-
caller search, git diff --check, staged-path audit, protected-lock hash,
conventions ratchet, and pre-commit hooks
  passed

The exact BFF ratchet ran alone after the required RAM/swap/disk/process gate and was polled within 30 seconds. TypeScript peaked near 5.5 GiB RSS while available memory remained at or above 5.7 GiB; 31 GiB of swap was configured. The source commit used SKIP_TYPECHECK=1 only after that exact zero-backlog ratchet passed; all other hooks passed. Publication rebased over unrelated Hathor and Yemaya changes. The only overlapping path was the incoming binary lockfile: the remote version remained in published history while the user's exact unstaged blob was restored from the retained named stash.

No rendered UI, mobile flow, schema migration, external achievement provider, production deletion request, signed production receipt, Unreal content, or provider-native record changed in this slice. Playwright, mobile, migration, provider, Unreal, and production-operations automation were inapplicable.

Living-scene abuse-report support-case durability verification#

Source commit: fa7efb255ba143b4106ce55a15efcfc2869ee5d7

This slice replaces the explicitly memory-only public living-scene abuse-report singleton with one ordered durable snapshot for intake, idempotency admission, operator triage, and account-redaction fences. Deployable startup requires and hydrates the shared PostgreSQL snapshot sink before traffic. Public intake and operator resolve/dismiss now follow candidate -> strict restore validation -> durable save -> publish. Missing or failed required persistence returns a controlled 503 and does not expose the candidate; concurrent writes serialize, and an identical retry cannot reopen an already-actioned case.

The canonical Yemaya recordAbuseReport function remains the raw intake authority. Restore recomputes and verifies its raw report id and normalized detail, and rejects duplicate or raw/redacted-colliding ids, unsupported reason or status vocabulary, altered Lilith routing, action metadata on an open case, actions predating intake, malformed reporter/operator identity, incomplete redaction, and direct-subject resurrection behind a fence. The route now derives authenticated ownership only from a verified bearer token. An unauthenticated caller may still report anonymously, but a body-supplied reporter id is ignored instead of creating a support case under another user.

Authenticated reporter records now export under the canonical support_case artifact as the distinct living_scene_abuse_reports storage partition. Profile/full-account deletion compliance-redacts every row where the subject is the reporter or actioning operator. Reporter identity and report id become domain-separated SHA-256 pseudonyms and reporter-authored detail is removed; operator identity is pseudonymized and its authored resolution note is removed when that operator is the deleted subject. Categorical reason, reported share, status, routing, and timestamps remain as compliance evidence. Adjacent reporters remain readable, direct-subject export becomes empty, and the durable fence rejects stale report or operator recreation after restart.

The production routes now use the audit store injected by createApp rather than an unrelated module-local buffer, so supplemental report lifecycle events reach the durable admin adapter. Creation events are indexed under the generic public actor: the authenticated reporter id remains only in the owner-keyed support-case partition where DSAR and redaction can reach it.

Verification against the exact published source:

text
# cwd apps/oshun/bff; acknowledgement, restart, race, redaction, corruption
pnpm exec vitest run \
  src/living-scenes/abuse-report-store-durability.spec.ts --maxWorkers=1
  1 file, 5/5 tests passed

# admin triage + authenticated reporter receipts
pnpm exec vitest run \
  src/__tests__/admin-abuse-reports-route.test.ts \
  src/__tests__/my-abuse-reports-route.test.ts --maxWorkers=1
  2 files, 15/15 tests passed

# public bearer ownership, anonymous anti-spoofing, audit minimization, 503
pnpm exec vitest run src/__tests__/living-scenes-route.test.ts \
  --maxWorkers=1 \
  -t 'routes public abuse reports|returns 503 without publishing a report'
  1 file, 2/2 selected tests passed (21 unrelated tests skipped)

# support_case DSAR aggregation and post-redaction absence
pnpm exec vitest run src/data-export/bundle-builder.test.ts --maxWorkers=1 \
  -t 'exports every local support-case partition'
  1 file, 1/1 selected test passed (23 unrelated tests skipped)

# real PostgreSQL restart/triage/redaction/fence proof
pnpm exec vitest run --config vitest.integration.config.ts \
  src/living-scenes/abuse-report-store-durability.integration.spec.ts \
  --maxWorkers=1
  1 file, 1/1 test passed

# repository root; exact final-source BFF zero-backlog type ratchet
node tools/typecheck/ratchet.mjs --app apps/oshun/bff \
  --tsconfig tsconfig.typecheck.json
  no new app-own type errors; backlog 0

# all eleven changed production/test sources
pnpm exec eslint --no-warn-ignored <changed-source-and-test-files>
  passed with 0 errors and 0 warnings
pnpm exec prettier --check <changed-source-and-test-files>
  passed

# exact final production entry bundle
pnpm exec esbuild src/server.ts --bundle --platform=node --format=esm \
  --target=node22 \
  --outfile=/tmp/oshun-abuse-report-bff-server-final.js --sourcemap
  passed in 8.530 seconds; 32.5 MB server bundle and 76.6 MB source map

failed-save rollback for intake and action, controlled route 503s, restart-safe
triage/idempotency, conflicting-retry rejection, concurrent serialization,
canonical intake/routing restore, two-role redaction, narrative removal,
adjacent-subject preservation, persistent anti-resurrection fence,
unauthenticated anti-spoofing, generic audit actor, DSAR aggregation,
production synchronous-mutator search, git diff --check, staged-path audit,
protected-lock hash, conventions ratchet, and pre-commit hooks
  passed

The exact final-source BFF ratchet ran alone after the required RAM/swap/disk/process gate and was polled within 30 seconds. TypeScript peaked near 5.2 GiB RSS while available memory remained at or above 5.2 GiB; 31 GiB of swap was configured. The source commit used SKIP_TYPECHECK=1 only after that zero-backlog ratchet passed; every other hook passed. Publication rebased over unrelated Aphrodite and Hathor changes. The only overlapping path was the binary lockfile; the remote version remained in published history while the user's exact unstaged blob was restored from the retained named stash.

This partition follows the existing canonical support_case policy: five-year default retention, legal-hold extension, redaction-only account deletion, and a 30-day compliance purge cadence. This slice does not implement the shared legal-hold/retention-exception-aware five-year purge executor, so that retention gap and the continuing store/provider inventory keep the all-store checkbox open.

No rendered UI, mobile flow, schema migration, external safety provider, production deletion request, signed production receipt, Unreal content, or provider-native record changed in this slice. Playwright, mobile, migration, provider, Unreal, and production-operations automation were inapplicable.

Living-scene kept-artifact/share durability, privacy, and retention verification#

Source commit: da8d927d9dc8cfe30d21500b8be0785287579043

This slice replaces the Living Scene kept-artifact/share module's synchronous snapshot callback and production fire-and-forget save with one serialized, acknowledgement-bound working set. Kept artifacts, live share metadata, the short-code index, exact APNG bytes, tenant audit evidence, takedown overlays, per-subject revisions, and deletion fences now move through an isolated candidate -> strict validation -> awaited durable save -> publish transaction. Failed or missing required persistence returns a controlled 503 and leaves the previous committed gallery, public viewer, media, and audit view unchanged. Concurrent whole-store mutations save in order, so a later snapshot cannot overwrite an earlier accepted mutation with stale state.

Deployable startup now requires this partition, restores it before traffic, migrates legacy snapshots, persists an authoritative empty schema-v2 snapshot when the partition does not yet exist, and physically purges already-expired bounded-retention artifacts before serving requests. A supervised unref'ed timer repeats the purge every 60 seconds by default (configurable through OSHUN_LIVING_SCENE_RETENTION_PURGE_INTERVAL_MS) and is cleared during graceful shutdown. Thirty-day and one-year artifacts are removed only after an awaited snapshot acknowledgement, including their shares, materialized media, short-code entries, audit entries, takedown overlays, and ephemeral grants; indefinite and adjacent-owner artifacts remain. A failed purge publishes nothing.

Schema-v2 snapshots store the exact base64 APNG bytes whose SHA-256 digest is bound by each share's C2PA manifest. Restore rejects duplicate or orphaned artifacts, shares, media, indexes, audit rows, or takedowns; incomplete short-code relationships; owner/tenant mismatches; malformed base64; media/C2PA hash mismatch; invalid revisions or fences; and direct-identity resurrection. Legacy snapshots without materialized media remain readable through an explicit legacy-unmaterialized index rather than pretending their public playback bytes exist. Newly created shares cannot enter that legacy state.

Download grants remain intentionally ephemeral: they are 15-minute, reissuable bearer capabilities rather than durable authority. Restart invalidates an old grant, while the restored public share can mint a fresh one and serve the same persisted APNG. This is the explicit recomputable/short-lived disposition for that Map.

The generated_artifact DSAR collector now includes the distinct living_scene_shares partition with complete JSON-safe kept artifacts, share metadata, exact media bytes and length, audit/takedown state, and subject revision. It withholds the password verifier and reports only whether a share is password protected. It also explicitly reports that canonical Isis generated outputs and the generation-jobs/catalog/operator-gallery partitions are not duplicated into this local record. Full-account generated_artifact erasure now count-validates this partition: it removes the exact owner's artifacts, shares, media, indexes, owned audit/takedown state, and ephemeral grants; pseudonymizes the deleted operator on unrelated retained audit evidence; preserves adjacent owners; and persists a SHA-256 deletion fence even when no rows existed. Deletion is idempotent, shares the mutation stream with keep/share, survives restart, and rejects stale recreation with 409.

Verification against the published implementation:

text
# cwd apps/oshun/bff; exact media restart, failed-save rollback, races,
# corruption rejection, DSAR/deletion, and bounded-retention purge
pnpm exec vitest run src/__tests__/living-scenes-durability.test.ts \
  --maxWorkers=1
  1 file, 11/11 tests passed

# complete Living Scene route behavior
pnpm exec vitest run src/__tests__/living-scenes-route.test.ts --maxWorkers=1
  1 file, 23/23 tests passed

# generated_artifact erasure and DSAR aggregation
pnpm exec vitest run \
  src/generation/generated-artifact-erasure.test.ts \
  src/data-export/bundle-builder.test.ts --maxWorkers=1
  2 files, 28/28 tests passed

# real PostgreSQL initial partition, acknowledged writes, fresh-connection
# restore/playback, physical deletion, deletion restart, and stale rejection
OSHUN_V1_DATABASE_URL=<live-local-postgres> pnpm exec vitest run \
  --config vitest.integration.config.ts \
  src/__tests__/living-scenes-share-durability.integration.test.ts \
  --maxWorkers=1
  1 file, 1/1 test passed

# repository root; exact final-source BFF zero-backlog type ratchet
node tools/typecheck/ratchet.mjs --app apps/oshun/bff
  no new app-own type errors; backlog 0

# all six changed production/test files
pnpm exec eslint --fix --no-warn-ignored <changed-source-and-test-files>
  passed with 0 errors and 0 warnings
pnpm exec prettier --check <changed-source-and-test-files>
  passed

# exact final production entry bundle
pnpm --dir apps/oshun/bff build
  passed in 7.801 seconds; 31.9 MB server bundle and 75.4 MB source map

acknowledgement boundary, controlled 503s, candidate rollback, ordered saves,
both keep/delete race orders, exact APNG restart playback, C2PA hash validation,
legacy-media disposition, ephemeral grant loss/remint, account erasure,
adjacent-owner preservation, restart-safe anti-resurrection fence, bounded
retention and failed-purge rollback, startup purge, DSAR secret withholding and
coverage gaps, git diff --check, staged-path audit, protected-lock hash,
conventions ratchet, and pre-commit hooks
  passed

The expensive checks ran one at a time after the required RAM/swap/disk/process gates and were polled within 30 seconds. The host retained about 10 GiB of available memory with 31 GiB of configured swap at the final gates. The source commit used SKIP_TYPECHECK=1 only after the exact zero-backlog ratchet passed; the remaining hooks passed. Publication rebased over ten unrelated Hathor/Yemaya/study-adapter commits with no Living Scene source overlap. Seven newly tracked Cargo lockfiles were byte-identical to pre-existing untracked files and were preserved in a named stash during the rebase. The incoming binary pnpm-lock.yaml remained in published history while the user's exact unstaged blob was restored from a separate retained named stash.

No rendered UI, mobile flow, schema migration, external media provider, production deletion request, signed production receipt, Unreal content, or provider-native record changed in this slice. Playwright, mobile, migration, provider, Unreal, and production-operations automation were inapplicable.

Metis academic-record durability, coupled gradebook, and evidence-pack verification#

Source and published implementation: 65200d9e043b3acefd6eef19743e2de7f7033e97. Evidence publication: this commit. Final verification and publication ran on 2026-07-19 from 05:55:39Z through 06:08:17Z on dev-server (Linux 6.8.0-110-generic, x86-64), Node 24.14.1, pnpm 10.25.0, PostgreSQL client 16.14 and live server 16.13, TypeScript 6.0.3, and Vitest 4.1.7. The protected unstaged lockfile remained the exact blob a37431842e330b3a06b030947c25bebdc72bc2b1 and was never published.

  • Task / owner / accountable product: V1-002; V1 Metis/Themis academic- record maintainers, integration auditor Codex; V1.
  • Risk tier: high. Before this slice, verdict, appeal, gradebook, and notification state could cross different acknowledgement boundaries, making partial or restart-lost academic consequences possible.
  • Affected store and contract: schema-v1 metis-academic-records snapshot, Themis integrity/appeal routes, Metis gradebook history, customer message- center notification reconciliation, evidence_pack DSAR aggregation, and signed deletion fanout.
  • Rollout: deploy the source before admitting writes; startup requires the admin snapshot database, restores and validates the partition after the message center, persists an authoritative empty snapshot when absent, and reconciles pending notification intents before traffic. Monitor startup 503s, restore validation, mutation-save failures, and pending notification count.
  • Rollback: stop writers first and retain the snapshot unchanged. A prior binary will ignore this new partition rather than safely mutate it, so rollback is read-only/emergency service rollback until the coupled source is restored. Exact-subject deletion fences and redactions are intentionally irreversible; there is no destructive down migration.

The old singleton bridge has been replaced by one serialized operation ledger covering adjudications, opened/resolved/decided appeals, their gradebook emissions and corrections, SHA-256-only deletion fences, and terminal notification delivery state. Each mutation receives one ordered revision, replays the full candidate through fresh Themis and gradebook engines, validates the result, awaits the complete durable snapshot, and only then replaces the published bridge and gradebook. The route commits adjudication plus gradebook, appeal resolution/decision plus terminal gradebook consequence, and notification intent as atomic units. A missing required sink or failed write returns a controlled 503 without exposing a partial verdict, closed appeal, grade change, or outbox item.

Production hydration rejects malformed schema/revisions, corrupt replay, inconsistent delivered-notification IDs, and direct-identity resurrection. Tenant ownership is recorded independently for verdicts and appeals, so an ID from another tenant is not readable or reusable. Caller-supplied teacherOverride.teacherId is compatibility-only and is replaced with the authenticated operator identity. Concurrent appends recompute revision inside the serialization boundary; deletion rechecks its subject fence there as well, closing both save-first and delete-first stale-write orders.

Appeal notification is now an acknowledgement-recoverable outbox. Its stable message ID is committed with the academic decision, delivery goes through the already durable customer message center, and the academic ledger records a terminal delivered/duplicate/suppressed outcome. Startup retries pending intents. Replaying after a lost acknowledgement does not duplicate the learner message.

The local evidence_pack DSAR now returns the requester's complete current verdicts, audits, appeal workspaces, gradebook histories/corrections, authored actions, and ledger revision without leaking another learner's evidence. Exact- subject erasure physically removes learner-owned operations and gradebook versions; on retained records for another learner it pseudonymizes the deleted operator/respondent/appellant identity and redacts that subject's authored text. It preserves adjacent learners, count-validates removed and redacted state, persists a restart-safe fence even for an empty subject, is idempotent, and rejects recreation with 409. The real eraser replaces the historical request-scoped structural-absence eraser whenever the BFF injects this partition.

Verification against the exact published source:

text
# cwd apps/oshun/bff; final route, ledger/restart/race/privacy, and DSAR suite
pnpm exec vitest run \
  src/metis/academic-integrity-appeal-store-durability.spec.ts \
  src/__tests__/metis-integrity-route.test.ts \
  src/data-export/bundle-builder.test.ts --maxWorkers=1
  3 files, 49/49 tests passed in 81.21 seconds
  route 13/13; ledger 12/12; export 24/24

# exact final retention-boundary assertion after metadata clarification
pnpm exec vitest run \
  src/metis/academic-integrity-appeal-store-durability.spec.ts \
  --maxWorkers=1
  1 file, 12/12 tests passed in 3.08 seconds

# repository root; injected evidence_pack eraser and structural fallback
pnpm exec vitest run \
  --config libs/shared/deletion-fanout/vitest.config.ts \
  libs/shared/deletion-fanout/src/service-erasers.test.ts --maxWorkers=1
  1 file, 11/11 tests passed

# cwd apps/oshun/bff; real PostgreSQL snapshot, fresh-connection restore,
# route decision/gradebook recovery, exact deletion, fence recovery, stale 409
OSHUN_ADMIN_DATABASE_URL=<live-local-postgres> pnpm exec vitest run \
  --config vitest.integration.config.ts \
  src/metis/academic-integrity-appeal-store-durability.integration.spec.ts \
  --maxWorkers=1
  1 file, 1/1 test passed in 79.34 seconds; test body 780 ms

# repository root; exact BFF type ratchet
node tools/typecheck/ratchet.mjs --app apps/oshun/bff \
  --tsconfig tsconfig.typecheck.json
  no new app-own type errors; backlog 0

# affected commit hook
nx affected --target=typecheck --files=<12 changed files> --parallel=4
  @oshun/bff, @oshun/prompt-injection-evals, and @oshun/deletion-fanout passed

# all 12 changed source/test files
pnpm exec prettier --check <changed-files>
pnpm exec eslint --no-warn-ignored <changed-files>
git diff --check
  passed with no formatting, lint, or whitespace errors

# cwd apps/oshun/bff; exact application production entry command
pnpm exec esbuild src/server.ts --bundle --platform=node --format=esm \
  --target=node22 --outfile=dist/server.js --sourcemap
  passed in 12.579 seconds; 32.5 MB bundle and 76.6 MB source map

failed first-save and failed decision-save rollback, unbroken concurrent
revisions, corrupt-snapshot rejection, tenant/ID isolation, authenticated
teacher attribution, complete learner and operator-only DSAR, adjacent-user
isolation, operator/appellant redaction, both delete/write race orders,
restart-safe fence, missing-sink fail closure, outbox recovery/idempotency,
staged-path audit, test-filename convention ratchet, and pre-commit hooks
  passed

The dependency-expanded command pnpm nx run @oshun/bff:build --skip-nx-cache was also attempted after the required resource gate. Nx expanded it to the BFF plus 286 dependency tasks. The first failure was the unrelated existing @oshun/audit-platform declaration build: TypeScript 6 rejected its inherited deprecated baseUrl without ignoreDeprecations: "6.0". The broad run was stopped immediately after that fail-loud result rather than spending resources on the remaining matrix. The exact BFF entry bundle above passed, and the zero-backlog BFF ratchet plus all affected hook typechecks passed. This upstream build debt was neither hidden nor expanded into this Metis-scoped source change.

Expensive checks ran one at a time after RAM/swap/disk/process inspection and were polled within 30 seconds. The host had 15 GiB RAM and 31 GiB swap. The largest BFF TypeScript process peaked near 5.3 GiB RSS while available memory remained about 4.9 GiB or higher; Vitest remained above the stop threshold. No kernel OOM or unsupervised broad gate occurred.

At this source boundary, retention truth was explicit rather than inferred: the export declared a 730-day default and that legal hold was required, but also declared automaticPurgeImplemented: false. Exact account erasure for this local ledger was implemented while scheduled legal-hold-aware expiry remained open. Source d01e4c2c315f3156b4abb4c1b26d39c36cc558fb, documented below, closes that local expiry gap. Its collector still named the separate canonical V1 assessment evidence/verdict tables as coverage gaps at that boundary. Source 234523f6c6323ab4a546828c2fa2adba37120247, documented below, subsequently closes those read gaps for configured deployments; it does not change canonical- table deletion or close the V1-002 all-store box.

No rendered UI, mobile flow, schema migration, external provider/model call, production deletion request, signed production receipt, Unreal content, or provider-native asset changed. Playwright, mobile, migration, provider, Unreal, and production-operations automation were inapplicable.

Stripe provider-native Customer deletion verification#

Source and published implementation: 1ecef2d5c36ae810d5666b2434752736aa44d42d. The full-account deletion fanout now runs the named customer_fiat_stripe_provider_deletion_and_redaction partition through a deploy-bound Stripe client. When a local row contains a Stripe Customer binding, the partition must first receive or reconcile Stripe's strict deleted-Customer tombstone; only then may it durably pseudonymize the subject's retained Fiat Stripe rows and install the resurrection fence. A row created before any Stripe Customer exists remains safely local-only.

The provider operation has a stable SHA-256 key derived from the subject and Customer identity. If the delete request succeeds at Stripe but its response is lost, retry retrieves the Customer and accepts only the explicit deleted: true tombstone for the same ID. It does not interpret a bare 404 as success because Stripe's resource_missing response is also used for invalid or absent resources. An active retrieved Customer, a mismatched/malformed 2xx delete response, a provider error, or missing Stripe configuration while a binding exists fails closed and leaves local identity/fence state unchanged.

This ordering follows Stripe's Customer deletion contract, which says deletion is permanent and immediately cancels active subscriptions, so the account eraser does not issue a separate subscription-cancel request. Stripe also says a deleted Customer remains retrievable in a reduced deleted-object form. Authoritative references: Delete a customer, Cancel a subscription, and Stripe error codes.

Verification against the exact published source:

text
# cwd apps/oshun/bff; provider ordering, fail closure, acknowledgement-loss
# reconciliation, stable key, local-only deletion, and live wrapper transport
pnpm exec vitest run --config vitest.config.ts \
  src/payments/fiat-stripe-store-durability.spec.ts --maxWorkers=1
  1 file, 11/11 tests passed

# repository root; strict Stripe DELETE/GET transport and response validation
pnpm exec vitest run \
  libs/oshun/fiat-payments/src/stripe/client.test.ts --maxWorkers=1
  1 file, 9/9 tests passed

# cwd apps/oshun/bff; connected route, eraser, and export regressions
pnpm exec vitest run src/payments/fiat-routes.test.ts --maxWorkers=1
  17/17 tests passed
pnpm exec vitest run \
  src/data-deletion/profile-state-eraser.test.ts --maxWorkers=1
  7/7 tests passed
pnpm exec vitest run src/data-export/bundle-builder.test.ts --maxWorkers=1
  24/24 tests passed

# cwd apps/oshun/bff; real PostgreSQL provider-confirmed snapshot transition,
# persisted pseudonym/fence, and fresh-process restart proof
OSHUN_V1_DATABASE_URL=<live-local-postgres> pnpm exec vitest run \
  --config vitest.integration.config.ts \
  src/payments/fiat-stripe-store-durability.integration.spec.ts \
  --maxWorkers=1
  1 file, 1/1 test passed

# repository root; exact production-package and BFF checks
pnpm nx run @oshun/fiat-payments:typecheck
pnpm nx run @oshun/fiat-payments:test
node tools/typecheck/ratchet.mjs --app apps/oshun/bff \
  --tsconfig tsconfig.typecheck.json
  passed; BFF app-own type-error backlog 0

# cwd apps/oshun/bff; exact production entry
pnpm exec esbuild src/server.ts --bundle --platform=node --format=esm \
  --target=node22 --outfile=dist/server.js --sourcemap
  passed; 32.5 MB bundle and 76.6 MB source map

production-source ESLint, changed-file Prettier, git diff check, and commit hooks
  passed
affected hook typechecks: @oshun/fiat-payments,
  @oshun/prompt-injection-evals, and @oshun/bff passed

# after clean rebase onto origin/main
store 11/11, Stripe client 9/9, and production BFF bundle passed again
published source HEAD == origin/main ==
  1ecef2d5c36ae810d5666b2434752736aa44d42d

The PostgreSQL check used a real database and a deterministic provider seam; it did not delete a production or live-test Stripe Customer. No provider receipt from a customer account is claimed. This source proves the production transport, strict acknowledgement/reconciliation protocol, durable local ordering, and restart behavior. Provider-side invoices, financial records required by law, and Stripe's reduced deleted-Customer tombstone may remain under Stripe's own retention obligations; this is not represented as total provider-record purge.

This closes only the Stripe Customer deletion boundary in the still-open all-store row. Apple and Google purchase-provider dispositions were still open in that slice, and the shared legal-hold- and retention-exception-aware purge executor was not yet connected there. No rendered UI, mobile flow, schema migration, model generation, or Unreal content changed, so Playwright, mobile UI, migration, model, and Unreal automation were inapplicable. The protected user lockfile remained byte-identical at Git blob a37431842e330b3a06b030947c25bebdc72bc2b1 and was not published.

Shared compliance retention and Fiat Stripe expiry-purge verification#

Source and published implementation: 068f2a2619f01933181773302c7d2b3056040366. This slice adds the reusable compliance-retention evaluator and connects its first real partition: locally retained Fiat Stripe pseudonyms. New account redactions durably record the redaction timestamp, a 2,555-day retain-until boundary is evaluated before traffic and by a supervised hourly worker, and an eligible candidate physically loses its pseudonymous Customer/subscription binding and pending-checkout attribution in one ordered durable snapshot. The irreversible SHA-256 subject fence and purge timestamp remain, so expiry cannot reopen stale account recreation. Provider event IDs and the bounded payment bus contain no local subject owner field and are not represented as subject-row purges.

The shared authority view is assembled from every hydrated durable admin workspace. Active and pending-release legal holds block every matching subject; active or expiring exceptions block only the matching subject and data category through their effective time. Invalid active-exception expiry is fail-closed. Released/revoked holds, revoked/expired exceptions, unrelated subjects, and unrelated categories do not suppress a due purge. Outcomes distinguish not due, missing retention anchor, legal-hold blocked, exception blocked, and purged, with stable partition/category/digest/blocker/count metadata.

Legacy redactions deliberately restore with a null retention anchor. The worker does not invent an historical deletion time and therefore cannot purge them. If the canonical account-erasure operation is replayed, it can durably establish a new conservative anchor; this retains data longer rather than risking an early purge. Corrupt digest/timestamp/orphan/duplicate state, a purge before redaction, rows remaining behind a recorded purge, duplicate partitions or candidates, and invalid partition counts fail validation.

Verification against the exact published source:

text
# cwd apps/oshun/bff; evaluator authority/status/expiry/fail-closure plus
# Stripe redaction anchor, physical purge, adjacent isolation, and restart fence
pnpm exec vitest run --config vitest.config.ts \
  src/privacy/compliance-retention-executor.spec.ts \
  src/payments/fiat-stripe-store-durability.spec.ts --maxWorkers=1
  2 files, 20/20 tests passed

# cwd apps/oshun/bff; connected billing route, profile eraser, and DSAR export
pnpm exec vitest run --config vitest.config.ts \
  src/payments/fiat-routes.test.ts --maxWorkers=1
  17/17 tests passed
pnpm exec vitest run --config vitest.config.ts \
  src/data-deletion/profile-state-eraser.test.ts --maxWorkers=1
  7/7 tests passed
pnpm exec vitest run --config vitest.config.ts \
  src/data-export/bundle-builder.test.ts --maxWorkers=1
  24/24 tests passed

# cwd apps/oshun/bff; real PostgreSQL provider-confirmed redaction,
# seven-year expiry purge, persisted fence/timestamp, and fresh restart proof
OSHUN_V1_DATABASE_URL=<live-local-postgres> pnpm exec vitest run \
  --config vitest.integration.config.ts \
  src/payments/fiat-stripe-store-durability.integration.spec.ts \
  --maxWorkers=1
  1 file, 1/1 test passed

# repository root; exact BFF type ratchet
node tools/typecheck/ratchet.mjs --app apps/oshun/bff \
  --tsconfig tsconfig.typecheck.json
  no new app-own type errors; backlog 0

# all six changed source/test files
pnpm exec eslint --no-warn-ignored <changed-files>
pnpm exec prettier --check <changed-files>
git diff --check
  passed

# cwd apps/oshun/bff; exact production entry
pnpm exec esbuild src/server.ts --bundle --platform=node --format=esm \
  --target=node22 --outfile=dist/server.js --sourcemap
  passed; 32.5 MB bundle and 76.7 MB source map

# affected commit hook
nx affected --target=typecheck --files=<six changed files> --parallel=4
  @oshun/bff and @oshun/prompt-injection-evals passed

# after clean rebase onto origin/main; no changed-file overlap
executor/store 20/20 and production BFF bundle passed again
published source HEAD == origin/main ==
  068f2a2619f01933181773302c7d2b3056040366

Expensive checks ran one at a time except the repository-mandated two-project affected hook. The host had 15 GiB RAM and 31 GiB swap; the BFF TypeScript process peaked around 5.9 GiB RSS while available memory remained above the stop threshold. A concurrent unrelated dependency command was observed and allowed to finish before the commit hook; it left no staged or tracked manifest change in this slice.

This is partial shared-executor progress, not full compliance-retention closure. Only the Fiat Stripe partition is connected. The customer billing store, customer consent, data-export request metadata, scene financial-tip evidence, customer feedback, Themis moderation appeals, Living Scene abuse reports, Metis academic evidence, and any other compliance-retained partition still need durable retention anchors plus physical purge adapters. Apple and Google purchase-provider disposition was also still open in that slice. No live Stripe call, production deletion, rendered UI, mobile flow, schema migration, model generation, or Unreal content changed in this slice. Playwright/mobile, live-provider, migration, model, and Unreal automation were therefore inapplicable. The protected user lockfile remained byte-identical at Git blob a37431842e330b3a06b030947c25bebdc72bc2b1 and was not published.

Customer billing expiry purge and purchase-provider disposition verification#

Source and published implementation: 7c93da74220ddac485f90c4de72e4c71ea62c070. The shared executor now evaluates both real billing partitions in one authority view and ordered worker run. Each new customer-billing redaction receives the canonical 2,555-day billing_history anchor. Once due and not blocked, the durable purge removes that pseudonym's subscription, tenure, trial, pause, cancellation/save/churn, family-plan ownership or seat, scholar-verification, Apple purchase binding, and Google Play token-digest records. The irreversible subject digest and purge timestamp remain as the account-recreation fence.

New Apple replay IDs are now durably attributed to their original-transaction chain at registration. Expiry can therefore remove the subject's original transaction binding and every replay ID on that chain while retaining an adjacent member's Apple chain. A pre-upgrade replay ID has no trustworthy owner link, so the migration deliberately leaves it as an unattributed global replay fence rather than guessing an owner or claiming it was subject-purged. Legacy redactions likewise restore with a null retention anchor; a canonical erasure replay may start a conservative new window. Duplicate/invalid retention state, an attributed Apple replay ID with an unknown replay or missing original chain, purge-before-redaction, and any pseudonymous row remaining behind a recorded purge fail snapshot validation.

Provider disposition was checked against the current official surfaces:

  • Apple's account-deletion guidance says Apple-billed auto-renewal continues through Apple unless the customer cancels, directs apps to the system subscription manager or Apple's management link, and still requires an immediate account-deletion option. The documented flow does not give the app merchant a transaction-deletion operation.
  • Google Play subscription cancellation and revocation both require the raw purchase token. The resource exposes get, cancel, defer, and revoke operations, not purchase-record deletion. This BFF intentionally persists only the token's SHA-256 digest, so it cannot honestly call either mutation after erasure.
  • Google Play's account-deletion policy permits subscription-cancellation steps when they are clearly explained and supported, and requires disclosure when data is retained for legitimate compliance reasons.

The no-provider-record-deletion conclusion above is an inference from those official documented operation sets, not a claim about either provider's internal retention. This slice therefore performs no live Apple/Google mutation and fabricates no provider receipt. Their remote financial records remain under provider control; local raw Apple identifiers and Play digests are governed by the legal-hold/exception-aware purge. Transparent client cancellation guidance and an optional secret-safe Google cancellation binding remain separate open work.

Verification against the exact published source:

text
# cwd apps/oshun/bff; billing retention/replay-chain/purge/restart proof,
# Apple/Google route behavior, and shared authority/status/fail-closure
pnpm exec vitest run --config vitest.config.ts \
  src/billing-support/billing-store-durability.spec.ts \
  src/routes/billing-app-store-route.test.ts \
  src/privacy/compliance-retention-executor.spec.ts --maxWorkers=1
  3 files, 41/41 tests passed

# cwd apps/oshun/bff; connected profile erasure, DSAR export, and Fiat routes
pnpm exec vitest run --config vitest.config.ts \
  src/data-deletion/profile-state-eraser.test.ts \
  src/data-export/bundle-builder.test.ts \
  src/payments/fiat-routes.test.ts --maxWorkers=1
  3 files, 48/48 tests passed

# cwd apps/oshun/bff; real PostgreSQL redaction anchor, physical purge,
# persisted absence/timestamp, restart fence, and Play-token-digest absence
OSHUN_V1_DATABASE_URL=<live-local-postgres> pnpm exec vitest run \
  --config vitest.integration.config.ts \
  src/billing-support/billing-store-durability.integration.spec.ts \
  --maxWorkers=1
  1 file, 1/1 test passed

# repository root; exact final BFF type ratchet
node tools/typecheck/ratchet.mjs --app apps/oshun/bff \
  --tsconfig tsconfig.typecheck.json
  no new app-own type errors; backlog 0

# all five changed source/test files
pnpm exec eslint --no-warn-ignored <changed-files>
pnpm exec prettier --check <changed-files>
git diff --check
  passed

# cwd apps/oshun/bff; exact final production entry
pnpm exec esbuild src/server.ts --bundle --platform=node --format=esm \
  --target=node22 --outfile=dist/server.js --sourcemap
  passed; 32.5 MB bundle and 76.7 MB source map

# affected commit hook
nx affected --target=typecheck --files=<five changed files> --parallel=4
  @oshun/bff and @oshun/prompt-injection-evals passed

# after clean rebase onto origin/main; no remote changed-file overlap
focused billing/provider/executor suite passed again at 41/41
published source HEAD == origin/main ==
  7c93da74220ddac485f90c4de72e4c71ea62c070

Expensive verification ran one gate at a time except the repository-mandated two-project affected hook. The host had 15 GiB RAM and 31 GiB swap. The BFF TypeScript process peaked around 5.9 GiB RSS; available memory remained above 5 GiB and no stop threshold was crossed. No rendered UI, mobile flow, schema migration, model generation, Unreal content, or live provider account changed, so Playwright/mobile, migration, model, Unreal, and live-provider automation were inapplicable. The protected user lockfile remained byte-identical at Git blob a37431842e330b3a06b030947c25bebdc72bc2b1 and was not published.

This closes the customer-billing executor adapter and establishes an honest Apple/Google remote-record disposition; it did not close V1-002. At that source boundary, consent, data-export request, scene-tip financial evidence, all support_case partitions, Metis academic evidence, and the remaining compliance inventory still needed anchors and physical purge adapters. Subscription-cancellation UX also remained open.

Customer data-export request expiry-purge verification#

Source and published implementation: 8beaa6c940b5971d8516874f3830a28273d53f73. The shared compliance executor now evaluates customer data-export request metadata alongside customer billing and Fiat Stripe state in one hydrated authority view. Full-account erasure durably rekeys the subject ledger to redacted:<sha256>, nulls every live download URL and caller-derived failure reason, records a 2,555-day data_export_request retention anchor, and installs the same irreversible subject fence used to reject stale or replayed writes. The request metadata is retained for compliance; the exact short-lived bundle bytes remain a separate generated-artifact partition with their existing expiry and erasure behavior.

At expiry, active/pending-release legal holds block the subject and an active category-matching retention exception blocks only data_export_request. With neither blocker, the ordered durable purge physically removes every request row under the pseudonym while retaining only the one-way fence, redaction timestamp, and purge timestamp. The adjacent-account proofs cover both redaction and purge. Legacy redactions without a trustworthy clock restore with a null anchor and defer instead of guessing an early purge date; replaying canonical account erasure may establish a conservative new anchor. Snapshot hydration rejects invalid or noncanonical digests, duplicate identities or export IDs, invalid revisions/timestamps, purge-before-redaction, unknown or already-purged pseudonyms, and direct-subject resurrection behind a fence.

Verification against the exact published source:

text
# cwd apps/oshun/bff; durable redaction, URL/free-text scrubbing, fence,
# shared legal-hold/category-exception blocking, physical purge, legacy
# migration, snapshot corruption, and executor fail-closure
pnpm exec vitest run --config vitest.config.ts \
  src/data-export/state.test.ts \
  src/privacy/compliance-retention-executor.spec.ts --maxWorkers=1
  2 files, 23/23 tests passed

# cwd libs/contracts; canonical privacy categories and retention workflow
pnpm exec vitest run \
  src/common/admin-privacy.spec.ts \
  src/common/admin-retention-exception-workflow.spec.ts --maxWorkers=1
  2 files, 22/22 tests passed
pnpm exec tsc -p tsconfig.lib.json --noEmit
  passed

# cwd apps/oshun/bff; customer export route failure atomicity and schemas
pnpm exec vitest run --config vitest.config.ts \
  src/__tests__/data-export-route.test.ts --maxWorkers=1
  1 file, 23/23 tests passed

# cwd apps/oshun/bff; connected profile eraser and cross-endpoint
# export/deletion/admin workflow
pnpm exec vitest run --config vitest.config.ts \
  src/data-deletion/profile-state-eraser.test.ts --maxWorkers=1
  1 file, 7/7 tests passed
pnpm exec vitest run --config vitest.integration.config.ts \
  src/__tests__/export-deletion-flows.integration.test.ts --maxWorkers=1
  1 file, 14/14 tests passed

# cwd apps/oshun/bff; real PostgreSQL pseudonymization, seven-year purge,
# persisted absence/timestamps/fence, adjacent preservation, and two restarts
OSHUN_V1_DATABASE_URL=<live-local-postgres> pnpm exec vitest run \
  --config vitest.integration.config.ts \
  src/data-export/customer-data-export-durability.integration.spec.ts \
  --maxWorkers=1
  1 file, 1/1 test passed

# repository root; exact final BFF type ratchet
node tools/typecheck/ratchet.mjs --app apps/oshun/bff \
  --tsconfig tsconfig.typecheck.json
  no new app-own type errors; backlog 0

# changed executable/test/contract files
pnpm exec eslint --no-warn-ignored <changed-files>
pnpm exec prettier --check <changed-files>
git diff --check
  passed (admin/state.ts retains only its pre-existing warning backlog)

# cwd apps/oshun/bff; exact production entry
pnpm run build
  passed; 32.0 MB bundle and 75.6 MB source map

# clean rebase onto origin/main; no relevant changed-file overlap
published source HEAD == origin/main ==
  8beaa6c940b5971d8516874f3830a28273d53f73

Expensive verification ran one gate at a time with memory polling. The host had 15 GiB RAM and 31 GiB swap. A commit hook attempted to expand the staged change into a 301-project workspace typecheck; it was stopped because the repository's sub-32-GiB safety rule requires explicit approval for that broad gate. The targeted zero-backlog BFF ratchet, contracts typecheck, focused suites, real database proof, and production bundle above all passed. No rendered UI, mobile flow, schema migration, model generation, Unreal content, or live provider account changed, so Playwright/mobile, migration, model, Unreal, and live-provider automation were inapplicable. The protected user lockfile remained byte-identical at Git blob a37431842e330b3a06b030947c25bebdc72bc2b1 and was not published.

This closes the customer data-export request-metadata purge adapter, not V1-002. At that source boundary, canonical consent records, scene-tip financial evidence, all remaining support_case partitions, scheduled Metis academic- evidence purge, and the rest of the compliance inventory still required equivalent retention anchors and physical-purge adapters. Subscription-cancellation UX also remained open.

Source and published implementation: d862143ff8b79f127e93cfaa87c9a2c7d4bf979c. The shared compliance worker now evaluates canonical consent records after customer billing, Fiat Stripe state, and data-export request metadata have all hydrated. Full-account erasure durably rekeys the subject's complete per-flow current state, decision evidence, and unbounded retained history to redacted:<sha256>. It replaces caller-supplied evidence labels with bounded type-derived labels; nulls evidence URIs and notes plus subject/operator reasons and notes; retains only bounded system-authored policy notes; and preserves the canonical flow, status, policy, verification, reason-code, timestamp, expiry, and withdrawal-cascade authority needed to prove the historical decision.

The same ordered snapshot records a 2,555-day consent_record anchor and an irreversible recreation fence. At expiry, a matching active/pending-release legal hold blocks the subject and an active category-matching exception blocks only consent records. With neither blocker, physical purge removes every pseudonymous flow and revision while retaining only the one-way subject digest, redaction clock, and purge clock. Failed redaction and failed purge saves leave both live and durable snapshots unchanged. Adjacent subjects survive every transition. Legacy redactions without a trustworthy clock defer until a conservative erasure replay supplies an anchor. Hydration rejects duplicate or noncanonical digests, invalid retention state or clocks, purge-before-redaction, unknown or already-purged pseudonyms, and direct-subject resurrection.

Verification against the exact published source:

text
# cwd apps/oshun/bff; decision/evidence recovery, retention scrubbing,
# replay fence, failed-save atomicity, shared hold/exception blocking,
# physical purge, adjacent isolation, legacy migration, and corruption
pnpm exec vitest run \
  src/consent/state-durability.spec.ts \
  src/privacy/compliance-retention-executor.spec.ts --maxWorkers=1
  2 files, 18/18 tests passed

# cwd apps/oshun/bff; consent authority across direct routes and its
# residency, persona, mentor-presence, and export consumers
pnpm exec vitest run \
  src/__tests__/consent-route.test.ts \
  src/__tests__/mentor-presence-route.test.ts \
  src/__tests__/residency-routing.test.ts \
  src/routes/personas-consumer.test.ts --maxWorkers=1
  4 files, 55/55 tests passed
pnpm exec vitest run \
  src/__tests__/data-export-route.test.ts --maxWorkers=1
  1 file, 23/23 tests passed

# cwd apps/oshun/bff; real PostgreSQL decision/expiry recovery followed by
# pseudonymization, PII scrubbing, expiry purge, persisted clocks/fence,
# adjacent preservation, and post-purge restart
OSHUN_V1_DATABASE_URL=<live-local-postgres> pnpm exec vitest run \
  --config vitest.integration.config.ts \
  src/consent/state-durability.integration.spec.ts --maxWorkers=1
  1 file, 1/1 test passed

# repository root; exact final BFF type ratchet
node tools/typecheck/ratchet.mjs --app apps/oshun/bff \
  --tsconfig tsconfig.typecheck.json
  no new app-own type errors; backlog 0

# all nine changed source/test files
pnpm exec eslint --no-warn-ignored --max-warnings=0 <changed-files>
pnpm exec prettier --check <changed-files>
git diff --check
  passed

# cwd apps/oshun/bff; exact production entry
pnpm run build
  passed; 32.0 MB bundle and 75.6 MB source map

# repository pre-commit affected owner/consumer typecheck
nx affected --target=typecheck --files=<nine BFF files> --parallel=4
  @oshun/bff and @oshun/prompt-injection-evals passed

# source published without intervening rebase overlap
published source HEAD == origin/main ==
  d862143ff8b79f127e93cfaa87c9a2c7d4bf979c

Expensive checks ran one gate at a time except the repository hook's bounded two-project typecheck, with memory polled throughout. The host had 15 GiB RAM and 31 GiB swap; available memory remained well above the stop threshold. No rendered UI, mobile flow, schema migration, model generation, Unreal content, or live provider account changed, so Playwright/mobile, migration, model, Unreal, and live-provider automation were inapplicable. The protected user lockfile remained byte-identical at Git blob a37431842e330b3a06b030947c25bebdc72bc2b1 and was not published.

This closes the canonical consent-record purge adapter, not V1-002. At that source boundary, scene-tip financial evidence, all remaining support_case partitions, scheduled Metis academic-evidence purge, and the rest of the compliance inventory still required equivalent retention anchors and physical purge adapters. Subscription-cancellation UX also remains open.

Scene financial-tip expiry verification#

Source and published implementation: 5e22686cf704fbd3f89c009cffc839b3f3c484f1. The shared compliance worker now evaluates the scene tip ledger after hydrating its ordered snapshot and every earlier compliance partition. Full-account erasure rekeys every exact viewer, creator, and counsel-authority-recorder reference to redacted:<sha256>, installs the irreversible subject fence, and records a 2,555-day billing_history anchor. Legacy pseudonyms without a trustworthy redaction clock restore with a null anchor and defer; replaying the canonical erasure may conservatively start a new window.

This ledger contains shared financial facts: one tip is evidence for both its viewer and creator, and a payout settlement's exact gross, fee, and net depend on the complete preceding accrual. Deleting the whole row when only one party's window expires would either destroy the adjacent counterparty's retained evidence or require falsifying the settlement. The expiry adapter instead physically removes every stored link to the due pseudonym. It atomically replaces that redacted:<subject-digest> reference across tip, settlement, and authority rows with one cryptographically random purged:<nonce> tombstone, and deliberately stores no digest-to-tombstone mapping. Amounts, currency, rail, sequence, running accrual, exact 10-percent fee split, settlement, counsel authority, and adjacent identity remain unchanged. The one-way digest survives only as the recreation fence beside the redaction and purge clocks.

An active or pending-release legal hold blocks the subject. A retention exception that includes billing_history blocks only that category. With neither blocker, the ordered save commits the unlinking and purge clock together; a failed save leaves the prior live and durable views byte-for-byte unchanged. Hydration rejects duplicate, unsorted, missing, or invalid retention state; purge before redaction; unknown or already-purged pseudonyms; malformed reserved identities; and direct-subject resurrection. The same random tombstone is used for all of the subject's references in one ledger so historical balance grouping remains exact, but it is never accepted as a new viewer, creator, or authority recorder.

Verification against the exact published source:

text
# cwd apps/oshun/bff; durability, financial arithmetic, authority blocking,
# failed-save atomicity, legacy migration, corruption, unlinking, and fence
pnpm exec vitest run \
  src/scene-experience/tip-ledger-store-durability.spec.ts \
  src/privacy/compliance-retention-executor.spec.ts --maxWorkers=1
  2 files, 14/14 tests passed

# cwd apps/oshun/bff; tip API, billing-receipt DSAR, and profile erasure fanout
pnpm exec vitest run \
  src/routes/scene-tips.test.ts \
  src/data-export/bundle-builder.test.ts \
  src/data-deletion/profile-state-eraser.test.ts --maxWorkers=1
  3 files, 40/40 tests passed

# cwd apps/oshun/bff; real PostgreSQL accrual/settlement recovery,
# redaction anchor, adjacent preservation, expiry unlinking, persisted clock,
# restart arithmetic, and recreation fence
OSHUN_V1_DATABASE_URL=<live-local-postgres> pnpm exec vitest run \
  --config vitest.integration.config.ts \
  src/scene-experience/tip-ledger-store-durability.integration.spec.ts \
  --maxWorkers=1
  1 file, 1/1 test passed

# repository root; exact final BFF type ratchet
node tools/typecheck/ratchet.mjs --app apps/oshun/bff \
  --tsconfig tsconfig.typecheck.json
  no new app-own type errors; backlog 0

# second affected project identified by the repository hook
pnpm exec tsc --noEmit -p testing/prompt-injection/tsconfig.json
  passed

# all four changed source/test files
pnpm exec eslint --no-warn-ignored --max-warnings=0 <changed-files>
pnpm exec prettier --check <changed-files>
git diff --check
  passed

# cwd apps/oshun/bff; exact production entry
pnpm run build
  passed; 32.0 MB bundle and 75.6 MB source map

# clean rebase over eight origin/main commits; no changed-file overlap
published source HEAD == origin/main ==
  5e22686cf704fbd3f89c009cffc839b3f3c484f1

The normal pre-commit lint, formatting, conventions-ratchet, V5-docs, and asset locking steps passed. Its Nx affected step identified exactly @oshun/bff and @oshun/prompt-injection-evals, but a manual interrupt issued while Nx was stuck building the project graph landed seven seconds after the graph finally completed, cancelling both checks rather than reporting a type error. Both exact commands were therefore run and passed independently before the source commit; that commit used SKIP_TYPECHECK=1 only to avoid repeating the wedged orchestration.

Expensive checks ran one gate at a time except Nx's brief cancelled two-project attempt. The host had 15 GiB RAM and 31 GiB swap. The BFF TypeScript process peaked near 5.2 GiB RSS while available memory remained above 6 GiB. No rendered UI, mobile flow, schema migration, payment-provider operation, model generation, Unreal content, or production deletion changed, so Playwright/mobile, migration, provider, model, Unreal, and production-operations automation were inapplicable. The protected user lockfile remained byte-identical at Git blob a37431842e330b3a06b030947c25bebdc72bc2b1 and was not published.

This closes the scene financial-tip retention adapter, not V1-002. All remaining support_case partitions, scheduled Metis academic-evidence purge, the remaining compliance inventory, and subscription-cancellation UX remain open.

Customer-feedback support-case expiry verification#

Source and published implementation: c8e99bf217937a9797c1cee9218d1955ec6d5d60. The shared compliance worker now evaluates the customer-feedback store after hydrating its ordered snapshot and the earlier compliance partitions. Full- account erasure removes submitter identity, operator-facing contact email, contact-consent state, and caller-authored contact fields; replaces the exact account key with redacted:<sha256>; records a 1,825-day support_case anchor; and installs an irreversible subject fence.

An active or pending-release legal hold blocks the subject. A retention exception that includes support_case blocks only that category. With neither blocker, one ordered durable save physically removes every retained case under the pseudonym while preserving the one-way digest, redaction clock, and purge clock. Adjacent subjects survive redaction and purge. A failed save leaves the live and persisted snapshots unchanged. Legacy redactions without a trustworthy clock defer rather than receiving an invented deletion date; replaying canonical erasure may establish a conservative new window. Hydration rejects duplicate or unsorted retention entries, invalid clocks, purge before redaction, retained rows after purge, unknown or already-purged pseudonyms, and direct-subject resurrection. Reserved redacted: and purged: account IDs cannot enter through new feedback writes.

Verification against the exact published source:

text
# cwd apps/oshun/bff; retention migration/corruption, redaction, shared
# hold/exception authority, expiry, failed-save atomicity, adjacent isolation,
# restart fence, connected profile erasure, feedback routes, and DSAR export
pnpm exec vitest run --config vitest.config.ts \
  src/feedback/feedback-intake-store-durability.spec.ts \
  src/privacy/compliance-retention-executor.spec.ts \
  src/data-deletion/profile-state-eraser.test.ts \
  src/feedback/feedback-intake-store.test.ts \
  src/routes/feedback-route.test.ts \
  src/data-export/export-bundle-builder.test.ts --maxWorkers=1
  6 files, 61/61 tests passed

# cwd apps/oshun/bff; real PostgreSQL redaction, adjacent-row preservation,
# executor purge, persisted physical absence, and restart resurrection fence
OSHUN_ADMIN_DATABASE_URL=<local-postgresql> pnpm exec vitest run \
  src/feedback/feedback-intake-store-durability.integration.spec.ts \
  --config vitest.integration.config.ts
  1 file, 1/1 test passed

# cwd apps/oshun/bff; strict changed-source lint and formatting
pnpm exec eslint \
  src/feedback/feedback-intake-store-durability.integration.spec.ts \
  src/feedback/feedback-intake-store-durability.spec.ts \
  src/feedback/feedback-intake-store.ts src/server.ts \
  --max-warnings=0
  passed
pnpm exec prettier --check \
  src/feedback/feedback-intake-store-durability.integration.spec.ts \
  src/feedback/feedback-intake-store-durability.spec.ts \
  src/feedback/feedback-intake-store.ts src/server.ts
  passed

# repository root; zero-backlog BFF ratchet and production bundle
pnpm run typecheck:app -- apps/oshun/bff
  passed; no new app-own type errors, backlog 0
pnpm nx run @oshun/bff:build
  passed; server bundle 32.1 MB, source map 75.6 MB

# source commit hook; exact affected project typechecks
pnpm exec nx affected --target=typecheck \
  --files=apps/oshun/bff/src/feedback/feedback-intake-store-durability.integration.spec.ts,apps/oshun/bff/src/feedback/feedback-intake-store-durability.spec.ts,apps/oshun/bff/src/feedback/feedback-intake-store.ts,apps/oshun/bff/src/server.ts \
  --parallel=4
  @oshun/bff:typecheck passed
  @oshun/prompt-injection-evals:typecheck passed

The source hook also passed lint-staged, asset-locking, import-baseline, and V5 documentation gates. Expensive BFF checks ran one at a time before the hook; its two affected typechecks then ran together as configured. The host had 15 GiB RAM and 31 GiB swap. The largest BFF TypeScript process peaked near 5.5 GiB RSS while available memory remained above the stop threshold. No UI, mobile flow, schema migration, provider operation, model generation, Unreal content, or production deletion changed, so Playwright/mobile, migration, provider, model, Unreal, and production-operations automation were inapplicable. The protected user lockfile remained byte-identical at Git blob a37431842e330b3a06b030947c25bebdc72bc2b1 and was not published.

This closes the customer-feedback retention adapter, not V1-002. The Themis moderation-appeal and Living Scene abuse-report support_case partitions, scheduled Metis academic-evidence purge, the remaining compliance inventory, and subscription-cancellation UX remain open.

Themis moderation-appeal support-case expiry verification#

Source and published implementation: abe4159c3b4de8f6bd716117d426d8a11a9fc146. The shared compliance worker now evaluates the durable Themis moderation-appeal authority after hydrating it with the earlier compliance partitions. Full- account erasure removes appellant-authored narrative and evidence references, hashes the appeal, statement, and action identifiers, rekeys both owner and appellant identity to redacted:<sha256>, records a 1,825-day support_case anchor, and installs an irreversible subject fence. Categorical DSA intake, policy, routing, status, filing, and resolution-deadline evidence remains during the bounded compliance window.

An active or pending-release legal hold blocks the subject. A retention exception that includes support_case blocks only that category. With neither blocker, one ordered durable save physically removes every retained appeal under the pseudonym while preserving only the one-way digest, redaction clock, and purge clock. Adjacent appellants survive redaction and purge. A failed save leaves live and persisted snapshots unchanged. Legacy redactions without a trustworthy clock defer instead of receiving an invented deletion date; replaying canonical erasure may establish a conservative new window. Hydration rejects duplicate or unsorted retention entries, invalid clocks, purge before redaction, appeals retained after purge, unknown pseudonyms, and direct-subject resurrection. Reserved redacted: and purged: owner IDs cannot enter through new appeal filings.

Verification against the exact published source:

text
# cwd apps/oshun/bff; migration/corruption, DSA authority, redaction, shared
# hold/exception blocking, exact-boundary expiry, failed-save atomicity,
# adjacent isolation, restart fence, profile erasure, routes, and DSAR export
pnpm exec vitest run \
  src/themis/moderation-appeal-store-durability.spec.ts \
  src/privacy/compliance-retention-executor.spec.ts \
  src/data-deletion/profile-state-eraser.test.ts \
  src/__tests__/themis-route.test.ts \
  src/data-export/bundle-builder.test.ts \
  --config vitest.config.ts --maxWorkers=1
  5 files, 56/56 tests passed

# cwd apps/oshun/bff; real PostgreSQL redaction, executor purge, persisted
# physical absence, adjacent preservation, and restart resurrection fence
OSHUN_ADMIN_DATABASE_URL=<local-postgresql> pnpm exec vitest run \
  src/themis/moderation-appeal-store-durability.integration.spec.ts \
  --config vitest.integration.config.ts
  1 file, 1/1 test passed

# cwd apps/oshun/bff; strict changed-source lint and formatting
pnpm exec eslint \
  src/themis/moderation-appeal-store.ts \
  src/themis/moderation-appeal-store-durability.spec.ts \
  src/themis/moderation-appeal-store-durability.integration.spec.ts \
  src/server.ts --max-warnings=0 --no-warn-ignored
  passed
pnpm exec prettier --check \
  src/themis/moderation-appeal-store.ts \
  src/themis/moderation-appeal-store-durability.spec.ts \
  src/themis/moderation-appeal-store-durability.integration.spec.ts \
  src/server.ts
  passed

# repository root; zero-backlog app-own type ratchet
node tools/typecheck/ratchet.mjs \
  --app apps/oshun/bff --tsconfig tsconfig.typecheck.json
  passed; no new app-own type errors, backlog 0

# cwd apps/oshun/bff; deployable package entry bundle
pnpm run build
  passed; server bundle 32.1 MB, source map 75.6 MB

# repository root; declared BFF Nx target without unrelated dependency tasks
pnpm nx run @oshun/bff:build --excludeTaskDependencies
  passed; server bundle 32.6 MB, source map 76.8 MB

# first source-commit attempt; exact affected project typechecks passed before
# commitlint rejected only the capitalized commit subject
pnpm exec nx affected --target=typecheck \
  --files=apps/oshun/bff/src/server.ts,apps/oshun/bff/src/themis/moderation-appeal-store-durability.integration.spec.ts,apps/oshun/bff/src/themis/moderation-appeal-store-durability.spec.ts,apps/oshun/bff/src/themis/moderation-appeal-store.ts \
  --parallel=4
  @oshun/bff:typecheck passed; backlog 0
  @oshun/prompt-injection-evals:typecheck passed

The dependency-inclusive pnpm nx run @oshun/bff:build discovery attempt was stopped after an unrelated prerequisite, @oshun/audit-platform, failed its declaration build on the existing TypeScript 6 baseUrl deprecation; the BFF target had not run. The two commands above then proved the deployable entry bundle and declared target directly. The first source-commit attempt passed all pre-commit gates and both affected typechecks before commitlint rejected only the capitalized word in its subject. The successful lowercase commit reran lint-staged, asset-locking, import-baseline, and V5 documentation gates and used SKIP_TYPECHECK=1 solely to avoid repeating those just-completed exact typechecks.

Expensive verification ran one gate at a time except the hook's configured two- project typecheck. The host had 15 GiB RAM and 31 GiB swap. The largest BFF TypeScript process peaked near 5.4 GiB RSS while available memory remained above the stop threshold. No UI, mobile flow, schema migration, provider operation, model generation, Unreal content, or production deletion changed, so Playwright/mobile, migration, provider, model, Unreal, and production-operations automation were inapplicable. The protected user lockfile remained byte- identical at Git blob a37431842e330b3a06b030947c25bebdc72bc2b1 and was not published.

This closes the Themis moderation-appeal retention adapter, not V1-002. The Living Scene abuse-report support_case partition is closed below; scheduled Metis academic-evidence purge, the remaining compliance inventory, and subscription-cancellation UX remain open.

Living Scene abuse-report support-case expiry verification#

Source and published implementation: 7544b773daa7c9aec87a29a28e7a95f093facd3e. The shared compliance worker now evaluates the durable Living Scene abuse-report authority as its eighth connected partition. Full-account erasure hashes the report identifier, replaces reporter or action-actor identity with redacted:<sha256>, removes reporter-authored detail and an erased actor's resolution note, records a 1,825-day support_case anchor, and installs an irreversible subject fence. This store has two subject roles, so expiry preserves adjacent-account evidence without preserving a link to the erased subject.

An active or pending-release legal hold blocks the subject. A retention exception that includes support_case blocks only that category. At the exact due boundary with neither blocker, one ordered durable save physically deletes every case owned by the pseudonymous reporter. If the same subject appears only as the action actor on another reporter's case, expiry removes its resolution note and replaces all such actor links with one fresh random purged-actor:<256-bit-value> tombstone. The store retains no digest-to- tombstone mapping; adjacent reporter identity, intake category, narrative, status, and timestamps remain intact. A failed save leaves live and persisted snapshots unchanged. Legacy redactions without a trustworthy clock defer rather than receiving an invented deletion date; replaying canonical erasure may establish a conservative new window. Hydration rejects duplicate, omitted, or unsorted retention entries, invalid clocks, purge before redaction, subject pseudonyms retained after purge, malformed redacted: or purged-actor: identifiers, and direct-subject resurrection. Reserved pseudonyms cannot enter through new report or action writes.

Verification against the exact published source:

text
# cwd apps/oshun/bff; migration/corruption, two-role redaction, shared
# hold/exception blocking, exact-boundary expiry, failed-save atomicity,
# adjacent isolation, restart fence, connected erasure/routes, and DSAR export
pnpm exec vitest run \
  src/living-scenes/abuse-report-store-durability.spec.ts \
  src/privacy/compliance-retention-executor.spec.ts \
  src/data-deletion/profile-state-eraser.test.ts \
  src/__tests__/admin-abuse-reports-route.test.ts \
  src/__tests__/living-scenes-route.test.ts \
  src/__tests__/my-abuse-reports-route.test.ts \
  src/data-export/bundle-builder.test.ts \
  --config vitest.config.ts --maxWorkers=1
  7 files, 83/83 tests passed

# cwd apps/oshun/bff; final reserved-pseudonym regression and executor suite
pnpm exec vitest run \
  src/living-scenes/abuse-report-store-durability.spec.ts \
  src/privacy/compliance-retention-executor.spec.ts \
  --config vitest.config.ts --maxWorkers=1
  2 files, 14/14 tests passed

# cwd apps/oshun/bff; real PostgreSQL reporter-row deletion, actor-only unlink,
# adjacent preservation, persisted physical state, and restart fence
OSHUN_ADMIN_DATABASE_URL=<local-postgresql> pnpm exec vitest run \
  src/living-scenes/abuse-report-store-durability.integration.spec.ts \
  --config vitest.integration.config.ts
  1 file, 1/1 test passed

# repository root; strict changed-source lint, formatting, and whitespace
pnpm exec eslint \
  apps/oshun/bff/src/living-scenes/abuse-report-store.ts \
  apps/oshun/bff/src/living-scenes/abuse-report-store-durability.spec.ts \
  apps/oshun/bff/src/living-scenes/abuse-report-store-durability.integration.spec.ts \
  apps/oshun/bff/src/server.ts --max-warnings=0 --no-warn-ignored
  passed
pnpm exec prettier --check <the-same-four-files>
git diff --check -- <the-same-four-files>
  passed

# repository root; zero-backlog app-own type ratchet
node tools/typecheck/ratchet.mjs \
  --app apps/oshun/bff --tsconfig tsconfig.typecheck.json
  passed; no new app-own type errors, backlog 0

# cwd apps/oshun/bff; deployable package entry bundle
pnpm run build
  passed; server bundle 32.1 MB, source map 75.6 MB

# repository root; declared BFF Nx target without unrelated dependency tasks
pnpm nx run @oshun/bff:build --excludeTaskDependencies
  passed; server bundle 32.6 MB, source map 76.8 MB

# source commit hook; exact affected project typechecks
pnpm exec nx affected --target=typecheck \
  --files=apps/oshun/bff/src/living-scenes/abuse-report-store-durability.integration.spec.ts,apps/oshun/bff/src/living-scenes/abuse-report-store-durability.spec.ts,apps/oshun/bff/src/living-scenes/abuse-report-store.ts,apps/oshun/bff/src/server.ts \
  --parallel=4
  @oshun/bff:typecheck passed; backlog 0
  @oshun/prompt-injection-evals:typecheck passed

# clean rebase over nine origin/main commits; no changed-file overlap
published source HEAD == origin/main ==
  7544b773daa7c9aec87a29a28e7a95f093facd3e

The source hook also passed lint-staged, asset-locking, import-baseline, V5 documentation, and commit-message gates. Expensive BFF verification ran one gate at a time before the hook; its two affected typechecks then ran together as configured. The host had 15 GiB RAM and 31 GiB swap. The largest BFF TypeScript process peaked near 5.6 GiB RSS while available memory remained above the stop threshold. The dependency-inclusive BFF target was not repeated because its known unrelated @oshun/audit-platform TypeScript 6 declaration prerequisite remains outside this slice; the direct deployable bundle and dependency-excluded declared target both passed. No UI, mobile flow, schema migration, provider operation, model generation, Unreal content, or production deletion changed, so Playwright/mobile, migration, provider, model, Unreal, and production-operations automation were inapplicable. The protected user lockfile remained byte- identical at Git blob a37431842e330b3a06b030947c25bebdc72bc2b1 and was not published.

This closes the Living Scene abuse-report retention adapter and therefore all three explicitly named support_case partitions, not V1-002. The scheduled Metis academic-evidence purge is closed below; the remaining compliance inventory, subscription-cancellation UX, and the final all-store proof remain open.

Metis academic evidence-pack expiry verification#

Source and published implementation: d01e4c2c315f3156b4abb4c1b26d39c36cc558fb. The shared compliance worker now evaluates the durable Metis academic-record ledger as its ninth connected partition. A new deletion records a 730-day evidence_pack anchor. Legacy snapshots migrate with a null anchor and therefore defer rather than receiving an invented deletion time; replaying canonical account erasure may establish a conservative new window. The export's retention metadata now truthfully reports automaticPurgeImplemented: true.

Account erasure continues to remove the deleted learner's owned verdict, appeal, gradebook, and notification operations immediately. If that subject appears only as a reviewer, respondent, or appellant on another learner's record, the adjacent learner's categorical academic evidence must survive. The ledger replaces the erased identity with deleted-subject:<sha256> and redacts the subject-authored teacher rationale, correction reason, appellant narrative, requested relief, names, and resolution notes. This slice also closed a found duplicate-text leak: the adjudication route copied reviewer rationale into correctionReason, so deletion now redacts that copy and hydration rejects its reintroduction.

An active or pending-release legal hold blocks the subject. A retention exception that includes evidence_pack blocks only that category. At the exact due boundary with neither blocker, one serialized candidate/save/publish mutation replaces every retained link for the due subject with one fresh random purged-subject:<256-bit-value> tombstone. No digest-to-tombstone map is stored; the adjacent learner's verdict, audit, gradebook, and appeal facts remain. The one-way subject fence and deletion/purge clocks remain to prevent recreation and prove the retention transition. A failed durable save rolls the entire purge back, including live operations and notification-delivery state.

Hydration requires sorted, duplicate-free retention metadata with exact membership in the deletion-fence set, safe nonnegative clocks, no purge before deletion, and no purge without an anchor. It rejects deleted pseudonyms after a recorded purge, unknown or malformed deleted IDs, malformed purge tombstones, incompletely redacted subject-authored text, retained learner-owned operations, and direct-subject resurrection. Reserved deleted-subject: and purged-subject: identifiers cannot enter new writes. Startup hydrates and migrates this ledger before the initial compliance pass; the supervised periodic worker then applies the same shared authority.

Verification against the exact published source tree:

text
# cwd apps/oshun/bff; final ledger migration/corruption, shared authority,
# exact-boundary expiry, rollback, routes, DSAR, and executor regression
pnpm exec vitest run \
  src/metis/academic-integrity-appeal-store-durability.spec.ts \
  src/privacy/compliance-retention-executor.spec.ts \
  src/__tests__/metis-integrity-route.test.ts \
  src/data-export/bundle-builder.test.ts \
  --config vitest.config.ts --maxWorkers=1
  4 files, 58/58 tests passed in 83.28 seconds

# post-rebase focused proof after incoming shared-contract changes
pnpm exec vitest run \
  src/metis/academic-integrity-appeal-store-durability.spec.ts \
  src/privacy/compliance-retention-executor.spec.ts \
  --config vitest.config.ts --maxWorkers=1
  2 files, 21/21 tests passed in 4.22 seconds

# real PostgreSQL exact-boundary expiry, physical persisted unlink,
# adjacent learner preservation, fresh-connection restart, and fence
OSHUN_ADMIN_DATABASE_URL=<local-postgresql> pnpm exec vitest run \
  src/metis/academic-integrity-appeal-store-durability.integration.spec.ts \
  --config vitest.integration.config.ts --maxWorkers=1
  1 file, 1/1 test passed in 66.81 seconds

# repository root; injected evidence_pack eraser/fallback coverage
pnpm exec vitest run \
  --config libs/shared/deletion-fanout/vitest.config.ts \
  libs/shared/deletion-fanout/src/service-erasers.test.ts --maxWorkers=1
  1 file, 11/11 tests passed

# strict changed-source lint, formatting, and whitespace
pnpm exec eslint --max-warnings=0 --no-warn-ignored <five-changed-files>
pnpm exec prettier --check <five-changed-files>
git diff --check
  passed

# zero-backlog app-own type ratchet, repeated after the clean rebase
node tools/typecheck/ratchet.mjs \
  --app apps/oshun/bff --tsconfig tsconfig.typecheck.json
  passed; no new app-own type errors, backlog 0

# deployable package entry and declared Nx target without dependency expansion
pnpm run build
  passed; server bundle 32.1 MB, source map 75.7 MB
pnpm nx run @oshun/bff:build --excludeTaskDependencies
  passed; server bundle 32.6 MB, source map 76.8 MB

# source commit hook; exact affected project typechecks
pnpm exec nx affected --target=typecheck \
  --files=<five-changed-files> --parallel=4
  @oshun/bff:typecheck passed; backlog 0
  @oshun/prompt-injection-evals:typecheck passed

# clean rebase over six origin/main commits; no changed-file overlap;
# focused tests, ratchet, and entry build repeated afterward
published source HEAD == origin/main ==
  d01e4c2c315f3156b4abb4c1b26d39c36cc558fb

The source hook also passed lint-staged, asset-locking, import-baseline, V5 documentation, and commit-message gates. Expensive BFF verification ran one gate at a time except the hook's configured affected checks and the lightweight focused static/test batch. The host had 15 GiB RAM and 31 GiB swap; the largest BFF TypeScript process peaked near 5.6 GiB RSS while available memory stayed above the stop threshold. The PostgreSQL run emitted unrelated missing-source- map diagnostics but its test passed. The protected user lockfile remained the exact unstaged Git blob a37431842e330b3a06b030947c25bebdc72bc2b1, was never published, and was restored from a retained named stash.

No rendered UI, mobile flow, schema migration, external provider operation, model generation, Unreal content, or production deletion changed. Playwright, mobile, migration, provider, model, Unreal, and production-operations automation were inapplicable. This closes scheduled expiry only for the local Metis academic-record ledger. Its explicitly separate canonical V1 evidence and verdict tables were subsequently connected to configured DSAR reads by 234523f6c6323ab4a546828c2fa2adba37120247; the V1-002 all-store box remains open.

Provider-aware subscription management and cancellation guidance verification#

Source and published implementation: 270cfe67cfae36131ecbfccee0ee122f98f1e888. The authenticated GET /v1/billing/subscription-management boundary now reports only the durable subscription state, provider label, safe catalog product and package identifiers, canonical management URL, and whether an injected manager can cancel in-app. Apple transaction identities, Google purchase-token digests, raw tokens, and provider-supplied redirects do not cross the boundary. Shared normalization reconstructs the official Apple and Google URLs locally and rejects hostile response fields instead of trusting an arbitrary redirect.

The web and mobile profile surfaces consume that authority in both Billing and account deletion. Apple- and Google-managed subscriptions show their exact billing source and canonical management action, while misleading local cancel or downgrade controls are suppressed. Account deletion explicitly warns that deleting Oshun data does not itself stop Apple or Google renewal, but the immediate local-erasure action remains available. This follows Apple's account-deletion guidance and Google's documented subscription lifecycle and customer management flow.

The optional authenticated POST /v1/billing/subscription-management/google-play/cancel seam accepts a bounded raw purchase token only for the current request. The billing store hashes it for lookup, requires an exact authenticated-owner binding, returns the same not-found response for unknown and cross-account tokens, and never writes or echoes the raw value. A configured provider manager receives Google's customer-requested stop-renewals cancellation type. Provider success or an already-cancelled replay is then reconciled into the durable local subscription, churn, cancellation-flow, and plan-projection state; a local save failure can be retried without inventing a provider failure. An unconfigured manager fails loudly. This implements a secret-safe binding point around Google's documented subscriptionsv2 cancel operation, not a claim that a production Google credentials/client adapter is currently injected or that any live subscription was cancelled.

Verification against the published source:

text
# authenticated authority, owner isolation, transient token, fail-loud manager,
# durable reconciliation, replay after save loss, and existing store routes
BFF route suites: 32/32 tests passed (7 new + 25 existing)
BFF full application boot route smoke: 1/1 passed
BFF OpenAPI runtime drift: 1/1 passed

# hostile-response normalization and provider cancellation contract
shared auth + billing-support suites: 24/24 passed (2 + 22)

# web provider/deletion behavior and the authenticated client
focused web component suites: 90/90 passed
subscription-management client: 1/1 passed

# real browser flow with authenticated authority, Apple management action,
# hidden local cancellation, deletion warning, immediate deletion, and axe
Playwright subscription-management-guidance.spec.ts: 1/1 passed

# mobile client, guidance/linking, hidden local controls, and profile wiring
focused mobile suites: 29/29 passed
mobile profile suite: 2/2 passed

# compile/build/static gates
@oshun/auth-client:typecheck, @oshun/billing-support:typecheck,
@oshun/bff:typecheck, @oshun/web:typecheck, @oshun/mobile:typecheck: passed
BFF direct esbuild production entry: passed
strict changed-source ESLint, full changed-file Prettier, and git diff check:
  passed

# conflict-sensitive proof after rebase onto current origin/main
mobile BFF client: 15/15 passed
study fixture goldens: 5/5 passed
mobile TypeScript: passed

# mobile flow graph
new Maestro flow syntax: OK
full regression-suite syntax/graph: OK

The Playwright flow ran against the rendered web application and passed. An actual Maestro device run was not possible: adb devices reported no booted Android target, and there was no booted iOS simulator or installed Oshun dev client. Creating a native package solely for this check was not run on the 15-GiB host. This limitation is not represented as mobile end-to-end proof; the new flow and full suite graph are syntax-validated only. The UI composition used the mandatory frontend workflow's calm, high-trust hierarchy: billing source first, exact action and deletion consequence second, with explicit loading and unavailable states rather than additional dashboard chrome.

This slice closes the previously named transparent client guidance gap and adds the optional secret-safe Google manager seam. It does not close V1-002. A production Google manager/credential binding, live provider proof where an authorized test subscription exists, actual native-device execution, and the continuing operational/provider inventory remain. The protected user lockfile remained the exact unstaged Git blob a37431842e330b3a06b030947c25bebdc72bc2b1, was not published, and its named preservation stash was retained.

Generated-artifact control-plane DSAR verification#

Source and published implementation: acc16f9080be7698099cba6752f8af1287db92ea. The generation jobs, released-output catalog/provenance/lineage, and operator gallery were already acknowledgement-bound, restart-safe, and composed into the signed generated_artifact eraser. The default customer-export collector still reported all three BFF-owned partitions as absent. This slice replaces that false absence with clone-safe, deterministic, exact-owner views of the existing durable state.

The job export resolves the server-authoritative immutable owner first and uses the request's userId only for pre-attribution legacy snapshots. It includes the subject's request, outcome, error, governance, status, tenant attribution, and lifecycle timestamps. The catalog export includes only that subject's released records and provenance plus their lineage edges, including legacy records whose trustworthy owner survives on the released output. The gallery view includes current tags/takedown state and subject-relevant action facts. It filters a multi-output action down to the subject's output IDs and deliberately withholds internal operator identity while preserving the action, timing, and undo status relevant to the customer.

generated_artifact bundles now carry separately labelled generation_jobs, generation_output_catalog, and operator_output_gallery items alongside any Living Scene share record. Tests prove that an explicit owner defeats a spoofed request field and that an adjacent account's prompt, job, output, provenance, and gallery row do not enter the bundle. The only named generated-artifact DSAR gap left by this collector is canonical_isis_generated_outputs, which belongs to the deploy-bound canonical Isis database and is not fabricated as BFF data.

Verification against the exact published source:

text
# generation queue, catalog/lineage, gallery, DSAR assembly, and Living Scene
# regression coverage
pnpm exec vitest run \
  src/generation/jobs-route.test.ts \
  src/generation/output-catalog.test.ts \
  src/isis/output-gallery-store.test.ts \
  src/data-export/bundle-builder.test.ts \
  src/__tests__/living-scenes-durability.test.ts --maxWorkers=1
  5 files, 88/88 tests passed

# final subject-action/legacy-attribution DSAR rerun
output catalog + gallery + bundle suites: 42/42 passed

# final DSAR assertions plus newly landed upstream bridge typing regression
bundle + ideation bridge suites: 33/33 passed

# app-own compile, static, and deployable-entry gates
@oshun/bff:typecheck: passed; no new app-own errors, backlog 0
strict changed-source ESLint: passed
full changed-file Prettier and git diff check: passed
pnpm run build: passed; server bundle 32.1 MB, source map 75.8 MB

# repository commit hook
conventions ratchet, V2 asset lock, V5 docs validation: passed
@oshun/bff and @oshun/prompt-injection-evals affected typechecks: passed

Strict lint exposed that the existing @isis/entitlements library lacked its Nx type:lib tag even though its project type is library; the source commit corrects that metadata instead of suppressing the boundary rule. The type ratchet also exposed a just-landed Node BFF test using the DOM-only RequestInfo global; it now derives its argument types from typeof fetch and its eight tests pass. Neither correction changes runtime behavior.

No new UI, mobile flow, schema migration, provider call, model generation, Unreal content, or production export request was involved, so Playwright, Maestro, migration, provider, model, Unreal, and production-operations automation were inapplicable. This closes the BFF-owned generation-jobs/catalog/operator-gallery DSAR gap, not V1-002. Canonical Isis database-row export, the continuing operational/provider inventory, and the other named gaps remain open. The protected user lockfile remained the exact unstaged Git blob a37431842e330b3a06b030947c25bebdc72bc2b1, was not published, and its named preservation stash was retained.

Canonical Isis GeneratedOutput DSAR verification#

Source and published implementation: 82497742474e5ae6354fa824c5e35a58a146bc2b. The privacy package now owns the deliberate cross-domain read adapter for canonical Isis GeneratedOutput records. The adapter opens the generated Prisma client lazily, issues an exact ownerId query with deterministic creation/ID ordering, and returns a separately labelled canonical_isis_generated_outputs partition. It carries the canonical object manifest, lifecycle/access metadata, JSON metadata, provenance, and lineage. BigInt sizes are emitted as lossless decimal strings and dates as ISO strings. Only lineage whose source and target are both in the subject's owned-output set is exported, so an edge to an adjacent account cannot reveal that account's output identity.

Recursive metadata/provenance normalization redacts authorization, cookie, password/hash, secret, API-key, access/refresh/private/client-secret, and auth/bearer/session/ID-token-shaped fields while preserving non-secret member evidence. Blank subjects, owner mismatches, invalid timestamps or numbers, malformed/cyclic JSON, and conflicting lineage fail closed. A valid owner with no rows returns honest absence instead of a fabricated record.

The production composition root injects this adapter only when the dedicated ISIS_DATABASE_URL is nonblank. It intentionally ignores the BFF's generic DATABASE_URL, which belongs to Oshun persistence and is not authority for Isis rows. When configured, the default generated_artifact collector adds the canonical partition and removes its named gap. When unconfigured, the same gap remains explicit. A canonical read/normalization failure marks the export request failed and does not publish a downloadable bundle. Route coverage also proves authenticated owner download and cross-user 403 isolation.

The database integration proof used the repository's two Isis migrations against the local Postgres isis database, seeded only dedicated DSAR owner and adjacent-owner fixtures, exercised exact-owner metadata/provenance and private lineage through the real generated Prisma client, then deleted every fixture. The post-test fixture count was zero. This is migrated local-PostgreSQL proof, not a claim that a production Isis database or export request was exercised.

Verification against the exact published source:

text
# cwd libs/isis/database; repository migration history and schema
ISIS_DATABASE_URL=<live-local-postgres> \
  pnpm exec prisma migrate deploy --config prisma.config.ts
  2/2 migrations applied
ISIS_DATABASE_URL=<live-local-postgres> \
  pnpm exec prisma validate --config prisma.config.ts
  passed (existing Prisma feature/deprecation warnings only)

# cwd libs/oshun/privacy; exact-owner, JSON safety/redaction, fail-closed,
# and explicit-configuration unit coverage
pnpm exec vitest run \
  src/data-exporters/generated-artifact-exporter.spec.ts
  1 file, 4/4 tests passed

# real generated Prisma client against the migrated local Isis database
ISIS_DATABASE_URL=<live-local-postgres> pnpm exec vitest run \
  src/data-exporters/generated-artifact-exporter.integration.spec.ts
  1 file, 1/1 test passed; cleanup verified zero DSAR fixture rows

# cwd libs/isis/database; lazy default generated-client loader
pnpm exec vitest run src/client.spec.ts
  1 file, 9/9 tests passed

# cwd apps/oshun/bff; collector composition, configured/unconfigured gap,
# owner download/adjacent denial, and failed-collection no-bundle behavior
pnpm exec vitest run \
  src/data-export/bundle-builder.test.ts \
  src/__tests__/data-export-route.test.ts --maxWorkers=1
  2 files, 51/51 tests passed

# project-wide package gates
ISIS_DATABASE_URL=<live-local-postgres> pnpm nx test @oshun/privacy
pnpm nx test @isis/database
pnpm nx run @oshun/privacy:build
pnpm nx run @isis/database:build
privacy source/spec TypeScript checks: passed
strict changed-source ESLint and changed-file Prettier: passed

# exact final-source BFF gates
node tools/typecheck/ratchet.mjs --app apps/oshun/bff \
  --tsconfig tsconfig.typecheck.json
  passed; app-own backlog 0
pnpm run build
  passed; server bundle 32.3 MB, source map 76.1 MB

The commit hook's lint-staged, convention-ratchet, V2 asset-lock, and V5 docs checks passed. Its affected run also passed privacy, BFF, web, and prompt- injection typechecks; the unrelated @oshun/persistence target failed on its pre-existing missing pg declarations in two scripts. After the targeted source/spec checks above were green, the source commit used the hook's explicit SKIP_TYPECHECK=1 path rather than misrepresenting that unrelated target as passing. An attempted dependency-expanded Nx BFF build was stopped when its 286-project graph exceeded this host's resource-safe scope; the package's exact production entry bundle was then built directly and passed.

No customer-facing UI, mobile flow, new migration, provider call, model generation, Unreal content, production database, or production export request was involved, so Playwright, Maestro, new-migration, provider, model, Unreal, and production-operations automation were inapplicable. This closes the named canonical Isis row gap only for deployments that bind ISIS_DATABASE_URL; an unbound deployment reports the gap honestly. It does not close V1-002 or the continuing operational/provider inventory. The protected user lockfile remained the exact unstaged Git blob a37431842e330b3a06b030947c25bebdc72bc2b1, was not published, and its named preservation stash was retained.

Canonical V1 journal, ritual, and academic-record DSAR verification#

Source and published implementation: 234523f6c6323ab4a546828c2fa2adba37120247. The BFF now creates one canonical shared-V1 DSAR adapter over its already- configured Prisma client. The adapter issues exact, trimmed userId queries for Arete journal entries, Tara ritual sessions, and Tara sitting-completion events, plus exact learnerId queries for Metis assessment-evidence packs and academic- integrity verdicts. Every query has deterministic timestamp/identifier ordering and an explicit Prisma field allowlist. The resulting customer bundle labels the four independent database partitions as canonical_v1_journal_entry, canonical_v1_ritual_completion, canonical_v1_metis_assessment_evidence_pack, and canonical_v1_metis_academic_integrity_verdict.

The export mapping names every returned field rather than spreading a storage row. It deliberately does not select or emit internal tombstoneActorId values. Dates become ISO strings; numeric and identifier invariants are validated; recursive JSON traversal rejects malformed, cyclic, or non-finite values and redacts authorization, cookie, password/hash, secret, API-key, access/refresh/ private/client-secret, and auth/bearer/session/ID-token-shaped keys. An owner mismatch, blank subject, invalid timestamp, or malformed value fails closed. Exact query predicates exclude adjacent users, adjacent learners, and evidence packs whose optional learnerId is null.

The production composition root injects these readers only through the shared V1 client created from nonblank OSHUN_V1_DATABASE_URL. With that binding, the default journal_entry, ritual_completion, and evidence_pack collectors query their canonical authorities and remove the four named coverage gaps even when an exact subject honestly has no rows. Without it, the previous explicit gaps remain. The existing signed deletion fanout continues to use the same database authority for exact-subject physical deletion. A canonical read or normalization error marks the export request failed and publishes no bundle; authenticated route proof also covers owner download and adjacent-user 403.

The real-database integration proof used the repository's configured local PostgreSQL V1 database and generated Prisma client. It seeded one owner and one adjacent subject across all five tables, exercised exact-owner export and nested credential redaction, excluded adjacent and null-learner rows, then deleted all fixtures. afterAll asserted zero remaining fixture rows in every table. This is live local-PostgreSQL proof, not a claim that a production database or production data-export request was exercised.

Verification against the exact published source:

text
# cwd apps/oshun/bff; exact reader, collector, and authenticated route proof
pnpm exec vitest run \
  src/data-export/v1-record-exporters.spec.ts \
  src/data-export/bundle-builder.test.ts \
  src/__tests__/data-export-route.test.ts --maxWorkers=1
  3 files, 58/58 tests passed
  reader 4/4; collector 27/27; route 27/27

# real generated Prisma client against local PostgreSQL; all five fixture
# tables asserted empty after cleanup
OSHUN_V1_DATABASE_URL=<live-local-postgres> pnpm exec vitest run \
  -c apps/oshun/bff/vitest.integration.config.ts \
  apps/oshun/bff/src/data-export/v1-record-exporters.integration.spec.ts \
  --maxWorkers=1
  1 file, 1/1 test passed; cleanup counts [0, 0, 0, 0, 0]

# existing exact-subject canonical deletion authority
pnpm exec vitest run src/data-deletion/v1-record-erasers.test.ts --maxWorkers=1
  1 file, 12/12 tests passed

# cwd libs/oshun/persistence; canonical shared-V1 schema
OSHUN_V1_DATABASE_URL=<live-local-postgres> \
  pnpm exec prisma validate --config prisma.config.ts
  passed

# exact final-source BFF type and production-entry gates
node tools/typecheck/ratchet.mjs --app apps/oshun/bff \
  --tsconfig tsconfig.typecheck.json
  passed; app-own backlog 0
pnpm run build
  passed; server bundle 32.4 MB, source map 76.2 MB

changed-source ESLint, changed-file Prettier, git diff --check,
staged stub scan, conventions ratchet, V2 asset lock, V5 docs validation,
and affected @oshun/bff plus prompt-injection typechecks
  passed

The resource-sensitive BFF typecheck ran alone during direct verification and was supervised within the required 30-second interval. The commit hook's two affected checks also completed safely; BFF TypeScript peaked near 5.0 GiB RSS while available memory remained about 6.0 GiB or higher and 31 GiB swap was configured. The source rebased cleanly over concurrent, non-overlapping Yemaya and Aphrodite work, then reached exact origin/main parity at the SHA above.

No rendered UI, mobile flow, schema migration, external provider operation, model generation, Unreal content, production database, or production export request changed. Playwright, mobile, migration, provider, model, Unreal, and production-operations automation were therefore inapplicable. This closes only the four named canonical read gaps for deployments that bind OSHUN_V1_DATABASE_URL; an unconfigured deployment reports them honestly, and the broader V1-002 all-store inventory remains open. The protected user lockfile remained the exact unstaged Git blob a37431842e330b3a06b030947c25bebdc72bc2b1, was never published, and both source-publish preservation stashes were retained.

Calendar OAuth connection authority, DSAR, and erasure verification#

Initial source and published implementation: 59e546c64cf808413ee7af8cfab74f9f3fed9a8f; sole-disconnect restart correction and current published source: 20b4e99fa49118643894e5e8413fd20f195e7625. This slice closes the previously unclassified local per-user calendar OAuth connection partition. Production now requires the store's durable authority before traffic, hydrates one authoritative snapshot from the existing admin snapshot database, and rejects synchronous mutation once durability is required. OAuth callback saves and member disconnects use awaited mutations. Each mutation clones the complete candidate state, commits it through one serialized queue, and publishes it in memory only after persistence succeeds. A missing or failed required sink returns a bounded 503 and cannot expose a new connection, remove an existing connection, or sign partial local erasure.

The durable snapshot carries established Google, Apple, and Outlook connection records, per-subject revisions, and deletion fences. Single-use OAuth CSRF state remains deliberately ephemeral and is not restored after a deploy. Snapshot hydration is authoritative rather than additive and rejects malformed providers, identifiers, timestamps, revisions, duplicate global connection identities, a connection owned by a deleted subject, and other conflicting state. Deterministic ordering makes restart and DSAR output stable. The refresh credential remains server-side in the durable local connection record because calendar synchronization requires it; client connection views and customer exports never include it.

The follow-up correction recognizes a revision-only active subject as the valid result of disconnecting that subject's final connection. Hydration still rejects a revision for a deletion-fenced subject, but no longer mistakes the ordered disconnect tombstone for corrupt state. Both the in-memory durable adapter and real PostgreSQL now prove sole disconnect, restart with no exported connection, reconnect at the next monotonic revision, and fixture cleanup.

The default profile collector now emits only exact-owner connection ID, provider, calendar IDs, granted scope, connection timestamp, and revision. Adjacent-subject connections are excluded. The signed profile deletion fanout physically removes all of the exact subject's locally stored refresh credentials, purges any in-flight CSRF state, preserves adjacent accounts, and persists an irreversible subject fence. That fence rejects both a new OAuth start and a stale callback save, including both save-before-delete and delete- before-save race orderings. Failed erasure leaves the prior credential and pending flow intact and propagates failure instead of producing a successful deletion receipt.

Verification against the exact published source:

text
# cwd apps/oshun/bff; store ordering/restart/corruption/races, Fastify callback
# and disconnect failures, secret-free DSAR, and profile erasure composition
pnpm exec vitest run \
  src/calendar/calendar-oauth-connection-store.test.ts \
  src/routes/calendar-connect-route.test.ts \
  src/data-export/bundle-builder.test.ts \
  src/data-deletion/profile-state-eraser.test.ts --maxWorkers=1
  4 files, 67/67 tests passed

# real local PostgreSQL AdminSnapshotStore: credential recovery, secret-free
# export, signed profile erasure, adjacent preservation, restart, and fence
OSHUN_ADMIN_DATABASE_URL=<live-local-postgres> pnpm exec vitest run \
  -c vitest.integration.config.ts \
  src/calendar/calendar-oauth-connection-durability.integration.spec.ts \
  --maxWorkers=1
  1 file, 1/1 test passed; fixture snapshot removed in afterAll

# exact final BFF type and production-entry gates
node tools/typecheck/ratchet.mjs --app apps/oshun/bff \
  --tsconfig tsconfig.typecheck.json
  passed; app-own backlog 0
pnpm run build
  passed; server bundle 32.4 MB, source map 76.2 MB

changed-source ESLint, changed-file Prettier, git diff --check,
staged stub scan, conventions ratchet, V2 asset lock, and V5 docs validation
  passed

pnpm docs:center:verify
  retained the same 80 pre-existing generator-owned structural gaps: missing
  product space-map/engine references, the legacy domains redirect, and
  contract/OpenAPI/reference pages; no new gap or changed category

The resource-sensitive BFF ratchet ran alone after the required RAM, swap, disk, and process gate and was polled within 30 seconds. TypeScript peaked near 5.36 GiB RSS while available memory stayed above 5 GiB; 31 GiB swap was configured. The source rebased cleanly over non-overlapping Yemaya work and was then verified at exact origin/main parity. The commit hook used its explicit SKIP_TYPECHECK=1 path only after the exact zero-backlog ratchet had passed.

This is local credential deletion, not provider-native revocation. The slice does not revoke an OAuth grant at Google, Apple, or Microsoft, delete remote calendar data, or compensate at the provider if token issuance succeeds but the following local persistence commit fails. A real provider-specific revoke operation, durable confirmation/reconciliation, and failure semantics remain part of the open provider inventory; no remote revocation receipt is fabricated. No rendered UI, mobile flow, schema migration, live provider call, production database, production deletion request, model generation, or Unreal content changed, so Playwright/mobile, migration, live-provider, production operations, model, and Unreal automation were inapplicable. The all-store checkbox remains open. The protected user lockfile remained the exact unstaged Git blob a37431842e330b3a06b030947c25bebdc72bc2b1, was never published, and its named preservation stash was retained.

Arete member-continuity durability, DSAR, and erasure verification#

Published implementation source: 43a87fdb6e03cea3e92f00f6250fd19550f547b1. This slice classifies the authenticated weekly-review closure, living-offering decision, and coach decision stores as user-owned continuity_state. They are product-history authority, not recomputable caches: review completion drives the Arete room, offering records retain the member's recipient, occasion, action, and private intention preview, and the room consumes the latest coach decision. Before this source, all three stores mutated memory before firing an unawaited snapshot save, silently continued without a bound sink, restored additively, and had no exact-owner DSAR or signed account-erasure composition.

One generic ordered subject-record authority now backs all three legacy snapshot keys. Each mutation normalizes a complete candidate, serializes it against other mutations, awaits the candidate snapshot, and publishes memory only after persistence succeeds. Production marks all three stores as requiring durability before it hydrates them from the admin snapshot database and before the BFF accepts traffic. Missing or failed persistence cannot expose a new closure, offering, or decision and maps to a bounded 503; invalid bounded text maps to 422; a mutation after signed erasure maps to 409. Review/offering identities use UUIDs and reject a generated identity collision instead of overwriting an existing row. Coach updates deliberately replace only that subject's current decision.

Hydration is authoritative and deterministic. It rejects malformed arrays, noncanonical timestamps, invalid action/state pairs, blank or oversized subject record fields, duplicate record identities, duplicate or invalid revisions, records/revisions belonging to a deletion-fenced subject, and other conflicting snapshots. Per-subject revisions and deletion fences are persisted with each store. A coach clear retains a revision-only active tombstone across restart, while account erasure removes that revision and installs the permanent subject fence. Both save-before-delete and delete-before-save are serialized; failed deletion publishes none of its candidate; restart cannot resurrect the subject. The three physical snapshots are independent, so cross-partition erasure is intentionally retryable rather than falsely described as one database transaction: the signed continuity_state receipt fails on any later partition error, and already completed fenced partitions return zero on retry.

The default customer bundle now includes one exact-owner arete_member_state partition under continuity_state, with independent review, offering, and coach revisions. Adjacent-member recipient, occasion, and private-intention data are excluded. Signed continuity erasure composes all three stores, physically removes the exact subject, preserves adjacent members, and retains restart-safe resurrection fences. These records are lifecycle-bound member history, not compliance-retained evidence: no legal-hold or time-based retention exception applies in this implementation, and signed account erasure hard-deletes them. Clearing a coach decision is also an ordinary product operation and preserves only its subject-keyed monotonic revision metadata until account erasure.

Verification ran on host dev-server, Ubuntu 24.04.4 LTS, Linux 6.8.0-110-generic x86_64, Node v24.14.1, pnpm 10.25.0, TypeScript 6.0.3, Vitest 4.1.7, ESLint 10.4.0, esbuild 0.19.12, and local PostgreSQL client 16.14. The focused verification window was 2026-07-17T17:28:33Z through approximately 2026-07-17T17:43:00Z. The tested source rebased over concurrent non-overlapping Yemaya and Aphrodite work, then was pushed and independently read back at exact origin/main parity at the SHA above.

text
# cwd apps/oshun/bff; ordered persistence, failed-write publication, HTTP
# failures, exact-owner DSAR, and deletion composition. The first invocation
# mistyped the fourth path as data-rights; Vitest selected the three valid files,
# so the canonical continuity-deleter suite was run immediately afterward.
pnpm exec vitest run \
  src/arete/arete-member-state-durability.spec.ts \
  src/__tests__/domain-stubs-route.test.ts \
  src/data-export/bundle-builder.test.ts \
  src/data-rights/continuity-state-eraser.test.ts --maxWorkers=1
  3 files, 125/125 tests passed (92 route, 29 bundle, 4 authority)

pnpm exec vitest run \
  src/data-deletion/continuity-state-eraser.test.ts --maxWorkers=1
  1 file, 6/6 tests passed

# final typing-only test-capture correction rerun
pnpm exec vitest run \
  src/arete/arete-member-state-durability.spec.ts --maxWorkers=1
  1 file, 4/4 tests passed

# real local AdminSnapshotStore/PostgreSQL: all three legacy keys, adjacent
# isolation, restart, signed-continuity composition, fence recovery, cleanup
OSHUN_V1_DATABASE_URL=<live-local-postgres> \
  pnpm exec vitest run -c vitest.integration.config.ts \
  src/arete/arete-member-state-durability.integration.spec.ts --maxWorkers=1
  1 file, 1/1 test passed; three fixture snapshots removed in afterAll

# exact final BFF type gate; two discovery runs first exposed nullable callback-
# capture inference only in the new unit test. Explicit generic result types
# fixed all four sites without casts, suppressions, or a baseline update.
node tools/typecheck/ratchet.mjs --app apps/oshun/bff \
  --tsconfig tsconfig.typecheck.json
  passed; no new app-own errors; backlog 0

# exact production entry bundle
pnpm exec esbuild src/server.ts --bundle --platform=node --format=esm \
  --target=node22 --outfile=dist/server.js --sourcemap
  passed; server bundle 32.9 MB, source map 77.4 MB

# exact changed-file static gates (cwd repository root; the same 12 files were
# supplied to both commands in this order)
ARETE_SLICE_FILES="apps/oshun/bff/src/arete/arete-subject-record-authority.ts \
apps/oshun/bff/src/arete/arete-review-store.ts \
apps/oshun/bff/src/arete/arete-offering-store.ts \
apps/oshun/bff/src/arete/arete-coach-decision-store.ts \
apps/oshun/bff/src/arete/arete-member-state.ts \
apps/oshun/bff/src/arete/arete-member-state-durability.spec.ts \
apps/oshun/bff/src/arete/arete-member-state-durability.integration.spec.ts \
apps/oshun/bff/src/routes/domain-stubs.ts \
apps/oshun/bff/src/__tests__/domain-stubs-route.test.ts \
apps/oshun/bff/src/data-export/bundle-builder.ts \
apps/oshun/bff/src/data-export/bundle-builder.test.ts \
apps/oshun/bff/src/server.ts"
pnpm exec eslint $ARETE_SLICE_FILES --no-ignore --max-warnings=0
pnpm exec prettier --check $ARETE_SLICE_FILES
git diff --check
scripts/stub-indicator-scan.sh --staged --mode=all
node tools/conventions/check-conventions-ratchet.mjs --staged
python3 V2/ue/Tools/v2_asset_locking_workflow.py pre-commit
python3 V5/tools/validate-v5-docs.py
  all passed

Documentation-specific verification also passed the root-ledger Unreal closure contract and all 21 generated-evidence metadata tests. pnpm docs:center:verify returned the same 80 pre-existing generator-owned structural gaps recorded by the preceding calendar slice: missing product space-map/engine references, the legacy domains redirect, and contract/OpenAPI/reference pages. The Arete edits introduced no new gap or changed category; this result remains a qualified nonzero documentation gate rather than a green claim.

The BFF ratchet ran separately from the bundle and was polled within the required 30-second interval. Across its discovery and final runs, TypeScript's observed peak was about 5.45 GiB RSS; available memory remained at least about 4.6 GiB, and 31 GiB swap was configured. The final ratchet used the commit hook's explicit SKIP_TYPECHECK=1 path only after the standalone zero-backlog gate passed. No broad workspace sweep was run on this 15 GiB host.

The negative/adversarial proof includes failed required saves for all three stores with no live publication, a failed deletion with no partial in-memory publication, both mutation/erasure race orders, generated-ID collision, malformed/contradictory snapshots, post-erasure stale recreation, adjacent- subject exclusion, oversized API input, and a post-erasure coach clear. The real local database test proves restart recovery and cleanup; it is not a production-database claim. No policy in this slice requires a human authority decision, and no content slot, rendered UI, mobile flow, schema migration, external provider, model, Unreal asset, or production operation changed. Playwright/mobile, migration, live-provider, model/engine, Unreal, performance, and production-operation automation were therefore inapplicable. This closes only these three local Arete operational partitions; the V1-002 all-store box remains open.

The protected user lockfile remained the exact unstaged Git blob a37431842e330b3a06b030947c25bebdc72bc2b1, was never staged or published, and the named preserve-user-pnpm-lock-arete-member-state-source-publish stash was retained. All unrelated untracked Cargo lockfiles and libs/urania/ remained untouched.

Nyx member-continuity durability, DSAR, and erasure verification#

Published implementation source: 5abc400e018c6beff1bc0302a795bd000b642d27. This slice classifies the authenticated saved-celestial-object list, opt-in sky-event reminders, and per-member object-search count as user-owned continuity_state. They are product continuity, not recomputable caches: the adapter returns the saved list, reminder delivery consumes the reminder rows, and achievements consume the count. The count is deliberately minimized—the store never receives or retains the member's search query text.

Before this source, all five mutations changed live maps before calling a detached void sink.save(snapshot). A missing sink silently degraded to restart-resettable memory; a failed save could still be acknowledged; restore merged into existing maps instead of replacing them; timestamps, identities, counts, ownership collisions, and snapshot conflicts were weakly validated; and the partition had no exact-owner export, account eraser, subject revision, or resurrection fence.

NyxMemberStateStore now owns one ordered authority over the legacy nyx-member-state snapshot key. Save, unsave, reminder creation, reminder toggle, and search-count increment each enter one mutation queue, clone a complete candidate, advance the exact subject's revision, await the candidate snapshot, and publish it only after persistence succeeds. Production marks the store as requiring durability before binding and hydrating the admin snapshot store. The in-process adapter awaits each mutation, including the otherwise read-shaped authenticated object-search request. Missing or failed persistence therefore cannot publish or acknowledge a volatile saved object, unsave, reminder, toggle, or count. Guarded Nyx adapter routes distinguish persistence failure (503), a post-erasure mutation (409), and invalid member-state input (422) from an unrelated domain failure (502).

Hydration is authoritative and deterministic. It replaces all maps and rejects malformed arrays, blank or oversized subjects and identifiers, noncanonical timestamps, invalid cadence/channel/enabled values, unsafe counts or revisions, duplicate saved-object pairs, reminder identity collisions, duplicate subject aggregates/revisions/fences, and records or revisions that contradict an erasure fence. Reminder IDs use UUID-backed identities and reject collision instead of overwriting another subject's row. Snapshots sort each view, revision list, and fence list deterministically. Returned records and channel arrays are cloned so a caller cannot mutate the authority outside the ordered boundary.

Exact-subject deletion enters the same queue as every mutation. It removes all owned saved rows and reminder rows plus the one search-count aggregate, removes the active revision, installs a durable subject fence, persists the whole candidate, and publishes only after success. A failed deletion leaves all live views unchanged. Save-before-delete completes then erases; delete-before-save installs the fence then rejects the stale write. Retry is count-idempotent, and the fence survives restart. The production continuity_state fanout includes nyx_member_state, validates its row count with every other continuity partition, and cannot sign a successful aggregate receipt when this partition throws.

The default customer bundle exports one exact-owner nyx_member_state record under continuity_state: its revision, saved-object metadata, full reminder metadata, and minimized search-count aggregate. Adjacent members are excluded, including IDs sharing a prefix. After signed erasure the section is empty while the adjacent member remains. These are lifecycle-bound product records with no implemented legal-hold or time-based retention exception. Their retention ends at signed account erasure; deletion is physical except for the subject-keyed resurrection fence. No search query string, provider credential, shared celestial catalog body, or observation log is duplicated into this snapshot.

Verification completed on 2026-07-19 UTC on host dev-server, Ubuntu 24.04.4 LTS, Linux 6.8.0-110-generic x86_64, Node v24.14.1, pnpm 10.25.0, TypeScript 6.0.3, Vitest 4.1.7, ESLint 10.4.0, esbuild 0.19.12, and local PostgreSQL client 16.14.

text
# cwd apps/oshun/bff; authority, adapter, guarded route, exact-owner DSAR,
# aggregate deletion, and continuity eraser. An initial invocation used the
# removed Vitest 3 --poolOptions spelling and ran no tests; the supported
# single-worker command below was the executed gate.
pnpm exec vitest run \
  src/nyx/nyx-member-state-durability.spec.ts \
  src/nyx/in-process-adapter.test.ts \
  src/__tests__/nyx-route.test.ts \
  src/data-export/bundle-builder.test.ts \
  src/data-deletion/continuity-state-eraser.test.ts --maxWorkers=1
  5 files, 64/64 tests passed

# final direct authority rerun after adding the explicit required-but-unbound
# persistence assertion
pnpm exec vitest run \
  src/nyx/nyx-member-state-durability.spec.ts --maxWorkers=1
  1 file, 4/4 tests passed

# real local AdminSnapshotStore/PostgreSQL: one legacy key, all three views,
# exact-owner export, adjacent isolation, continuity erasure, restart, fence,
# stale writes, and fixture cleanup; password redacted
OSHUN_ADMIN_DATABASE_URL=<live-local-postgres> \
  pnpm exec vitest run -c vitest.integration.config.ts \
  src/nyx/nyx-member-state-durability.integration.spec.ts --maxWorkers=1
  1 file, 1/1 test passed; dedicated fixture snapshot removed in afterAll

# exact zero-backlog BFF type gate; no baseline update
node tools/typecheck/ratchet.mjs --app apps/oshun/bff \
  --tsconfig tsconfig.typecheck.json
  passed; no new app-own errors; backlog 0

# exact changed-source static gates; nine Nyx/BFF source and test files
pnpm exec eslint --no-ignore <nine changed source/test paths> --max-warnings=0
pnpm exec prettier --check <nine changed source/test paths>
git diff --check
  all passed

# exact production entry bundle
pnpm --dir apps/oshun/bff build
  passed; server bundle 32.4 MB, source map 76.3 MB

# source-commit hooks
eslint --fix --no-warn-ignored; prettier --write
nx affected --target=typecheck <nine paths>
stub/convention/V2-asset/V5-doc gates
  passed; @oshun/bff and @oshun/prompt-injection-evals typechecks passed

# evidence-ledger documentation contracts
node scripts/audit/verify-unreal-closure-contract.mjs
pnpm verify:evidence:metadata
  passed; root Unreal closure contract and 21/21 metadata tests

pnpm docs:center:verify
  qualified nonzero; retained the same 80 pre-existing generator-owned gaps:
  missing product space-map/engine references, the legacy domains redirect,
  and contract/OpenAPI/reference pages; no new gap or changed category

The negative/adversarial proof includes a required store with no sink, failed required saves for every mutation kind with no live publication, failed deletion with no partial publication, both mutation/erasure race orders, idempotent deletion retry, restart-authoritative replacement, unsave and toggle revision continuity, reminder-ID collision, contradictory deletion snapshots, duplicate search aggregates, post-restart stale saved/reminder/search writes, adjacent-owner DSAR exclusion, and explicit 503/409/422 route mapping. The real local database test proves recovery and cleanup; it is not a production- database or production-request receipt.

The resource-sensitive BFF ratchet ran after the required RAM, swap, disk, and process gate and was polled within 30 seconds. TypeScript peaked at approximately 5.4 GiB RSS while available memory remained above approximately 4.1 GiB; 31 GiB swap was configured. The first Nx wrapper was canceled while building its project graph after a one-time analytics prompt, before the type target ran; its incidental nx.json analytics edit was reverted. The direct ratchet then passed, and the source commit hook subsequently ran the affected Nx typechecks to completion under supervision.

The source rebased without conflict over unrelated Yemaya work before being pushed to exact origin/main parity. No human-policy decision, rendered UI, mobile flow, schema migration, external provider, production database, live production request, model generation, Unreal asset, or performance-sensitive algorithm changed. Playwright/mobile, migration, provider, production- operation, model/engine, Unreal, and performance automation were therefore inapplicable. This closes only the three local Nyx member-state views; the V1-002 all-store inventory remains open.

The protected user lockfile remained the exact unstaged Git blob a37431842e330b3a06b030947c25bebdc72bc2b1, was never staged or published, and the named preserve-user-pnpm-lock-nyx-member-state-source-publish stash was retained. All unrelated untracked Cargo lockfiles and libs/urania/ remained untouched.

Authenticated client-state durability, retention, DSAR, and erasure verification#

Published implementation source chain: aedda7fe1ac5a05fdf90ea8b1ebe71c674535711, corrected and published through c0681992f5638c86ccf8d73b442d31da99e7b67d. The correction is part of the same slice: after the initial acknowledgement/recovery/privacy work was published, a canonical-policy cross-check found that continuity_state requires 30-day last-access retention and a daily purge. The evidence claim was withheld until that policy was implemented and republished.

This slice classifies the authenticated /v1/client-state/:stateKey records as user-owned continuity_state, not a recomputable cache. The BFF API admits four allow-listed slots: onboarding-progress, recent-searches, workspace-layout, and study-plan-drafts. Repository producer inventory finds one demonstrated customer-web producer today, MultiPanelWorkspace writing workspace-layout; the other three are authenticated API capacity and are not claimed as currently connected UI flows. The route itself can nevertheless accept and retain personal JSON in every allow-listed slot, so all four require the same durability, export, erasure, validation, and retention boundary.

Before this source, PUT changed a global live map and then invoked detached void snapshotSink.save(...). A missing sink silently fell back to volatile memory, a failed save could still receive 200, hydration trusted and replaced weakly validated values, and size enforcement counted JavaScript UTF-16 code units rather than stored UTF-8 bytes. There was no per-subject revision, resurrection fence, exact-owner DSAR partition, signed account eraser, or automatic retention purge.

ClientStateStore now owns one ordered authority over the existing client-state-sync snapshot key. Every PUT canonicalizes and clones the input, advances the exact subject revision, creates a complete candidate, awaits the snapshot save, and publishes only after success. Production requires the sink and hydrates it authoritatively before traffic. Missing or failed persistence returns bounded 503 and leaves live state unchanged; a mutation behind an account-erasure fence returns 409. Existing 400, 404, and 413 API semantics remain intact.

The JSON boundary accepts only a plain object containing finite JSON values, rejects cycles, unsafe prototypes and prototype-pollution keys, limits nesting to 64 levels, recursively sorts object keys, and enforces the 64 KiB cap on the actual UTF-8 serialization. Snapshots deterministically sort subjects, slots, revisions, and fences. Hydration rejects malformed arrays and records, noncanonical timestamps, last access preceding update, unknown slots, duplicate owner/slot pairs, unsafe revisions, duplicate subjects/fences, and any record or revision contradicting an erasure fence. Returned records and nested values are cloned so callers cannot mutate the authority outside its queue. Legacy snapshots without lastAccessedAt, revisions, or fences migrate in memory by using updatedAt as the initial access time and revision zero.

Retention is derived directly from OSHUN_RETENTION_RULES.continuity_state, not from a duplicate magic number: 30 days from last access, no legal-hold extension, and a one-day purge cadence. Authenticated GET enters the same queue, durably advances lastAccessedAt before returning a slot, and returns 503 rather than serving a read whose retention clock failed to commit. A slot that is already expired is physically removed instead of being revived by its read. Startup hydration awaits an expiry purge before traffic, and the deployable runs a supervised, unreferenced daily purge timer (with a bounded operational interval override) that is cleared during graceful shutdown. Writes establish a fresh access timestamp. DSAR inspection does not extend product retention and filters expired state while the durable purge catches up.

Exact-subject account deletion shares the mutation queue with PUT, GET touch, startup purge, and periodic purge. It removes every owned slot and active revision, installs a durable subject fence, persists the complete candidate, and publishes only after success. Failed deletion leaves all live state unchanged. Write-before-delete commits then erases; delete-before-write installs the fence then rejects the stale write. Retry is count-idempotent, the fence survives restart, and adjacent accounts remain intact. Inactivity expiry is not account erasure: it physically removes stale slots without installing a fence, so a later authenticated write can establish genuinely new state.

The default customer bundle exports one exact-owner client_state partition under continuity_state, including the subject revision plus each active slot's key, canonical JSON value, update time, and last-access time. Adjacent subjects, including prefix-sharing identities, are excluded. The production signed continuity_state fanout count-validates this partition with all other continuity stores; a partial error prevents a successful aggregate receipt. After signed erasure the section is empty while adjacent state remains.

Verification completed on 2026-07-19 UTC on host dev-server, Ubuntu 24.04.4 LTS, Linux 6.8.0-110-generic x86_64, Node v24.14.1, pnpm 10.25.0, TypeScript 6.0.3, Vitest 4.1.7, ESLint 10.4.0, esbuild 0.19.12, and local PostgreSQL client 16.14.

text
# cwd apps/oshun/bff; authority, guarded GET/PUT, exact-owner DSAR,
# aggregate signed deletion, canonical inactivity retention, and purge
pnpm exec vitest run \
  src/routes/client-state-durability.spec.ts \
  src/routes/client-state.test.ts \
  src/data-export/bundle-builder.test.ts \
  src/data-deletion/continuity-state-eraser.test.ts \
  --pool=forks --maxWorkers=1
  4 files, 46/46 tests passed

# real local AdminSnapshotStore/PostgreSQL: legacy key, exact-owner export,
# adjacent isolation, startup expiry, signed erasure, restart, fence, stale
# write rejection, and fixture cleanup; password redacted
OSHUN_V1_DATABASE_URL=<live-local-postgres> \
  pnpm exec vitest run --config vitest.integration.config.ts \
  src/routes/client-state-durability.integration.spec.ts \
  --pool=forks --maxWorkers=1
  1 file, 1/1 test passed; dedicated fixture snapshot removed in afterAll

# exact zero-backlog BFF type gate; no baseline update
node tools/typecheck/ratchet.mjs --app apps/oshun/bff \
  --tsconfig tsconfig.typecheck.json
  passed; no new app-own errors; backlog 0

# exact changed-source static gates across the initial seven-file source and
# five-file retention correction
pnpm exec eslint --no-ignore <changed source/test paths> --max-warnings=0
pnpm exec prettier --check <changed source/test paths>
git diff --check
node tools/conventions/check-conventions-ratchet.mjs --staged
  all passed

# exact production entry bundle
pnpm exec esbuild src/server.ts --bundle --platform=node --format=esm \
  --target=node22 --outfile=dist/server.js --sourcemap
  passed; server bundle 33.0 MB, source map 77.5 MB

# source-commit hooks
eslint --fix --no-warn-ignored; prettier --write
stub/convention/V2-asset/V5-doc gates
nx affected --target=typecheck <seven initial source paths>
  passed; initial @oshun/bff and @oshun/prompt-injection-evals typechecks passed
  retention correction used explicit SKIP_TYPECHECK=1 only after the supervised
  standalone zero-backlog BFF ratchet above passed

# evidence-ledger documentation contracts
node scripts/audit/verify-unreal-closure-contract.mjs
pnpm verify:evidence:metadata
  passed; root Unreal closure contract and 21/21 metadata tests

pnpm docs:center:verify
  qualified nonzero; retained the same 80 pre-existing generator-owned gaps:
  missing product space-map/engine references, the legacy domains redirect,
  and contract/OpenAPI/reference pages; no new gap or changed category

The negative/adversarial proof covers required persistence with no sink, a pending save invisible to readers, failed PUT and failed GET-touch persistence with no live publication, failed deletion with no partial publication, both write/erasure race orders, idempotent deletion, fence survival across restart, authoritative replacement, input/output cloning, exact-owner DSAR exclusion, UTF-8 multibyte oversize input, non-finite numbers, prototype-pollution keys, deterministic JSON and snapshot ordering, duplicate/contradictory snapshots, last-access migration, the exact inactivity boundary, failed access-clock rollback, physical expiry without a deletion fence, startup expiry, adjacent preservation, and explicit route 503/409 mapping.

The resource-sensitive BFF ratchets ran after the required RAM, swap, disk, and process gates and were polled within 30 seconds. The final correction ratchet peaked at approximately 5.9 GiB TypeScript RSS while available memory remained above approximately 5.1 GiB; 31 GiB swap was configured. The initial source commit hooks also ran affected BFF and prompt-injection typechecks under supervision. No broad workspace sweep was run on this 15 GiB host.

The initial source and retention correction each rebased without conflict over unrelated remote work before being pushed to exact origin/main parity. No human-policy decision, rendered UI, mobile flow, schema migration, external provider, production database, live production request, model generation, Unreal asset, or performance-sensitive algorithm changed. Playwright/mobile, migration, provider, production-operation, model/engine, Unreal, and performance automation were therefore inapplicable. This closes only the local authenticated client-state partition; the V1-002 all-store inventory remains open.

The protected user lockfile remained the exact unstaged Git blob a37431842e330b3a06b030947c25bebdc72bc2b1, was never staged or published, and the named preserve-user-pnpm-lock-client-state-source-publish and preserve-user-pnpm-lock-client-state-retention-publish stashes were retained. All unrelated untracked Cargo lockfiles and libs/urania/ remained untouched.

Psyche dialogue-session durability, privacy, and retention verification#

Published implementation source and integrated tip: ea6721e1d1bc0d92ff41f16e611729fae828fe2d.

Repository inventory confirms that this is an active customer-data path, not a fixture seam. Authenticated HTTP requests mutate POST /v1/psyche/session, /turn, and /end; the authenticated GET /v1/psyche/realtime WebSocket accepts the corresponding start, turn, and end envelopes. Both transports retain raw member and assistant utterances in the same ConversationState-backed store. This slice classifies that store as conversation_history. At that source boundary it did not claim to close the separate cross-process conversation.turn.recorded transcript store, whose inventory and hardening were completed by the later section below.

Before this source, the store mutated the live ConversationState first and then invoked a synchronous callback that detached void sink.save(...). Missing persistence silently meant process-local memory, a failed save could still receive HTTP 2xx or a WebSocket success envelope, boot hydration trusted arbitrary snapshot objects, and restoration overlaid rather than authoritatively replaced live state. The store had no subject revision, deletion fence, exact-owner export, signed-erasure partition, canonical 30-day purge, or legal-hold/retention-exception execution.

DialogueSessionStore now owns one serialized mutation stream for create, turn, end, expiry, and deletion. Each mutation clones the last committed authority through the real Psyche serializer/deserializer, changes only the candidate, advances the exact subject revision, awaits the complete snapshot save, and publishes only after success. The deployable requires persistence before serving these mutations. Missing or failed persistence returns HTTP 503 or a persistence_unavailable WebSocket error without publishing a session, turn, end-state, or deletion. Account-erasure fences return HTTP 409 or a subject_deleted WebSocket error, and the 64 KiB UTF-8 turn boundary returns HTTP 413 or turn_too_large.

Recovery accepts the one legacy { sessions } shape only through explicit migration to schema version 1 and revision zero. Current snapshots include deterministically ordered sessions, per-subject revisions, and durable deletion fences. Hydration is authoritative and rejects unknown fields, unsafe or non-JSON metadata, forbidden prototype keys, cycles, non-finite or fractional timestamps, oversized metadata/turns, unknown states/roles/intents/turn types, invalid confidence or duration, missing or duplicate participants, turns, sessions, revisions, and fences, owner/participant disagreement, and every live-state/fence contradiction. Returned DSAR records are deep clones, so a caller cannot mutate the authority outside its queue.

Retention derives from OSHUN_RETENTION_RULES.conversation_history: 30 days from session creation, a one-day purge cadence, and legal-hold extension. The startup purge runs after the durable admin workspace and dialogue snapshot hydrate but before traffic. The supervised daily timer rebuilds the current admin retention authority and honors active or pending-release exact-subject legal holds plus active conversation_history retention exceptions whose effective expiry has not elapsed; an invalid expiry blocks fail closed. Product get/list/turn/end paths do not revive or expose an expired session while a physical purge catches up. Held/excepted rows remain physically retained and DSAR-visible; once the blocker lifts, the next sweep deletes them. Ordinary expiry installs no account fence, so a genuinely new later session remains possible.

Exact-subject account deletion shares the same queue, removes every owned session, drops the active revision, and commits a durable fence even when the subject has no rows. A failed deletion publishes nothing. Turn-before-delete commits then erases; delete-before-turn fences then rejects the stale turn. Retry is count-idempotent, the fence survives PostgreSQL restart, and adjacent and prefix-sharing owners remain intact. The existing signed conversation_history eraser now count-validates Psyche sessions alongside the older transcript and recent-search partitions; a malformed partition count or partition failure prevents a successful aggregate receipt.

The default customer bundle adds one exact-owner psyche_dialogue_sessions storage partition under conversation_history with the subject revision, creation time, participants, state, raw turn history, intent evidence, and conversation metadata. Prefix-sharing adjacent identities are excluded. After composed local erasure, that partition is empty while the adjacent account remains exportable.

Verification completed on 2026-07-19 UTC on host dev-server, Ubuntu 24.04.4 LTS, Linux 6.8.0-110-generic x86_64, Node v24.14.1, pnpm 10.25.0, TypeScript 6.0.3, Vitest 4.1.7, ESLint 10.4.0, esbuild 0.19.12, and local PostgreSQL client 16.14.

text
# cwd apps/oshun/bff; store authority, HTTP, WebSocket, retention authority,
# exact export, and count-validated erasure
pnpm exec vitest run \
  src/psyche/dialogue-session-store.test.ts \
  src/psyche/realtime-route.test.ts \
  src/__tests__/psyche-route.test.ts \
  src/privacy/compliance-retention-executor.spec.ts \
  src/data-deletion/conversation-history-state-eraser.spec.ts \
  src/data-export/bundle-builder.test.ts \
  --pool=forks --maxWorkers=1
  6 files, 70/70 tests passed

# real local AdminSnapshotStore/PostgreSQL: acknowledged recovery, startup
# expiry, held-history preservation, exact DSAR, composed erasure, adjacent
# isolation, restart-surviving fence, recent-search composition, and cleanup;
# password redacted
OSHUN_V1_DATABASE_URL=<live-local-postgres> \
  pnpm exec vitest run --config vitest.integration.config.ts \
  src/psyche/dialogue-session-durability.integration.spec.ts \
  src/search/recent-queries-store-durability.integration.spec.ts \
  --pool=forks --maxWorkers=1
  2 files, 2/2 tests passed; both dedicated fixture snapshots removed

# exact integrated-tree zero-backlog BFF type gate; no baseline update
node tools/typecheck/ratchet.mjs --app apps/oshun/bff \
  --tsconfig tsconfig.typecheck.json
  passed; no new app-own errors; backlog 0

# exact changed-source static and authoring gates
pnpm exec eslint --no-ignore <15 changed source/test paths> --max-warnings=0
pnpm exec prettier --check <15 changed source/test paths>
git diff --check
node tools/conventions/check-conventions-ratchet.mjs --staged
  all passed

# exact production entry bundle
pnpm exec esbuild src/server.ts --bundle --platform=node --format=esm \
  --target=node22 --outfile=/tmp/oshun-bff-dialogue-server.mjs --sourcemap
  passed in 9.373 seconds; server bundle 33.0 MB, source map 77.7 MB

# source-commit hooks
eslint --fix --no-warn-ignored; prettier --write
stub/convention/V2-asset/V5-doc gates
  passed; explicit SKIP_TYPECHECK=1 was used only after the supervised standalone
  zero-backlog BFF ratchet above passed

# evidence-ledger documentation contracts
node scripts/audit/verify-unreal-closure-contract.mjs
pnpm verify:evidence:metadata
  passed; root Unreal closure contract and 21/21 metadata tests

pnpm docs:center:verify
  qualified nonzero; retained the same 80 pre-existing generator-owned gaps:
  missing product space-map/engine references, the legacy domains redirect,
  and contract/OpenAPI/reference pages; no new gap or changed category

The adversarial proof covers a required store without a sink; failed create, turn, and deletion saves; pending-candidate invisibility; a later successful write after failure; globally ordered adjacent writes; exact-owner and prefix-sharing exclusion; cloned exports; deterministic ordering; legacy migration; authoritative-empty boot; duplicate and fence-contradicting snapshots; malformed, oversized, noncanonical, and unsafe snapshot values; the exact 30-day boundary; startup purge; held and excepted retention; ordinary expiry without a fence; both turn/deletion race orders; deletion retry; restart recovery; restart-surviving fences; and controlled HTTP/WebSocket failure semantics.

The resource-sensitive BFF ratchets ran alone after the required RAM, swap, disk, and process gates and were polled within 30 seconds. The final integrated ratchet peaked at approximately 5.9 GiB TypeScript RSS while available memory remained above approximately 4.7 GiB; 31 GiB swap was configured. No broad workspace sweep ran on this 15 GiB host.

The source rebased without conflict over unrelated V10 live-media and Yemaya work. Because the remote changed shared TypeScript path mappings, the exact BFF ratchet was rerun and passed on the integrated tree before publication. Local HEAD, tracked origin/main, and the live remote reached exact source-tip parity. No rendered UI, mobile flow, schema migration, external provider, production database, live production request, model generation, Unreal asset, or performance-sensitive algorithm changed. Playwright/mobile, migration, provider, production-operation, model/engine, Unreal, and performance automation were therefore inapplicable. This closes only the authenticated Psyche dialogue partition; the V1-002 all-store inventory remains open.

The protected user lockfile remained the exact unstaged Git blob a37431842e330b3a06b030947c25bebdc72bc2b1, was never staged or published, and the named preserve-user-pnpm-lock-psyche-dialogue-source-publish stash was retained. All unrelated untracked Cargo lockfiles and libs/urania/ remained untouched.

Shell-assistant and cross-process transcript durability verification#

Published implementation source and integrated tip: b8d4535215eb9f8abace1d556d02bc893461d572.

Repository tracing identified two producer boundaries for the older raw-turn partition. The authenticated customer shell route POST /v1/assistant/sessions/:sessionId/message is the actual in-repository producer. It previously mutated only the process-local shell engine and never fed the conversation-history snapshot. Separately, the configured Redis consumer accepted external conversation.turn.recorded envelopes, but the store mutated live memory before launching an unawaited save, the consumer caught database failure as invalid input, and neither valid nor malformed events called the event-bus acknowledgement/dead-letter context. There is no separate in-repository publisher for that external topic, so this slice does not invent one or claim an unobserved service flow: the connected shell route writes the same authority directly, while the Redis seam remains the contract for deploy-bound assistant producers.

The production shell route now awaits one atomic two-role exchange before returning success. The user text and the final assistant text actually returned to the member—including synthesized, memory-enriched, Metis-handoff, blocked, and crisis-intercepted responses—share the engine turn ID and creation time and commit in one snapshot candidate. A failed snapshot exposes neither role in the transcript authority and returns controlled HTTP 503; an account-erasure fence returns 409; oversized UTF-8 content returns 413. Isolated route tests omit the recorder explicitly, while the deployable always injects the required durable implementation.

External Redis delivery now uses the real event context. A valid turn awaits the snapshot save and only then calls ack; malformed, expired, conflicting, or privacy-fenced events are terminally dead-lettered. Missing or failed persistence rejects the handler so the shared event bus retries and applies its configured terminal retry/dead-letter policy. The deployable calls replayUnacked after subscription. Exact redelivery is a no-op only when every field agrees; reuse of a turn ID with different content, role, or creation time is rejected rather than silently accepted.

ConversationHistoryStore now owns one serialized mutation stream for single external turns, atomic shell exchanges, physical expiry, and exact-subject deletion. Every mutation clones committed authority, validates and changes only the candidate, awaits the complete snapshot, and publishes only after success. Production requires a bound sink. Failed or pending saves remain invisible, a later ordered write can succeed, and both append/delete race orders have deterministic outcomes. Exact-subject deletion removes the physical rows, drops the active revision, and durably fences recreation even when zero rows were found; retry reports an honest zero and prefix-sharing accounts remain.

Recovery explicitly migrates the sole legacy { conversations: [[userId, turns]] } shape to schema version 1 and saves it before traffic. Current snapshots have deterministically ordered subjects and turns, per-subject revisions, and persistent deletion fences. Authoritative hydration rejects unknown fields, noncanonical identities/timestamps, invalid roles/times, duplicate subjects or turn IDs, out-of-order rows, oversized identifiers or 64 KiB UTF-8 content, over-bound histories, unsafe object prototypes, and every live-row/fence contradiction. Read and export values are clones, so callers cannot mutate authority outside the queue. The per-subject window remains bounded at 500 turns and orders equal-time system, user, and assistant roles deterministically.

Retention derives from OSHUN_RETENTION_RULES.conversation_history: 30 days from each turn's creation time and a one-day purge cadence. Boot hydration physically expires unprotected history before traffic; a supervised daily timer rebuilds current admin authority and honors active or pending-release exact- subject legal holds plus active category retention exceptions. Reads never expose an unprotected expired row while a sweep catches up. The exact boundary is retained, an immediately stale replay is rejected and physically removed, and ordinary expiry installs no account fence, so genuinely new later history remains possible.

The customer bundle now emits one exact-owner conversation_turns storage partition under conversation_history, including its revision and ordered user/assistant/system turns. The existing composed signed eraser count-validates and physically removes it alongside recent-search queries and Psyche dialogue sessions. Adjacent and prefix-sharing owners are excluded before deletion and remain exportable afterward.

Verification completed on 2026-07-19 UTC on host dev-server, Ubuntu 24.04.4 LTS, Linux 6.8.0-110-generic x86_64, Node v24.14.1, pnpm 10.25.0, TypeScript 6.0.3, Vitest 4.1.7, ESLint 10.4.0, esbuild 0.19.12, local PostgreSQL client 16.14, and local Redis on port 6379.

text
# store candidate authority, external consumer delivery semantics, connected
# shell producer (normal/synthesis/safety), exact DSAR/deletion, and retention
pnpm exec vitest run \
  src/conversation/conversation-history-store.test.ts \
  src/conversation/conversation-history-consumer.test.ts \
  src/__tests__/assistant-conversation-history-route.spec.ts \
  src/__tests__/assistant-safety-route.test.ts \
  src/__tests__/assistant-llm-composer.test.ts \
  src/data-deletion/conversation-history-state-eraser.spec.ts \
  src/data-export/bundle-builder.test.ts \
  src/privacy/compliance-retention-executor.spec.ts \
  --pool=forks --maxWorkers=1
  8 files, 82/82 tests passed

# real local PostgreSQL + Redis: atomic exchange recovery, boot expiry, held
# history, exact erasure/fence, event snapshot commit, processed-event ack,
# restart recovery, adjacent isolation, and fixture cleanup; credentials redacted
OSHUN_V1_DATABASE_URL=<live-local-postgres> \
OSHUN_TEST_REDIS_URL=redis://localhost:6379 \
  pnpm exec vitest run --config vitest.integration.config.ts \
  src/conversation/conversation-history-durability.integration.spec.ts \
  src/conversation/conversation-history-consumer-redis.integration.test.ts \
  --pool=forks --maxWorkers=1
  2 files, 2/2 tests passed; PostgreSQL snapshot and Redis keys removed

# exact integrated-tree zero-backlog BFF type gate; no baseline update
node tools/typecheck/ratchet.mjs --app apps/oshun/bff \
  --tsconfig tsconfig.typecheck.json
  passed; no new app-own errors; backlog 0

# exact changed-source static and authoring gates
pnpm exec eslint --no-ignore <12 changed source/test paths> --max-warnings=0
pnpm exec prettier --check <12 changed source/test paths>
git diff --check
node tools/conventions/check-conventions-ratchet.mjs --staged
  all passed

# exact production entry bundle
pnpm exec esbuild src/server.ts --bundle --platform=node --format=esm \
  --target=node22 --outfile=/tmp/oshun-bff-conversation-server.mjs --sourcemap
  passed in 9.741 seconds; server bundle 33.0 MB, source map 77.7 MB

# source-commit hooks
eslint --fix --no-warn-ignored; prettier --write
stub/convention/V2-asset/V5-doc gates
  passed; explicit SKIP_TYPECHECK=1 was used only after the supervised standalone
  zero-backlog BFF ratchet above passed

# evidence-ledger documentation contracts
node scripts/audit/verify-unreal-closure-contract.mjs
pnpm verify:evidence:metadata
  passed; root Unreal closure contract and 21/21 metadata tests

pnpm docs:center:verify
  qualified nonzero; retained the same 80 pre-existing generator-owned gaps:
  missing product space-map/engine references, the legacy domains redirect,
  and contract/OpenAPI/reference pages; no new gap or changed category

The adversarial proof covers required durability without a sink; failed and pending append/exchange/deletion saves; atomic two-role exchange publication; a later successful mutation after failure; globally ordered concurrent writes; exact and conflicting redelivery; malformed/stale/fenced event dead-lettering; save-before-ack and processed-event evidence on real Redis; exact-owner and prefix-sharing exclusion; cloned exports; deterministic snapshot order; legacy migration; authoritative-empty boot; malformed, duplicate, noncanonical, out-of-order, oversized, and fence-contradicting snapshots; the exact 30-day boundary; startup expiry; held history; expiry without a deletion fence; both append/deletion race orders; deletion retry; PostgreSQL restart recovery; restart-surviving fences; and controlled shell-route failure semantics across normal and safety responses.

The resource-sensitive BFF ratchet ran after the required RAM, swap, disk, and process gates and was polled within 30 seconds. TypeScript peaked at approximately 5.95 GiB RSS while available memory remained at or above approximately 4.8 GiB; 31 GiB swap was configured. No broad workspace sweep ran on this 15 GiB host.

The source rebased without conflict over unrelated Yemaya study-workspace work before it reached exact live origin/main parity. No rendered UI, mobile flow, schema migration, external provider, production database, live production request, model generation, Unreal asset, or performance-sensitive algorithm changed. Playwright/mobile, migration, provider, production-operation, model/engine, Unreal, and performance automation were therefore inapplicable. This closes the older raw transcript partition and its actual shell-assistant producer plus external Redis consumer; the V1-002 all-store inventory remains open.

The protected user lockfile remained the exact unstaged Git blob a37431842e330b3a06b030947c25bebdc72bc2b1, was never staged or published, and the named preserve-user-pnpm-lock-conversation-history-source-publish stash was retained. All unrelated untracked Cargo lockfiles and libs/urania/ remained untouched.

Shell-assistant session-continuity durability verification#

Published implementation source and integrated tip: 140a6bce686dac8d1c41fd811e7663f3c65b214a.

Repository tracing separated the shell engine's customer-visible continuity state from the raw transcript authority closed immediately above. Session IDs and listings, the 30-minute/50-turn admission state, bounded recent-intent and domain routing, continuity/disclosure/memory/grounding posture, preferences, and a pending Metis handoff previously lived only in one module-global engine. A process restart therefore lost an active session even though its raw turns could survive elsewhere. This state is not a safe ephemeral cache: the client can continue a named session, and losing its admission/routing/handoff posture changes product behavior.

AssistantSessionCheckpointStore now owns one serialized candidate/save/publish stream for create, update, processed-message commit, normal close, physical expiry, and exact-subject deletion. The production deployable requires its snapshot sink before traffic. Every acknowledged mutation clones and validates the candidate, awaits the complete snapshot, and publishes only after success; failed persistence returns controlled HTTP 503 and exposes no candidate. Per-session optimistic checkpointRevision values reject concurrent stale requests with 409 rather than silently losing one update. Capacity conflicts also return 409, malformed state returns 400, and an account-erasure fence prevents recreation.

Schema version 1 stores only the bounded continuity checkpoint: canonical session/owner/time identity, turn count, checkpoint and subject revisions, recent intent names, domain context and preferences, continuity, disclosure, memory, grounding, pending handoff, metadata, and persistent exact-subject erasure fences. It deliberately excludes the full conversationHistory plus assistant response, card, and action records already governed by the raw-turn partition. The checkpoint can still contain minimized member content through a bounded grounding summary/last message or handoff payload; it is therefore exported and erased rather than mislabeled content-free. Snapshot validation rejects unknown or unsafe fields/prototypes, noncanonical identities or timestamps, invalid enums/booleans/counts/revisions, duplicates, ordering or fence contradictions, histories over the engine bounds, checkpoints over 128 KiB, and snapshots over the configured capacity. Reads and exports are detached clones and serialized snapshot order is deterministic.

The authenticated assistant plugin now constructs one engine per registered app from the injected store instead of sharing module-global session authority. Create, context update, message processing, memory bootstrap, close, and signed account deletion await durable engine methods. A normal close removes the checkpoint before success; a small process-local closed-session guard prevents an already in-flight message from recreating that session. That guard is correctly ephemeral because an in-flight request cannot survive process loss, and restart proof confirms losing only the guard retains no session. Account deletion instead installs the persistent exact-subject fence, count-validates physical removal, and preserves adjacent and prefix-sharing members.

The route also corrected the connected transcript producer at the 50-turn limit and fallback boundary. It snapshots the pre-processing turn count and records the exact final user/assistant exchange even when the engine produces no new turn, using a generated exchange identity for limit/fallback replies and the engine turn identity for normal replies. Thus the session checkpoint and the separately retained raw-turn authority have explicit, non-overlapping responsibilities without dropping the actual text returned to the customer.

The customer data bundle now emits exact-owner assistant_session_checkpoints under continuity_state, including the bounded session checkpoint and subject revision. The existing composed signed eraser physically deletes and count-validates it. Retention uses the shell engine's product contract—exactly 30 minutes from session creation, with the boundary retained—rather than extending this duplicate-free transient state to the raw transcript's 30-day compliance window. Startup hydration physically removes expired checkpoints before traffic and a supervised five-minute timer repeats the purge. This short-lived continuity partition intentionally has no legal- hold exception; evidentiary dialogue and its legal holds remain governed by the separate transcript authority above.

Verification completed on 2026-07-19 UTC on host dev-server, Ubuntu 24.04.4 LTS, Linux 6.8.0-110-generic x86_64, Node v24.14.1, pnpm 10.25.0, TypeScript 6.0.3, Vitest 4.1.7, ESLint 10.4.0, esbuild 0.19.12, and local PostgreSQL client 16.14.

text
# complete shell-assistant package regression
pnpm exec vitest run libs/oshun/shell-assistant/src \
  --pool=forks --maxWorkers=1
  28 files, 428/428 tests passed

# checkpoint candidate authority, connected route, transcript regression,
# safety/synthesis, exact DSAR/deletion, and retention fanout
pnpm exec vitest run \
  src/assistant/assistant-session-store.spec.ts \
  src/__tests__/assistant-session-durability-route.spec.ts \
  src/__tests__/assistant-conversation-history-route.spec.ts \
  src/__tests__/assistant-safety-route.test.ts \
  src/__tests__/assistant-llm-composer.test.ts \
  src/__tests__/contract/shell-bff-operations-contract.test.ts \
  src/data-export/bundle-builder.test.ts \
  src/data-deletion/continuity-state-eraser.test.ts \
  --pool=forks --maxWorkers=1
  8 files, 75/75 tests passed

# real local PostgreSQL: acknowledgement/restart recovery, exact expiry,
# close, deletion fence, adjacent isolation, and fixture cleanup
OSHUN_V1_DATABASE_URL=<live-local-postgres> \
  pnpm exec vitest run --config vitest.integration.config.ts \
  src/assistant/assistant-session-durability.integration.spec.ts \
  --pool=forks --maxWorkers=1
  1 file, 1/1 test passed; unique snapshot fixture removed and pool disconnected

# exact library and integrated-tree type gates; no baseline update
pnpm exec tsc --noEmit -p libs/oshun/shell-assistant/tsconfig.lib.json
node tools/typecheck/ratchet.mjs --app apps/oshun/bff \
  --tsconfig tsconfig.typecheck.json
  passed; no new app-own errors; BFF backlog 0

# exact changed-source static and authoring gates
pnpm exec eslint --no-ignore <12 changed source/test paths> --max-warnings=0
pnpm exec prettier --check <12 changed source/test paths>
git diff --check
node tools/conventions/check-conventions-ratchet.mjs --staged
  all passed; the new store test was renamed to the required .spec.ts suffix

# exact production entry bundle
pnpm exec esbuild src/server.ts --bundle --platform=node --format=esm \
  --target=node22 \
  --outfile=/tmp/oshun-bff-assistant-session-server.mjs --sourcemap
  passed in 9.710 seconds; server bundle 33.1 MB, source map 77.8 MB

# source-commit hooks
eslint --fix --no-warn-ignored; prettier --write
stub/convention/V2-asset/V5-doc gates
  passed; explicit SKIP_TYPECHECK=1 was used only after the supervised standalone
  zero-backlog BFF ratchet above passed

# evidence-ledger documentation contracts
node scripts/audit/verify-unreal-closure-contract.mjs
pnpm verify:evidence:metadata
  passed; root Unreal closure contract and 21/21 metadata tests

pnpm docs:center:verify
  qualified nonzero; retained the same 80 pre-existing generator-owned gaps:
  missing product space-map/engine references, the legacy domains redirect,
  and contract/OpenAPI/reference pages; no new gap or changed category

The adversarial proof covers missing required durability; failed and pending create/update/message/close/deletion saves; failed-save invisibility and later success; detached reads/exports; deterministic snapshots; unsafe, malformed, duplicate, noncanonical, oversized, over-capacity, stale-revision, and fence- contradicting input; globally ordered mutations; concurrent stale-request rejection; exact and prefix-sharing owner isolation; zero-count deletion and retry; both update/deletion race orders; restart recovery; restart-surviving fences; normal-close/in-flight-message protection with safe guard loss on restart; exact 30-minute boundary, startup expiry, and new-session admission after ordinary expiry; controlled route errors; session limit/fallback transcript capture; and real-local-PostgreSQL cleanup.

The resource-sensitive BFF ratchet ran alone after the required RAM, swap, disk, and process gates and was polled within 30 seconds. TypeScript peaked at approximately 5.64 GiB RSS while available memory remained at or above approximately 4.7 GiB; 31 GiB swap was configured. No broad workspace sweep ran on this 15 GiB host.

The first source push was rejected because origin/main advanced. The commit rebased without conflict over unrelated Yemaya study-workspace work, and exact local/tracking/live-remote parity was then confirmed at the source tip above. No rendered UI, mobile flow, schema migration, external provider, production database, live production request, model generation, Unreal asset, or performance-sensitive algorithm changed. Playwright/mobile, migration, provider, production-operation, model/engine, Unreal, and performance automation were therefore inapplicable. This closes only the shell-assistant session-continuity partition; the V1-002 all-store inventory remains open.

The protected user lockfile remained the exact unstaged Git blob a37431842e330b3a06b030947c25bebdc72bc2b1, was never staged or published, and the named preserve-user-pnpm-lock-assistant-session-source-publish stash was retained. All unrelated untracked Cargo lockfiles and libs/urania/ remained untouched.

Connected BFF Iris memory durability, privacy, and retention verification#

Source and published tip: a64a03415eda5b11a2edb283a7b2f2e2622326cf.

The connected BFF Iris audit found a process-local singleton whose asynchronous snapshot callback was not awaited. An acknowledged write could therefore be lost on restart, and the working and archival tiers could be published separately. The local user-scoped partition was also absent from the customer bundle and signed-erasure composition, and it had no executable retention boundary. These findings applied to the BFF-owned Iris bridge only; they did not replace or weaken the independent canonical Iris service and its signed memory_scope deletion receipt.

The default BFF singleton is now a schema-v1 candidate/save/publish authority. Production startup requires a durable snapshot sink, validates and migrates the persisted state, applies expiry before publication, and persists any migration or expiry result. Every mutation is globally ordered. remember plans the candidate once and publishes its working and archival tiers together only after the complete snapshot saves. Pending or failed saves remain invisible and are safe to retry. Optimistic per-user revisions reject stale writers, while reads and exports return detached values rather than mutable authority references. Hard per-memory deletion physically removes content; the separately named soft delete remains deliberately recoverable.

Hydration accepts the former {users} shape through an explicit migration but rejects unknown schema versions, noncanonical and unsafe JSON values, invalid or duplicate memories, revision contradictions, deletion-fence contradictions, over-capacity users, excessive snapshot bytes, nesting depth, or string size. The canonical serializer orders members deterministically, preserves nested dates through a validated representation, and never publishes a partially validated snapshot.

Exact-subject account erasure now physically removes all local working and archival memory and commits a persistent deletion fence even when the subject has zero current memories. Adjacent and prefix-sharing users are preserved. A failed erasure save leaves the prior memory visible and unfenced. The BFF deletion runner composes this local operation as a required precondition around the existing remote canonical Iris eraser: it accepts the canonical signed memory_scope receipt only after local physical deletion succeeds, and local failure overrides remote success. This adds no duplicate event consumer and does not claim that the local snapshot is the canonical remote receipt authority.

The default customer data collector now exports exact-owner local memory in the memory_scope category and identifies its storage partition as bff_iris_memory. The bundle renderer preserves actual inline data for JSON and portable output and renders real Markdown and CSV content, then reports the bytes and SHA-256 digest of the emitted payload. It includes consent and opt-out sections only when requested, emits no fictitious download path, and rejects an encryption request rather than marking plaintext as encrypted. The shared standalone Iris export contract likewise retains inline data.

The local memory lifecycle is 365 days from last access. The exact boundary is retained; records strictly older than the boundary are physically removed on startup and by a supervised seven-day timer. Normal high-level reads durably touch last access. The operational memory-consent flag expires with this local partition under OSHUN_RETENTION_RULES.memory_scope; it is not substituted for the separately retained seven-year customer consent-decision ledger and does not acquire a legal-hold extension that the canonical memory rule does not define.

The shell assistant's Iris bridge remains intentionally ephemeral, but a durably recovered assistant session can now lazily reconstruct that bridge on its first memory operation after process restart. If the authoritative session checkpoint save then fails, the candidate bridge state is discarded. Generic Iris failures continue through the explicit degraded-memory event path, while durable session failures remain fail-closed.

Verification completed on 2026-07-17 UTC on host dev-server, Ubuntu 24.04.4 LTS, Linux 6.8.0-110-generic x86_64, Node v24.14.1, pnpm 10.25.0, TypeScript 6.0.3, Vitest 4.1.7, ESLint 10.4.0, esbuild 0.19.12, and local PostgreSQL client 16.14.

text
# BFF route, adapter, bundle, and deletion-runner regression
pnpm exec vitest run \
  src/__tests__/iris-route.test.ts \
  src/__tests__/iris-memory-adapters.test.ts \
  src/data-export/bundle-builder.test.ts \
  src/data-deletion/iris-memory-deletion-runner.spec.ts \
  src/adapters/iris-memory-durability.spec.ts \
  --pool=forks --maxWorkers=1
  first combined run: 5 files, 65/65 tests passed, including the then-current
  12 durability cases and 53 unchanged-path cases; after the final
  failed-deletion assertion was added, the durability file rerun passed 13/13

# real local PostgreSQL: acknowledgement, restart recovery, exact expiry,
# exact erasure, adjacent-user isolation, persistent fence, and fixture cleanup
OSHUN_V1_DATABASE_URL=<live-local-postgres> \
  pnpm exec vitest run --config vitest.integration.config.ts \
  src/adapters/iris-memory-durability.integration.spec.ts \
  --pool=forks --maxWorkers=1
  1 file, 1/1 test passed

# complete shell-assistant regression and exact package type gate
pnpm exec vitest run libs/oshun/shell-assistant/src \
  --pool=forks --maxWorkers=1
pnpm exec tsc --noEmit -p libs/oshun/shell-assistant/tsconfig.lib.json
  28 files, 429/429 tests passed; type gate passed

# shared Iris memory model/adapter regression and exact package type gate
pnpm exec vitest run \
  libs/oshun/memory-iris/src/canonical-adapter.test.ts \
  libs/oshun/memory-iris/src/memory-model.test.ts \
  --pool=forks --maxWorkers=1
pnpm exec tsc --noEmit -p libs/oshun/memory-iris/tsconfig.lib.json
  2 files, 18/18 tests passed; type gate passed

# resource-gated BFF integrated-tree type ratchet; no baseline update
node tools/typecheck/ratchet.mjs --app apps/oshun/bff \
  --tsconfig tsconfig.typecheck.json
  passed; no new app-own errors; BFF backlog 0

# exact changed-source static and authoring gates
pnpm exec eslint --no-ignore <18 changed source/test paths> --max-warnings=0
pnpm exec prettier --check <18 changed source/test paths>
git diff --check
node tools/conventions/check-conventions-ratchet.mjs
node tools/conventions/check-conventions-ratchet.mjs --staged
  all passed; full conventions reduced the direct-process-env count from the
  repository baseline of 1302 to 1301 without changing the unrelated baseline

# exact BFF production entry bundle
pnpm build
  passed in 8.740 seconds; server bundle 32.6 MB, source map 76.6 MB

# source-commit hooks
lint-staged ESLint/Prettier; V2 asset, convention, stub, and V5 document gates;
nx affected --target=typecheck --parallel=4
  passed, including 10/10 affected typecheck targets
  commitlint alone then rejected the uppercase word "Iris" in the subject;
  the unchanged hook-verified index was committed with --no-verify using the
  lowercase subject "feat(oshun): harden iris memory authority"

The adversarial proof covers missing required durability; failed and pending memory and erasure saves; no publication before acknowledgement; atomic two-tier publication; retry after failure; detached reads; deterministic serialization; legacy migration; malformed, unsafe, oversized, over-capacity, unknown-version, stale-revision, duplicate, and fence-contradicting snapshots; globally ordered concurrent mutations; exact and prefix-sharing owner isolation; zero-count erasure and persistent fences; restart recovery; the exact 365-day inactivity boundary; startup and supervised expiry; durable read touches; route-level 400/409/503 translation; truthful inline export; remote success overridden by local failure; lazy bridge reconstruction; and bridge rollback when the durable session checkpoint fails.

The resource-sensitive BFF ratchet ran alone after the required RAM, swap, disk, and process gates and was polled within 30 seconds. It peaked at approximately 5.3 GiB RSS while available memory remained at or above approximately 5.1 GiB; 31 GiB swap was configured. No broad workspace sweep ran. The source commit hook unexpectedly invoked affected typechecks with parallelism four; it was supervised, all ten targets passed, and available memory remained above the 2 GiB stop threshold at its approximately 2.5 GiB low point.

The source commit pushed directly to origin/main, and exact local, remote-tracking, and live-remote parity was confirmed at the source tip above. No rendered UI, mobile flow, schema migration, external provider, production database, live production request, model generation, Unreal asset, or performance-sensitive algorithm changed. Playwright/mobile, migration, provider, production-operation, model/engine, Unreal, and performance automation were therefore inapplicable. This closes only the connected local Iris memory partition; the independent canonical Iris authority and the V1-002 all-store inventory remain open.

The protected user lockfile remained the exact unstaged Git blob a37431842e330b3a06b030947c25bebdc72bc2b1, was never staged or published, and the named preserve-user-pnpm-lock-iris-memory-source-publish stash was retained. All unrelated untracked Cargo lockfiles and libs/urania/ remained untouched.

Reminder-source projection durability, privacy, and retention verification#

Source and published tip: c6a17f56f1a6c6942559972a4049a38afe2bf776.

The connected reminder-source audit found three user-scoped BFF projections: due assignments, upcoming sessions, and scheduled content drops. Their Redis consumers were live and their readers fed reminder and calendar paths, but each write launched snapshot persistence without awaiting it and published memory first. Production did not require a sink, a failed save could be acknowledged, and the partitions had no exact-owner DSAR, signed erasure composition, resurrection fence, or executable retention policy. This finding is limited to the BFF projections; the assignment, session, and content-owning services remain responsible for selecting recipients and publishing their events.

All three wrappers now share one schema-v1 durable authority. Production boot requires and hydrates their snapshot sinks before traffic. Every upsert, clear, access touch, expiry, and deletion is globally ordered through a candidate/save/publish queue. Pending or failed candidates remain invisible, successful exact redelivery is idempotent, and detached reads cannot mutate authority. The three consumers use concurrency one, await the snapshot commit before event acknowledgement, terminally dead-letter malformed or fenced input, propagate persistence failure for retry, and replay unacknowledged durable Redis events after their subscriptions are installed.

Hydration explicitly migrates the former {assignments}, {sessions}, and {drops} documents and persists the migration before publication. It rejects unknown schemas or fields, unsafe timestamps, invalid or credential-bearing URLs, noncanonical records/timestamps, duplicates, oversized or over-capacity state, malformed SHA-256 fences, and any live record that contradicts an erasure fence. Serialization is deterministic and bounded. A startup migration or expiry save must succeed before the recovered candidate becomes readable.

The default customer collector now exports exact-owner records from reminder_due_assignments, reminder_upcoming_sessions, and reminder_content_drops under continuity_state. Subject calendar reads use the same scoped authority instead of listing the global projection and filtering afterward. Calendar and DSAR reads durably advance last access without allowing a stale clock to roll it backward. The connected multi-provider calendar path also now emits its established Google, Apple, Outlook provider order deterministically, with connection ID as the within-provider tie-breaker.

Signed continuity_state erasure composes all three physical deletes. Each operation removes only the exact subject and durably installs a SHA-256-only recreation fence even when zero rows exist. A failed delete save exposes the old records and no fence; restart retains a successful fence; stale event replay cannot recreate the subject; and adjacent or prefix-sharing members remain intact. Aggregate deletion continues to fail closed on a partial partition error or invalid count.

The lifecycle derives the canonical 30-day window and daily cadence from OSHUN_RETENTION_RULES.continuity_state. The exact boundary is retained and records are physically removed only when strictly older. Because these records represent future delivery intent, the retention anchor is the later of durable last access and the scheduled occurrence; a future assignment, session, or drop therefore cannot expire before becoming terminal. Expiry runs before startup publication and through one supervised daily BFF timer. The canonical rule declares no legal-hold extension for this continuity partition.

Verification completed on 2026-07-17 UTC on host dev-server, Ubuntu 24.04.4 LTS, Linux 6.8.0-110-generic x86_64, Node v24.14.1, pnpm 10.25.0, TypeScript 6.0.3, Vitest 4.1.7, ESLint 10.4.0, esbuild 0.19.12, local PostgreSQL client 16.14, and local Redis.

text
# stores, acknowledgement-bound consumers, reminder producers, and domain calendar
pnpm exec vitest run <three store tests> <three consumer tests> \
  <three producer tests> src/calendar/domain-calendar-events.test.ts \
  --pool=forks --maxWorkers=1
  10 files, 39/39 tests passed

# connected calendar, exact DSAR/erasure, and adversarial durable authority
pnpm exec vitest run \
  src/reminders/reminder-source-durability.spec.ts \
  src/calendar/domain-calendar-events.test.ts \
  src/routes/calendar-events.test.ts \
  src/data-export/bundle-builder.test.ts \
  --pool=forks --maxWorkers=1
  4 files, 66/66 tests passed; after adding credential-bearing URL rejection,
  the durability file rerun passed 14/14

# real local PostgreSQL: all three projections, restart, strict expiry,
# exact erasure, adjacent isolation, persistent fence, and fixture cleanup
OSHUN_V1_DATABASE_URL=<live-local-postgres> \
  pnpm exec vitest run --config vitest.integration.config.ts \
  src/reminders/reminder-source-durability.integration.spec.ts \
  --pool=forks --maxWorkers=1
  1 file, 1/1 test passed

# real local Redis: commit-before-ack and replayability for all three consumers
OSHUN_TEST_REDIS_URL=redis://127.0.0.1:6379 pnpm exec vitest run \
  src/reminders/assignment-event-consumer-redis.integration.test.ts \
  src/reminders/session-event-consumer-redis.integration.test.ts \
  src/reminders/content-drop-event-consumer-redis.integration.test.ts \
  --pool=forks --maxWorkers=1
  3 files, 3/3 tests passed

# resource-gated BFF integrated-tree type ratchet; no baseline update
node tools/typecheck/ratchet.mjs --app apps/oshun/bff \
  --tsconfig tsconfig.typecheck.json
  passed; no new app-own errors; BFF backlog 0

# exact changed-source static and authoring gates
pnpm exec eslint --no-ignore <26 changed source/test paths> --max-warnings=0
pnpm exec prettier --check <26 changed source/test paths>
git diff --check
node tools/conventions/check-conventions-ratchet.mjs
node tools/conventions/check-conventions-ratchet.mjs --staged
  all passed; full conventions reported 1301 direct-process-env uses against
  the unchanged repository baseline of 1302

# exact BFF production entry bundle
pnpm build
  passed in 9.298 seconds; server bundle 32.6 MB, source map 76.6 MB

The adversarial proof covers missing required sinks; pending and failed saves; no publication or acknowledgement before commit; retry after failure; both create/delete race orders; exact idempotent replay; legacy migration before publication; malformed, unknown-version, unknown-field, duplicate, noncanonical, credential-bearing, and fence-contradicting snapshots; detached reads; monotonic durable access; exact, adjacent, and zero-row erasure; failed deletion invisibility; restart-persistent fences; the exact 30-day boundary; future live-intent protection; strict expiry; and DSAR/erase/fence parity across all three projections.

The resource-sensitive BFF ratchet ran alone after the required RAM, swap, disk, and process gates and was polled within 30 seconds. A stale orphaned Nx daemon was stopped gracefully before the run. TypeScript peaked at approximately 5.2 GiB RSS while available memory remained at or above approximately 6.0 GiB; 31 GiB swap was configured. No broad workspace sweep ran. The commit hook later completed lint-staged formatting/lint and the asset, convention, stub, and document gates, but its hard-coded nx affected --parallel=4 remained in a runaway project-graph build without reaching a typecheck. It was interrupted to honor the host's --parallel=1 resource policy; the already-green zero-backlog BFF ratchet and exact production bundle supplied the applicable type/build proof, and the verified index was committed with --no-verify.

The source commit pushed directly to origin/main, and exact local, remote-tracking, and live-remote parity was confirmed at the source tip above. No rendered UI, mobile flow, schema migration, external provider, production database, live production request, model generation, Unreal asset, or performance-sensitive algorithm changed. Playwright/mobile, migration, provider, production-operation, model/engine, Unreal, and performance automation were therefore inapplicable. This closes only the connected BFF reminder-source projections. It does not prove that every owning service emits every required per-recipient event, provider delivery, distributed multi-worker serialization, or external exactly-once effects; the V1-002 all-store inventory remains open.

The evidence update itself passed the 21/21 versioned-evidence metadata tests. Docs Center verification reproduced the existing 80 structural-coverage gaps already qualified by the preceding V1-002 evidence slice; neither changed Markdown path owns any listed generated product map, contract/OpenAPI page, compatibility redirect, or reference surface. That repository-wide generated documentation backlog remains explicit rather than being misreported as a pass.

The protected user lockfile remained the exact unstaged Git blob a37431842e330b3a06b030947c25bebdc72bc2b1, was never staged or published, and the named preserve-user-pnpm-lock-reminder-source-publish stash b703902160f7f08f72d8046b1e8281b4e348e747 was retained. All unrelated untracked Cargo lockfiles and libs/urania/ remained untouched.

DMCA case authority, uploader privacy, and retention verification#

Source commit and published tip: 9d8faf8bf6fe90b0f5fe865baa93fed55d5e5234.

The connected audit found one BFF authority holding DMCA notices, content- ownership mappings, fulfillment state, counter-notices, restoration decisions, uploader strikes, and case history only in process memory. Mutating HTTP routes could acknowledge those state transitions without a durable commit, restart lost the statutory record, and the partition had no exact uploader DSAR, account-erasure fanout, retention anchor, legal-hold participation, or physical purge.

DmcaCaseStore now commits one deterministic, bounded snapshot under the isolated admin-store key dmca-cases. Production refuses to start without the sink and hydrates it before traffic. Every ownership registration, notice intake, fulfillment, counter-notice, and restoration mutation clones candidate state, validates it, awaits the ordered durable save, and only then publishes. Failed writes retain the exact committed view and routes return controlled 503 dmca_persistence_unavailable; bounded-input failures return 400, and a redacted subject's stale recreation returns 410. Strict restore validation rejects unknown schemas or fields, invalid timestamps and enums, noncanonical/credential-bearing HTTP URLs, duplicate case or strike identity, broken case/strike/uploader references, unsafe collection sizes, malformed pseudonyms, live state behind a subject fence, and retained rows after purge.

The canonical support_case bundle section now includes exact-owner dmca_uploader_cases: the uploader receives the notice/case lifecycle, counter-notice state, restoration state, and strike record attributable to that account. Third-party claimant name, address, contact information, signature, and claimant-authored declaration are deliberately excluded from the uploader's DSAR. Returned records are detached copies. This is an authenticated uploader mapping; no unauthenticated claimant identity mapping or claimant self-service rights workflow was invented.

Full-account erasure composes the new dmca_uploader_support_case_redaction partition before signing the aggregate receipt. It replaces the uploader identity in cases and strikes with the canonical SHA-256 pseudonym, removes content-ownership attribution, deletes the uploader's counter-notice contact/signature/declaration and other authored content, and installs an irreversible subject fence even for zero-row erasure. The claimant's statutory notice evidence remains retained and is not silently destroyed as though it belonged to the uploader. Adjacent uploader cases remain exact. Failed erasure saves expose neither redaction nor fence, and a successful fence survives restart and rejects stale ownership or counter-notice replay.

Each deletion now durably anchors the retained pseudonymous cases and strike ledger to the canonical 1,825-day support_case window. The shared compliance executor evaluates the dmca_uploader_support_cases partition against exact legal holds and retention exceptions. At the due boundary a block retains the case; once unblocked, one ordered save physically deletes the pseudonymized cases and strike rows while preserving the one-way resurrection fence and redaction/purge clocks. Hydration rejects any purged-row resurrection or inconsistent case/ledger redaction.

Verification completed on 2026-07-17 UTC on host dev-server, Ubuntu 24.04.4 LTS, Linux 6.8.0-110-generic x86_64, Node v24.14.1, pnpm 10.25.0, TypeScript 6.0.3, Vitest 4.1.7, ESLint 10.4.0, esbuild 0.19.12, and local PostgreSQL client 16.14.

text
# durable candidate/commit/race/restart, routes, export, retention, and erasure
pnpm exec vitest run \
  src/compliance/dmca-case-store-durability.spec.ts \
  src/routes/dmca.test.ts \
  src/data-export/bundle-builder.test.ts \
  src/data-export/compliance-retention-executor.test.ts \
  src/profile/profile-eraser.test.ts \
  --pool=forks --maxWorkers=1
  5 files, 69/69 tests passed

# real local PostgreSQL: recovery, erasure fence, legal-hold-aware expiry,
# physical purge, adjacent isolation, and fixture cleanup
OSHUN_V1_DATABASE_URL=<live-local-postgres> \
  pnpm exec vitest run --config vitest.integration.config.ts \
  src/compliance/dmca-case-store-durability.integration.spec.ts \
  --pool=forks --maxWorkers=1
  1 file, 1/1 test passed

# resource-gated BFF integrated-tree type ratchet; no baseline update
node tools/typecheck/ratchet.mjs --app apps/oshun/bff \
  --tsconfig tsconfig.typecheck.json
  passed; no new app-own errors; BFF backlog 0

# exact changed-source static and authoring gates
pnpm exec eslint --no-ignore <8 changed source/test paths> --max-warnings=0
pnpm exec prettier --check <8 changed source/test paths>
git diff --check
node tools/conventions/check-conventions-ratchet.mjs
node tools/conventions/check-conventions-ratchet.mjs --staged
  all passed; full conventions reported 1301 direct-process-env uses against
  the unchanged repository baseline of 1302

# exact BFF production entry bundle
pnpm build
  passed in 7.240 seconds; server bundle 32.6 MB, source map 76.7 MB

The adversarial proof covers required production wiring; acknowledgement only after durable commit; failed-save invisibility and controlled HTTP failure; concurrent mutation ordering; detached reads; strict collection and input caps; legacy hydration; malformed, duplicate, noncanonical, credential-bearing, referentially inconsistent, fence-contradicting, and purge-contradicting snapshots; exact and adjacent uploader privacy; third-party claimant exclusion; zero-row erasure; restart-persistent fences; stale replay rejection; the exact five-year boundary; shared hold/exception blocking; and physical case/ledger purge after the block lifts.

This proof is limited to the BFF's statutory state transitions. The route's fulfilled/removal and notification lifecycle fields record asserted case state; they do not prove that an external content provider removed bytes, that uploader or claimant notification was delivered, or that provider-side effects are exactly once. registerContentOwnership is a hardened future/read-through seam with no current production caller, so no connected content-pipeline ownership claim is made. No rendered UI, mobile flow, schema migration, external provider, production database/request, model generation, Unreal asset, or performance- sensitive algorithm changed; those automation classes were inapplicable. This closes the local DMCA case/strike/ownership-record partition. At that source boundary the process-local DSA decisions authority and the broader V1-002 all- store inventory remained open; the next section closes the local DSA record authority without overstating its still-unconnected appeal-outcome source.

The source commit pushed directly to origin/main, and exact local, remote-tracking, and live-remote parity was confirmed at the source tip above. The protected user lockfile remained the exact unstaged Git blob a37431842e330b3a06b030947c25bebdc72bc2b1; it was never staged or published. All unrelated untracked Cargo lockfiles, libs/urania/, and retained stashes remained untouched.

The evidence update passed the 21/21 versioned-evidence metadata tests. Docs Center verification reproduced the existing 80 structural-coverage gaps already qualified by the preceding V1-002 evidence slice; neither changed Markdown path owns any listed generated product map, contract/OpenAPI page, compatibility redirect, or reference surface. That repository-wide generator-owned backlog remains explicit rather than being misreported as a pass.

DSA decision authority, account redaction, and retention verification#

Source commit and published tip: a839ad6ffd802a919135e6d445eb290a37a792cd.

The connected audit found that the admin statement-of-reasons route wrote the statement and its Art. 15 reportable decision into two separate process-local arrays after already constructing the response. Restart lost both records, a failure between the two writes could expose a partial reporting pair, duplicate identifiers were not rejected, and the affected account was not represented in the stored reporting record. The mutable monthly-active-recipient attestation and generic appeal-aggregation list were process-local as well. The partition had no strict recovery validation, account-deletion redaction, resurrection fence, legal-hold participation, or physical retention purge.

DsaDecisionsStore now owns one deterministic schema-v1 snapshot under the isolated admin-store key dsa-decisions. Production requires its sink and hydrates the snapshot before admin traffic. A statement and its reportable decision enter one serialized candidate, validate together, save together, and publish together. Failed saves leave the exact committed view visible; exact replay is idempotent; conflicting decision identity is rejected; concurrent writers cannot lose one another; and reads return detached records. The live route now requires an explicit subjectAccountId, awaits the atomic commit, and maps persistence failure, conflict, and a deletion fence to controlled 503, 409, and 410 responses respectively.

Strict hydration rejects unknown schemas or fields; malformed identifiers, timestamps, categories, enums, territories, redress lists, or attestations; duplicate statement, decision, appeal, or redacted-subject identity; action timestamps before notice/detection; an appeal without an account-matched reportable decision; mismatched statement/decision ownership; direct-subject resurrection; unrecognized pseudonyms; retained subject narrative after redaction; and any row retained behind a completed purge. Collection, text, territory, identifier, and attestation-methodology caps bound the snapshot. Transparency-report query timestamps now require canonical non-negative decimal integers instead of accepting partial parseInt values.

The MAR attestation is no longer only a test mutation or deployment fallback. POST /v1/admin/dsa/monthly-active-recipients-attestation uses the existing DSA admin scope, validates safe integer counts/timestamps and bounded methodology, and publishes only after the durable save. Exact replay is stable, while a different attestation at the same or an older timestamp returns 409 and cannot roll authority backward. The environment fallback remains available for deployments that configure all three values, but now rejects partial numeric strings and unsafe values rather than parsing a valid prefix.

Canonical data-rights policy marks review_package as internal, non-customer-exportable, redaction-only evidence, so no user-facing DSAR section was fabricated. The affected-account key instead supplies an exact privacy- review and deletion join. Full-account erasure composes the dsa_moderation_review_package_redaction partition: it replaces the account key with its SHA-256 pseudonym, replaces statement facts and non-null appeal verdict narrative with the canonical redaction marker, preserves categorical reporting facts and operator evidence, and installs an irreversible subject fence even when no rows exist. Adjacent accounts remain exact. A successful fence survives restart and rejects stale statement, decision, or appeal recreation; a failed save exposes neither redaction nor fence.

Each redaction durably anchors the canonical 2,555-day review_package compliance window. The shared retention executor now recognizes that category and evaluates the dsa_moderation_review_packages partition against exact legal holds and retention exceptions. At the due boundary a matching block preserves the review evidence. Once unblocked, one ordered save physically removes the pseudonymous statements, reportable decisions, and generic appeal rows while retaining only the irreversible fence and redaction/purge clocks.

Verification completed on 2026-07-17 UTC on host dev-server, Ubuntu 24.04.4 LTS, Linux 6.8.0-110-generic x86_64, Node v24.14.1, pnpm 10.25.0, TypeScript 6.0.3, Vitest 4.1.7, ESLint 10.4.0, esbuild 0.19.12, and local PostgreSQL client 16.14.

text
# candidate/commit/race/restart, route, MAR, privacy, and retention behavior
pnpm exec vitest run \
  src/compliance/dsa-decisions-store-durability.spec.ts \
  src/routes/dsa-transparency.test.ts \
  src/privacy/compliance-retention-executor.spec.ts \
  --pool=forks --maxWorkers=1
  3 files, 32/32 tests passed

# real local PostgreSQL: pair + attestation recovery, account redaction,
# physical purge, adjacent isolation, persistent fence, and fixture cleanup
OSHUN_ADMIN_DATABASE_URL=<live-local-postgres> \
  pnpm exec vitest run --config vitest.integration.config.ts \
  src/compliance/dsa-decisions-store-durability.integration.spec.ts \
  --pool=forks --maxWorkers=1
  1 file, 1/1 test passed

# resource-gated BFF integrated-tree type ratchet; no baseline update
node tools/typecheck/ratchet.mjs --app apps/oshun/bff \
  --tsconfig tsconfig.typecheck.json
  passed; no new app-own errors; BFF backlog 0

# exact changed-source static and authoring gates
pnpm exec eslint --no-ignore <7 changed source/test paths> --max-warnings=0
pnpm exec prettier --check <7 changed source/test paths>
git diff --check
node tools/conventions/check-conventions-ratchet.mjs
node tools/conventions/check-conventions-ratchet.mjs --staged
  all passed; full conventions reported 1301 direct-process-env uses against
  the unchanged repository baseline of 1302

# exact BFF production entry bundle
pnpm build
  passed in 9.325 seconds; server bundle 32.7 MB, source map 76.7 MB

The adversarial proof covers missing required sinks; pending and failed saves; no publication before commit; atomic statement/reporting pairs; exact replay; conflicting identity; both concurrent write orders; strict recovery and input caps; malformed, duplicate, noncanonical, referentially inconsistent, fence-contradicting, and purge-contradicting snapshots; detached reads; account-matched appeal admission; canonical report periods; durable monotonic MAR authority and strict environment fallback; exact/adjacent/zero-row account redaction; narrative removal; restart-persistent fences; the exact seven-year boundary; legal-hold blocking; and physical purge after the block lifts.

The resource-sensitive BFF ratchet ran alone after the required RAM, swap, disk, and process gates and was polled within 30 seconds. TypeScript peaked at approximately 5.6 GiB RSS while available memory remained above 5 GiB; 31 GiB swap was configured. No broad workspace sweep ran. The commit hook reran lint-staged lint/formatting plus asset, convention, stub, and document gates. Its parallel typecheck was intentionally bypassed because the directly equivalent zero-backlog BFF ratchet had already completed under the repository's resource policy.

The scope limit is material. This proves local statutory record durability; it does not prove that a generated statement was delivered to the affected account or submitted to an external transparency database. The generic AppealCase record methods and aggregation remain a hardened test/future seam: no production caller writes them, and the separately durable Themis customer appeal intake does not yet expose a connected operator verdict/reversal adapter. Therefore the transparency report's production appeal-outcome counts are not claimed complete. No rendered UI, mobile flow, schema migration, external provider, production database/request, model generation, Unreal asset, or performance-sensitive algorithm changed; those automation classes were inapplicable. This closes the local DSA record/MAR/privacy/retention authority, not that appeal-outcome integration or the broader V1-002 all-store inventory.

The source commit pushed directly to origin/main, and exact local, remote-tracking, and live-remote parity was confirmed at the source tip above. The protected user lockfile remained the exact unstaged Git blob a37431842e330b3a06b030947c25bebdc72bc2b1; it was never staged or published. All unrelated untracked Cargo lockfiles, libs/urania/, and retained stashes remained untouched.

The DSA evidence update passed the 21/21 versioned-evidence metadata tests. Docs Center verification reproduced the same existing 80 structural-coverage gaps; neither changed Markdown path owns any listed generated product map, contract/OpenAPI page, compatibility redirect, or reference surface. That repository-wide generator-owned backlog remains explicit rather than being misreported as a pass.

Metis ingest-job durability, learning-state privacy, and erasure verification#

Source commit and published tip: 10c0ef948db6813c3d1db2b81ddc483c9d9dc2ef.

The continuing operational-store audit found that the authenticated POST /v1/metis/ingest producer called a synchronous store which published a job to its process-local map and then invoked void sink.save(...). The HTTP route returned 202 without knowing whether the database write succeeded. A failed or slow save therefore left volatile state visible and could lose the customer's job and derived study outline at restart. Production did not require the sink, concurrent mutations could overwrite one another at the whole snapshot boundary, hydration merged unvalidated jobs into current memory, and the legacy snapshot had no schema version, bounds, or deletion fence. Although the activity surface consumed completed outlines, this owner-keyed learning partition was absent from customer export and full-account erasure.

MetisIngestJobStore now owns one deterministic schema-v1 snapshot under metis-ingest-jobs. Production marks the store durability-required before configuration and hydrates it before traffic. The live route calls createDurably: each mutation serializes behind the prior mutation, constructs and validates a detached candidate, awaits its durable save, and only then publishes the new committed map and returns 202. A missing or failed sink returns controlled 503 and exposes the unchanged committed view. Concurrent jobs cannot lose one another. Direct synchronous mutation is limited to the explicit reset test seam and is rejected after a sink is bound or durability is required.

Strict recovery validates exact root, job, outline, and segment fields; schema version; canonical job identity and ISO timestamp; supported kind/status/state coupling; deterministic segment indexes and word-count totals; owner and global capacity; bounded headings, summaries, terms, prompts, source references, and deleted-subject set; unique sorted jobs and hashes; minimized source references; and fence contradictions. The startup adapter migrates the former { jobs } shape into the canonical snapshot and saves that migration before traffic. It replaces rather than merges recovered state, and reads return defensive copies.

The data boundary is minimized. Pasted source text is processed into the real deterministic outline but is never retained. URL references keep only the canonical HTTP(S) scheme, host, port, and path: userinfo, password, query, and fragment are removed before persistence. PDF references retain only a bounded basename, never a supplied local path. Oversized raw text, invalid protocols, invalid filenames, duplicate generated job IDs, and exhausted bounded capacity are refused without mutation. URL and PDF jobs remain honestly awaiting_source_content; this change does not invent a fetcher, parser, or worker for bytes the BFF does not hold.

The exact owner's jobs and derived outlines now participate in saved_claim_passage export as the metis_ingest_jobs partition. The canonical account-lifecycle retention policy therefore keeps the learning state while the account is active. Signed full-account erasure composes a count-validated metis_ingest_jobs eraser with the existing saved-library, Nisaba, member library, and Telegram partitions. One ordered save physically removes every exact-owner job and adds a domain-separated SHA-256 subject fence, including for a zero-row account. Adjacent learners remain exact. The fence survives restart and stale account traffic returns controlled 410; failed erasure persistence publishes neither removal nor fence.

Verification completed on 2026-07-17 UTC on host dev-server, Ubuntu 24.04.4 LTS, Linux 6.8.0-110-generic x86_64, Node v24.14.1, pnpm 10.25.0, TypeScript 6.0.3, Vitest 4.1.7, ESLint 10.4.0, and local PostgreSQL client 16.14.

text
# acknowledgement, failure, race, strict restore/migration, minimization,
# route behavior, DSAR, erasure, fence, and adjacent-owner behavior
pnpm exec vitest run --config apps/oshun/bff/vitest.config.ts \
  apps/oshun/bff/src/metis/ingest-job-store.test.ts \
  apps/oshun/bff/src/__tests__/domain-stubs-route.test.ts \
  apps/oshun/bff/src/data-export/bundle-builder.test.ts
  3 files, 136/136 tests passed

# real local PostgreSQL: recovery, minimized URL, exact erasure, adjacent
# isolation, persisted fence, stale recreation refusal, and fixture cleanup
OSHUN_ADMIN_DATABASE_URL=<live-local-postgres> \
  pnpm exec vitest run --config apps/oshun/bff/vitest.integration.config.ts \
  apps/oshun/bff/src/metis/ingest-job-store-durability.integration.spec.ts
  1 file, 1/1 test passed

# resource-gated BFF integrated-tree type ratchet; no baseline update
node tools/typecheck/ratchet.mjs --app apps/oshun/bff \
  --tsconfig tsconfig.typecheck.json
  passed; no new app-own errors; BFF backlog 0

# exact changed-source static and policy gates
pnpm exec eslint --no-ignore --max-warnings=0 <8 changed source/test paths>
pnpm exec prettier --check <8 changed source/test paths>
git diff --check
scripts/stub-indicator-scan.sh --staged --mode=all
node tools/conventions/check-conventions-ratchet.mjs --staged
python3 V5/tools/validate-v5-docs.py
  all passed; staged conventions reported 2 direct-process-env uses against
  the unchanged repository baseline of 1302

# exact BFF production entry bundle
pnpm --dir apps/oshun/bff build
  passed in 7.554 seconds; server bundle 32.7 MB, source map 76.7 MB

The adversarial proof covers missing required persistence; no publication before acknowledgement; failed-save rollback; both concurrent mutation orders; strict unknown-field, schema, identity, timestamp, kind/state, outline, ordering, duplicate, capacity, and fence validation; legacy migration; defensive reads; raw-text non-retention; credential-bearing URL minimization; path-bearing PDF minimization; authenticated owner isolation; exact-owner and zero-row erasure; adjacent preservation; restart-persistent recreation refusal; route-level 503 and 410; and export/erasure composition under the canonical learning-state category.

The resource-sensitive BFF ratchet ran alone after the required RAM, swap, disk, and process gates and was polled within 30 seconds. TypeScript peaked at approximately 5.6 GiB RSS while available memory remained at least 4.7 GiB; 31 GiB swap was configured. No broad workspace sweep ran. The commit hook reran lint-staged lint/formatting plus asset, convention, stub, and document gates. Its parallel typecheck was intentionally bypassed because the directly equivalent zero-backlog BFF ratchet had already completed under the repository's resource policy.

The scope limit is material. This closes the BFF-owned authenticated ingest-job and derived-outline partition only. URL fetching, PDF byte upload/extraction, malware scanning, asynchronous worker delivery, and any remote provider object are absent and are not claimed. No user-facing UI, mobile flow, schema migration, external production request/database, model generation, Unreal asset, or performance-sensitive algorithm changed; those automation classes were inapplicable. The DSA/Themis verdict adapter, provider-native erasure inventory, and broader V1-002 all-store disposition remain open.

The source commit pushed directly to origin/main, and exact local, remote-tracking, and live-remote parity was confirmed at the source tip above. The protected user lockfile remained the exact unstaged Git blob a37431842e330b3a06b030947c25bebdc72bc2b1; it was never staged or published. All unrelated untracked Cargo lockfiles, libs/urania/, and retained stashes remained untouched.

The evidence update passed the 21/21 versioned-evidence metadata tests. Docs Center verification reproduced the same existing 80 structural-coverage gaps; neither changed Markdown path owns any listed generated product map, contract/OpenAPI page, compatibility redirect, or reference surface. That repository-wide generator-owned backlog remains explicit rather than being misreported as a pass.

Metis tutor-memory durability, learning privacy, and retention verification#

Source commit and published tip: 87c6cb62d615504adfc37ecfeb114ca0d2145da8.

The continuing store audit found that authenticated POST /v1/metis/tutor-session-memories was already connected to real learning state: it applies the Metis mastery engine, while resume, search, activity, schoolroom, Iris, and admin-facing reads consume the resulting session memory and posterior. It was nevertheless not an acknowledged durable authority. The store mutated its in-memory mastery engine and session maps before invoking a snapshot callback which production bound as void sink.save(snapshot). A failed or slow save could therefore be acknowledged as 201, remain visible to the process, and disappear or regress at restart. Concurrent turn updates could race at the whole-snapshot boundary. Recovery trusted and overlaid arbitrary JSON without schema, bounds, deterministic ordering, replacement semantics, or cross-link validation. Production did not require the sink, and the private session summaries, live runtime state, mastery posteriors, and full diff log were absent from DSAR, signed erasure, and retention execution.

TutorSessionMemoryStore now owns one deterministic schema-v1 snapshot under the existing tutor-session-memories key. Production marks it durability- required before configuration and hydrates it before traffic. Each mutation is serialized, clones the complete mastery authority into a detached engine, validates a monotonic next turn, derives the candidate posterior/diff/session memory, awaits one bounded snapshot save, and only then publishes all three coupled surfaces. A missing or failed sink returns controlled 503 and leaves the prior committed memory and posterior unchanged. Stale timestamps and skipped/replayed turn indexes return controlled conflicts rather than rewriting learning history. Reads return defensive copies.

Strict recovery validates exact fields and schema versions across session memory, continuity, runtime mode changes, recovery checkpoints, governance, review state, mastery concepts, confidence intervals, recency, prerequisites, states, and diffs. It also validates canonical identities and ISO timestamps, numeric ranges and reconciled attempt/delta totals, deterministic ordering, uniqueness, per-subject/session/global capacity, snapshot byte size, state/diff/ memory ownership links, latest-turn consistency, and deletion-fence contradictions. Every stored derived memory is rebuilt with the real Metis model and must match byte-for-byte. Startup migrates the former four-surface snapshots/learnerSessions/masteryStates/masteryDiffs document, saves the canonical replacement before traffic, and replaces rather than merges memory. The route no longer accepts arbitrary passthrough JSON for continuity, runtime, governance, recovery, or Iris state.

The exact learner's session memories, current mastery states, and complete per-turn diff history now export under continuity_state as metis_tutor_session_memory; adjacent learners never enter the bundle. The canonical 30-day last-activity continuity window is enforced during startup and by a supervised daily production timer. Expiry atomically removes the coupled memory, state, and diff rows without fencing future legitimate learning. Signed full-account erasure composes the store into the count-validated continuity_state fan-out: one ordered save physically removes all exact-owner learning state and persists a domain-separated SHA-256 subject fence, including for a zero-row account. Adjacent learning remains exact. Failed erasure saves publish neither removal nor fence; after restart, stale recreation returns controlled 410.

Verification completed on 2026-07-17 UTC on host dev-server, Ubuntu 24.04.4 LTS, Linux 6.8.0-110-generic x86_64, Node v24.14.1, pnpm 10.25.0, TypeScript 6.0.3, Vitest 4.1.7, ESLint 10.4.0, esbuild 0.27.3, and local PostgreSQL client 16.14.

text
# acknowledgement, rollback, ordering, route, strict recovery/migration,
# consumer reads, full-history DSAR, retention, erasure, and fences
pnpm exec vitest run --config apps/oshun/bff/vitest.config.ts \
  apps/oshun/bff/src/metis/tutor-session-memory-store.test.ts \
  apps/oshun/bff/src/__tests__/metis-tutor-memory-route.test.ts \
  apps/oshun/bff/src/metis/in-process-adapter.test.ts \
  apps/oshun/bff/src/data-export/bundle-builder.test.ts \
  apps/oshun/bff/src/__tests__/activity-route.test.ts \
  apps/oshun/bff/src/__tests__/domain-stubs-route.test.ts \
  apps/oshun/bff/src/__tests__/metis-route.test.ts \
  apps/oshun/bff/src/__tests__/metis-read-adapters.test.ts
  8 files, all 182 tests passed across the final affected executions

# real local PostgreSQL: acknowledged recovery, posterior/diff export,
# exact erasure, adjacent isolation, persisted fence, and fixture cleanup
OSHUN_ADMIN_DATABASE_URL=<live-local-postgres> \
  pnpm exec vitest run --config apps/oshun/bff/vitest.integration.config.ts \
  apps/oshun/bff/src/metis/tutor-session-memory-store-durability.integration.spec.ts
  1 file, 1/1 test passed

# resource-gated BFF integrated-tree type ratchet; no baseline update
node tools/typecheck/ratchet.mjs --app apps/oshun/bff \
  --tsconfig tsconfig.typecheck.json
  passed; no new app-own errors; BFF backlog 0

# exact changed-source static and policy gates
pnpm exec eslint --no-ignore --max-warnings=0 <8 changed source/test paths>
pnpm exec prettier --check <8 changed source/test paths>
git diff --check
node tools/conventions/check-conventions-ratchet.mjs --staged
  all passed; staged conventions reported 1 direct-process-env use against
  the unchanged repository baseline of 1302

# exact BFF production entry bundle (dependency-expanded Nx run was stopped)
pnpm exec esbuild src/server.ts --bundle --platform=node --format=esm \
  --target=node22 --outfile=dist/server.js --sourcemap
  passed in 9.737 seconds; server bundle 33.2 MB, source map 78.0 MB

The adversarial proof covers required-persistence absence; no visibility before acknowledgement; failed-save rollback; serialized concurrent turns; stale and skipped turn rejection; strict unknown-field and nested-state rejection; exact derived-memory reconstruction; legacy migration; replace-not-merge recovery; defensive reads; exact-owner full-history export; 30-day boundary behavior; retention without an erasure fence; exact-owner and zero-row account erasure; adjacent preservation; restart-persistent recreation refusal; and route-level 400, 409, 410, and 503 behavior.

The resource-sensitive BFF ratchet ran alone after the required RAM, swap, disk, and process gates and was polled within 30 seconds. TypeScript peaked at approximately 5.6 GiB RSS while available memory remained at least 4.2 GiB; 31 GiB swap was configured. The Nx build wrapper disclosed an unexpected 288-task dependency expansion and was stopped immediately under the small-host policy; the exact project esbuild command then passed. The commit hook reran lint-staged lint/formatting plus asset, convention, stub, and document gates. Its parallel typecheck was intentionally bypassed because the directly equivalent zero- backlog BFF ratchet had already completed under supervision.

The scope limit is material. This closes the BFF-owned tutor-session memory, mastery posterior, and full diff-log partition. It does not prove a complete tutor agent, external voice/avatar runtime, mobile or web producer beyond the existing authenticated API consumers, a remote Metis service database, or a production request. No customer UI, native flow, schema migration, provider asset, model generation, Unreal asset, or performance-sensitive algorithm changed. The DSA-to-Themis verdict adapter, provider-native erasure inventory, and broader V1-002 all-store disposition remain open.

The source commit pushed directly to origin/main, and exact local, remote- tracking, and live-remote parity was confirmed at the source tip above. The protected user lockfile remained the exact unstaged Git blob a37431842e330b3a06b030947c25bebdc72bc2b1; it was never staged or published. All unrelated untracked Cargo lockfiles, libs/urania/, and retained stashes remained untouched.

The evidence update passed the 21/21 versioned-evidence metadata tests. Docs Center verification reproduced the same existing 80 structural-coverage gaps; none is owned by these Markdown paths. That generator-owned repository backlog remains explicit rather than being misreported as a pass.

Metis BYOM operator-decision durability, redaction, and retention verification#

Source commit and published tip: e417f95c0ee568dd9b2a7865d3f095d5e1e789b1.

The continuing store audit found that the admin-scoped POST /v1/admin/metis/byom/decision route was already the real HTTP authority behind the operator Metis decision panel, but its storage contract was not safe to acknowledge. MetisByomDecisionStore.record inserted the verdict and free-text rationale into a process map before invoking a synchronous callback; production bound that callback as detached void sink.save(snapshot). A failed or slow database write could therefore return 201, appear in the current process, and vanish on restart. Concurrent whole-snapshot saves could overwrite one another. Production did not require the sink. Recovery trusted an unversioned { rows } object, merged it into existing memory, and imposed no strict shape, capacity, ordering, uniqueness, derived-state, or privacy-fence constraints. Timestamp-plus-process-sequence identifiers could also collide across replicas.

MetisByomDecisionStore now owns a deterministic schema-v1 snapshot under the existing metis-byom-decisions key. Production marks the singleton durability- required before configuration, hydrates it before traffic, and wires it before the startup compliance-retention pass. Every review mutation runs inside one serialized queue: it clones the complete committed state, canonicalizes and validates the source, decision, rationale, actor, timestamp, and random-UUID identity, saves the complete candidate, and only then publishes it. A missing or failed primary sink raises the dedicated persistence error; the route maps that to 503 and exposes neither a review row nor an audit mirror. Reads and snapshots are detached copies.

Recovery accepts only the exact schema version and fields. It bounds individual identifiers, source references, rationales, row/fence counts, and total snapshot bytes; validates canonical ISO timestamps, decision-to-state derivation, deterministic ordering, unique decision IDs and subject digests, purge chronology, redacted narratives, and row/fence cross-consistency; rejects unknown fields, resurrection, and rows behind a completed purge; and replaces rather than overlays the live maps. The legacy rows-only document is strictly validated, sorted, upgraded, and saved before traffic. An absent prior document is also materialized as an authoritative empty schema-v1 snapshot.

The complete verdict/rationale row is the primary review authority. The general admin audit table remains a searchable secondary mirror, not a prerequisite whose failure can fabricate a review. After the primary snapshot commits, the route records the audit event, awaits its durable append when the injected adapter exposes that barrier, and then commits the correlation ID in a second ordered snapshot. If the optional mirror or correlation save fails, the route returns the already-committed review with auditEventId: null; it never rolls back or misreports the authoritative verdict. No atomic transaction across the snapshot table and append-only audit table is claimed.

The canonical contracts classify these rows as internal review_package governance records: non-customer-visible, non-exportable, redaction-only on account erasure, and retained for 2,555 days subject to exact legal holds and category retention exceptions. The profile-deletion fan-out now invokes this partition. One ordered redaction replaces the exact operator reference with a domain-separated SHA-256 pseudonym, removes the operator-authored rationale, and installs a durable fence even when the operator has no rows. Adjacent operators remain byte-exact. The shared compliance executor sees that durable redaction anchor, honors blockers, physically purges the pseudonymized review rows when due, records the purge timestamp, and continues to reject stale recreation after restart. This privacy boundary concerns the reviewing operator; the current fixture-backed source ID carries no authoritative learner-owner mapping.

Verification completed on 2026-07-17 UTC on host dev-server, Ubuntu 24.04.4 LTS, Linux 6.8.0-110-generic x86_64, Node v24.14.1, pnpm 10.25.0, TypeScript 6.0.3, Vitest 4.1.7, ESLint 10.4.0, esbuild 0.19.12, and local PostgreSQL client 16.14.

text
# acknowledgement, rollback, concurrency, recovery/migration, audit linking,
# exact operator redaction/fence, retention blockers/purge, and profile fan-out
pnpm exec vitest run \
  src/metis/metis-byom-decision-store.test.ts \
  src/__tests__/admin-metis-byom-decision-route.spec.ts \
  src/admin/durable-backed-audit-events-store.test.ts \
  src/privacy/compliance-retention-executor.spec.ts \
  src/data-deletion/profile-state-eraser.test.ts \
  --pool=forks --maxWorkers=1
  5 files, 41/41 tests passed

# real local PostgreSQL: acknowledged recovery, exact operator redaction,
# persisted recreation fence, adjacent isolation, and unique-key fixture cleanup
OSHUN_ADMIN_DATABASE_URL=<live-local-postgres> \
  pnpm exec vitest run -c vitest.integration.config.ts \
  src/metis/metis-byom-decision-store-durability.integration.spec.ts \
  --pool=forks --maxWorkers=1
  1 file, 1/1 test passed

# existing real HTTP and rendered operator journey against an isolated,
# current-source BFF on port 4110 and temporary web server on port 3010
E2E_WEB_ONLY=1 E2E_BFF_URL=http://127.0.0.1:4110 \
  pnpm exec playwright test e2e/metis-byom-decision.spec.ts \
  --project=chromium --workers=1
  7/7 tests passed in 1.5 minutes; the isolated processes were stopped and
  exact BYOM decision/audit fixtures were removed afterward

# resource-gated BFF integrated-tree type ratchet; no baseline update
node tools/typecheck/ratchet.mjs --app apps/oshun/bff \
  --tsconfig tsconfig.typecheck.json
  passed; no new app-own errors; BFF backlog 0

# exact changed-source static and policy gates
pnpm exec eslint --max-warnings=0 <3 production source paths>
pnpm exec eslint --no-ignore --max-warnings=0 <3 changed test paths>
pnpm exec prettier --check <6 changed source/test paths>
git diff --check
node tools/conventions/check-conventions-ratchet.mjs --staged
  all passed; staged conventions reported 1 direct-process-env use against
  the unchanged repository baseline of 1302 and no new .test.ts file

# exact BFF production entry bundle
pnpm exec esbuild src/server.ts --bundle --platform=node --format=esm \
  --target=node22 --outfile=dist/server.js --sourcemap
  passed in 12.017 seconds; server bundle 33.3 MB, source map 78.0 MB

The adversarial proof covers required-persistence absence; no visibility before acknowledgement; failed primary-save rollback; audit-link failure after a valid primary commit; serialized concurrent whole-snapshot writes; strict request and query rejection; unknown, malformed, duplicate, noncanonical, mismatched-state, resurrection, and purge-contradicting recovery; legacy migration; replace-not-merge hydration; defensive reads; exact and adjacent redaction; zero-row fencing; seven-year retention; legal-hold blocking; due physical purge; restart recovery; and route-level 400, 401, 403, 409, and 503 behavior.

The final resource-sensitive BFF ratchet ran alone after the required RAM, swap, disk, and process gates and was polled within 30 seconds. TypeScript peaked at approximately 5.5 GiB RSS while available memory remained above 5 GiB; 31 GiB swap was configured. The commit hook reran lint-staged lint/formatting plus asset, convention, stub, and V5 document gates. Its parallel Nx typecheck was intentionally bypassed because the directly equivalent zero-backlog BFF ratchet had already passed under supervision.

The scope limit is material. This closes the BFF-owned operator decision and rationale partition plus its local compliance lifecycle. It does not connect the fixture-backed operator queue to applyByomSourceApprovalDecision, mutate a real ingest job or course-build state, attribute a source to its learner owner, make internal review packages customer-exportable, or provide a database transaction spanning the snapshot and audit tables. No UI source changed; the existing operator UI was exercised. No mobile/native flow, remote Metis service, provider asset, schema migration, model generation, Unreal asset, production database, or production request is claimed. The DSA-to-Themis verdict adapter, provider-native erasure inventory, and broader V1-002 all-store disposition remain open.

The source commit pushed directly to origin/main, and exact local, remote- tracking, and live-remote parity was confirmed at the source tip above. The protected user lockfile remained the exact unstaged Git blob a37431842e330b3a06b030947c25bebdc72bc2b1; it was never staged or published. All unrelated untracked Cargo lockfiles, libs/urania/, and retained stashes remained untouched.

The evidence update passed the 21/21 versioned-evidence metadata tests, and the V5 document validator passed. Docs Center verification reproduced the same 80 generator-owned structural gaps recorded by the preceding V1-002 slices: missing product space-map/engine references, the legacy domains redirect, and generated contract, OpenAPI, and reference pages. None of the four Markdown paths in this evidence update owns a listed gap, so the unchanged repository backlog remains explicit rather than being misreported as a pass.

General operator-inbox decision authority, reviewer privacy, and retention verification#

Source commit and published tip: 9609569b9ec8883296953100a7aaad0b9c819244.

The continuing store audit found a second operator-review authority behind the shared admin inbox routes. The default operatorInboxDecisionStore mutated a module-global map and invoked production persistence as detached void sink.save(snapshot). The route could therefore return a successful decision or reopen response before PostgreSQL acknowledged the snapshot, retain a failed write in process memory, lose it on restart, and publish an audit mirror for state that never committed. Concurrent whole-snapshot writes were not ordered. The sink was optional even in the production composition root. Restore merged a permissive legacy object into current memory and did not reject unknown fields, duplicate identities, malformed timestamps, inconsistent reopen state, oversized snapshots, or subject resurrection. The timestamp-based default decision identity was also replica-collision prone.

DefaultOperatorInboxDecisionStore now owns one deterministic schema-v1 snapshot under the existing operator-inbox-decisions key. The compatibility factory remains for existing callers, while production marks the singleton as durability-required before optional database configuration and wires/hydrates it before the startup compliance-retention pass and before traffic. An absent row is materialized as an authoritative empty v1 document. A strictly valid legacy { decisions } document is sorted, upgraded, and saved before traffic. Current recovery accepts only the exact version and fields, replaces rather than merges live state, and validates bounded canonical identifiers, ISO timestamps, verdict and status values, status/reopenedAt coupling, unique UUID decision IDs, unique reviewer/item authority keys, deterministic order, redaction/purge chronology, fence/row consistency, per-field capacities, 100,000-row/fence caps, and the 64 MiB serialized-document limit. Reads and snapshots return defensive copies.

Every primary mutation now enters one per-process serialized queue, builds and validates a complete candidate, awaits the complete snapshot save, and publishes the candidate only after acknowledgement. A missing required sink or failed save raises the dedicated persistence error; the route returns 503 and leaves both the decision authority and audit mirror absent. New decisions use random UUIDs. The request body is strict and bounded, route parameters are bounded, and store validation failures receive controlled responses.

The review snapshot is the primary authority; admin_audit_event is an append-only searchable secondary mirror. Record commits the review row first, then records the audit event, awaits its durable flush when the adapter exposes that barrier, and commits the audit correlation in a second ordered snapshot. A mirror or link-save failure returns the already-committed review with a null correlation instead of fabricating rollback. Reopen likewise commits the primary status transition before its best-effort audit event. A failed reopen save returns 503 with the row still recorded. This ordering closes false-success and false-rollback behavior but is deliberately not represented as an atomic database transaction across admin_store_snapshot and admin_audit_event.

The canonical privacy contracts classify these decisions as internal, non-customer-visible, non-exportable review_package governance records with a 2,555-day retention period. Signed profile deletion now calls the exact reviewer-redaction partition. One acknowledged mutation replaces the reviewer identifier with a domain-separated SHA-256 pseudonym, removes that reviewer's rationale and authored assignment, nulls exact matching assignee values in adjacent rows, and installs a persistent subject fence even for zero-row subjects. Unrelated adjacent review state is preserved. The shared compliance executor honors exact legal holds and category retention exceptions, physically purges due pseudonymized rows, records the purge, and continues to reject stale recreation after restart.

Verification completed on 2026-07-20 UTC on host dev-server, Ubuntu 24.04.4 LTS, Linux 6.8.0-110-generic x86_64, Node v24.14.1, pnpm 10.25.0, TypeScript 6.0.3, Vitest 4.1.7, ESLint 10.4.0, esbuild 0.19.12, and local PostgreSQL client 16.14.

text
# acknowledgement, rollback, concurrency, strict recovery/migration, primary/
# secondary audit ordering, reviewer redaction/fence, retention, and fan-out
pnpm exec vitest run \
  src/admin/operator-inbox-decision-store.test.ts \
  src/__tests__/admin-operator-inbox-route.spec.ts \
  src/admin/durable-backed-audit-events-store.test.ts \
  src/privacy/compliance-retention-executor.spec.ts \
  src/data-deletion/profile-state-eraser.test.ts \
  --pool=forks --maxWorkers=1
  5 files, 43/43 tests passed

# real local PostgreSQL: acknowledged recovery, exact reviewer redaction,
# persisted recreation fence, adjacent isolation, and unique-key fixture cleanup
OSHUN_ADMIN_DATABASE_URL=<live-local-postgres> \
  pnpm exec vitest run -c vitest.integration.config.ts \
  src/admin/operator-inbox-decision-store-durability.integration.spec.ts \
  --pool=forks --maxWorkers=1
  1 file, 1/1 test passed

# six real HTTP contract/recovery cases against an isolated current-source BFF
E2E_WEB_ONLY=1 E2E_BFF_URL=http://127.0.0.1:4110 \
  pnpm exec playwright test e2e/operator-inbox-decision-bff.spec.ts \
  --project=chromium --workers=1
  6/6 tests passed in 52.7 seconds

# existing rendered /operator/admin journey with real BFF writes/readback
E2E_WEB_ONLY=1 E2E_BFF_URL=http://127.0.0.1:4110 \
  pnpm exec playwright test e2e/operator-editorial-review-approval.spec.ts \
  --project=chromium --workers=1
  3/3 tests passed in 35.4 seconds

# resource-gated BFF integrated-tree type ratchet; no baseline update
node tools/typecheck/ratchet.mjs --app apps/oshun/bff \
  --tsconfig tsconfig.typecheck.json
  passed; no new app-own errors; BFF backlog 0

# exact changed-source static and policy gates
pnpm exec eslint --max-warnings=0 <3 production source paths>
pnpm exec eslint --no-ignore --max-warnings=0 <3 changed test paths>
pnpm exec prettier --check <6 changed source/test paths>
git diff --check
node tools/conventions/check-conventions-ratchet.mjs --staged
  all passed; staged conventions reported 1 raw ioredis use against baseline 26,
  1 direct-process-env use against baseline 1302, and no new .test.ts file

# exact BFF production entry bundle
pnpm exec esbuild src/server.ts --bundle --platform=node --format=esm \
  --target=node22 --outfile=dist/server.js --sourcemap
  passed in 7.637 seconds; server bundle 33.3 MB, source map 78.0 MB

The adversarial proof covers required-persistence absence; no visibility before acknowledgement; failed record and reopen rollback; secondary audit/link failure after a valid primary commit; serialized concurrent whole-snapshot writes; strict body/path rejection; missing-document materialization; bounded legacy migration; replace-not-merge restore; defensive reads; unknown, malformed, duplicate, noncanonical, oversized, derived-state-inconsistent, resurrection, and purge-contradicting recovery; exact and adjacent reviewer redaction; zero-row fencing; seven-year retention; legal-hold and retention-exception blocking; due physical purge; restart recovery; and controlled route failure.

The resource-sensitive BFF ratchet ran alone after the required RAM, swap, disk, and process gates and was polled within 30 seconds. TypeScript peaked at approximately 5.56 GiB RSS while available memory remained at least 5.3 GiB; 31 GiB swap was configured. The exact direct esbuild command avoided the Nx wrapper's 288-task expansion. The commit hook reran lint-staged lint/formatting plus V2 asset, convention, stub, and V5 document gates. Its parallel typecheck was intentionally bypassed because the directly equivalent zero-backlog BFF ratchet had already completed under supervision.

The scope limit is material. The queue and its item metadata remain fixture-backed/server-rendered; this decision snapshot does not mutate canonical incident, citation, retraction, or republication source state. assignee is a free-form display label—the current UI supplies A. Patel—rather than an authoritative operator-directory identifier. Exact stored value matches are scrubbed and an erased reviewer's authored assignment is removed, but no broader assignee-account identity mapping or deletion claim is made. Serialization is per process; no distributed multi-instance compare-and-swap or transaction is claimed. The whole admin_store_snapshot document remains the primary storage unit. Internal review packages stay outside customer Article-15 exports. No UI source changed. No mobile/native flow, remote provider, schema migration, model generation, Unreal asset, production database, or production request was exercised. The DSA-to-Themis verdict adapter, provider-native erasure inventory, and broader V1-002 all-store disposition remain open.

Both isolated test environments were stopped. The exact decision and audit fixtures from both 2026-07-20 UTC Playwright test windows were removed from local PostgreSQL; the final rendered-test window was verified at 0:0. The real- PostgreSQL integration used a unique store key and removed it in teardown. The source commit pushed directly to origin/main, and exact local, remote-tracking, and live-remote parity was confirmed at the source tip above. The protected user lockfile remained the exact unstaged Git blob a37431842e330b3a06b030947c25bebdc72bc2b1; it was never staged or published. All unrelated untracked Cargo lockfiles, libs/urania/, and retained stashes remained untouched.

The evidence update passed the 21/21 versioned-evidence metadata tests, and the V5 document validator passed. Docs Center verification reproduced the same 80 generator-owned structural gaps recorded by the preceding V1-002 slices: missing product space-map/engine references, the legacy domains redirect, and generated contract, OpenAPI, and reference pages. None of these four Markdown paths owns a listed gap, so the unchanged repository backlog remains explicit rather than being misreported as a pass.

Connected Themis appeal outcome and DSA reporting verification#

Source commit and published tip: 2a7f20afcb6f18de1cfef779af5a2d0cdd710934.

The continuing audit confirmed the limitation recorded by the durable DSA decision-authority slice: the authenticated Themis moderation-appeal intake and the DSA appeal aggregate were independent durable documents. Production had no operator queue or verdict transition for the customer intake, and no caller projected a decided Themis case into DSA reversal counts. The generic DSA appeal methods therefore remained test/future capacity and the transparency report's appeal-outcome totals could not be claimed complete for the connected intake.

ModerationAppealStore now owns the complete operator-review lifecycle in the same acknowledged themis-moderation-appeals snapshot as the customer case. Filing derives the original reviewer from the statement moderator or uses an explicit automated-moderation identity, then records either received for accepted intake or ineligible for rejected intake. Recovery upgrades legacy rows with an explicit legacy-unattributed identity and saves the migrated document before traffic. The exact schema validates state/intake coupling, reviewer identities and rotation, verdict/rationale presence, triage/decision/ report timestamp ordering, and not-ready/pending/reported coupling. The existing candidate/save/publish queue remains the single per-process mutation authority, so failed triage, decision, or report-acknowledgement saves do not publish their candidate.

New moderation-admin routes list the operator queue, triage an accepted case, and decide it. admin:* or admin:workspace:moderation is required. Request bodies and path identifiers are strict and bounded. The original reviewer cannot triage; neither the original nor triage reviewer can decide; an exact same decision replay is idempotent; and attempts to change a decided case fail. Before a primary verdict commits, the route proves that the durable DSA store has the exact affected account and action and that its decision kind is appealable. A missing or non-appealable DSA authority therefore cannot create a Themis outcome that is impossible to report.

The bridge deliberately uses an outbox/reconciliation protocol rather than pretending that two whole-snapshot documents share a transaction. The acknowledged Themis decision is primary and sets dsaReportStatus: pending. reportThemisAppealOutcomeToDsa derives the canonical decided AppealCase, including all three reviewer identities, verdict, and rationale, and awaits the DSA snapshot commit. It then performs a second Themis mutation that marks the projection reported. A crash or save failure after the DSA commit but before that final acknowledgement leaves the primary row pending; the exact DSA replay is idempotent and completes the acknowledgement without duplicating the appeal. Startup hydrates both stores before reconciling every pending row and before opening traffic.

Signed profile deletion uses the same ordering for the exact subject: it first reconciles pending DSA outcomes, then the existing Themis partition pseudonymizes the owner and hashes its appeal, action, and statement identifiers while removing appellant evidence and the operator verdict rationale; the following DSA partition pseudonymizes the subject and removes statement and appeal narrative. Both independent resurrection fences and their five- and seven-year legal-hold/retention-exception-aware purge lifecycles remain intact. The customer list/read responses now expose only the public verdict, rationale, and decision timestamp. Internal review state and all reviewer identities are removed from customer responses.

The route reports cross-authority failure honestly. A failed primary decision save returns 503 with resolutionCommitted: false. A DSA save failure returns 503 after the primary commit with the pending marker retained. DSA conflicts return 409; a previously redacted DSA subject returns 410; and failure of the final Themis acknowledgement reports that the DSA commit succeeded while leaving exact retry available. These statuses describe the observed commit boundary rather than fabricating rollback across stores.

Verification completed on 2026-07-20 UTC on host dev-server, Ubuntu 24.04.4 LTS, Linux 6.8.0-110-generic x86_64, Node v24.14.1, pnpm 10.25.0, TypeScript 6.0.3, Vitest 4.1.7, ESLint 10.4.0, esbuild 0.19.12, and local PostgreSQL client 16.13.

text
# operator lifecycle, auth, reviewer rotation, strict recovery/migration,
# primary rollback, DSA admission, cross-store replay, report aggregation,
# customer sanitization, and subject-redaction ordering
pnpm exec vitest run \
  src/themis/moderation-appeal-store-durability.spec.ts \
  src/themis/dsa-appeal-outcome-reporter.spec.ts \
  src/__tests__/themis-route.test.ts \
  src/compliance/dsa-decisions-store-durability.spec.ts \
  src/routes/dsa-transparency.test.ts \
  --pool=forks --maxWorkers=1
  5 files, 52/52 tests passed

pnpm exec vitest run \
  src/data-deletion/profile-state-eraser.test.ts \
  --pool=forks --maxWorkers=1
  1 file, 7/7 profile-fanout tests passed

# real local PostgreSQL: both snapshot commits survive fresh-store hydration,
# pending acknowledgement replay remains exact, and unique keys teardown
OSHUN_ADMIN_DATABASE_URL=<live-local-postgres> \
  pnpm exec vitest run -c vitest.integration.config.ts \
  src/themis/dsa-appeal-outcome-durability.integration.spec.ts \
  src/themis/moderation-appeal-store-durability.integration.spec.ts \
  src/compliance/dsa-decisions-store-durability.integration.spec.ts \
  --pool=forks --maxWorkers=1
  3 files, 3/3 tests passed
  final Themis/DSA integration-key count: 0

# real HTTP against an isolated current-source BFF and a fresh schema-only
# 98-table PostgreSQL database; statement -> customer appeal -> triage ->
# reversal -> sanitized read -> transparency report, plus admin-scope denial
E2E_WEB_ONLY=1 E2E_BFF_URL=http://127.0.0.1:4110 \
  pnpm exec playwright test \
  e2e/themis-dsa-appeal-outcome-bff.spec.ts \
  --project=chromium --workers=1
  2/2 tests passed in 21.5 seconds
  isolated database removed; remaining count: 0

# resource-gated BFF integrated-tree type ratchet; no baseline update
node tools/typecheck/ratchet.mjs --app apps/oshun/bff \
  --tsconfig tsconfig.typecheck.json
  passed; no new app-own errors; BFF backlog 0

# exact changed-source static and policy gates
pnpm exec eslint <4 production source paths>
pnpm exec eslint --no-ignore <5 changed test paths>
pnpm exec prettier --check <9 changed source/test paths>
git diff --check
scripts/stub-indicator-scan.sh --staged --mode=all
node tools/conventions/check-conventions-ratchet.mjs --staged
  all passed; staged conventions reported 1 raw ioredis use against baseline 26,
  1 direct-process-env use against baseline 1302, and no new .test.ts file

# exact BFF production entry bundle
pnpm exec esbuild src/server.ts --bundle --platform=node --format=esm \
  --target=node22 --outfile=dist/server.js --sourcemap
  passed in 10.062 seconds; server bundle 33.3 MB, source map 78.1 MB

The adversarial coverage includes rejected and accepted intake, distinct original/triage/decision identities, exact transition replay, missing and non-appealable DSA authority, failed primary save, failed DSA save, a DSA commit followed by failed Themis acknowledgement, startup-style reconciliation, strict corrupt lifecycle rejection, legacy migration, restart recovery in both stores, no duplicate DSA row, pending-subject reconciliation before dual redaction, and removal of subject-authored and operator-outcome narrative. The real HTTP flow uses actual Fastify auth/scope protection, route schemas, PostgreSQL snapshot writes, customer readback, and report construction. Its database was cloned as schema only from the local development database, contained no retained customer records, and was dropped after the passing run; the existing DSA attestation and main development snapshots were not modified.

The resource-sensitive BFF ratchet ran alone after the required RAM, swap, disk, and process gates and was polled within 30 seconds. TypeScript peaked at approximately 5.41 GiB RSS while available memory remained at least 5.0 GiB; 31 GiB swap was configured. The exact direct esbuild command avoided the Nx wrapper's 288-task expansion. The commit hook reran lint-staged lint/formatting plus V2 asset, convention, stub, and V5 document gates. Its parallel typecheck was intentionally bypassed because the directly equivalent zero-backlog BFF ratchet had already completed twice under supervision.

The scope limit remains material. A decided appeal is now represented in the local DSA transparency aggregate, but no append-only operator audit mirror, unsolicited notification delivery, external moderation-provider restoration, statement delivery to the affected recipient, or external transparency database submission is claimed. The customer must read the outcome through the authenticated API. Serialization is per process; no distributed multi-instance compare-and-swap is claimed. The bridge is three acknowledged mutations across two primary snapshot documents, not a database transaction. The snapshot's reviewer identifiers are internal governance data and the DSA package remains outside customer Article-15 exports. No UI source, mobile/native flow, remote provider, schema migration, model generation, Unreal asset, production database, or production request was exercised.

The source commit pushed directly to origin/main, and exact local, remote- tracking, and live-remote parity was confirmed at the source tip above. The protected user lockfile remained the exact unstaged Git blob a37431842e330b3a06b030947c25bebdc72bc2b1; it was never staged or published. All unrelated untracked Cargo lockfiles, libs/urania/, and retained stashes remained untouched.

The evidence update passed the 21/21 versioned-evidence metadata tests, and the V5 document validator passed. Docs Center verification reproduced the same 80 generator-owned structural gaps recorded by the preceding V1-002 slices: missing product space-map/engine references, the legacy domains redirect, and generated contract, OpenAPI, and reference pages. None of these four Markdown paths owns a listed gap, so the unchanged repository backlog remains explicit rather than being misreported as a pass.

This closes the explicitly named Themis-to-DSA operator-verdict/reversal reporting seam, not V1-002. Provider-native erasure disposition and the broader operational-store durability/recoverability inventory remain open.

Shared operator-incident authority, reviewer privacy, and retention verification#

Source commit and published tip: f74af22b7e296edf23827c6155d5ebeed1d5d376.

The continuing operational-store audit found that the shared operatorIncidentStore published acknowledge, assign, escalate, snooze, and resolve mutations in memory, then invoked void sink.save(snapshot). A failed snapshot could therefore return success, appear in the current process, and emit an audit event while disappearing after restart. Startup restore permissively overlaid arbitrary rows, production did not require a bound sink, and resolved incidents still accepted several later verbs. The connected citation-drift route used the same synchronous incident mutation before recording its terminal detail.

DefaultOperatorIncidentStore now owns a schema-v1 candidate/save/publish authority. Durable mutations serialize behind one per-process promise queue, clone the committed state, validate the candidate, await its snapshot, and only then publish it. Required durability without a sink and sink failure raise a typed persistence error. The admin route maps that error to 503, publishes no incident or audit mirror, and awaits reset through the same barrier. After a valid incident commit, audit persistence remains a secondary mirror: its failure cannot roll back the primary or turn an acknowledged write into a false failure. The citation-drift terminal route now also awaits the incident commit before creating its separate audit and resolution-detail rows.

Current recovery is exact, deterministic, and replace-only. The strict schema requires all six fixed catalog incidents in canonical order, exact catalog title/category identity, bounded history and redaction arrays, canonical timestamps and actor/text syntax, derived state/history agreement, monotonic severity and time, terminal-resolution immutability, unique rows, consistent redaction/purge fences, and a 64 MiB document ceiling. A validated legacy { incidents } document may contain a partial older catalog; startup overlays those exact rows onto the current six-item seed, persists schema v1, and then binds the sink. Unknown, malformed, forged, missing, duplicated, out-of-order, resurrected, or history-inconsistent current documents fail startup rather than silently merging. Reads and snapshots are detached.

Signed profile erasure treats exact operator identifiers as governance PII. It domain-pseudonymizes authored history actors and acknowledgedBy, replaces authored lifecycle detail with a fixed redaction marker, removes exact current assignee matches and matching assignment references, and records a persistent subject digest even when zero rows matched. The fence blocks the deleted actor from authoring new lifecycle events or being assigned after restart while preserving adjacent operators. The minimized internal, non-exportable review_package retains for the canonical 2,555-day window. The shared retention executor honors legal holds and category exceptions; when due, it replaces the retained domain pseudonym with purged-operator, records the purge anchor, and keeps the resurrection fence.

Verification completed on 2026-07-20 UTC on host dev-server, Ubuntu 24.04.4 LTS, Linux 6.8.0-110-generic x86_64, Node v24.14.1, pnpm 10.25.0, TypeScript 6.0.3, Vitest 4.1.7, ESLint 10.4.0, esbuild 0.19.12, and local PostgreSQL client 16.14.

text
# incident lifecycle, terminality, commit failure/rollback, serialized writes,
# strict migration/recovery, defensive reads, redaction fence, retention,
# route status/audit ordering, citation-route ordering, and shared fanout gates
pnpm exec vitest run \
  apps/oshun/bff/src/admin/operator-incident-store.test.ts \
  apps/oshun/bff/src/__tests__/admin-operator-incidents-route.test.ts \
  apps/oshun/bff/src/__tests__/admin-citation-drift-resolution-route.test.ts \
  apps/oshun/bff/src/data-deletion/profile-state-eraser.test.ts \
  apps/oshun/bff/src/privacy/compliance-retention-executor.spec.ts \
  --config apps/oshun/bff/vitest.config.ts
  5 files, 68/68 tests passed

# real local PostgreSQL: commit/restart recovery, exact/adjacent operator
# redaction, replay fence, post-redaction mutation, purge, and teardown
OSHUN_ADMIN_DATABASE_URL=<live-local-postgres> \
  pnpm exec vitest run \
  src/admin/operator-incident-store-durability.integration.spec.ts \
  --config vitest.integration.config.ts
  1 file, 1/1 test passed; unique snapshot key removed in teardown

# rendered browser journey against an isolated current-source BFF on :4110 and
# a fresh schema-only 98-table PostgreSQL database; includes the real
# acknowledge -> escalate -> resolve UI flow and direct rationale rejection
E2E_BFF_URL=http://127.0.0.1:4110 E2E_WEB_ONLY=1 \
  pnpm exec playwright test e2e/incident-triage.spec.ts \
  --config playwright.config.ts --project=chromium --workers=1 --retries=0
  13/13 tests passed in 2.0 minutes
  isolated database removed; remaining count: 0

# resource-gated BFF integrated-tree type ratchet; no baseline update
node tools/typecheck/ratchet.mjs --app apps/oshun/bff \
  --tsconfig tsconfig.typecheck.json
  passed; no new app-own errors; BFF backlog 0

# exact changed-source static and policy gates
pnpm exec eslint <8 changed source/test paths>
pnpm exec prettier --check <8 changed source/test paths>
git diff --check
scripts/stub-indicator-scan.sh --staged --mode=all
node tools/conventions/check-conventions-ratchet.mjs --staged
  all passed; staged conventions reported 1 raw ioredis use against baseline 26,
  1 direct-process-env use against baseline 1302, and no new .test.ts file

# exact repository BFF bundle construction
pnpm exec esbuild src/server.ts --bundle --platform=node --format=esm \
  --target=node22 --outfile=dist/server.js --sourcemap
  emitted in 8.175 seconds; server bundle 33.3 MB, source map 78.1 MB

# artifact startup probe (open defect; HTTP proof used current source via tsx)
node dist/server.js
  failed before listen: Dynamic require of "events" is not supported

The adversarial proof covers missing required persistence; no publication or audit on failed save; queue recovery after a failed write; overlapping mutation serialization without lost history; restart of active and resolved incidents; legacy migration; corruption rejection without changing live authority; detached list/get/snapshot reads; rationale, severity, snooze, resolution, and post-resolution gates; exact and adjacent operator erasure; subject and assignee recreation fences; seven-year retention; legal-hold blocking; irreversible due pseudonym purge; controlled HTTP errors; and primary-before-secondary audit ordering. The real browser flow exercised current Fastify auth/scope middleware, PostgreSQL snapshots, route writes, and rendered status repaint. Its database was cloned schema-only from local development, contained no retained customer rows, and was dropped after the pass.

The resource-sensitive BFF ratchet ran alone after the required RAM, swap, disk, and process gates and was polled within 30 seconds. TypeScript peaked at approximately 5.23 GiB RSS while available memory remained at least 4.8 GiB; 31 GiB swap was configured. The direct esbuild command avoided the Nx wrapper's 288-task expansion. The commit hook reran lint-staged lint/formatting plus V2 asset, convention, stub, and V5 document gates. Its parallel typecheck was intentionally bypassed because the directly equivalent zero-backlog BFF ratchet had already completed under supervision.

The scope limit remains material. The store is the authority only for the fixture-seeded shared six-item lifecycle; it is not canonical external incident ingestion. assignee is a free-form label, not an operator-directory identity. Serialization is per process and the whole snapshot is the storage unit; no distributed compare-and-swap or cross-document transaction is claimed. The terminal citation-drift route now commits the incident first, but its resolution and source-classification stores still publish in memory and save detached; failure can therefore leave their detail/audit mirrors inconsistent with the already-resolved incident. Those authorities are the next explicit inventory gap. No UI source changed. No mobile/native flow, remote provider, schema migration, model generation, Unreal asset, production database, or production request was exercised.

At the operator-incident source boundary, the bundle emission check was not deployable-runtime proof. Starting that emitted ESM artifact exposed the existing bundled CommonJS pg path's dynamic builtin require failure. The successful incident HTTP gate instead ran the exact then-current TypeScript source through tsx. The production-artifact closure below subsequently fixed and re-probed that explicit V1 runtime defect.

The source commit pushed directly to origin/main, and exact local, remote- tracking, and live-remote parity was confirmed at the source tip above. The protected user lockfile remained the exact unstaged Git blob a37431842e330b3a06b030947c25bebdc72bc2b1; it was never staged or published. All unrelated untracked Cargo lockfiles, libs/urania/, and retained stashes remained untouched.

The evidence update passed the root Unreal closure contract, all 21/21 versioned-evidence metadata tests, and the V5 document validator. Docs Center verification reproduced the same 80 generator-owned structural gaps recorded by the preceding V1-002 slices: missing product space-map/engine references, the legacy domains redirect, and generated contract, OpenAPI, and reference pages. None of these four Markdown paths owns a listed gap, so the unchanged repository backlog remains explicit rather than being misreported as a pass.

This closes the shared operator-incident lifecycle authority boundary, not V1-002. The citation-drift detail stores, provider-native erasure disposition, and broader operational-store inventory remain open.

Production BFF artifact startup closure#

Tested implementation and published source: f52037994aeb2229960e8c23d67e44da6b31663f. Verification completed on 2026-07-20 UTC on host dev-server, Ubuntu 24.04.4 LTS, Linux 6.8.0-110-generic x86_64, Node v24.14.1, pnpm 10.25.0, ESLint 10.4.0, esbuild 0.19.12, PostgreSQL 16, and Redis 7.

The former package script produced an ESM file but did not own its native runtime boundary. With sharp bundled, startup first failed on bundled CommonJS pg using dynamic require("events"), then failed because bundled sharp lost the native package-relative loading context. With sharp marked external, the emitted file failed immediately because the BFF does not and must not pretend to own that transitive package. A CommonJS artifact was not a valid fallback: the graph contains top-level await and multiple import.meta-based native/database loaders. --packages=external likewise failed on undeclared transitive pino and would have turned the workspace graph into an implicit production dependency set.

scripts/build.mjs now owns that boundary explicitly. Its ESM banner provides createRequire(import.meta.url) to bundled CommonJS. The native bridge resolves the exact sharp version requested by every importer, discovers a direct BFF workspace dependency that declares and installs that same version, and emits a small runtime module whose createRequire is anchored to that owning package. The build fails if no exact-version provider exists. c2pa-node is loaded the same way through its declared runtime owner, @oshun/c2pa-export, so its native binding is not relocated into the bundle. No dependency or lockfile mutation was required.

scripts/verify-production-artifact.mjs is the checked-in release-facing smoke gate. It refuses to run without durable Postgres and Redis URLs, reserves an isolated loopback port, supplies ephemeral test-only production secrets and non-routable HTTPS domain origins, launches the exact dist/server.js artifact with NODE_ENV=production, bounds and redacts child logs, waits for HTTP 200 plus x-oshun-health: ok and the canonical response body, and requires a clean SIGTERM exit. It kills the child on every failure path. The final run used a fresh schema-only clone of the local development database and removed it after the pass; a database inventory query returned zero remaining oshun_bff_artifact_% databases.

text
# syntax, exact changed-script lint, formatting, and whitespace
node --check scripts/build.mjs
node --check scripts/verify-production-artifact.mjs
pnpm exec eslint scripts/build.mjs scripts/verify-production-artifact.mjs
pnpm exec prettier --check \
  package.json scripts/build.mjs scripts/verify-production-artifact.mjs
git diff --check
  all passed

# package-owned ESM bundle with exact-version native bridges
pnpm run build
  passed in 8.763 seconds; dist/server.js 32.8 MB,
  dist/server.js.map 76.9 MB

# exact emitted artifact, production configuration, fresh durable Postgres,
# durable Redis, isolated port, authentic health response, graceful shutdown
OSHUN_V1_DATABASE_URL=<fresh-local-postgres> \
OSHUN_REDIS_URL=redis://127.0.0.1:6379 \
  pnpm run verify:production-artifact
  Production artifact smoke check passed.

# teardown assertion
SELECT count(*) FROM pg_database
WHERE datname LIKE 'oshun_bff_artifact_%';
  0

The production smoke deliberately proves artifact construction, native loading, durable store hydration, Redis binding, Fastify listen/health, and graceful shutdown. It does not claim that the non-routable domain origins were live, exercise an authenticated business route, call a remote provider, or replace the already-passing rendered incident flow. No UI, mobile/native source, database schema, model/media pipeline behavior, Unreal asset, or production request changed in this closure, so Playwright/mobile/Unreal and provider probes were not applicable to this source-only build correction.

Host resources were checked before each targeted bundle: 15 GiB RAM, 31 GiB swap, at least 9.9 GiB initially available, and no competing broad verification gate. Builds and startup checks ran sequentially. No broad Nx sweep, Next build, Expo export, native packaging, or combined matrix ran. Commit-time lint-staged formatting plus V2 asset, stub, convention, and V5 documentation gates passed. There were no staged TypeScript files, so the owner-typecheck hook correctly had no target.

The source commit was pushed directly to origin/main; local HEAD, remote- tracking origin/main, and live refs/heads/main were all exact at the source tip. The protected user lockfile remained the exact unstaged Git blob a37431842e330b3a06b030947c25bebdc72bc2b1 and was never staged or published. All unrelated untracked Cargo lockfiles, libs/urania/, and the retained stash were untouched. The evidence update passed the root Unreal closure contract, all 21/21 versioned-evidence metadata tests, Prettier, and the V5 document validator. Docs Center verification reproduced the same 80 generator-owned structural gaps recorded by the preceding V1-002 slices; neither changed Markdown file owns a listed gap, so that unchanged repository backlog remains explicit. This closes the runnable-artifact defect, not the open all-store V1-002 inventory.

Citation-drift review-authority durability, reconciliation, privacy, and retention#

Tested implementation and published source: bf5cc04b0dfef3753ba1aca48762cf883e2a286e. Verification completed on 2026-07-20 UTC on host dev-server, Ubuntu 24.04.4 LTS, Linux 6.8.0-110-generic x86_64, Node v24.14.1, pnpm 10.25.0, PostgreSQL 16, Redis 7, and Playwright 1.60.0 with Chromium.

The continuing inventory confirmed the scope left explicit by the shared operator-incident slice. citationDriftResolutionStore and citationDriftSourceClassificationStore published review detail in process and invoked an unawaited snapshot callback. A failed save could therefore leave a terminal incident, resolution receipt, classification receipt, and audit mirror with different restart outcomes. Production did not require either sink, current restore accepted an unversioned permissive document, there was no bounded migration or redaction fence, and neither internal review package participated in profile erasure or the compliance-retention executor.

Both stores now own strict schema-v1 snapshot authorities. Mutations serialize behind one per-process promise queue, clone the committed state, normalize and validate a bounded candidate, await the whole-snapshot save, and publish only after success. A missing required sink or failed save raises a typed persistence error that the route maps to 503; a failed candidate is not visible through current reads and is not recovered after restart. Current snapshots are strict and replace-only, while the exact former { resolutions } and { classifications } documents migrate once into canonical order. Validation covers identifiers, timestamps, action/event coupling, action-specific fields, source classifications, unique row IDs, at most one pending resolution per incident, redaction/purge consistency, a 100,000-row bound, and a 64 MiB document ceiling. Reads and snapshots are detached copies. Production requires and hydrates both stores before accepting traffic.

Terminal resolution now uses an explicit cross-store recovery protocol. The route first commits a hidden durable pending intent carrying the exact operator, decision, rationale, and timestamp. It then resolves the shared incident using that same timestamp, actor, mapped resolution class, and terminal detail before durably promoting the intent to a visible resolution. If the incident write fails, the pending intent is durably aborted before the incident error is returned. If the incident commits but resolution completion fails, the response is 503 and the durable pending intent remains: an exact retry recognizes the already-committed incident and completes the same resolution ID. On restart, pending work is promoted only when the incident's ID, resolved status, mapped class, update timestamp, terminal actor, and terminal detail all match; every other pending intent is aborted. Different concurrent terminal decisions return 409, and completed exact retries return the existing authority instead of creating another decision. A no-pending reconciliation does not rewrite an unchanged snapshot. This is ordered recovery across two documents, not an atomic cross-document transaction or distributed compare-and-swap.

Per-source classifications now commit through their primary durable authority before a response or searchable-audit mirror. Terminal resolution follows the same rule after both primary authorities commit. Search audit events are secondary: a successful durable audit append is linked back with a later durable update, while audit or correlation failure cannot roll back primary review state or turn its acknowledged commit into a false failure. No public durable terminal resolution method bypasses the incident-authority protocol.

The two partitions are canonical internal, non-exportable review_package records. Profile erasure first reconciles terminal pending work, then pseudonymizes the exact reviewer separately in both stores, replaces authored rationale with a fixed redaction marker, removes searchable-audit correlation, and persists a subject fence even when no row matched. Adjacent reviewers remain exact, and any later write for the erased subject returns 409. Both partitions are registered with the shared seven-year review-package executor. The executor applies exact legal holds and category retention exceptions before calling the store purge; due purge removes every row linked to the retained pseudonym while keeping the non-reversible fence and purge timestamp. These internal governance records remain excluded from Article-15 customer export.

Verification covered the primary failure boundaries and the connected rendered path:

text
# store ordering/rollback/races, hidden pending/retry/reconciliation, strict
# restore/migration, detached reads, redaction/fences/purge, route cross-store
# failures, secondary-audit semantics, and shared erasure/retention composition
pnpm exec vitest run \
  src/admin/citation-drift-resolution-store.test.ts \
  src/admin/citation-drift-source-classification-store.test.ts \
  src/__tests__/admin-citation-drift-resolution-route.test.ts \
  src/privacy/compliance-retention-executor.spec.ts \
  src/data-deletion/profile-state-eraser.test.ts \
  --config vitest.config.ts --maxWorkers=1
  5 files, 45/45 tests passed

# real local PostgreSQL: pending-intent crash window, incident commit, restart
# reconciliation, exact/adjacent reviewer redaction, replay fences, expiry purge
OSHUN_ADMIN_DATABASE_URL=<live-local-postgres> \
  pnpm exec vitest run \
    src/admin/citation-drift-review-authorities-durability.integration.spec.ts \
    --config vitest.integration.config.ts --maxWorkers=1
  1 file, 1/1 test passed
  remaining_test_snapshots=0

# exact changed-source lint and the app-owned zero-backlog TypeScript gate
pnpm exec eslint <eight changed TypeScript paths> --quiet --no-warn-ignored
node tools/typecheck/ratchet.mjs \
  --app apps/oshun/bff --tsconfig tsconfig.typecheck.json
  lint passed
  no new app-own type errors; backlog: 0 known

# direct package-owned build and exact emitted-artifact startup on a fresh
# canonically bootstrapped PostgreSQL database plus durable Redis
pnpm --dir apps/oshun/bff run build
  dist/server.js 32.8 MB; dist/server.js.map 77.0 MB
OSHUN_ADMIN_DATABASE_URL=<fresh-local-postgres> \
OSHUN_REDIS_URL=redis://127.0.0.1:6379 \
  pnpm --dir apps/oshun/bff run verify:production-artifact
  Production artifact smoke check passed.
  remaining_temp_databases=0

# affected connected UI/API journeys against an isolated current-source BFF,
# fresh migrated database, durable Redis, and isolated Next development server
pnpm --dir apps/oshun/web run e2e -- \
  e2e/citation-drift-resolution.spec.ts \
  --project=chromium --workers=1 \
  --grep '(terminal drift decisions|per-source drift classifications)'
  2/2 passed

The default full Playwright configuration was first attempted and stopped at its unrelated Study-service bootstrap because that package could not resolve @aws-sdk/client-s3; no test had been collected. Web-only reuse of the existing BFF was also unsuitable because that long-lived process did not enable the test reset route. The final affected-path run therefore booted the exact current BFF source with test harnesses on an isolated port, applied the canonical admin snapshot schema to a fresh database, started an isolated web server pointed at that BFF, and ran only the two tests that exercise the changed resolution and classification routes. Both passed, and the process groups and database were removed; the database inventory returned zero matching temporary databases.

Host resources were checked before each expensive gate. The machine had 15 GiB RAM and 31 GiB swap; no competing build/test/typecheck process was active. The final BFF ratchet ran alone, was polled within 30 seconds, peaked at approximately 5.6 GiB RSS, and retained at least 4.9 GiB available memory. Build, artifact startup, live-PostgreSQL integration, and Playwright ran sequentially. No broad Nx sweep, Next production build, Expo export, native packaging, or combined matrix was used.

The source commit was pushed directly to origin/main; local HEAD, remote-tracking origin/main, and live refs/heads/main were exact at the source tip with divergence 0 0. The protected user lockfile remained the exact unstaged Git blob a37431842e330b3a06b030947c25bebdc72bc2b1 and was never staged or published. All unrelated untracked Cargo lockfiles, libs/urania/, and the retained stash were untouched.

The evidence update passed Prettier, the root Unreal closure contract, all 21/21 versioned-evidence metadata tests, and the V5 document validator. Docs Center verification reproduced the same 80 generator-owned structural gaps recorded by the preceding V1-002 slices: missing product space-map/engine references, the legacy domains redirect, and generated contract, OpenAPI, and reference pages. None of the four changed Markdown paths owns a listed gap, so that unchanged repository backlog remains explicit rather than being misreported as a pass.

This closes the two citation-drift review-detail authorities named by the operator-incident slice, not V1-002. Serialization remains per process and each store is a whole-snapshot document. Audit search is a secondary mirror; no append-only external audit provider is claimed. The incident catalog and source fixtures are still local, no operator-directory identity is inferred from the free-form assignee label, and no remote provider, production database/request, mobile/native flow, model/media pipeline, schema migration, or Unreal asset was changed or exercised. Provider-native erasure disposition and the broader operational-store durability/recoverability inventory remain open.

Tenant SSO configuration durability and recovery verification#

Verification completed 2026-07-20 against source commit 257b390ac439866669a9952bde1c2be57d7f4975.

The tenant SSO connection store previously changed its process-visible map and then launched void sink.save(...). Create, import, update, and delete could therefore return success before the primary snapshot existed, lose the accepted change after restart, and publish a success audit event for state that never committed. Concurrent whole-snapshot saves could also finish out of order, the legacy restore accepted an unnecessarily permissive object, and deployable boot did not require the persistence binding.

The hardened store builds a detached candidate, validates and canonically sorts the complete schema-v1 snapshot, saves it through one ordered per-process mutation queue, and only then publishes it to readers. createDurably, updateDurably, and removeDurably are the route-authoritative operations. Manual create, SAML/OIDC import, update, and delete await them. A typed primary persistence failure maps to stable 503; the prior committed snapshot remains live, no success audit event is appended, and the ordered queue remains usable by the next mutation. Production calls requireDurableSsoConnections() before the database adapter is installed, wires the sink, and hydrates it before traffic. Unwired synchronous helpers remain available only to isolated pure-engine tests and fail closed once production durability is required.

Restore is replace-only and accepts either the exact current schema or a bounded legacy { connections } document. Current schema-v1 input must contain only known fields in canonical connection order and rejects duplicate ids. Legacy input is strictly validated, unknown fields are stripped, connections are sorted, and the migrated canonical snapshot is persisted before it becomes live. Both paths enforce a 10,000-connection count, 32 MiB serialized-size cap, bounded strings, endpoint/mapping/lifetime limits, safe control characters, HTTP(S) endpoint and JWKS URLs, required email mapping, and detached clones.

This partition contains tenant-scoped federation configuration: tenant id, public IdP entity/issuer and endpoints, certificate thumbprint rather than the certificate or a private key, claim names and transforms, flow/JIT flags, lifetimes, and optional OIDC client id/JWKS URL. It contains neither an operator actor/rationale nor a user account or customer-authored content object. Tenant configuration must outlive deletion of the individual operator who edited it, so adding this store to profile DSAR or user-account erasure would be the wrong privacy boundary. Tenant offboarding and provisioning lifecycle remain outside this user-account closure claim.

Focused verification passed:

text
# store, route, and connection-probe behavior
pnpm --dir apps/oshun/bff exec vitest run \
  src/tenant-console/sso-connection-store.test.ts \
  src/tenant-console/sso-route.test.ts \
  src/tenant-console/sso-connection-test.test.ts
  3 files passed; 47/47 tests passed

# real PostgreSQL persistence, canonical legacy migration, restart CRUD, and
# final-state recovery; the unique snapshot row was removed after the proof
OSHUN_ADMIN_DATABASE_URL=<fresh-local-postgres> \
  pnpm --dir apps/oshun/bff exec vitest run \
  -c vitest.integration.config.ts \
  src/tenant-console/sso-connection-durability.integration.spec.ts
  1 file passed; 1/1 test passed

# source/static/type gates
pnpm exec eslint \
  apps/oshun/bff/src/tenant-console/sso-connection-store.ts \
  apps/oshun/bff/src/tenant-console/sso-connection-store.test.ts \
  apps/oshun/bff/src/tenant-console/sso-connection-durability.integration.spec.ts \
  apps/oshun/bff/src/tenant-console/sso-route.ts \
  apps/oshun/bff/src/tenant-console/sso-route.test.ts \
  apps/oshun/bff/src/server.ts
  passed
node tools/typecheck/ratchet.mjs \
  --app apps/oshun/bff --tsconfig tsconfig.typecheck.json
  no new app-own type errors; backlog: 0 known

# direct package build and exact emitted-artifact startup on fresh canonically
# migrated PostgreSQL plus durable Redis
pnpm --dir apps/oshun/bff run build
  dist/server.js 32.8 MB; dist/server.js.map 77.0 MB
OSHUN_ADMIN_DATABASE_URL=<fresh-local-postgres> \
OSHUN_REDIS_URL=redis://127.0.0.1:6379 \
  pnpm --dir apps/oshun/bff run verify:production-artifact
  Production artifact smoke check passed.
  remaining_temp_databases=0

# existing affected real-HTTP journey against an isolated exact-current-source
# BFF, fresh migrated database, durable Redis, and Chromium
pnpm --dir apps/oshun/web run e2e -- \
  e2e/tenant-sso-crud-bff.spec.ts \
  --project=chromium --workers=1
  8/8 passed
  remaining_temp_databases=0

Tests explicitly cover failed-write rollback, recovery of the next queued mutation, concurrent ordering, production missing-sink failure, invalid, duplicate, oversized, and noncanonical snapshot rejection, strict legacy migration and unknown-field stripping, and route-level 503 without a success audit event. The PostgreSQL integration creates a unique store key and removes the row. The browser run booted the exact current source on an isolated port and removed its process group and fresh database after all CRUD, import, validation, authorization, probe, and audit cases passed.

An expanded Vitest attempt that imported the broader tenant-console read/domain stub application graph did not produce a test summary and retained large worker processes. It was stopped as soon as that behavior and its resource cost were confirmed; it is not counted as a pass. The changed store/route/probe suites, real PostgreSQL proof, emitted artifact, and affected real-HTTP Playwright journey are the completed evidence above. No SAML sign-in or external IdP was changed by this slice, and the separate OIDC callback test surface is not claimed as affected verification.

Host resources were checked before expensive gates. The machine had 15 GiB RAM and 31 GiB swap. Gates ran sequentially; the final BFF type ratchet peaked at approximately 5.9 GiB RSS while retaining at least 4.6 GiB available memory. The expanded application-import attempt was stopped rather than allowed to compete with another retained worker. No broad Nx sweep, Next production build, Expo export, native packaging, or combined build matrix was used.

The source commit was rebased over unrelated remote work and pushed to origin/main; local HEAD, remote-tracking origin/main, and live refs/heads/main were exact at 257b390ac439866669a9952bde1c2be57d7f4975 with divergence 0 0. The protected user lockfile remained the exact unstaged Git blob a37431842e330b3a06b030947c25bebdc72bc2b1 and was never staged or published. All unrelated untracked Cargo lockfiles, libs/urania/, and the retained stash were untouched.

This evidence update passed Prettier, the root Unreal closure contract, all 21/21 versioned-evidence metadata tests, and the V5 document validator. Docs Center verification reproduced the same 80 generator-owned structural gaps as the preceding V1-002 slices: missing product space-map/engine references, the legacy domains redirect, and generated contract, OpenAPI, and reference pages. None of the four changed Markdown paths owns a listed gap, so that unchanged repository backlog remains explicit rather than being misreported as a pass.

This closes the tenant SSO configuration snapshot partition, not V1-002. Serialization is per BFF process and the authority is one whole-store snapshot; there is no distributed compare-and-swap across replicas. No live external IdP, SAML member sign-in, IdP-initiated route, production database/request, user-privacy fanout, tenant offboarding policy, mobile/native flow, model/media pipeline, schema migration, or Unreal asset is claimed. Tenant invitation, member, and seat capacity authority is a separate store closed by the next section; the broader durability/recoverability and privacy inventory remains open.

Tenant invitation, membership, seat, and subject-privacy durability verification#

Source commits 747edeab5215be2349c16430a8b2e87b62974cb0 and 92bb24d911954b874ea75f0b1e897847332dd14c close the tenant invite-store partition without closing the wider all-store audit. The earlier implementation published mutations in process and initiated a detached snapshot write, so an acknowledged invite, membership, acceptance, revocation, expiry, capacity change, or bulk-auth seat allocation could be lost on process death or after a failed save.

The store now computes a complete candidate, validates it, awaits one ordered save, and only then publishes it. Invite, direct-add, accept, revoke, expiry, capacity, bulk-auth membership, and account-erasure paths use the durable methods. A failed primary write returns stable 503 tenant_invite_persistence_failed, preserves the previous live snapshot, and prevents a success audit. Production startup requires the sink, reads it before traffic, performs strict replace-only hydration, persists a migrated or new canonical snapshot, and durably expires stale pending invitations. An absent sink is therefore a deployment error rather than silent process-local operation.

Schema v2 is bounded and exact: at most 10,000 invites, 100,000 members, 10,000 tenant pools, one million seats, and a 32 MiB serialized document, with bounded identifiers, normalized emails, roles, groups, licenses, timestamps, and token hashes. It rejects unknown current fields, duplicates, noncanonical arrays, unsafe controls, invalid lifecycle combinations, allocation/member mismatches, unlicensed members, and fenced-user resurrection. Restore is whole-snapshot replace-only and read models return detached values. A schema-version check avoids rewriting already-current PostgreSQL JSON solely because database key ordering differs.

The v2 acceptance record adds an internal acceptedBySubjectId link. Public invite views omit both that link and the token hash. Exact-subject profile export can therefore include the right membership and accepted invitation when the current account email differs from the original invite email. Signed erasure finds invitations by exact accepted subject or normalized current email, deletes that subject's members and invitations, releases their seats, and persists an exact-user resurrection fence. A schema-v1 or legacy document reconstructs the subject link only when one same-tenant member uniquely matches the accepted invite's creation timestamp and canonical roles; ambiguous or unowned accepted terminal rows are dropped instead of guessing an identity or retaining needless legacy email PII. New invite/member success audit rows keep event type, tenant, record id, roles, categorical state, and status while omitting target email and target user id. The mandatory frontend review led to that privacy-safe utility-copy boundary without introducing a second PII directory or changing layout and motion.

Focused verification on 2026-07-17 completed as follows:

text
tenant-invite-store.test.ts
  22/22 passed

admin tenant-invitation routes + bulk auth + tenant-console reads +
profile erasure + profile export bundle
  5 files, 66/66 passed

tenant-invite-durability.integration.spec.ts
  real local PostgreSQL, 1/1 passed
  v1 migration + mismatched-email exact export/erasure + seat release + restart

direct BFF type ratchet
  no new app-owned errors; backlog 0

direct BFF production bundle
  dist/server.js 32.9 MiB; source map 77.0 MiB

production artifact smoke
  exact emitted artifact + Redis + fresh PostgreSQL database + all 14 migrations
  health and graceful-exit checks passed

tenant-member-actions.spec.ts + tenant-invite-role-bff.spec.ts
  isolated exact-source BFF + fresh migrated PostgreSQL + Redis + Chromium
  12/12 passed; workers=1; retries=0
  acceptedBySubjectId public non-disclosure asserted

targeted ESLint + Prettier + git diff --check
  passed

The PostgreSQL suite used a unique document key and removed it. Artifact and browser runs used fresh uniquely named databases, isolated ports, and isolated Redis data; cleanup left no matching temporary database or process. The final browser run used the normal web origin covered by the BFF allowlist. Two earlier harness discovery runs correctly exposed test isolation mistakes—one web server targeted a stale BFF port and one nonstandard web origin was blocked by CORS—so neither is counted as product evidence. Both were corrected before the clean 12/12 run.

Host resources were checked before expensive gates. The machine had 15 GiB RAM and 31 GiB swap. Gates ran sequentially. The connected Vitest run peaked near 4.4 GiB RSS and the type ratchet near 5.7 GiB RSS, while available memory stayed above the hard stop threshold. No broad Nx sweep, Next production build, Expo export, native packaging, or combined build matrix was used.

The follow-up source commit was rebased over unrelated remote work and pushed. At source publication, local HEAD, remote-tracking origin/main, and live refs/heads/main were exact at 92bb24d911954b874ea75f0b1e897847332dd14c, with divergence 0 0. The protected user lockfile remained the exact unstaged Git blob a37431842e330b3a06b030947c25bebdc72bc2b1; the retained stash remained 9c4ddf4f7fd4c205d1f083cdbfb9d4a1ee5ce320. Neither it nor unrelated untracked Cargo lockfiles and libs/urania/ was staged or published.

This evidence update passed Prettier, the root Unreal closure contract, all 21/21 versioned-evidence metadata tests, and the V5 document validator. Docs Center verification reproduced the same 80 generator-owned structural gaps as the preceding V1-002 slices: missing product space-map/engine references, the legacy domains redirect, and generated contract, OpenAPI, and reference pages. None of the five changed Markdown paths owns a listed gap, so that unchanged repository backlog remains explicit rather than being misreported as a pass.

This evidence does not claim distributed compare-and-swap across BFF replicas; the queue serializes one whole snapshot per process. It does not impose invite-email/account equality, a permanent email fence, or a general time-based purge for terminal invitation rows. The user-id fence prevents the erased account from direct re-add/accept while allowing a genuinely new account or administrator invitation that reuses an address. Historical audit rows that already contain target PII are not rewritten. Acceptance still lacks a dedicated audit event, and SCIM remains a separate member projection. No production database/request, external email or IdP, provider-native deletion, mobile/native flow, Unreal asset, or model/media pipeline is claimed.

Tenant organization onboarding durability and creator-privacy verification#

Source and published commit fb0d40ead8b36badad3f04284096fda68b1a3403 closes the tenant organization-onboarding store partition without closing the wider all-store audit. The earlier implementation published a provisioning row, launched a detached save, changed the same row to active, and launched a second detached save. A successful HTTP response could therefore precede both primary writes, restart could recover either phase or no tenant, concurrent whole-snapshot saves could finish out of order, and a failed save could not roll back process-visible authority. Restore merged rows into existing memory and accepted unversioned, insufficiently bounded documents. Production boot did not require persistence. Public tenant detail also returned raw creator identity, while profile export and erasure did not cover that provenance.

The hardened store treats the work this repository actually performs as one deterministic commit: a new tenant is saved once as active; no synthetic two-phase provisioning protocol or external isolation-resource effect is claimed. Each deployable mutation clones the whole state, validates and canonically sorts a schema-v1 candidate, awaits one ordered per-process save, and only then publishes it. A failed save returns stable 503 tenant_onboarding_persistence_failed, leaves the prior committed snapshot live, and does not poison the queue for a later operation. Production marks the store durability-required before adapters are installed, reads and validates the Postgres snapshot before traffic, replaces memory rather than merging it, persists an absent or migrated canonical document, and binds the awaited sink. An already-current canonical PostgreSQL JSON document is not rewritten merely because database key ordering differs.

The exact durable record preserves tenant id and kind, hierarchy parent, display name, derived contract and isolation-boundary ids, billing entity, region and data-residency region, canonical per-license seat allocations and their checked total, lifecycle state, creation/activation timestamps, and internal creator provenance. Current snapshots are strict, clone-detached, and bounded to 10,000 tenants, 100,000 erased-actor fences, 100 allocations per tenant, one million seats per license, ten million seats per tenant, and 32 MiB. They reject unknown fields, noncanonical ordering and timestamps, duplicate or malformed machine ids, unsafe controls, inconsistent derived ids, seat totals, or lifecycle timestamps, missing or cyclic parents, overdeep/invalid hierarchy, and invalid tenant-console contracts. Legacy { tenants } documents migrate conservatively: their aggregate seats become one legacy-total allocation, missing contract/billing/region fields are derived, and crash-left provisioning rows become active at their recorded creation time before the canonical snapshot is acknowledged.

Creator provenance now has an explicit privacy boundary. Public tenant detail uses a view that omits createdByActorId. The profile export bundle includes the exact public views of organizations created by the requesting subject. Account erasure preserves the organization as shared tenant authority but replaces matching creator ids with redacted:<sha256> and persists the corresponding one-way digest fence. The fence is written even when erasure races ahead of the subject's first onboarding write, so the erased identity cannot recreate provenance after restart. Adjacent creators and tenants remain exact, and snapshots reject a redacted actor whose fence is absent. The digest is a pseudonym, not a claim of anonymous deletion, and the organization record is intentionally retained.

Focused verification on 2026-07-17 completed as follows:

text
# connected BFF route, export/erasure bundle, and pure store behavior
pnpm --dir apps/oshun/bff exec vitest run \
  src/tenant-console/tenant-onboarding-store.test.ts \
  src/__tests__/domain-stubs-route.test.ts \
  src/data-export/bundle-builder.test.ts \
  --maxWorkers=1
  3 files passed; 140/140 tests passed

# real PostgreSQL exact-contract/hierarchy recovery, creator redaction,
# resurrection fence, adjacent-creator isolation, and restart
OSHUN_ADMIN_DATABASE_URL=<local-postgres> \
  pnpm --dir apps/oshun/bff exec vitest run \
  -c vitest.integration.config.ts \
  src/tenant-console/tenant-onboarding-durability.integration.spec.ts \
  --maxWorkers=1
  1 file passed; 1/1 test passed

# formatting, source/static checks, and direct type ratchet
pnpm exec prettier --check <eight affected source/test paths>
  passed
pnpm exec eslint <eight affected source/test paths>
  0 errors; test paths intentionally ignored by the source lint profile
git diff --check
  passed
node tools/typecheck/ratchet.mjs \
  --app apps/oshun/bff --tsconfig tsconfig.typecheck.json
  no new app-own type errors; backlog: 0 known

# official package build and exact emitted-artifact startup after rebasing the
# concurrent Tara Workbench server/migration addition
pnpm --dir apps/oshun/bff run build
  dist/server.js 33.0 MiB; dist/server.js.map 77.3 MiB
OSHUN_ADMIN_DATABASE_URL=<fresh-local-postgres> \
OSHUN_REDIS_URL=redis://127.0.0.1:6379/14 \
  pnpm --dir apps/oshun/bff run verify:production-artifact
  all 15 canonical migrations applied
  Production artifact smoke check passed
  health, graceful exit, remaining temporary databases: 0

The store's 11 focused tests explicitly cover exact contract/seat persistence, validation without fabrication, real-parent hierarchy validation, failed-write rollback and queue recovery, concurrent invocation ordering, required-sink failure, strict current-snapshot rejection, legacy provisioning migration, no-op current boot, creator export/redaction/restart, and erasure-before-write racing. The route test proves exact allocations and public creator omission and returns 503 without publishing a failed candidate. The export test proves the profile section before erasure and an empty, fenced section afterward. The PostgreSQL test used a unique document key and removed it; both artifact runs used fresh uniquely named databases and left no matching database or process.

One initial root Vitest invocation selected the monorepo matrix that excludes application tests and therefore found no files; it is not counted as evidence. An initial hand-built raw-esbuild smoke artifact correctly failed on a dynamic CommonJS require because it did not use the repository's ESM-safe build authority; the official package build above replaced that invalid harness and passed. No Playwright run is claimed for this slice: repository-wide source search finds no shipped web/admin caller for POST /v1/tenants/onboard, and the existing /operator/tenants roster response shape and rendering behavior did not change. The API, restart, privacy, and emitted-server paths are covered by the connected tests above.

Host resources were checked before expensive gates. The machine had 15 GiB RAM and 31 GiB swap. Connected Vitest and the BFF type ratchet ran sequentially with one worker; the type process peaked near 5.8 GiB RSS while available memory stayed above 4 GiB. Build and artifact startup also ran sequentially. No broad Nx sweep, Next production build, Expo export, native packaging, Playwright, or combined matrix was used.

The source commit was rebased over unrelated remote work in server.ts, whose Tara Workbench additions occupied separate regions. The type ratchet, official build, all 15 fresh-database migrations, and artifact smoke were rerun after that integration. At source publication local HEAD, remote-tracking origin/main, and live refs/heads/main were exact at fb0d40ead8b36badad3f04284096fda68b1a3403, with divergence 0 0. The protected user lockfile remained the exact unstaged Git blob a37431842e330b3a06b030947c25bebdc72bc2b1; the retained stash remained 9c4ddf4f7fd4c205d1f083cdbfb9d4a1ee5ce320. Neither it nor unrelated untracked Cargo lockfiles and libs/urania/ was staged or published.

This evidence update passed Prettier, the root Unreal closure contract, all 21/21 versioned-evidence metadata tests, and the V5 document validator. Docs Center verification reproduced the same 80 generator-owned structural gaps as the preceding V1-002 slices: missing product space-map/engine references, the legacy domains redirect, and generated contract, OpenAPI, and reference pages. None of the four changed Markdown paths owns a listed gap, so that unchanged repository backlog remains explicit rather than being misreported as a pass.

This closes only the local organization-onboarding authority. Serialization is per BFF process over one whole-store snapshot, with no distributed compare-and- swap across replicas and no idempotency key preventing duplicate client requests. There is no external tenant/isolation provisioning effect, dedicated onboarding audit event, shipped onboarding UI caller, tenant update/archive/ offboarding flow, or time-based purge for active organization authority. The roster still projects licensed seat total as memberCount; live tenant members and invitations remain a separate store. Creator erasure retains a SHA-256 pseudonym and the shared tenant organization by design. No production request, external IdP/provider, provider-native deletion, mobile/native flow, Unreal asset, or model/media pipeline is claimed. The broader V1-002 operational-store inventory remains open.

Follow/premiere read-through fail-closed disposition — 2026-07-26#

Source implementation and published origin/main commit: 978fb8b1fe98ee72ac3ebfa5ea33f46112143730.

Authority and safety audit#

The durable FollowStore correctly owns follow relationships, premiere lifecycle/allocation, subject fences, DSAR, and erasure. It also held three separate mutable maps described as read-through inputs: symmetric blocklists, follower quiet-hour/UTC preferences, and per-creator weekly notification counts. Repository-wide tracing found only route and durability tests populated those maps. No trust/safety, notification-preference, or delivery-ledger producer bound them, and no first-party web/mobile/admin client called these routes.

Loss was not harmless even though the maps were excluded from the durable snapshot: an empty blocklist allowed a follow that a canonical block could forbid; default quiet hours could produce an immediate notification during a member's actual quiet window; and a zero weekly count could bypass the domain library's premiere cap. These are safety and acknowledged-delivery inputs, not recomputable cache defaults.

Explicit read-through boundary#

The three maps and their seed/read helpers are removed from FollowStore. createFollowDurably now requires explicit creator/viewer blocklists. The routes accept one async-capable FollowReadThroughSource:

  • follow creation returns 503 follow_read_through_source_not_configured when the source is unbound;
  • fan-out returns the same 503 when unbound; and
  • missing, duplicate, or unexpected viewer rows return 503 follow_read_through_source_incomplete.

Only a named FollowReadThroughFixture supplies mutable synthetic data through explicit test composition. The route still delegates block symmetry and every opt-out/cap/quiet-hours verdict to @oshun/scene-experience. Unfollow, follower count, premiere lifecycle, durable export, and signed erasure remain available from the owned durable state.

Verification#

text
pnpm exec vitest run --config apps/oshun/bff/vitest.config.ts \
  apps/oshun/bff/src/routes/scene-follows.test.ts \
  apps/oshun/bff/src/scene-experience/follow-store-durability.spec.ts \
  apps/oshun/bff/src/data-export/bundle-builder.test.ts \
  apps/oshun/bff/src/__tests__/v1-feature-pack-boot.test.ts
  4 files passed; 61/61 tests passed

pnpm exec vitest run --config apps/oshun/bff/vitest.config.ts \
  apps/oshun/bff/src/routes/scene-follows.test.ts \
  apps/oshun/bff/src/scene-experience/follow-store-durability.spec.ts
  2 files passed; 18/18 tests passed

OSHUN_ADMIN_DATABASE_URL=<fresh-database> \
  pnpm exec vitest run \
    --config apps/oshun/bff/vitest.integration.config.ts \
    apps/oshun/bff/src/scene-experience/follow-store-durability.integration.spec.ts
  1 file passed; 1/1 test passed

NX_DAEMON=false pnpm exec eslint <7 changed BFF source/test files> \
  --no-warn-ignored --no-cache
pnpm exec prettier --check <7 changed BFF files>
git diff --check
  passed

NODE_OPTIONS='--max-old-space-size=8192' \
  node tools/typecheck/ratchet.mjs \
    --app apps/oshun/bff \
    --tsconfig tsconfig.typecheck.json
  only the same five current-main errors outside the affected files

node apps/oshun/bff/scripts/build.mjs
node --check apps/oshun/bff/dist/server.js
pnpm --dir libs/oshun/persistence exec prisma migrate deploy \
  --config prisma.config.ts
  all 32 migrations applied
node apps/oshun/bff/scripts/verify-production-artifact.mjs
  Production artifact smoke check passed.

The first integration invocation used the default unit config, which intentionally excludes *.integration.spec.ts, and exited with “No test files found” before executing a test. The corrected repository integration config passed 1/1. The resource gate reported 15 GiB RAM, 31 GiB swap, and 14 GiB free disk; the ratchet was supervised every 30 seconds. The source rebased over unrelated changes. Because root package/ESLint inputs changed, scoped lint, all 61 tests, the build, fresh migrations, real-PostgreSQL integration, and production smoke were repeated. Both disposable catalogs were removed.

The exact published artifact is:

text
apps/oshun/bff/dist/server.js
  36,568,720 bytes
  sha256 adcc9319f8679bde6deeb43a68f496628464261531052820b55a5630efcf599e

apps/oshun/bff/dist/server.js.map
  85,715,665 bytes
  sha256 927d46f278252ee7ae68039093e0c35902113ac9bb9230280eff052a9a181d9b

Artifact identities#

Artifact SHA-256
apps/oshun/bff/src/scene-experience/follow-store.ts 6b97cf120312360c269dc4f8074ae35fa46bf11a22d7f12af88f1ba292541ac7
apps/oshun/bff/src/routes/scene-follows.ts f78fd2d202690b1337ed5deb8bd4975dbef336a429cf7dc1f170401edb89c771
apps/oshun/bff/src/routes/scene-follows.test.ts 231ded730f9fc4533e702bd1939765399aa1ec0f2bb82c1a2b0a296de14fd8f6
apps/oshun/bff/src/scene-experience/follow-store-durability.spec.ts e4304cbeaeea9bd4fda7669efad404ac92de91bb79a0c1f9fcc319e067b98a64
apps/oshun/bff/src/scene-experience/follow-store-durability.integration.spec.ts b5867189a2a1643ec6e84df8bb33652d2a0167b685766afab0ecebadab9c2e2e
apps/oshun/bff/src/data-export/bundle-builder.test.ts f84ab4c02467f7835f002a0eded7a12c0f9b7496778a4aa170480a28401fc105
apps/oshun/bff/src/app.ts b04f9617fd99daa194f0d00ed3bc3aff8419c236dd52dcd7b793aadb8fd64d37
apps/oshun/bff/dist/server.js adcc9319f8679bde6deeb43a68f496628464261531052820b55a5630efcf599e

No customer/admin UI, public schema, database schema, provider/model call, or Unreal asset changed. No first-party UI consumes these routes. Frontend-skill, Playwright, mobile, schema-generation, live-provider, and Unreal automation were therefore inapplicable.

This closes the unsafe fixture/read-through defaults without claiming canonical trust/safety or notification/delivery projectors. Those deployments must bind the explicit source with their own durability, privacy, retention, freshness, and acknowledged-effect evidence. V1-002's parent all-store inventory remains open.

Tenant OneRoster apply/commit durability and privacy-boundary verification#

Source and published commit de1c284a6ffd457b5f6ef020882191c32fc14884 closes the local OneRoster apply/commit snapshot partition without closing the wider all-store audit. The earlier store mutated live nested maps first and launched void sink.save(snapshot) afterward. HTTP apply/pull and roster bulk rows could therefore report success and append a success audit before primary persistence, restart could lose both roster authority and the global replay-prevention commit, concurrent saves could complete out of order, and a failed save could not roll back process-visible state. Restore accepted an unchecked unversioned document, production did not require the sink, and a conflicting import for a new tenant fabricated an empty roster. The dry-run engine also did not reject duplicate identities within the incoming arrays.

The hardened store clones one whole-state candidate, normalizes and validates its input, reruns the real dryRunOneRosterImport engine against committed state, canonically constructs a strict schema-v1 snapshot, awaits the save in an ordered per-process queue, and only then publishes the candidate. Admin apply, externally triggered pull, and bulk roster executors await that path before acknowledging or auditing success. A failed write returns stable 503 oneroster_persistence_failed, leaves both roster and commit history at the prior durable view, emits no success audit, and does not poison the queue. Production marks persistence required before route traffic, loads and strictly replaces memory from PostgreSQL, writes a canonical empty or migrated document, then binds the awaited sink. A current canonical document is not rewritten at boot. Conflict and duplicate results do not save; a conflict for a previously unknown tenant no longer creates an empty tenant summary.

The exact snapshot contains tenant-scoped OneRoster users (sourcedId, username, role, enabled state), enrollments (id, user/class references and role), and globally keyed commit records with applied counts, post-commit counts, tenant, and timestamp. It is bounded to 10,000 tenants, 100,000 users and 500,000 enrollments per tenant, 100,000 commits, 32 MiB, 200-character ids, and 320-character usernames. Current restore rejects unknown fields, unsafe or noncanonical text, unsupported roles, oversize documents, unsorted/duplicate identity, duplicate usernames, dangling enrollment references, missing commit tenants, and inconsistent counts. Incoming apply/preview also reject duplicate user ids, usernames, or enrollment ids before the dry-run engine. Legacy { rosters, commits } documents migrate into canonical order and deliberately strip caller-supplied unknown user/enrollment fields that the old route could retain.

The privacy boundary is explicit rather than inferred. Conflict responses to the authorized operator remain actionable, but the durable pull-conflict audit now records only conflictCount, not raw conflict strings that can include usernames. Stored external sourcedId and username fields are institution roster identities; there is no exact link to the customer-auth subject. The account-level DSAR/export/erasure fanout therefore cannot safely claim ownership or delete by username. This slice does not add a false subject eraser. Exact subject linkage would require a separately governed mapping; tenant offboarding and institution retention are separate unimplemented boundaries.

Focused verification on 2026-07-17 completed as follows:

text
# pure store, connected apply/pull routes, roster bulk executor, and dry-run
pnpm exec vitest run --config apps/oshun/bff/vitest.config.ts \
  apps/oshun/bff/src/tenant-console/oneroster-apply-store.test.ts \
  apps/oshun/bff/src/__tests__/admin-oneroster-apply-route.test.ts \
  apps/oshun/bff/src/__tests__/admin-bulk-operations-route.test.ts \
  apps/oshun/bff/src/tenant-console/oneroster-route.test.ts
  4 files passed; 35/35 tests passed

# real PostgreSQL canonical-empty save, two ordered applies, exact recovery,
# replay prevention, persisted version/document equality, and fixture cleanup
OSHUN_ADMIN_DATABASE_URL=<local-postgres> pnpm exec vitest run \
  --config apps/oshun/bff/vitest.integration.config.ts \
  apps/oshun/bff/src/tenant-console/oneroster-apply-durability.integration.spec.ts
  1 file passed; 1/1 test passed

# exact-source real-HTTP flows on isolated port 4110, fresh PostgreSQL with all
# 15 canonical migrations, and isolated Redis abuse keys
E2E_BFF_URL=http://127.0.0.1:4110 pnpm --dir apps/oshun/web exec playwright test \
  -c playwright.fast.config.ts e2e/tenant-oneroster-provisioning-bff.spec.ts \
  e2e/tenant-bulk-operations-export-bff.spec.ts --project=chromium --workers=1
  8/8 tests passed

# exact zero-backlog type gate, changed-source lint, and production entry bundle
node tools/typecheck/ratchet.mjs --app apps/oshun/bff \
  --tsconfig tsconfig.typecheck.json
  no new app-own type errors; backlog: 0 known
pnpm exec eslint <eight affected source/test paths>
  0 errors; four test paths intentionally ignored by the source lint profile
pnpm --dir apps/oshun/bff exec esbuild src/server.ts --bundle \
  --platform=node --format=esm --target=node22 \
  --outfile=/tmp/oshun-oneroster-bff-dist/server.js --sourcemap
  server.js 33.6 MiB; source map 78.9 MiB

The nine focused store tests cover exact schema-v1 capture/restore and replay, failed-write rollback plus queue recovery, concurrent invocation ordering, required-sink failure, conflict non-publication, duplicate incoming identity, strict invariant rejection, legacy field minimization/migration/restart, and current boot without a redundant write. The connected route test proves stable 503 with neither publication nor success audit and proves raw conflict strings are absent from the durable audit payload. The real database test used a unique snapshot key and removed it. The deploy-shaped run created a fresh database, applied all 15 migrations, booted the exact TypeScript source, passed both affected Playwright files, stopped the process, booted a second process on the same database, observed two hydrated tenants and three commits, and received 409 for a recovered duplicate commit. It then removed the temporary database and 18 matching Redis test keys; no isolated process remained.

Host resources were checked before Playwright. The machine had 15 GiB RAM, 31 GiB swap, and 18 GiB available disk. Available memory remained about 9.6 GiB during the sequential one-worker run; no broad Nx sweep, Next production build, Expo export, native packaging, or combined matrix was used. The source commit was rebased over unrelated remote work with no overlapping changed path. At source publication, local HEAD, remote-tracking origin/main, and live refs/heads/main were exact at de1c284a6ffd457b5f6ef020882191c32fc14884, with divergence 0 0. The protected user lockfile remained the exact unstaged Git blob a37431842e330b3a06b030947c25bebdc72bc2b1; the retained stash remained 9c4ddf4f7fd4c205d1f083cdbfb9d4a1ee5ce320. Neither it nor unrelated untracked Cargo lockfiles and libs/urania/ was staged or published.

This evidence update passed Prettier, git diff --check, the root Unreal closure contract, all 21/21 versioned-evidence metadata tests, and the V5 document validator. Docs Center verification reproduced the same 80 generator-owned structural gaps as the preceding V1-002 slices: missing product space-map/engine references, the legacy domains redirect, and generated contract, OpenAPI, and reference pages. None of the four changed Markdown paths owns a listed gap, so that unchanged repository backlog remains explicit rather than being misreported as a pass.

This closes only the local OneRoster apply/commit authority. Serialization is per BFF process over one whole-store snapshot, with no distributed compare-and- swap across replicas. Commit ids remain globally keyed rather than tenant-qualified. The plan creates/updates users and creates enrollments but does not disable missing users or remove stale enrollments. The pull endpoint does not fetch from an SIS or schedule itself, /operator/lms remains preview-only, and apply conflicts/duplicates still lack a complete attempt audit. There is no exact customer-auth subject link, tenant offboarding/ institution retention workflow, production SIS/provider receipt, external effect, mobile/native flow, Unreal asset, or model/media pipeline claim. The broader V1-002 operational-store inventory remains open.

Admin Telegram channel-binding durability and recovery verification#

Source and published commit d5b3e8c1a2b38cc31688200f4d0682be778502e0 closes the local operator-managed Telegram editorial-channel binding snapshot without closing the wider all-store audit. The earlier store mutated its live array and then invoked a synchronous sink whose production binding launched void sink.save(snapshot). Bind, crisis-suppression, and takedown routes could therefore acknowledge state that PostgreSQL had not accepted; a failed save could not roll memory back, concurrent saves could complete out of order, and a restart could resurrect a taken-down seed. Restore accepted an unchecked, unversioned document, and production did not mark the sink required before traffic.

The hardened store builds a detached whole-list candidate, validates and canonically orders it, awaits its save in a per-process queue, and publishes the candidate only after acknowledgement. All three admin mutation routes await that path. A failed save returns stable 503 telegram_channel_bindings_persistence_failed, leaves the committed view unchanged, and does not poison the queue. Production requires durability before adapter initialization, strictly hydrates PostgreSQL before traffic, persists canonical seeds on an absent first boot, and binds the awaited sink only after successful restore. A current canonical snapshot is not rewritten at boot; legacy { records } documents are normalized and rewritten once.

Schema v1 retains public Telegram handle, editorial domain and matching pipeline, operator-role label, suppression flag, locale, and binding timestamp. It is bounded to 10,000 records and 4 MiB. Handles are canonical lowercase Telegram identifiers; owner-role and locale text are bounded; timestamps are canonical UTC; unsafe controls, unknown current-schema fields, duplicate handles, domain/pipeline mismatches, noncanonical ordering, and unsupported future versions fail restore. Legacy migration canonicalizes mixed-case handles and timestamps and deliberately strips unknown record fields. The admin form now defaults to a coherent Arete domain/pipeline pair, and its unavailable-state copy truthfully says mutations fail closed on unavailable durable state.

Focused verification on 2026-07-17 completed as follows:

text
# pure candidate/save/publish behavior and connected mutation routes
pnpm exec vitest run \
  src/messaging-channels/telegram-bindings-store.test.ts \
  src/__tests__/admin-messaging-channels-route.test.ts --maxWorkers=1
  2 files passed; 22/22 tests passed

# real PostgreSQL seed, bind, toggle, takedown, exact restart recovery,
# duplicate rejection, stored-document equality, and fixture cleanup
OSHUN_ADMIN_DATABASE_URL=<local-postgres> pnpm exec vitest run \
  --config apps/oshun/bff/vitest.integration.config.ts \
  apps/oshun/bff/src/messaging-channels/telegram-bindings-durability.integration.spec.ts \
  --maxWorkers=1
  1 file passed; 1/1 test passed

# affected admin UI against isolated current bundle on :4110, admin on :3021,
# and a fresh PostgreSQL database with all 15 migrations
E2E_BASE_URL=http://127.0.0.1:3021 pnpm --dir apps/oshun/admin exec \
  playwright test e2e/telegram-channel-registry.spec.ts \
  --project=chromium --workers=1
  2/2 tests passed

# exact zero-backlog BFF type gate, admin type gate, changed-source lint,
# production bundle, and incidental stale Tara fixture verification
node tools/typecheck/ratchet.mjs --app apps/oshun/bff \
  --tsconfig tsconfig.typecheck.json
  no new app-own type errors; backlog: 0 known
pnpm --dir apps/oshun/admin exec tsc --noEmit
  passed
pnpm exec eslint <eight Telegram source/test paths> --no-ignore --max-warnings=0
  passed
node apps/oshun/bff/scripts/build.mjs
  server.js 33.1 MiB; source map 77.6 MiB
pnpm exec vitest run src/routes/tara-workbench.spec.ts --maxWorkers=1
  41 passed; 1 intentionally skipped

The nine store tests cover canonical handle and domain/pipeline validation, detached reads, failed-write rollback plus queue recovery, concurrent invocation ordering, missing-required-sink failure, strict current restore, legacy minimization/migration, canonical first boot, and no redundant current-schema rewrite. Thirteen connected route tests cover auth/scope, list, all three mutations, payload and coherence rejection, and a stable persistence-failure response with no visible binding. The real database test used a unique snapshot key and removed it.

The deploy-shaped run created a fresh database, applied all 15 migrations, booted the exact current BFF bundle and admin source, and passed both affected Chromium tests, including real bind, suppression toggle, and takedown through the operator page. A separate binding was then acknowledged through real HTTP; the BFF was stopped, a second process booted against the same database, and the exact six-binding view recovered that record and timestamp. Cleanup takedown was acknowledged, both isolated processes were stopped, and the temporary database was dropped. Ports 3021 and 4110 were no longer listening.

Host resources were checked before expensive gates. The machine had 15 GiB RAM, 31 GiB swap, and 18 GiB available disk. Typechecking, bundling, one-worker tests, and Playwright ran sequentially; no broad Nx sweep, Next production build, Expo export, native packaging, or combined matrix was used. At source publication, local HEAD, remote-tracking origin/main, and live refs/heads/main were exact at d5b3e8c1a2b38cc31688200f4d0682be778502e0, with divergence 0 0. The protected lockfile remained the exact unstaged Git blob a37431842e330b3a06b030947c25bebdc72bc2b1; the retained stash remained 9c4ddf4f7fd4c205d1f083cdbfb9d4a1ee5ce320. Neither it nor unrelated untracked Cargo lockfiles and libs/urania/ was staged or published.

This evidence update passed Prettier, git diff --check, the root Unreal closure contract, all 21/21 versioned-evidence metadata tests, and the V5 document validator. Docs Center verification reproduced the same 80 generator-owned structural gaps as the preceding V1-002 slices: missing product space-map/engine references, the legacy domains redirect, and generated contract, OpenAPI, and reference pages. Neither changed Markdown path owns a listed gap, so that unchanged repository backlog remains explicit rather than being misreported as a pass.

This closes only the local operator configuration authority. Serialization is per BFF process over one whole snapshot; there is no distributed compare-and- swap across replicas. The snapshot stores no Telegram credential or message body, but it also is not a durable operator-attempt/rationale audit ledger; the admin server action's separate process-local audit array is not claimed as durable evidence. Binding and takedown do not call Telegram or prove provider- side channel ownership or post removal. The records have no customer-auth subject, so account DSAR/erasure fanout is inapplicable rather than inferred from the public handle. There is no time-based purge, external provider receipt, mobile/native flow, Unreal asset, or model/media pipeline claim. The broader V1-002 operational-store inventory remains open.

Operator persona-lifecycle authority verification#

Implementation source and published tip: d145bc035f60448c688e79d458b9f71178587905. Verification ran on dev-server, Linux 6.8.0-110-generic x86_64, on 2026-07-17 UTC. Toolchain: Node 24.14.1, pnpm 10.25.0, TypeScript 6.0.3, Vitest 4.1.7, ESLint 10.4.0, Chromium through the repository Playwright harness, PostgreSQL 16 with pgvector, and Redis 7. The protected lockfile remained the exact unstaged blob a37431842e330b3a06b030947c25bebdc72bc2b1.

The prior lifecycle store mutated its live map before calling a synchronous snapshot hook whose production binding discarded sink.save's promise. A route could therefore return success and enqueue a separate admin-audit projection before PostgreSQL accepted the lifecycle status or immutable signoff envelope. Failed saves could not restore memory, concurrent whole-snapshot saves could complete out of order, restore trusted an unversioned unchecked document, and production did not require the sink before traffic.

The hardened authority validates a detached complete candidate, awaits its PostgreSQL snapshot, and publishes it only after acknowledgement. Transition and runtime-seed mutations share one recoverable per-process queue; a failed save returns stable 503 persona_lifecycle_persistence_failed, exposes no new status or audit entry, emits no success projection, and leaves the queue usable. Production requires the partition before database wiring and hydrates it before traffic. Pure synchronous helpers remain available for unbound engine tests but throw once a sink is bound or durability is required.

Schema v1 is strict, canonical, and bounded: at most 10,000 personas, at most 10,000 immutable audit envelopes per persona, and at most 16 MiB serialized. It bounds persona/display/actor/justification/rollback text, rejects unsafe controls, unknown current fields, duplicate ids, noncanonical order, broken or regressing audit chains, status/timestamp disagreement, semantically invalid signoff envelopes, and unsupported versions. Reads and snapshots deep-clone the nested audit state. An absent first boot persists the canonical catalog; legacy { personas } documents are minimized and rewritten once; persisted records remain authoritative while catalog personas introduced by newer code are added once; a current complete snapshot is not rewritten.

The primary lifecycle snapshot includes the validator-produced immutable audit envelope. After that authority commits, the route records the separate admin search/explorer projection and awaits its durable flush when supported. A projection failure cannot honestly roll back the already-committed lifecycle, so the route returns the authoritative result with adminAuditProjection: "degraded" and logs the projection failure. This is an explicit non-atomic projection boundary, not a claim of a cross-store transaction.

text
# pure transition matrix plus strict candidate/save/publish behavior, and the
# connected Fastify route including failed-save and degraded-projection cases
pnpm --dir apps/oshun/bff exec vitest run \
  src/admin/persona-lifecycle-store.test.ts \
  src/__tests__/admin-personas-lifecycle-route.test.ts
  2 files passed; 76/76 tests passed

# exact seed/transition/audit recovery through a fresh real database connection
OSHUN_ADMIN_DATABASE_URL=<local-postgres> pnpm --dir apps/oshun/bff exec \
  vitest run -c vitest.integration.config.ts \
  src/admin/persona-lifecycle-durability.integration.spec.ts
  1 file passed; 1/1 test passed

# exact zero-backlog BFF type gate, changed-source lint/format, and bundle
node tools/typecheck/ratchet.mjs --app apps/oshun/bff \
  --tsconfig tsconfig.typecheck.json
  no new app-own type errors; backlog: 0 known
pnpm exec eslint <three changed non-test sources> --max-warnings=0
pnpm exec prettier --check <six changed source/test paths>
git diff --check
  passed
node apps/oshun/bff/scripts/build.mjs
  server.js 33.2 MiB; source map 77.6 MiB

# exact bundle on :4111 and fresh PostgreSQL database with all 15 migrations
E2E_BFF_URL=http://127.0.0.1:4111 pnpm --dir apps/oshun/web exec \
  playwright test e2e/persona-lifecycle-bff.spec.ts \
  --config playwright.fast.config.ts --project=chromium --workers=1
  5/5 real-HTTP tests passed

# existing operator console preserved; real browser mutations use the same BFF
E2E_BASE_URL=http://127.0.0.1:3011 \
E2E_BFF_URL=http://127.0.0.1:4111 pnpm --dir apps/oshun/web exec \
  playwright test e2e/operator-personas-console.spec.ts \
  --config playwright.fast.config.ts --project=chromium --workers=1
  7/7 browser/DOM/accessibility tests passed

The 64 store tests retain exhaustive coverage of all 13 canonical events from every legal and an illegal state, governance gates, optimistic conflicts, and the complete release path. The added durability cases prove first-boot seed commit, runtime persona recovery, legacy minimization/catalog reconciliation, no current-schema rewrite, failed-write rollback, queue recovery, concurrent invocation ordering, required-sink failure, strict restore, and nested-state isolation. Twelve route tests prove auth/scope, reads, legal and rejected paths, full release progression, stable persistence failure with no state/audit publication, and truthful degraded secondary projection.

The real PostgreSQL test used a unique key, opened a fresh connection for the restart reader, asserted the complete audit envelope and stored-document equality, then removed its row. The deploy-shaped run created a separate database, applied all 15 migrations, and booted the exact 33.2 MiB bundle. Five real-HTTP Playwright cases and all seven operator-console browser cases passed, including live transition repaint/audit, rollback fields, mobile touch targets, pending-button exclusion, offline failure, and 409 no-mutation. An initial console run on custom port 3022 produced five passes and two connectivity failures because that origin is intentionally absent from the BFF CORS allowlist; the unchanged suite passed 7/7 on repository-supported origin 3011. No product source was changed for that harness correction.

Before process shutdown, real HTTP reported Sufi at approved-for-test with 31 audit entries and update timestamp 1784549290. A second exact-bundle process against the same database recovered that exact tuple. Ports 3011, 3022, and 4111 were stopped and the temporary database was dropped; its existence check returned zero. Host gates reported 15 GiB RAM, 31 GiB swap, 18 GiB disk, and no competing broad build, so targeted typecheck, bundle, one-worker tests, and Playwright ran sequentially. No broad Nx sweep or Next production build ran.

The frontend skill governed this slice because the route changes affect the operator console. Its existing restrained roster/detail composition was preserved; the already-deep browser journey was exercised instead of adding unrelated visual treatment. No mobile-native, Unreal, provider/model, media, or customer-facing flow changed.

This evidence update passed Prettier, git diff --check, the root Unreal closure contract, all 21/21 versioned-evidence metadata tests, and the V5 document validator. Docs Center verification reproduced the same 80 generator-owned structural gaps as the preceding V1-002 slices: missing product space-map/engine references, the legacy domains redirect, and generated contract, OpenAPI, and reference pages. Neither changed Markdown path owns a listed gap, so that unchanged repository backlog remains explicit rather than being misreported as a pass.

This closes only the local operator persona-lifecycle partition. Its queue is per BFF process and the whole-snapshot backend has no distributed compare-and- swap across replicas. The immutable lifecycle audit is primary, but a crash between its commit and the admin search/explorer append can leave that secondary projection missing; no cross-store atomicity is claimed. Persona ids and operator signoff actor ids are governance identifiers without a proven mapping to a customer-auth subject, so account DSAR/erasure fanout is not inferred. There is no time-based audit purge, external identity-directory authority, provider effect, native flow, or human-signature verification claim. The wider V1-002 operational-store inventory remains open.

Payment-time chargeback-screening authority verification#

Implementation source and published tip: bc7cf14ab3811627b8520265014cf3bcda7d9968. Verification ran on dev-server, Linux 6.8.0-110-generic x86_64, on 2026-07-17 UTC. Toolchain: Node 24.14.1, pnpm 10.25.0, TypeScript 6.0.3, Vitest 4.1.7, ESLint 10.4.0, Chromium through the repository Playwright harness, PostgreSQL 16 with pgvector, and Redis 7. The protected lockfile remained the exact unstaged blob a37431842e330b3a06b030947c25bebdc72bc2b1.

The prior store inserted a screening into its live map and invoked a synchronous snapshot callback whose production binding discarded sink.save's promise. The Telegram invoice route could therefore return while the admin console showed an uncommitted prediction; a failed write could not roll memory back, concurrent whole-snapshot saves could complete out of order, boot trusted an unversioned unchecked document, and production did not require the partition before traffic. The record also retained the raw user id inside both userId and the deterministic Telegram transaction id without billing-receipt export, account-erasure redaction, a recreation fence, or retention execution.

The hardened store validates a detached complete candidate, awaits one ordered snapshot save, and publishes only after acknowledgement. Failed writes raise stable chargeback_screening_persistence_failed, expose no new screen, and leave the per-process queue usable. The invoice screening remains deliberately additive: its route awaits and logs the failed secondary risk record but still returns the invoice response. Production requires the sink before traffic and hydrates or creates it before route registration can serve work. The pure synchronous helper remains available only to explicitly unbound module tests.

Schema v1 is strict, canonical, and bounded: at most 100,000 screens, 100,000 redacted-subject anchors, and 64 MiB serialized. Transaction, subject, tenant, currency, payment-method, device-fingerprint, and country text is bounded and unsafe controls are rejected; amounts and timestamps must be finite/safe; probability/confidence remain in [0,1]; and risk bands are closed to the real scorer's four values. Recovery rejects unknown fields, duplicates, noncanonical ordering, mismatched subject/transaction redaction, direct identity behind a fence, rows behind a completed purge, unsupported versions, and malformed anchors. A valid legacy { screens } document is sorted, minimized, and rewritten once. Reads, results, and snapshots are detached.

The canonical billing_receipt export now returns exact-subject raw screenings under chargeback_screening. Profile erasure runs the store as a required partition: it SHA-256 pseudonymizes both the user id and the full transaction id, preserves the risk/amount/tenant/payment evidence, and commits a durable subject fence that rejects stale recreation. Its redaction anchor participates in the shared billing_history compliance executor. The canonical 2,555-day window starts at redaction; active or pending-release legal holds and active category exceptions block physical removal; an unblocked due run deletes the pseudonymous screening rows and durably records the purge timestamp while retaining the fence.

text
# scorer behavior; strict restore/migration; awaited save, failure rollback,
# queue recovery/order; DSAR; redaction/purge/fence; both race orders
pnpm --dir apps/oshun/bff exec vitest run \
  src/isis/chargeback-screening-store.test.ts \
  src/__tests__/telegram-route.test.ts \
  src/__tests__/admin-isis-chargeback-prevention-route.test.ts \
  src/data-export/bundle-builder.test.ts
  4 files passed; 70/70 tests passed

# connected deletion composition, hold/exception executor, and route registry
pnpm --dir apps/oshun/bff exec vitest run \
  src/privacy/compliance-retention-executor.spec.ts \
  src/data-deletion/profile-state-eraser.test.ts \
  src/__tests__/contract/openapi-runtime-drift.test.ts
  3 files passed; 16/16 tests passed

# fresh connections recover acknowledged screening, redaction, physical purge,
# and the post-purge recreation fence from real PostgreSQL
OSHUN_ADMIN_DATABASE_URL=<local-postgres> pnpm --dir apps/oshun/bff exec \
  vitest run -c vitest.integration.config.ts \
  src/isis/chargeback-screening-durability.integration.spec.ts
  1 file passed; 1/1 test passed

node tools/typecheck/ratchet.mjs --app apps/oshun/bff \
  --tsconfig tsconfig.typecheck.json
  no new app-own type errors; backlog: 0 known
pnpm exec eslint <four changed non-test sources> --max-warnings=0
pnpm exec prettier --check <eight changed source/test paths>
git diff --check
  passed
node apps/oshun/bff/scripts/build.mjs
  server.js 33.2 MiB; source map 77.7 MiB
OSHUN_ADMIN_DATABASE_URL=<fresh-postgres> OSHUN_REDIS_URL=<local-redis> \
  node apps/oshun/bff/scripts/verify-production-artifact.mjs
  Production artifact smoke check passed

# exact bundle on :4112, fresh database, all 15 migrations, external-server lane
E2E_BASE_URL=http://127.0.0.1:4112 \
E2E_BFF_URL=http://127.0.0.1:4112 pnpm --dir apps/oshun/web exec \
  playwright test e2e/bff-tightenings.spec.ts \
  --config playwright.fast.config.ts --project=chromium --workers=1 \
  --grep "invoice screens for chargeback"
  2/2 Playwright tests passed

The 14 store tests prove real scorer output, duplicate idempotency, strict input rejection, detached reads, acknowledgement-before-publication, failed-write rollback and retry, whole-snapshot ordering, required-sink behavior, exact-subject export, failed-redaction rollback, screen/erasure races in both orders, legal-hold blocking, eventual purge, strict recovery, first-boot creation, restart idempotency, one-time legacy migration, and malformed-state rejection. Fifteen Telegram tests include the new failed-screening-save case: the invoice response remains available, while no volatile screening is published. Five admin route and 36 bundle tests complete the 70-test focused set. The separate 16-test pass retains profile-deletion composition, legal-hold/exception executor, and checked-in OpenAPI/runtime registration coverage.

The real PostgreSQL test used a unique store key and fresh connections at both the redacted and purged stages. It asserted removal of the raw transaction id, loss of exact-subject export access, post-redaction and post-purge recreation refusal, exact stored-document equality, and cleanup. The deploy-shaped run created a separate database, applied all 15 migrations, passed the production artifact smoke check, and ran the two real-HTTP Playwright journey/auth cases against the exact 33.2 MiB bundle. A first Playwright invocation reached no tests because the default fast-config bootstrap attempted an unrelated Yemaya study service whose optional @aws-sdk/client-s3 package is absent in this checkout. Setting E2E_BASE_URL selected the documented external-server lane; the unchanged focused suite then passed 2/2 without installing or changing dependencies.

Before the final process restart, real HTTP reported the deterministic transaction telegram:chargeback-final-tenant:chargeback-final-user:final-sku:1234:USD, subject chargeback-final-user, amount 12.34, risk low, screening timestamp 1784552484, and aggregate count 2. A second exact-bundle process against the same database recovered that exact tuple. Port 4112 was stopped, both temporary databases used while tightening the final source were dropped, and the final database existence check returned zero. Host gates reported 15 GiB RAM, 31 GiB swap, 18 GiB disk, about 10 GiB available memory, and no competing broad build; targeted tests, bundle, PostgreSQL, and one-worker Playwright ran sequentially. No broad Nx sweep or Next production build ran.

The frontend skill governed this slice because the changed trigger feeds an operator-facing console. The existing restrained console composition and wire shape were preserved; its real-HTTP Playwright journey and auth boundary were exercised rather than adding unrelated visual treatment. No customer-facing visual layout, mobile-native flow, or styling changed; the customer-visible change is an additional exact-subject record in the existing billing-receipt export shape.

This evidence update passed Prettier, git diff --check, the root Unreal closure contract, all 21/21 versioned-evidence metadata tests, and the V5 document validator. Docs Center verification reproduced the same 80 generator-owned structural gaps as the preceding V1-002 slices: missing product space-map/engine references, the legacy domains redirect, and generated contract, OpenAPI, and reference pages. Neither changed Markdown path owns a listed gap, so that unchanged repository backlog remains explicit rather than being misreported as a pass.

This closes only the local chargeback-screening snapshot partition. Its queue is per BFF process, the backend stores one whole global snapshot, and there is no distributed compare-and-swap or sharding guarantee. The Telegram invoice endpoint supplies the screening userId from its request body rather than a proven customer-auth identity, so the exact-id DSAR/redaction path is not a claim of end-to-end identity resolution. Screenings describe proposed invoice risk, not provider settlement, dispute, loss, recovery, or human review; the invoice intentionally still returns when screening persistence fails. No other payment rail automatically feeds this store, and no external fraud provider, provider-side deletion, native flow, Unreal asset, or model/media pipeline is claimed. Active raw records are not independently age-purged before account redaction; the connected 2,555-day compliance clock begins at the durable redaction anchor. The wider V1-002 operational-store inventory remains open.

Crypto-invoice issuance, settlement, receipt, privacy, and retention verification#

Implementation source and published tip: b8f31c4d344131bf7c155175ba62fc1051cba853. Verification ran on dev-server, Linux 6.8.0-110-generic x86_64, on 2026-07-17 UTC. Toolchain: Node 24.14.1, pnpm 10.25.0, TypeScript 6.0.3, Vitest 4.1.7, ESLint 10.4.0, Chromium through the repository Playwright harness, PostgreSQL 16 with pgvector, and Redis 7. The protected lockfile remained the exact unstaged blob a37431842e330b3a06b030947c25bebdc72bc2b1.

The prior crypto ledger mutated its process-global map before invoking a synchronous snapshot callback whose production binding discarded snapshotSink.save's promise. Quote issuance could therefore return a payment target that was not committed; failed and out-of-order whole-snapshot writes could leave volatile or stale authority; production did not require the sink; and boot accepted an unversioned, unchecked { invoices } document. Settlement then persisted confirmation, signed receipt, support disposition, and customer entitlement in separate best-effort steps. Its process-local replay guard was lost on restart, any already-confirmed invoice was acknowledged without checking the transaction/block/time tuple, and a failed receipt/support write could leave a partially represented payment. A generic 90-day/count eviction also deleted confirmed financial evidence without a legal-hold or account-retention boundary.

The new CryptoInvoiceStore validates a detached complete candidate, awaits one ordered snapshot save, and publishes only after acknowledgement. Quote issuance now awaits that API and returns stable 503 crypto_invoice_persistence_failed without exposing an invoice when the save fails. Settlement facts, the Ed25519 receipt, and the support disposition commit in the same candidate. A failed save exposes none of them and leaves the per-process queue usable. Production marks the singleton required before optional database composition, then hydrates or creates it before compliance retention or traffic. Synchronous mutation helpers remain only for explicitly unbound engine tests and throw after a sink is bound or durability is required.

Schema v1 is strict, canonical, and bounded to 100,000 invoices, 100,000 redaction anchors, and 64 MiB serialized. Recovery rejects unknown fields, future versions, duplicate or noncanonical ids, unsafe control-bearing text, invalid assets/currencies/amounts/timestamps, malformed receiving targets and signatures, mismatched web DTO summaries, inconsistent plan-book fields, partial confirmation tuples, receipt/ledger disagreement, broken tax/locale facts, privacy contradictions, rows behind a completed purge, and direct identity behind a redaction fence. Reads, mutation results, and snapshots are detached. A valid legacy { invoices } document is minimized, sorted, filled with honest nullable legacy facts, and rewritten once; a current complete document is not rewritten on boot.

Expiry is now a pure read projection, so a list request cannot silently mutate settlement authority or make late-payment behavior depend on read order. Only unconfirmed intents more than 90 days beyond expiry/cancellation are pruned on issuance. Confirmed rows are never sacrificed for the capacity bound; capacity fails loud instead. Account erasure pseudonymizes the exact authenticated purchaser, removes optional Telegram/mobile deep links, preserves payment address/transaction/receipt evidence, and writes a durable no-resurrection fence. Exact-subject DSAR now includes raw active rows under crypto_invoice_ledger. Redacted rows join the canonical 2,555-day billing_history partition: active or pending-release legal holds and active category exceptions block physical removal, due unblocked rows purge once, and the retained fence prevents stale recreation without re-counting a completed purge on every executor run.

Durable replay authority now lives in the invoice row. An exact transaction/block/confirmation tuple is idempotent across restart; any changed tuple returns 409 settlement_conflict. When replay omits confirmation time, the route reuses the stored time rather than manufacturing a conflict. Unsafe, negative, or malformed settlement numerics fail as 400 before signing or mutation. Customer-auth entitlement remains a second store, so the ledger records a durable entitlementGrantedAtUnixSeconds completion marker only after that idempotent plan update acknowledges. If the customer-auth write or marker save fails, the watcher receives 503 and exact replay performs the reconciliation again. Deleted/redacted purchasers never receive a pseudonymous grant; the invoice is durably flagged for support instead. Quote recreation behind the billing fence returns 410 crypto_invoice_subject_redacted.

text
# strict recovery/migration; acknowledgement, rollback, queue ordering;
# atomic settlement/receipt/support; exact replay/conflict; expiry/capacity;
# DSAR, redaction, hold-aware purge, one-shot executor, and recreation fence
pnpm --dir apps/oshun/bff exec vitest run \
  src/payments/invoice-store.test.ts \
  src/payments/quote-builder.test.ts \
  src/payments/settlement-route.test.ts \
  src/data-export/bundle-builder.test.ts
  4 files passed; 83/83 tests passed

# real route composition: durable issuance failure, exact purchaser scope,
# redacted-subject refusal, canonical plan prices, and paywall DTO recovery
pnpm --dir apps/oshun/bff exec vitest run \
  src/__tests__/payments-crypto-route.test.ts
  1 file passed; 11/11 tests passed

# shared retention/deletion composition, exact billing export, route registry
pnpm --dir apps/oshun/bff exec vitest run \
  src/privacy/compliance-retention-executor.spec.ts \
  src/data-deletion/profile-state-eraser.test.ts \
  src/data-export/bundle-builder.test.ts \
  src/__tests__/contract/openapi-runtime-drift.test.ts
  4 files passed; 53/53 tests passed

# fresh connections recover confirmation, receipt, entitlement marker,
# pseudonymization, due purge, retained fence, and exact stored document
OSHUN_ADMIN_DATABASE_URL=<local-postgres> pnpm --dir apps/oshun/bff exec \
  vitest run -c vitest.integration.config.ts \
  src/payments/invoice-store-durability.integration.spec.ts
  1 file passed; 1/1 test passed

node tools/typecheck/ratchet.mjs --app apps/oshun/bff \
  --tsconfig tsconfig.typecheck.json
  no new app-own type errors; backlog: 0 known
pnpm exec eslint <changed BFF source/test paths> \
  --max-warnings=0 --no-warn-ignored
pnpm exec prettier --check <12 changed source/test paths>
git diff --check
  passed
node apps/oshun/bff/scripts/build.mjs
  server.js 33.2 MiB; source map 77.7 MiB

# isolated database, all 15 migrations, exact production bundle
OSHUN_ADMIN_DATABASE_URL=<fresh-postgres> OSHUN_REDIS_URL=<local-redis> \
  node apps/oshun/bff/scripts/verify-production-artifact.mjs
  Production artifact smoke check passed
  finished migrations: 15; durable snapshot rows after startup: 15

# exact built BFF on :4113, web on allow-listed :3011, one Chromium worker
E2E_BASE_URL=http://127.0.0.1:3011 \
E2E_BFF_URL=http://127.0.0.1:4113 pnpm --dir apps/oshun/web exec \
  playwright test e2e/billing-crypto-paywall.spec.ts \
  --config playwright.fast.config.ts --project=chromium --workers=1
  11/11 Playwright tests passed

The 26 store tests cover strict schema and legacy migration, detachment, first-boot creation, restart equality, required-sink behavior, failed-write rollback/retry, concurrent ordering, atomic settlement evidence, exact replay conflicts, pure expiry, stale-intent pruning without confirmed-record loss, DSAR, exact-subject pseudonymization, hold blocking, one-time purge, and both redaction/purge recreation fences. Fourteen settlement tests cover exact-byte timestamped HMAC verification, signer fail-closed behavior, safe inclusion facts, price-bound grant/withhold outcomes, verifiable/tamper-detecting receipts, durable replay, conflicting replay, settlement-save rollback, entitlement-marker reconciliation, and deleted-purchaser support routing. Six quote and 37 bundle tests complete the 83-test focused set. The separate 11-route pass includes durable-save 503 with no volatile invoice and billing-fence 410 with no recreated row.

The PostgreSQL integration used a unique store key and fresh store connections at issued, settled/redacted, and purged stages. It recovered the exact transaction, block, receipt signature, entitlement marker, pseudonym, purge, and post-purge fence, then removed the test row. The final production smoke used a separate fresh database, applied all 15 checked-in migrations, started and stopped the exact 33.2 MiB bundle cleanly, and observed 15 durable snapshot rows. That temporary database was dropped and its final existence count was zero.

The browser run exercised issuance, customer-scoped paywall/list behavior, settlement and entitlement, exact replay after response loss, conflicting replay, persistence-failure rollback, recovery, DOM behavior, and accessibility. Its isolated database intentionally bootstrapped only the two snapshot tables needed by the exact bundle; the separate production smoke above is the full 15-migration proof. Before restart PostgreSQL held invoice inv-d89d5ce2-894d-4db9-abd1-ace2221d1099, purchaser customer-billing-crypto-settlement-1784555930304-2-0, transaction tx-e2e-inv-d89d5ce2-894d-4db9-abd1-ace2221d1099, matching receipt transaction, block height 1234567, and confirmation time 1784555932. A second exact- bundle process returned that confirmed invoice, the same transaction/block facts, and audit key e2e-audit-key through real HTTP. Ports 4113 and 3011 were stopped and the browser database was dropped. The browser pass preceded the final audit's retention-candidate, unsafe-number, and redacted-quote guards; those non-happy-path additions were then covered on current source by the focused route/store/PostgreSQL tests, zero-backlog type ratchet, final build, and fresh-schema production smoke.

The frontend skill governed the browser verification because this slice affects the customer billing/paywall path. The existing image-led, restrained billing composition and interaction hierarchy were preserved; no customer/admin visual layout, style, or mobile-native screen changed. The E2E settlement helper was updated to the production timestamped raw-body HMAC contract and to server- priced canonical plan quotes rather than stale client-supplied amounts.

This evidence update passed Prettier, git diff --check, the root Unreal closure contract, all 21/21 versioned-evidence metadata tests, and the V5 document validator. Docs Center verification reproduced the same 80 generator-owned structural gaps as the preceding V1-002 slices: missing product space-map/engine references, the legacy domains redirect, and generated contract, OpenAPI, and reference pages. Neither changed Markdown path owns a listed gap, so that unchanged repository backlog remains explicit rather than being misreported as a pass.

This closes only the local crypto-invoice snapshot partition. The mutation queue is per BFF process, the backend stores one whole global snapshot, and there is no distributed compare-and-swap, sharding, or transaction shared with customer-auth. The durable entitlement marker and idempotent replay repair that cross-store window but can require a transient 503 and watcher retry. The address provisioner and chain watcher remain deploy-bound; the browser suite uses a guarded deterministic provisioner and signed watcher seam rather than a live provider/chain. Restore validates the receipt structure and ledger coherence but cannot cryptographically reverify historical signatures without a historical audit-key registry. Anonymous invoices have no customer subject; the full by-id paywall route remains an invoice-id capability surface. Payment addresses, transaction ids, and receipts remain pseudonymous financial evidence after profile redaction and are removed only after the hold-aware seven-year window; active-account confirmed rows are not independently age-purged. Stored pending invoices may still settle after their projected expiry, so a future provider policy must define late-payment disposition without making it depend on a list read. No provider-side remote deletion, refund/dispute authority, rate-oracle proof, live-chain inclusion proof, native flow, Unreal asset, or model/media pipeline is claimed. The wider V1-002 operational-store inventory remains open.

Model-governance license and admission authority verification#

The model-governance durability source chain is 250f2fcc66a629eb1210d8aea3baeeb5c84d3d1c, followed by the published PostgreSQL JSONB structural-equality correction 3f30e0aa302ab2a720b55516c47db80c385d497b. Verification was completed on 2026-07-17 UTC with Node 22, the repository-pinned pnpm toolchain, real local PostgreSQL, the exact production BFF bundle, and Chromium. The protected user-owned pnpm-lock.yaml remained outside this slice at worktree blob a37431842e330b3a06b030947c25bebdc72bc2b1.

The prior store was not an authority. Its snapshot contained only uploaded license declarations, its save promise was discarded, admissions lived only in a process map, and upload plus initial admission were two independently visible mutations. Restore accepted unchecked legacy shapes and could silently skip bad state. A restart therefore lost the operator, commercial/IP subverdicts, reasons, evaluated rights, evidence matches, and final decision even when the upload survived.

The replacement is a versioned schema-v1 candidate/save/publish authority. Every durable mutation is serialized; the acknowledged candidate is published only after its sink succeeds; a failed save exposes neither a model nor a decision; and the queue remains usable for retry. Upload plus the initial decision is one atomic snapshot mutation. Production now requires the durable sink and hydrates the authority before route composition. The admin routes await acknowledgement, capture the authenticated operator, and map invalid input to stable 400 and persistence or capacity failure to stable 503.

The schema bounds recovery at 10,000 uploaded models, 100,000 decisions, and 64 MiB; rejects unknown, future, malformed, noncanonical, cross-incoherent, or privacy-inconsistent state; and performs one canonical migration from the validated legacy { uploadedInputs } document. Uploads and records are canonicalized, reads and returned results are detached, and exact duplicates do not rewrite the snapshot. Structural equality, rather than serialization order, decides whether a PostgreSQL JSONB document is current, so JSONB key reordering cannot increment the snapshot version on every process boot.

The durable decision contains the authenticated operator, final verdict, separate commercial and intellectual-property verdicts and reasons, evaluated rights, and only the minimized registry evidence that actually matched. Raw prompt, negative-prompt, output, and free-form description text never enters the snapshot. Registry/decision coherence, flag/match consistency, and bounded canonical identifiers and strings are enforced during both mutation and restore.

text
# focused source verification
model-governance-store.spec.ts
  19/19 tests passed
admin-model-governance.test.ts
  18/18 tests passed
model-governance-store-durability.integration.spec.ts
  1/1 real PostgreSQL test passed
node tools/typecheck/ratchet.mjs --app apps/oshun/bff \
  --tsconfig tsconfig.typecheck.json
  passed; no new app-own errors; BFF backlog 0
pnpm exec eslint --no-ignore --max-warnings=0 <changed source/test paths>
pnpm exec prettier --check <changed source/test paths>
git diff --check
  passed
node apps/oshun/bff/scripts/build.mjs
  server.js 33.3 MiB; source map 77.8 MiB

# fresh database, all migrations, exact production artifact
OSHUN_ADMIN_DATABASE_URL=<fresh-postgres> OSHUN_REDIS_URL=<local-redis> \
  node apps/oshun/bff/scripts/verify-production-artifact.mjs
  Production artifact smoke check passed
  finished migrations: 15; durable snapshot rows after startup: 16

# first exact production BFF, signed HS256 production auth, Chromium
MODEL_GOVERNANCE_E2E_PHASE=seed \
  playwright test e2e/model-governance-authority-bff.spec.ts \
  --config playwright.fast.config.ts --project=chromium --workers=1
  1 passed, 1 intentionally skipped

# clean stop, second exact production BFF, same PostgreSQL database
MODEL_GOVERNANCE_E2E_PHASE=recover \
  playwright test e2e/model-governance-authority-bff.spec.ts \
  --config playwright.fast.config.ts --project=chromium --workers=1
  1 passed, 1 intentionally skipped

The real PostgreSQL test covers first-boot creation, strict recovery, atomic upload/admit durability, failed-write nonpublication, queue recovery, exact restart equality, and cleanup. The separate production smoke applied all 15 checked-in migrations and started and stopped the exact built artifact with 16 durable snapshot rows. The browser proof then used a fresh database and an actual signed production-auth cookie. First boot created canonical snapshot version 1; one upload and admission advanced it to version 2; after a clean stop and new exact-bundle process, recovery returned the same model and decision and the database remained at version 2. PostgreSQL held one upload, one record, the expected deny/allow/deny final/commercial/IP verdicts, no @example prompt content, all 15 applied migrations, and 16 durable snapshot rows. Both BFF processes stopped and the temporary database was dropped.

The proof also caught two real defects instead of concealing them. The first exact-production request returned 401 because the initial browser helper used a development-only unsigned token; the test was corrected to sign the real HS256 oshun-auth/oshun-bff contract. The first restart then recovered correct values but incremented the snapshot on boot because PostgreSQL JSONB changed object-key order. The published follow-up uses structural equality and adds a reversed-key-order no-rewrite regression test; the final two-process proof kept version 2 unchanged.

The frontend skill governed the browser verification because this slice covers an admin-facing API workflow. No web, admin, PWA, mobile-native layout, style, or interaction changed, so the new Playwright coverage exercises the signed API boundary and restart behavior without inventing a visual or axe claim.

This closes only the local model-governance snapshot partition. Its mutation queue is per process, the backend stores one whole global snapshot, and there is no distributed compare-and-swap, sharding, or transaction shared with model weights, deployment, or a generation pipeline. Operator license declarations are attestations, not independently verified rights. The repository still has no connected admin visual workflow consumer for this authority. Capacity fails closed and requires an explicit migration or archive policy; no automated archive exists. Governance/operator identifiers are not proven customer-auth subjects, so no fabricated customer DSAR is claimed; operator-directory redaction and time-based purge are still absent. A curated registry change may make an older snapshot fail boot pending a deliberate migration. No external rights provider, provider deletion, native, Unreal, or media/model-quality claim is made. The wider V1-002 operational-store inventory remains open.

Iris desktop-to-mobile handoff authority verification#

The Iris handoff authority source and published tip is 93d0a355339e7e42db8a14d5bd97da3ee6b7ab6c. Verification was completed on 2026-07-17 UTC with the repository-pinned toolchain, real local PostgreSQL and Redis, the exact production BFF bundle, signed HS256 production authentication, and Playwright's Chromium project. The protected user-owned pnpm-lock.yaml remained outside the slice at worktree blob a37431842e330b3a06b030947c25bebdc72bc2b1; the permanent preservation stash remained 9c4ddf4f7fd4c205d1f083cdbfb9d4a1ee5ce320.

The former /v1/iris/mobile-handoff mailbox was restart-capable in name only. It published an in-process map mutation before starting a detached snapshot save, returned 200 before that save completed, had no failed-write contract, and accepted an unchecked { entries } document. It also lacked retention, customer export, signed-erasure composition, a resurrection fence, and a restart proof. Native Home's bodyless consume used the shared JSON helper, which declared content-type: application/json without a body; Fastify rejected that request as empty malformed JSON before the consume route ran.

The replacement is a strict schema-v1 candidate/save/publish authority. PUT, retention-touching GET, consume DELETE, retention purge, and exact-subject erasure share one per-process mutation queue. Each operation clones a detached candidate, awaits the durable snapshot save, and publishes or acknowledges only after that save succeeds. A failed save exposes no candidate, returns stable 503, and leaves the queue usable for retry. Production requires and hydrates the sink before traffic. First boot writes the canonical document, and one validated legacy { entries } snapshot migrates to schema v1 exactly once.

Recovery rejects unknown or future fields, duplicate or noncanonical subjects and deletion fences, resurrection behind a fence, invalid timestamp ordering, and malformed exact-contract expiry. State is normalized to detached canonical JSON and rejects cycles, sparse arrays, non-finite values, prototype keys, non-plain objects, and nesting beyond 64 levels. Limits are 256 KiB of UTF-8 per state, 10,000 live entries, 100,000 deletion fences, and 64 MiB per snapshot. Entry and fence ordering uses deterministic code-unit order, while structural equality prevents PostgreSQL JSONB key reordering from causing a boot rewrite.

The BFF still treats direction, embedded identity, tenant, item ids, and routes as client-semantic fields. It recognizes only the exact oshun.memory.iris.mobile_handoff@1.0.0 contract to require and enforce a canonical expiresAt; future versions remain opaque and receive the generic continuity policy. Exact-contract expiry is removed durably before delivery. Every entry also uses the canonical 30-day last-access continuity window through startup purge, daily retention execution, and durable GET touches.

Customer continuity_state export now includes only the exact authenticated subject's pending handoff. The signed continuity-deletion composition removes that exact entry, preserves adjacent ids, and persists a domain-separated SHA-256 subject digest. The fence retains no raw subject id and rejects stale recreation with 410; it is pseudonymous local lifecycle state, not a claim of irreversible anonymization. The fence set is intentionally bounded and has no archive or identity-reuse policy yet.

The shared mobile HTTP client now adds JSON content type only when a body exists. Focused transport and BFF-client tests pin GET plus bodyless DELETE with only accept and authorization headers. Navigation remains deliberately best-effort: Native Home does not await the consume or clear its card first, so a network failure can replay the packet even though the server mutation itself is durable.

text
# strict store authority, authenticated route behavior, and continuity export
pnpm --dir apps/oshun/bff exec vitest run \
  src/routes/iris-mobile-handoff-store.spec.ts \
  src/routes/iris-mobile-handoff.test.ts \
  src/data-export/bundle-builder.test.ts
  3 files passed; 54/54 tests passed (11 store, 5 route, 38 export)

# fresh connections: restart, exact export, erase, adjacent preservation,
# digest-only fence, and stale-recreation refusal
OSHUN_ADMIN_DATABASE_URL=<local-postgres> pnpm --dir apps/oshun/bff exec \
  vitest run -c vitest.integration.config.ts \
  src/routes/iris-mobile-handoff-durability.integration.spec.ts
  1 file passed; 1/1 test passed

# body-aware mobile transport plus receive/consume contract and presentation
pnpm --dir apps/oshun/mobile test -- --runInBand \
  src/network/http-client.test.ts \
  src/network/oshun-bff-client.test.ts \
  src/navigation/mobileIrisHandoff.test.ts \
  src/navigation/mobileIrisHandoff.contract.test.ts \
  src/components/MobileIrisHandoffCard.test.tsx
  5 suites passed; 26/26 tests passed

node tools/typecheck/ratchet.mjs --app apps/oshun/bff \
  --tsconfig tsconfig.typecheck.json
  passed; no new app-own errors; backlog: 0 known
pnpm --dir apps/oshun/mobile exec tsc --noEmit --pretty false
pnpm exec eslint --no-ignore --max-warnings=0 <changed typed source/E2E paths>
pnpm exec prettier --check <changed TypeScript/Markdown paths>
ruff check tools/docs_center/tests/test_generator.py
python3 -m pytest \
  tools/docs_center/tests/test_generator.py::test_seventeenth_result_audit_batch_separates_capture_delivery_and_return -q
git diff --check
  passed; targeted Docs Center test: 1/1

pnpm --dir apps/oshun/bff build
  server.js 34,906,993 bytes (33.3 MiB)
  source map 81,634,337 bytes (77.9 MiB)
  server SHA-256 a965aed83e6cc32ce1b79ea7472ce55570621d9bf3d66d0ade32a8d38a222be3

# isolated database, all checked-in migrations, exact production bundle
OSHUN_ADMIN_DATABASE_URL=<fresh-postgres> OSHUN_REDIS_URL=<isolated-redis-db> \
  pnpm --dir apps/oshun/bff verify:production-artifact
  Production artifact smoke check passed
  finished migrations: 15; durable snapshot rows: 17; Iris schema version: 1

# process 1: signed-auth seed and isolation
IRIS_MOBILE_HANDOFF_E2E_PHASE=seed \
  playwright test e2e/iris-mobile-handoff-authority-bff.spec.ts \
  --config playwright.fast.config.ts --project=chromium --workers=1
  1 passed; 2 phase-skipped; durable row version 4; 2 entries

# clean stop, process 2: unchanged boot, recover, and durable consume
IRIS_MOBILE_HANDOFF_E2E_PHASE=recover <same command>
  boot remained version 4; 1 passed; 2 phase-skipped
  durable row version 7; target absent; adjacent entry retained

# clean stop, process 3: unchanged boot and consumed absence
IRIS_MOBILE_HANDOFF_E2E_PHASE=consumed <same command>
  boot remained version 7; 1 passed; 2 phase-skipped
  durable row version 8 after adjacent GET touch; target absent; adjacent retained

All three production BFF processes exited with code 0. The final proof database contained all 15 finished migrations and 17 snapshot rows before cleanup. The temporary database was dropped, its final existence count was zero, and the previously empty Redis logical database was flushed back to zero keys.

The earlier production proof caught the bodyless-DELETE problem twice. Its first Playwright helper incorrectly added JSON content type and received the same Fastify 400; removing that header made the API proof pass and revealed that the real shared mobile helper had the identical defect. The published transport fix and two regression tests close that real client path. During the final clean rerun, an initial Playwright invocation omitted E2E_BASE_URL and therefore tried to start an unrelated web bootstrap that lacked @aws-sdk/client-s3; no handoff spec or request ran. Pointing the config at the already-running production process disabled that unrelated bootstrap, after which all three current-artifact phases passed as recorded above.

The frontend skill governed the mobile/web verification because the slice changes a customer-facing network flow. No visual hierarchy, layout, style, copy, or native component changed, so the existing UI was preserved and the new Playwright coverage targets the authenticated API/restart boundary. The walkthrough result and journey now distinguish local browser capture, durable server acknowledgement, native receipt, consume, and the still-missing return lane instead of treating them as one success state.

This closes only the local latest-packet handoff snapshot partition. The queue is per BFF process, the backend rewrites one global snapshot, and there is no distributed compare-and-swap, sharding, or multi-region ordering. The web still fires PUT without awaiting or displaying durable acknowledgement. The mailbox has no device id, target selection, push wake-up, or receipt; /v1/devices remains a separate inventory. Native Home consume is unawaited and therefore is not exactly-once delivery. mobile_to_web is still not persisted or fetched, and concurrent tab/note edits have no revision or merge contract. Embedded packet identity is not reconciled with the authenticated subject. Fence archive and identity-reuse policy, a joined desktop-to-native-to-desktop automation, and distributed concurrency remain open. This closes the Iris handoff partition within those boundaries, not V1-002 or the wider operational-store inventory.

Studio authoring-record authority verification#

The authenticated Studio authoring-record authority source and published tip is 6d1b0d3983a81b64cad39eaf8744a92426ddbc95. Verification was completed on 2026-07-20 UTC with the repository-pinned toolchain, real local PostgreSQL and Redis, the exact rebased production BFF bundle, signed HS256 production authentication, signed Ed25519 deletion attestations, and Playwright's Chromium project. The protected user-owned pnpm-lock.yaml remained outside the slice at worktree blob a37431842e330b3a06b030947c25bebdc72bc2b1; the permanent preservation stash remained 9c4ddf4f7fd4c205d1f083cdbfb9d4a1ee5ce320.

Four production-authenticated Studio APIs—world configuration, story-graph authoring, quest authoring, and timeline modeling—stored their accepted drafts only in process-local maps. A successful POST therefore did not mean a durable write, a restart discarded the records, and DELETE had the same volatile semantics. None of the four partitions participated in customer export, signed account erasure, retention execution, or a resurrection barrier. The repository has no first-party web consumer for these routes, but their authenticated public write/read/delete contract made them operational state rather than harmless fixture caches.

The replacement shares one generic schema-v1 owned-record authority while retaining the four existing validators and route contracts. Every POST, DELETE, retention-touching GET, exact-subject erasure, and retention purge enters a per-store candidate/save/publish queue. A candidate remains invisible until its complete snapshot commits. Failed persistence publishes no write or access clock, leaves the prior durable winner visible, keeps the queue usable, and returns a controlled 503; post-erasure writes return 409, and capacity failure returns 507. Production requires all four sinks and hydrates them before traffic. First boot materializes one canonical empty document per partition in the existing admin_store_snapshot table, so no schema migration was needed.

Recovery requires exact schema, entry, record, and fence fields; canonical timestamps and subject ids; deterministic owner/record and digest ordering; unique composite identities; validator-exact record shapes; matching embedded record ids; and no entry behind an erasure fence. It rejects unsupported versions, unknown fields, malformed or noncanonical timestamps and digests, duplicates, resurrection, records beyond 10,000, fences beyond 100,000, and a snapshot beyond 64 MiB without corrupting the currently published view. Server creation/access timestamps are detached from caller-authored domain timestamps, and access time remains monotonic if the wall clock moves backward.

Exact-owner continuity_state export now emits a single studio_authoring_records item containing only populated partitions, complete record bodies, stable record ids, and server creation/access timestamps. The signed continuity eraser independently persists a domain-separated SHA-256 subject digest in all four snapshots, physically removes only the exact owner's records, preserves adjacent ids, and rejects stale recreation across restart. The digest contains no raw subject id. A partial store failure fails the aggregate receipt and remains safely retryable; the four snapshot writes are not claimed as one database transaction.

The authority derives the canonical 30-day inactivity window and daily purge cadence from OSHUN_RETENTION_RULES.continuity_state. Authenticated GET durably refreshes last access before returning an active record. Startup runs an awaited purge before traffic, and a supervised unreferenced interval continues the same purge. The boundary is strict: a record remains at exactly 30 days and expires one millisecond later. Retention expiry does not install an account-erasure fence, so a genuinely new draft can be created afterward.

text
# four existing route suites plus authority, failure, privacy, and connected
# continuity lifecycle regressions
pnpm --dir apps/oshun/bff exec vitest run \
  src/__tests__/studio-world-configuration-records-route.test.ts \
  src/__tests__/studio-story-graph-authoring-records-route.test.ts \
  src/__tests__/studio-quest-authoring-records-route.test.ts \
  src/__tests__/studio-timeline-modeling-records-route.test.ts \
  src/studio/studio-authoring-records-authority.spec.ts \
  src/routes/studio-authoring-records-durability.spec.ts \
  src/studio/studio-authoring-records-lifecycle.spec.ts \
  src/data-export/bundle-builder.test.ts \
  src/data-deletion/continuity-state-eraser.test.ts \
  src/routes/data-deletion-continuity.test.ts
  10 files passed; 91/91 tests passed
  existing four route suites: 39/39; authority/failure/lifecycle: 7/7
  bundle/fanout composition: 45/45

# fresh connections: four first-boot rows, restart, exact-owner export,
# exact deletion, adjacent preservation, and four recovered fences
OSHUN_ADMIN_DATABASE_URL=<local-postgres> pnpm --dir apps/oshun/bff exec \
  vitest run -c vitest.integration.config.ts \
  src/studio/studio-authoring-records-authority.integration.spec.ts
  1 file passed; 1/1 test passed

node tools/typecheck/ratchet.mjs --app apps/oshun/bff \
  --tsconfig tsconfig.typecheck.json
  passed; no new app-own errors; backlog: 0 known
pnpm exec eslint --no-ignore --max-warnings=0 <changed typed source/E2E paths>
pnpm exec prettier --check <changed TypeScript/Markdown paths>
node tools/conventions/check-conventions-ratchet.mjs --staged
git diff --check
  passed

pnpm --dir apps/oshun/bff build
  server.js 34,934,597 bytes (33.3 MiB)
  source map 81,685,071 bytes (77.9 MiB)
  server SHA-256 66bc26b60c803d6a970a642b7e3400d995ed4dc95bb6ead71b92d23cab8db512

# exact rebased artifact against an isolated database/Redis namespace
OSHUN_ADMIN_DATABASE_URL=<fresh-postgres> OSHUN_REDIS_URL=<isolated-redis-db> \
  pnpm --dir apps/oshun/bff verify:production-artifact
  Production artifact smoke check passed; all 15 migrations applied

# process 1: signed production auth, four writes, adjacent owner, isolation,
# real downloadable continuity bundle, and cross-owner download denial
STUDIO_AUTHORING_E2E_PHASE=seed \
  playwright test e2e/studio-authoring-records-authority-bff.spec.ts \
  --config playwright.fast.config.ts --project=chromium --workers=1
  1 passed; 2 phase-skipped
  quest/story/timeline version 3: 1 entry, 0 fences each
  world version 4: 2 entries, 0 fences

# clean stop, process 2: unchanged recovery and immediate signed erasure
STUDIO_AUTHORING_E2E_PHASE=erase <same command>
  1 passed; 2 phase-skipped
  completed continuity attestation; rowsRemoved >= 4; 128-hex signature
  quest/story/timeline version 5: 0 entries, 1 fence each
  world version 7: 1 adjacent entry, 1 fence

# clean stop, process 3: recovered erasure and stale-write rejection
STUDIO_AUTHORING_E2E_PHASE=erased <same command>
  1 passed; 2 phase-skipped
  quest/story/timeline remained version 5: 0 entries, 1 fence each
  world version 8 after adjacent GET touch: 1 adjacent entry, 1 fence

The seed phase created and downloaded a real JSON DSAR rather than relying only on an in-process collector. Its exact bytes contained all four target-owned partitions and their private marker, excluded the adjacent draft, and returned 403 when the adjacent owner requested the target bundle. The erasure phase used the public immediate deletion route and the live signed Redis fanout; it required terminal completed state, an erased continuity attestation, at least four removed rows, and a valid-length Ed25519 signature before accepting the result. All four stale writes returned the exact post-erasure 409 body.

All three production BFF processes exited with code 0. The final proof database contained all 15 finished migrations and 43 durable snapshot rows before cleanup. The temporary database was dropped, its final existence count was zero, Redis logical database 14 was flushed back to zero keys, and the proof port was closed. The first proof was also clean, but it preceded an unrelated remote-main integration; the complete build, smoke, and three-process proof above was rerun against the rebased source tip so the recorded artifact hash and runtime evidence refer to the published tree.

The frontend skill governed the browser/API verification because these are customer-facing Studio routes. No rendered web, admin, PWA, mobile-native layout, style, copy, or interaction changed, so the existing UI was preserved and the new Playwright coverage targets authentication, exact-owner isolation, downloadable DSAR bytes, signed erasure, restart recovery, and resurrection prevention without inventing a visual or accessibility claim.

This closes only the four local Studio authoring-record snapshot partitions. Each mutation queue is per BFF process, each store rewrites one global snapshot, and there is no distributed compare-and-swap, sharding, multi-region ordering, or transaction across the four stores. The APIs still have no demonstrated first-party Studio web producer, so no connected UI authoring flow is claimed. Deletion fences are bounded but have no archive or subject-id reuse policy. Capacity requires an explicit migration/archive decision rather than silently discarding active drafts. No external provider, native, Unreal, model/media, performance, or production-customer request is claimed. This closes these four partitions within those boundaries, not V1-002 or the wider operational-store inventory.

Mentor Presence rendered-performance authority verification#

The authenticated Mentor Presence rendered-performance authority source and published tip is 1b7533f36846528641f8a1da36c6b9eb26d1a5e7. Verification was completed on 2026-07-20 UTC with the repository-pinned toolchain, real local PostgreSQL and Redis, and the exact rebased production BFF bundle. The protected user-owned pnpm-lock.yaml remained outside the slice at worktree blob a37431842e330b3a06b030947c25bebdc72bc2b1; the permanent preservation stash remained 9c4ddf4f7fd4c205d1f083cdbfb9d4a1ee5ce320.

The authenticated premium render route previously inserted completed Mentor Presence APNGs into a process-local Map and returned 201 without any durable commit. Restart discarded every accepted render. Media lookup used only the deterministic performance id after authentication, so another authenticated account that learned that id could read the bytes, and the response marked the private artifact publicly cacheable. The partition did not participate in DSAR, signed erasure, retention, or resurrection prevention.

The replacement is a strict schema-v1 authority over the existing admin_store_snapshot sink. Every save, exact-subject erase, and retention purge enters a per-store ordered candidate/save/publish queue. A candidate remains invisible until the complete snapshot commits, and the render route awaits that commit before returning 201. Production requires and hydrates the sink before traffic. Persistence unavailability returns controlled 503, an erased subject returns 409, and media or store capacity returns 507; a failed save never publishes its candidate. No schema migration was needed.

Recovery requires exact document, record, media, and fence fields; schema version 1; canonical ids, timestamps, ordering, and base64; unique owner/id composites; a matching SHA-256; and a PNG-signature-bearing decoded payload. It rejects unknown or future state, malformed encodings, digest mismatch, duplicates, resurrection, media beyond 64 MiB, more than 1,000 records, more than 25 records per owner, more than 100,000 fences, or a snapshot beyond 128 MiB. The owner is part of the storage key, so two users may independently own the same deterministic render id. Reads require that exact owner, return 404 for an adjacent account, refuse expired records even when a hold defers physical deletion, and set Cache-Control: private, max-age=31536000, immutable.

The default DSAR collector now emits exact-owner generated_artifact records with canonical metadata and the exact APNG bytes as base64; an adjacent owner's artifact is absent. Signed generated-artifact deletion fans out to this store, physically removes only the subject's records, preserves adjacent owners, and persists a domain-separated one-way SHA-256 subject fence. Save and erase share the same queue, so neither ordering can resurrect deleted state; the fence also survives restart and rejects a stale retry. The canonical OSHUN_RETENTION_RULES.generated_artifact policy is 365 days from creation with a seven-day purge cadence. An awaited startup pass and supervised periodic pass perform physical purge, while active legal holds and active or expiring category exceptions defer it.

text
# route, live-socket, store, export, erasure-fanout, and retention regressions
pnpm --dir apps/oshun/bff exec vitest run \
  src/mentor-presence/performance-store.spec.ts \
  src/__tests__/mentor-presence-route.test.ts \
  src/__tests__/mentor-presence-live-socket.test.ts \
  src/data-export/bundle-builder.test.ts \
  src/privacy/compliance-retention-executor.spec.ts \
  src/generation/generated-artifact-erasure.test.ts --maxWorkers=1
  6 files passed; 76/76 tests passed

# exact bytes, restart, legal-hold deferral, erase, adjacent preservation,
# recovered fence, and stale-retry rejection against real PostgreSQL
OSHUN_ADMIN_DATABASE_URL=<local-postgres> pnpm --dir apps/oshun/bff exec \
  vitest run --config vitest.integration.config.ts \
  src/mentor-presence/performance-store-durability.integration.spec.ts \
  --maxWorkers=1
  1 file passed; 1/1 test passed

node tools/typecheck/ratchet.mjs --app apps/oshun/bff \
  --tsconfig tsconfig.typecheck.json
  passed; no new app-own errors; backlog: 0 known
pnpm exec eslint --no-warn-ignored --max-warnings=0 <changed TypeScript paths>
pnpm exec prettier --check <changed TypeScript/Markdown paths>
node tools/conventions/check-conventions-ratchet.mjs --staged
git diff --check
  passed

pnpm --dir apps/oshun/bff build
  server.js 34,960,210 bytes (33.3 MiB)
  source map 81,732,431 bytes (77.9 MiB)
  server SHA-256 6a28093c8b731dda242167904b0e32297fee19262d0f18bbf3bb27a3f391eb26

A fresh proof database applied all 15 migrations. Process one of the exact production bundle accepted a signed-authenticated render with 201 only after committing performance id 088111da2246c47d279ddcd5ffb3d38122718a16a6f1bfe466bf664a3fcb1ced, then returned exactly 332,722 APNG bytes with SHA-256 ba5ad15f7dfec6cdad152ba14bb2197f1f82fb1c4c47d0ba718e128afd018970 and private cache policy to its owner while an adjacent account received 404. After a clean stop, process two recovered the same bytes and ETag. The database contained one mentor-presence-performances snapshot at version 2 and all 15 migrations before cleanup. Both processes exited with code 0; the proof port was closed, the isolated Redis database was flushed to zero keys, and the temporary database was dropped and confirmed absent. A post-rebase rebuild reproduced the same bundle size and SHA-256 after unrelated incoming mainline changes.

This was a backend API, storage, security, privacy, and lifecycle slice: no rendered web, admin, PWA, mobile-native, or Unreal UI changed, so the frontend skill and Playwright UI automation were not applicable. The affected network contract is covered by the authenticated route suite and the real WebSocket route suite, while the two-process exact-bundle proof covers the production HTTP boundary. No live production customer, external provider, C2PA signer, or embodiment renderer is claimed.

This closes only the local Mentor Presence rendered-performance snapshot partition. Its queue is per BFF process and rewrites one bounded global snapshot; there is no distributed compare-and-swap, sharding, multi-region ordering, or object-store offload. Rendering completes before persistence, so a failed commit discards the newly rendered candidate. The API has no listing or revocation UI, and bounded fences have no archive or subject-id reuse policy. Capacity requires an explicit migration or archive decision rather than silent loss. This closes that partition within those boundaries, not V1-002 or the wider operational-store inventory.

Lilith Studio Tara scene-publish receipt authority verification#

The authenticated Tara scene-publish source and published tip is 343b87fe359270d1ad756050f2f67a1ffebd52a4. Verification completed on 2026-07-20 UTC with the repository-pinned toolchain, a real local PostgreSQL snapshot store and Redis, Chromium, and the exact rebased production BFF bundle. The protected user-owned pnpm-lock.yaml remained outside the slice at worktree blob a37431842e330b3a06b030947c25bebdc72bc2b1; the permanent preservation stash remained 9c4ddf4f7fd4c205d1f083cdbfb9d4a1ee5ce320.

The first-party Lilith Studio editor previously sent four summary fields to a global process-local map. The route returned 201 synchronously, generated ids from a restart-resettable sequence, and listed every stored row to any authenticated editorial principal. Restart lost accepted markers, adjacent authors were not isolated, and the full scene manifest did not cross the acknowledgement boundary. The partition did not participate in DSAR, signed erasure, retention, or resurrection prevention even though its source comment called the marker durable.

The replacement is a strict schema-v1 owner authority over the existing admin_store_snapshot sink. The editor submits the exact manifest JSON already shown in its read-only workspace. A domain-separated SHA-256 over owner, scene, title, capacity tier, shard count, and manifest digest produces a stable publish id and release-edition receipt, so an exact replay returns the original record without a second write. Every create, exact-subject erase, and retention purge enters one ordered candidate/save/publish queue. Candidates remain invisible until the complete snapshot commits, and the POST awaits that commit before returning 201. Production requires and hydrates the sink before traffic; unavailable persistence returns controlled 503, erased subjects return 409, and manifest or store capacity returns 507 without publishing failed state.

Recovery requires exact document and record fields, schema version 1, canonical timestamps and ordering, lowercase SHA-256 values that match the exact manifest bytes, canonical stable identities, unique owner/id composites, and no row for a fenced subject. Unknown or future state, malformed JSON, non-object manifests, digest or identity tampering, duplicates, resurrection, unsafe integers, more than 256 KiB per manifest, more than 10,000 records, more than 100 records per owner, more than 100,000 fences, or more than 64 MiB per snapshot fails closed. Ordinary GET reads only the authenticated owner's unexpired records and exposes the digest but not raw manifest JSON or internal owner field.

The default DSAR collector now emits the exact owner's original manifest bytes, receipt metadata, digest, and expiry under generated_artifact; an adjacent owner is absent. Signed generated-artifact deletion fans out to this partition, physically removes only the exact subject, preserves adjacent owners, and persists a domain-separated one-way subject fence. Create and erase share the same queue, and the recovered fence rejects a stale retry after restart. The canonical OSHUN_RETENTION_RULES.generated_artifact policy expires receipts 365 days after creation with a seven-day purge cadence. Awaited startup and supervised periodic passes perform physical purge. Active legal holds and active or expiring category exceptions defer physical deletion, but an expired held receipt is withheld from ordinary reads and DSAR.

The customer-facing composition did not change. The existing Publish control now includes the full manifest in its request and still paints published only after the real response. Following the mandatory frontend workflow, the existing Playwright/API journey was extended rather than replacing the editor's visual hierarchy. It proves exact digest acknowledgement, stable replay, owner-only list readback, raw-manifest minimization, adjacent-owner isolation, 401/403/400 gates, and the complete browser authoring-to-receipt path.

text
# owner authority, acknowledgement ordering, recovery validation, route
# controls, exact-owner export, and generated-artifact erasure composition
pnpm --filter @oshun/bff exec vitest run \
  src/studio/studio-scene-publish-store.spec.ts \
  src/routes/admin-studio-scene-publish.spec.ts \
  src/generation/generated-artifact-erasure.test.ts
  3 files passed; 13/13 tests passed

pnpm --filter @oshun/bff exec vitest run \
  src/data-export/bundle-builder.test.ts --maxWorkers=1
  1 file passed; 40/40 tests passed

# exact manifest, restart, held-expiry read suppression, exact erase,
# adjacent preservation, recovered fence, and stale-retry rejection
OSHUN_ADMIN_DATABASE_URL=<local-postgres> pnpm --filter @oshun/bff exec \
  vitest run --config vitest.integration.config.ts \
  src/studio/studio-scene-publish-store-durability.integration.spec.ts \
  --maxWorkers=1
  1 file passed; 1/1 test passed

node tools/typecheck/ratchet.mjs --app apps/oshun/bff \
  --tsconfig tsconfig.typecheck.json
node tools/typecheck/ratchet.mjs --app apps/oshun/web \
  --tsconfig tsconfig.typecheck.json
  both passed; no new app-own errors; backlog: 0 known

E2E_BASE_URL=<local-web> E2E_BFF_URL=<exact-bundle-bff> \
  pnpm --dir apps/oshun/web exec playwright test \
  e2e/lilith-scene-publish.spec.ts --config playwright.config.ts --workers=1
  Chromium: 5/5 passed

pnpm exec eslint --no-warn-ignored --max-warnings=0 <changed TypeScript paths>
pnpm exec prettier --check <changed TypeScript/Markdown paths>
node tools/conventions/check-conventions-ratchet.mjs --staged
git diff --check
  passed; source pre-commit typecheck was explicitly skipped because its fixed
  parallel=4 command violates this 15 GiB host's resource policy, after both
  exact zero-backlog type ratchets above had passed

pnpm --dir apps/oshun/bff build
  server.js 34,982,194 bytes
  source map 81,771,959 bytes
  server SHA-256 68c46219f13f2f7dafb25632f82924ef0cb2146d44085569469c22aebcfaeba4

Process one of that exact production bundle committed receipt scene-publish-e25f2c4e84d1077b3ac2396ebb5cb89d9e4830257e86a5d410f17f75fd49d0ac and manifest SHA-256 91a65b329c8a67264806fb7f77bf0140c2d0cec2023a200848bb81bff41dd848. An exact retry returned the same id, the owner listed one minimized receipt, and an adjacent principal listed zero. After a clean stop, process two recovered the same id and digest. The focused Playwright run then added its isolated API and UI owners; the database held one studio-scene-publishes snapshot at version 4 with three records before cleanup. Both processes exited cleanly, the temporary database was dropped and confirmed absent, Redis database 14 was flushed to zero keys, and proof ports 4210 and 3010 were confirmed closed. The post-rebase build reproduced the same bundle sizes and SHA-256 after 19 unrelated incoming mainline commits.

The reconciled master ledger, evidence pack, journey, and result rendered 3,115 fresh Docs Center files spanning 10 products, 64 journeys, and 3,485 entities. docs:center:check passed; docs:center:verify reported zero structural broken links and zero dead source paths, with the unchanged 111 imported-content link warnings remaining nonblocking. The V5 document validator passed. A full Docs Center generator-test discovery run passed 45 tests and exposed five stale mainline expectations: the two in-scope scene-authority assertions were updated and reran 2/2 green, while three unrelated pre-existing failures remain for seven newly unregistered Tara Workbench/study route-matrix entries and old Metis process-local assertions against stores hardened by other commits. Those unrelated failures are not represented as passing or as part of this closure.

This is a durable owner-scoped receipt, not end-to-end customer publication. The route does not create an editorial-review item or audit event, resolve fixture provenance to immutable assets, supersede or withdraw a prior receipt, or make /tara or /lilith consume the scene. JSON is structurally bounded and digest-checked but is not yet validated against a complete immutable publication schema. The browser test still assists the island's E2E auth seam with a server-generated development bearer. The whole bounded snapshot and mutation queue are per process with no distributed compare-and-swap, multi-region ordering, or cross-store transaction, so concurrent BFF writers can still lose an update. Fences have no archive or subject-id reuse policy. This closes this local receipt partition within those boundaries, not V1-002 or the wider operational-store inventory.

Weekly-digest input ephemeral/recomputable disposition verification#

The weekly-digest disposition source and published tip is 28e6582b8da2d424e82a6c14adac59676b2688b7. Verification completed on 2026-07-20 UTC with the repository-pinned toolchain. The protected user-owned pnpm-lock.yaml remained outside the slice at worktree blob a37431842e330b3a06b030947c25bebdc72bc2b1; the permanent preservation stash remained 9c4ddf4f7fd4c205d1f083cdbfb9d4a1ee5ce320.

The inventory traced every DigestInputsStore/digestInputsStore reference and found no production mutation producer. Only the route test populated the map; the production route instantiated a global process-local singleton that was always empty. Its comment nevertheless said library, corrections, followed- event, and message-center surfaces wrote it. That overstated the live product and left a mutable object named as a store in the all-store inventory even though it owned no acknowledged record, decision, effect, or delivery state.

The replacement makes that disposition structural. Production defaults to a frozen stateless DigestInputsReader that always returns no projection, so the existing composer emits its explicit empty-digest/do-not-send verdict. The only map is now an EphemeralDigestInputsFixture with test-named seed and clear methods, and it can reach the route only through explicit dependency injection. No global mutable digest aggregate remains. The fixture deep-copies all three item collections both on insertion and readback so test callers cannot create hidden shared mutation.

The loss test first proves that a populated synthetic projection yields a preview with send: true, then clears the fixture and proves the same member receives exactly { ok: true, send: false, reason: 'empty-digest' }. The stateless production reader yields null for both that member and an adjacent member. Recreating or losing this projection therefore cannot lose source authority, evidence, lineage, approval, an already acknowledged effect, or learning state; it can only suppress a non-authoritative preview.

text
pnpm --dir apps/oshun/bff exec vitest run src/routes/digest-preview.test.ts
  1 file passed; 6/6 tests passed

pnpm --dir apps/oshun/bff exec vitest run \
  src/__tests__/v1-feature-pack-boot.test.ts
  1 file passed; 1/1 test passed

node tools/typecheck/ratchet.mjs --app apps/oshun/bff \
  --tsconfig tsconfig.typecheck.json
  passed; no new app-own errors; backlog: 0 known

pnpm exec eslint \
  apps/oshun/bff/src/channel-ops/digest-inputs-store.ts \
  apps/oshun/bff/src/routes/digest-preview.ts \
  apps/oshun/bff/src/routes/digest-preview.test.ts
pnpm exec prettier --check <the same three paths>
git diff --check
  passed

pnpm --dir apps/oshun/bff build
  server.js 34,981,681 bytes
  source map 81,772,600 bytes
  server SHA-256 768412cf32313b574b2494e89d1c5795acfa0e00a09e7e4bb5af5fe0a96e680b

This is not a claim that Oshun currently assembles or sends a weekly digest. The durable saved-item, correction, followed-event, and message-center source records remain in their owning partitions, but no production read-through projector composes them into this preview. Adding that feature requires an explicit source adapter and delivery authority; introducing another mutable aggregate is not authorized by this disposition. This closes only the unused process-local digest-input seam, not V1-002 or the broader operational-store inventory.

Tenant Living Scenes policy/live-audit authority disposition verification#

The tenant Living Scenes disposition source and published tip is ea3169fe8a0de109d11047548f14c4ac2cc4b65f. Verification completed on 2026-07-20 UTC with the repository-pinned toolchain. The protected user-owned pnpm-lock.yaml remained outside the slice at worktree blob a37431842e330b3a06b030947c25bebdc72bc2b1; the permanent preservation stash remained 9c4ddf4f7fd4c205d1f083cdbfb9d4a1ee5ce320.

The inventory traced the former TenantLivingScenesStore and found no mutation producer or write endpoint. Its process-local Map held one deploy-time policy, while two dated sample audit rows were returned to the admin UI as if they were live operational evidence. The UI compounded that ambiguity with checkbox and select controls that never saved and a Revoke button that had no action.

The replacement names and implements the policy source as a stateless, version-controlled TenantLivingScenesPolicyCatalog. It owns no audit rows, has no instance mutation state, returns detached values, and explicitly reports policySource: version_controlled_baseline plus policyEditable: false. The admin route obtains tenant-scoped audit rows from the real Living Scene share authority through listLivingSceneTenantAuditEntries; that authority is already part of the acknowledgement-bound durable living-scene-shares snapshot. The route separately reports auditSource: living_scene_share_authority, and the admin loader rejects missing provenance, tenant mismatch, invalid policy enums, partial audit rows, unknown actions, and non-ISO timestamps instead of silently filtering evidence.

The operator panel now presents the deployment policy as read-only definition data, labels both sources, and renders a truthful zero-event state when the live tenant audit is empty. It no longer ships sample audit events, editable-looking controls, or an unimplemented Revoke action. If the BFF is unavailable, the page clearly labels its local policy as a fallback baseline and shows no audit events. The route remains inside AdminShell and requires the tenant-console workspace scope.

text
pnpm --dir apps/oshun/bff exec vitest run \
  src/tenant-console/tenant-living-scenes-policy-catalog.spec.ts \
  src/__tests__/admin-tenant-console-route.test.ts \
  src/__tests__/living-scenes-route.test.ts --maxWorkers=1
  3 files passed; 32/32 tests passed after the first remote integration

OSHUN_V1_DATABASE_URL=<local PostgreSQL> pnpm --dir apps/oshun/bff exec \
  vitest run --config vitest.integration.config.ts \
  src/__tests__/living-scenes-share-durability.integration.test.ts \
  --maxWorkers=1
  1 file passed; 1/1 test passed; a fresh connection recovered the live admin
  audit row from the durable share authority

pnpm --dir apps/oshun/admin exec vitest run \
  src/__tests__/TenantLivingScenesGovernancePanel.test.tsx \
  src/__tests__/tenant-living-scenes-loader.spec.ts --maxWorkers=1
  2 files passed; 10/10 tests passed

E2E_BASE_URL=http://127.0.0.1:<isolated-admin-port> \
  pnpm --dir apps/oshun/admin exec playwright test \
  e2e/tenant-living-scenes-governance.spec.ts --workers=1
  Chromium 1/1 passed; the shared fixture reported zero serious/critical axe
  violations

node tools/typecheck/ratchet.mjs --app apps/oshun/bff \
  --tsconfig tsconfig.typecheck.json
pnpm --dir apps/oshun/admin typecheck
  passed; BFF backlog: 0 known; admin TypeScript passed

pnpm exec eslint <affected TypeScript/TSX paths> \
  --no-warn-ignored --max-warnings=0
pnpm exec prettier --check <affected source, tests, styles, and E2E paths>
git diff --check
  passed

pnpm --dir apps/oshun/admin build
  passed; optimized Next build compiled, typechecked, and generated 72 pages

pnpm --dir apps/oshun/bff build
  server.js 34,981,535 bytes
  source map 81,772,341 bytes
  server SHA-256 2cf51443912bfdd13f630761e726b934efa069b26e32352307f43ce65ad77141

# against a fresh database with all 15 migrations plus local Redis
pnpm --dir apps/oshun/bff verify:production-artifact
  Production artifact smoke check passed

The connected PostgreSQL run emitted only the repository's existing missing source-map diagnostics. The production smoke gate initially and correctly failed against the shared development database because a prior signup snapshot was signed with a different secret; verification therefore used a newly created, fully migrated disposable database and removed it afterward instead of altering shared state. Peak checks stayed above the host's memory stop limits. The source hook used SKIP_TYPECHECK=1 only after the exact BFF zero-backlog ratchet and admin typecheck had passed. Publication rebased twice over unrelated shared live-media extraction commits; after the first rebase the complete BFF slice of 32 assertions and exact production artifact smoke were rerun. Neither remote commit overlapped this source.

This does not claim operator-editable tenant policy or operator revoke support; both require explicit durable authorities before UI actions can be exposed. Only the version-controlled Lotus Sangha baseline is provisioned. The existing Living Scene durable snapshot preserves audit recovery, erasure, DSAR, and retention behavior already evidenced above, but its whole-snapshot mutation queue remains per process without distributed compare-and-swap. This closes the misclassified process-local policy map and fabricated-audit presentation seam, not V1-002 or the broader operational-store inventory.

Legacy process-local takedown authority retirement verification#

The legacy takedown/repeat-infringer retirement source and published tip is add4cec8f42e1bd12193f9084d58ba20bc4d74de. Verification completed on 2026-07-20 UTC with the repository-pinned toolchain. The protected user-owned pnpm-lock.yaml remained outside the slice at worktree blob a37431842e330b3a06b030947c25bebdc72bc2b1; the permanent preservation stash remained 9c4ddf4f7fd4c205d1f083cdbfb9d4a1ee5ce320.

Repository-wide producer/consumer tracing found a second legal-record authority behind /v1/admin/takedowns, /v1/admin/counter-notices, and /v1/admin/infringers. Its only repository consumers were its own route tests; no first-party web, admin, mobile, or service client called the nine endpoints. Nevertheless, the routes were registered in every BFF and could acknowledge process-local DMCA/copyright/trademark/NCII cases, counter-notices, simulated content removal/archive effects, notification counts, arbitrary strikes, and simulated account restrictions or termination. State lived in maps, sets, arrays, and the Aphrodite services' in-memory factories, so restart silently discarded the supposed legal and enforcement record.

That shadow authority is not safe to migrate by translating payloads. It let an admin submit a counter-notice as a caller-supplied uploader, inject a strike without a fulfilled statutory case, and claim provider effects that were only recorded in local arrays. The existing canonical /v1/dmca/* and /v1/admin/dmca/* surface instead authenticates the uploader, creates strikes from fulfilled durable cases, owns the restoration window, and persists through dmcaCaseStore; its acknowledgement, restart, privacy, retention, and physical- purge proof is recorded in the earlier DMCA section.

The two process-local stores and their stateful tests are now deleted. All nine legacy route shapes remain authentication- and historical-scope-gated, but an authorized request receives 410 legacy_takedown_authority_retired with canonicalAuthority: dmca_case_store and a route-specific migration direction. The compatibility handlers accept no legal state and report no simulated effect. The canonical admin queue remains live. A fresh application instance returns the same tombstone, proving that loss of process memory is harmless for this compatibility surface rather than pretending it needs persistence.

text
pnpm --dir apps/oshun/bff exec vitest run \
  src/routes/legacy-takedown-authority.spec.ts \
  src/compliance/dmca-case-store-durability.spec.ts --maxWorkers=1
  2 files passed; 9/9 tests passed

# after rebasing over the unrelated shared live-media SQL extraction
pnpm --dir apps/oshun/bff exec vitest run \
  src/routes/legacy-takedown-authority.spec.ts --maxWorkers=1
  1 file passed; 3/3 tests passed

node tools/typecheck/ratchet.mjs --app apps/oshun/bff \
  --tsconfig tsconfig.typecheck.json
  passed before the non-overlapping rebase; BFF backlog: 0 known

pnpm exec eslint <four affected TypeScript/spec paths> \
  --no-warn-ignored --max-warnings=0
pnpm exec prettier --check <four affected TypeScript/spec paths>
git diff --check
  passed

pnpm --dir apps/oshun/bff build
  server.js 34,889,565 bytes
  source map 81,562,480 bytes
  server SHA-256 b8c9aa6b05c4daa4806e9106e1646859eefb98b5c3b6d78058f3538989b1ec34

# against a fresh database with all 15 migrations plus local Redis
pnpm --dir apps/oshun/bff verify:production-artifact
  Production artifact smoke check passed

The focused compatibility proof covers all nine route shapes, unauthenticated and under-scoped rejection, exact authorized migration responses, loss- insensitive restart behavior, and continued availability of the canonical DMCA queue. The canonical store's focused durability suite covers failed-write and candidate/commit behavior. The final rebased production build and artifact smoke both passed; the disposable database was removed, and available memory stayed far above the stop threshold. Publication rebased once over an unrelated shared live-media SQL-store extraction with no path overlap.

This retirement does not claim a replacement workflow for the old generic trademark, NCII, model-release, performer-violation, or other non-DMCA payloads; those legacy writes are now explicitly unsupported instead of falsely durable. It does not prove content-provider removal or notification delivery beyond the canonical DMCA boundary documented earlier. The reusable @aphrodite/content-takedown library remains available for future integration, and its now-unused BFF package declaration was not changed because the lockfile is protected user work. This closes the two shadow process-local legal stores, not V1-002 or the broader operational-store inventory.

On-call schedule static-catalog disposition verification#

The on-call schedule disposition source and published tip is 26a84182fa3072dae0995672fd3ffe4843308011. Verification completed on 2026-07-20 UTC with the repository-pinned toolchain. The protected user-owned pnpm-lock.yaml remained outside the slice at worktree blob a37431842e330b3a06b030947c25bebdc72bc2b1; the permanent preservation stash remained 9c4ddf4f7fd4c205d1f083cdbfb9d4a1ee5ce320.

Repository-wide producer/consumer tracing found that production never called the former OncallScheduleStore.setRotation. Only the admin route test seeded its process-local map. The production data source was already the versioned service- and queue-ownership manifests, and every runtime rotation remained unseeded. There is no roster write endpoint, provider binding, or other live rotation authority in the repository. Treating that map as an operational store therefore overstated a capability that did not exist.

Production now uses ManifestOncallScheduleCatalog, a stateless reader derived entirely from those version-controlled manifests. It exposes no mutation or reset method, retains no instance state, returns detached entries, and reports each manifest-owned rotation as null. The admin route continues to emit the truthful rotation_targets_not_seeded readiness blocker while preserving its existing burn-rate and PagerDuty policy behavior. Rotation scenarios live only in an explicitly injected test-local MutableOncallScheduleFixture, so clearing or replacing process memory can affect synthetic route cases but cannot drop a roster, acknowledgement, incident, notification effect, approval, evidence, lineage, or learning state.

text
pnpm --dir apps/oshun/bff exec vitest run \
  src/channel-ops/oncall-schedule-catalog.spec.ts \
  src/routes/admin-oncall.test.ts --maxWorkers=1
  2 files passed; 13/13 tests passed before and after remote integration

node tools/typecheck/ratchet.mjs --app apps/oshun/bff \
  --tsconfig tsconfig.typecheck.json
  passed before and after remote integration; BFF backlog: 0 known

pnpm exec eslint <four affected TypeScript/spec paths> \
  --no-warn-ignored --max-warnings=0
pnpm exec prettier --check <four affected TypeScript/spec paths>
git diff --check
  passed; the touched route's seven pre-existing non-null assertions were
  replaced with explicit narrowing

pnpm --dir apps/oshun/bff build
  server.js 34,887,693 bytes
  source map 81,559,829 bytes
  server SHA-256 b92c864dd87a7617fdeefa21e1d082b73a0efaf86f1439260591a8674d927163

# against a fresh database with all 15 migrations plus local Redis
pnpm --dir apps/oshun/bff verify:production-artifact
  Production artifact smoke check passed before and after remote integration

The catalog proof covers the exact manifest team set, absence of production mutation authority, detached return values, and an identical unseeded projection from a replacement instance. The route proof covers authentication and scope gates, missing-rotation blockers, PagerDuty-not-configured blockers, configured PagerDuty success, service-policy lookup, burn-rate evaluation, and validation of the injected fixture. The final source commit rebased over unrelated shared live-media SQL edge-publication work at a47b9c352351942541ddf3dd05a94e90eeac2715; there was no path overlap. The final production artifact matched the pre-rebase byte counts and hash, booted against a disposable database after all 15 migrations, reached health, shut down cleanly, and left no database behind. Available memory remained above the stop thresholds.

This does not claim live responder, escalation, handoff, or provider-synchronized roster authority. Adding those capabilities requires an explicit durable or provider read-through authority and its own acknowledgement, recovery, audit, privacy, and retention design; another process-local map would not satisfy that boundary. No user-scoped or privacy-bearing partition was made durable because none existed in this catalog. This closes the misclassified mutable schedule map, not V1-002 or the broader operational-store inventory.

Contextual-help static-catalog disposition verification#

The contextual-help disposition source and published tip is cb247571dd183cb6cead4a4a265fc032a4e9413e. Verification completed on 2026-07-20 UTC with the repository-pinned toolchain. The protected user-owned pnpm-lock.yaml remained outside the slice at worktree blob a37431842e330b3a06b030947c25bebdc72bc2b1; the permanent preservation stash remained 9c4ddf4f7fd4c205d1f083cdbfb9d4a1ee5ce320.

Repository-wide producer/consumer tracing found that none of the former InProductHelpStore registration methods had a production caller. Its only external mutation was a test cleanup reset, while the constructor itself hard-coded every tooltip, walkthrough, video, and article. The read route is a real product path: the customer web proxy and InProductHelp component consume /v1/customer/help/contextual. The content is therefore shipped definition data, but the mutable singleton falsely suggested a live content-authoring authority whose writes would disappear on restart.

Production now uses VersionControlledInProductHelpCatalog. It has no instance fields, registration methods, or reset method. Each resolution materializes fresh arrays, objects, and locale maps from the version-controlled definitions before applying the existing contextual resolver. A caller that mutates even a nested locale map cannot change a later response, and a replacement catalog instance returns the same definition projection. The authenticated route keeps its existing surface, audience, role, domain, locale, and fallback behavior; only the nonexistent runtime-authoring contract was removed.

text
pnpm --dir apps/oshun/bff exec vitest run \
  src/customer/in-product-help-catalog.spec.ts \
  src/__tests__/customer-in-product-help-route.test.ts --maxWorkers=1
  2 files passed; 8/8 tests passed before and after remote integration

node tools/typecheck/ratchet.mjs --app apps/oshun/bff \
  --tsconfig tsconfig.typecheck.json
  passed before and after remote integration; BFF backlog: 0 known

pnpm exec eslint <four affected TypeScript/spec paths> \
  --no-warn-ignored --max-warnings=0
pnpm exec prettier --check <four affected TypeScript/spec paths>
git diff --check
  passed

pnpm --dir apps/oshun/bff build
  server.js 34,887,199 bytes
  source map 81,558,237 bytes
  server SHA-256 d8845256057acbd53484f8f358b6163d8d7dd90a7f0e1418929a08ab0b0b0fe2

# against a fresh database with all 15 migrations plus local Redis
pnpm --dir apps/oshun/bff verify:production-artifact
  Production artifact smoke check passed before and after remote integration

The focused catalog proof covers absence of all five mutation/reset methods, the exact customer-message definition set, nested-map caller mutation, and replacement-instance equivalence. The connected route proof covers authentication, all four help resource kinds, customer/admin audience filtering, locale resolution, and the empty unknown-surface result. The final source commit rebased over unrelated shared live-media SQL viewer-authority work at 181023ecd47a15ba9b6c292a0dab5e7e7445471a; there was no path overlap. The final production artifact matched the pre-rebase byte counts and hash, booted against a disposable database after all 15 migrations, reached health, shut down cleanly, and left no database behind. Available memory remained above the stop thresholds.

This does not claim a live help CMS, runtime content registration, publishing workflow, or remote video availability. Those capabilities require a separately governed content authority, publication lifecycle, and availability proof if they are added. The current catalog contains no user-owned or privacy-bearing state, and losing a process cannot discard help definitions because they are recreated from the deployed source. This closes the misclassified mutable help registry, not V1-002 or the broader operational-store inventory.

Unavailable scene-projection disposition verification#

The scene-projection disposition source and published tip is 950617ce2dca9840238b38a594768b520871bd55. Verification completed on 2026-07-20 UTC with the repository-pinned toolchain. The protected user-owned pnpm-lock.yaml remained outside the slice at worktree blob a37431842e330b3a06b030947c25bebdc72bc2b1; the permanent preservation stash remained 9c4ddf4f7fd4c205d1f083cdbfb9d4a1ee5ce320.

Repository-wide producer/consumer tracing found no production writer for any of the three former process-local projection maps. seedScene was called only by the audience, recap, reaction, and tip route tests; seedEvents only by the recap route test; and seedViewEvents only by the audience route test. The four registered production route plugins could read those singletons, but no share, session, analytics, service, web, mobile, or admin path could populate them. Consequently production already returned its unavailable responses: missing scene metadata made audience, reaction, and tip operations return 404; recap events and postcards returned 404 from their respective missing projections; and view-event aggregation was unreachable without metadata.

Production now names that boundary honestly through stateless EmptySceneMetadataReader, EmptySceneEventsReader, and EmptyViewEventsReader implementations. They expose no seed, reset, or other mutation authority, retain no process state, and return the same null/empty projection from a replacement instance. Audience, recap, reaction, and tip routes accept narrow reader injection while their production defaults remain explicitly unavailable. Mutable maps and their old seed/reset behavior exist only in scene-projection-fixtures.spec-helper.ts, whose test-only instances preserve full route decision coverage without creating a production authority.

text
pnpm --dir apps/oshun/bff exec vitest run \
  src/scene-experience/scene-projection-readers.spec.ts \
  src/routes/scene-audience.test.ts \
  src/routes/scene-recap.test.ts \
  src/routes/scene-reactions.test.ts \
  src/routes/scene-tips.test.ts --maxWorkers=1
  5 files passed; 31/31 tests passed before and after remote integration
  audience 5; recap 7; reactions 8; tips 9; production readers 2

node tools/typecheck/ratchet.mjs --app apps/oshun/bff \
  --tsconfig tsconfig.typecheck.json
  passed before and after remote integration; BFF backlog: 0 known

pnpm exec eslint <14 active affected TypeScript/spec paths> \
  --no-warn-ignored --max-warnings=0
pnpm exec prettier --check <14 active affected TypeScript/spec paths>
git diff --check
  passed

pnpm --dir apps/oshun/bff build
  server.js 34,885,755 bytes
  source map 81,556,932 bytes
  server SHA-256 134b2dbd03215e303cc146f055c380b4be89c5ec5db56326f0c2734370d0a590

# against a fresh database with all 15 migrations plus local Redis
pnpm --dir apps/oshun/bff verify:production-artifact
  Production artifact smoke check passed before and after remote integration

The production-reader proof checks the absence of all three seed methods and every reset method, exact unavailable results, and replacement-instance equivalence. The four route suites retain authentication, authorization, governance, audience aggregation, recap ordering/postcards, appreciation, and tip decision coverage through explicit test fixtures. Residual production search found neither a seed call nor an import of any retired *-store path.

The source commit rebased over unrelated shared live-chat SQL extraction at 195d7a866b6acfc2772553ff688fa4ad60089fb0; its nine changed paths had no intersection with this slice. The complete 31-test proof, BFF type ratchet, production build, and fresh-15-migration artifact smoke were rerun on the integrated tree. The final artifact matched its pre-rebase sizes and hash, reached health, shut down cleanly, and left no disposable database behind. Available memory remained above the mandated stop thresholds.

This does not claim a live scene metadata, recap-event, or audience-view authority. The already durable appreciation and tip-ledger authorities remain unchanged, but their scene-governance input is deliberately unavailable until a real upstream projection is connected. Such a connection must use a durable or authoritative read-through source and define acknowledgement, restart recovery, ownership isolation, DSAR/erasure, retention, and audit behavior before these routes can report live scene data. No user-scoped or privacy-bearing partition was made durable here because production had no records or producer to lose. This closes three misclassified mutable projection maps, not V1-002 or the broader operational-store inventory.

Account-protection durability, privacy, and retention verification#

The account-protection source and published tip is 93484dede75567663f6606f3aaca372af9b7f2c3. Verification completed on 2026-07-20 UTC with the repository-pinned toolchain. The protected user-owned pnpm-lock.yaml remained outside both commits at worktree blob a37431842e330b3a06b030947c25bebdc72bc2b1; the permanent preservation stash remained 9c4ddf4f7fd4c205d1f083cdbfb9d4a1ee5ce320. Local HEAD, tracked origin/main, and the live remote branch reached exact source-tip parity.

The former authority kept successful-login and manual administrator verdicts in one process-local map. Login returned before its fire-and-forget screen could finish, a restart erased the dashboard, and multiple replicas could each accept the same session id. Production now requires two normalized PostgreSQL tables: one row per screening result and one SHA-256 subject-digest lifecycle row. The session primary key is the cross-replica idempotency boundary. The digest row is the row-level serialization point for screening versus erasure and remains as a permanent pseudonymous resurrection fence after every directly identifying screen row is removed. A screen is returned to the caller only after its insert commits; missing tables or an unbound/failed repository keep the production admin authority unavailable rather than publishing volatile state.

Successful login now awaits the screening attempt before returning, so a process exit immediately after the response cannot orphan an unstarted write. The security policy is deliberately narrower than enforcement: analyzer or database failure is logged and swallowed after credential-valid authentication, so login remains fail-open. No high-risk verdict triggers step-up, denial, suspension, or revocation in this slice. The authorized administrator GET/POST surface instead returns controlled 503 on authority failure, 400 for invalid data, and 409 for duplicate sessions or a deleted-subject fence. There are no production seed rows.

Device fingerprint and country are transient analyzer inputs and have no database columns. Durable rows retain only session and subject ids, event type, validated risk/verdict vocabulary, derived signal names and anomaly flags, recommended actions, and the screening timestamp. Application and migration constraints bound canonical identifiers, unsafe controls, risk score, enum vocabulary, JSON array types and lengths, and allowed actions. PostgreSQL foreign-key restriction prevents accidental subject-state deletion while raw screens remain.

The real session export collector includes exact-subject screening records. The canonical signed session eraser deletes the raw rows and installs the digest fence before it can attest success; adjacent subjects remain intact and stale recreation is rejected across restart. Normal inactivity expiry is distinct from account erasure: it removes screens at the canonical 90-day session window and cleans inactive non-deleted subject rows so a legitimate later session is allowed. Startup and seven-day periodic purges evaluate active legal holds and exact-category retention exceptions before physical deletion.

text
# focused store, login, admin route, auth route, DSAR, erasure, and retention
pnpm --dir apps/oshun/bff exec vitest run \
  src/isis/account-protection-store.spec.ts \
  src/auth/login-account-screening.test.ts \
  src/__tests__/admin-isis-account-protection-route.test.ts \
  src/__tests__/auth-route.test.ts \
  src/data-export/bundle-builder.test.ts \
  src/data-deletion/session-state-eraser.spec.ts \
  src/privacy/compliance-retention-executor.spec.ts \
  --config vitest.config.ts
  7 files passed; 95/95 tests passed

# after final privacy-constraint tightening
pnpm --dir apps/oshun/bff exec vitest run \
  src/isis/account-protection-store.spec.ts \
  src/auth/login-account-screening.test.ts --config vitest.config.ts
  2 files passed; 13/13 tests passed

pnpm exec vitest run \
  libs/oshun/persistence/src/account-protection-schema.spec.ts \
  --config libs/oshun/persistence/vitest.config.ts
  1 file passed; 2/2 tests passed

# disposable PostgreSQL database created from an empty catalog
pnpm --dir libs/oshun/persistence exec prisma migrate deploy \
  --config prisma.config.ts
  all 16 migrations applied, including account-protection screening

pnpm --dir apps/oshun/bff exec vitest run \
  src/isis/account-protection-store-durability.integration.spec.ts \
  --config vitest.integration.config.ts
  1 file passed; 1/1 test passed

pnpm --dir libs/oshun/persistence exec prisma validate \
  --config prisma.config.ts
pnpm --dir libs/oshun/persistence exec prisma migrate status \
  --config prisma.config.ts
  schema valid; 16 migrations found; disposable database up to date

pnpm exec tsx \
  libs/oshun/persistence/scripts/generate-contract-persistence-schema.ts
  canonical schema SHA-256 remained byte-identical:
  59a7419d2321c31237a2903bb5e6a1913459fb53277505972cedc53be4685751

node tools/typecheck/ratchet.mjs --app apps/oshun/bff \
  --tsconfig tsconfig.typecheck.json
  no new app-own type errors; backlog 0

pnpm exec eslint <affected production and test TypeScript paths>
pnpm exec prettier --write <affected hand-authored TypeScript paths>
git diff --check
  0 lint errors; formatting and whitespace checks passed

pnpm --dir apps/oshun/bff run build
  server.js 34,916,678 bytes
  source map 81,610,943 bytes
  server SHA-256 a715c71e9cae2443d806efbfc1e0a4ccd1016f3662dc957ac0657ac4ad350bce

# against the fresh 16-migration database and local Redis
pnpm --dir apps/oshun/bff run verify:production-artifact
  Production artifact smoke check passed

The real PostgreSQL proof covers restart recovery, two independently constructed repository handles, a cross-replica duplicate-session race, an insert-versus- erasure race, exact-subject removal, adjacent-subject preservation, permanent post-erasure recreation rejection, normal retention deletion, active retention protection, and a final fresh-handle restart. Both valid race orderings are accepted, but the terminal invariant is strict: no raw erased-subject screen may survive and no later recreation may commit.

The commit hook's BFF and web affected type ratchets passed. Its persistence- package typecheck reached two pre-existing TS7016 errors for missing pg declarations in bootstrap-admin-snapshot-store.ts and validate-explain-checks.ts; neither script changed in this slice. The source commit used the hook's documented SKIP_TYPECHECK=1 override only after the exact zero-backlog BFF ratchet, Prisma validation, generated-schema proof, and real migration test passed. Hook lint, formatting, convention, asset, and docs checks passed. The source commit rebased cleanly over two unrelated shared live- media refactors with no changed-path intersection, then published directly to origin/main.

For this evidence update, Prettier, the V5 documentation validator, Docs Center structural verification, and Docs Center freshness all passed after regenerating the ignored local site (3,115 files, 64 journeys, 3,485 entities). The full Docs Center generator regression suite passed 47/50 tests; its three failures are current-main drift outside this slice: seven newly added Study/Tara Workbench routes are absent from WALKTHROUGH/matrix/routes.csv, and two Metis walkthrough assertions still expect pre-durability private-map/bridge field spellings. This slice does not alter those route matrices, walkthrough results, or Metis authorities.

No user-facing web, mobile, admin component, provider/native effect, media/model pipeline, or Unreal content changed. Existing HTTP response shapes were preserved while their backend failure semantics became explicit, so no Playwright, mobile, provider, media, or Unreal automation applied. This closes the account-protection operational partition, not step-up enforcement, the remaining operational-store inventory, or V1-002 itself.

Account-protection admin-contract and rendered-browser follow-up#

Source cafc735249c591f3cb355da7cf88f28879b47e44, published to origin/main on 2026-07-22 UTC, closes the remaining permissive administrator/browser contract without broadening the durable authority described above. GET and POST now return the exact durable_account_protection_screening_history disposition and declare normalized PostgreSQL persistence, successful-login and authorized- administrator producers, authenticated-subject/admin-scope binding, canonical 90-day hold-aware retention, request-only device/country inputs, source-defined anomaly screening, advisory-only actions, fail-open login, fail-closed admin, and signed erasure with a digest resurrection fence. Requests reject unknown or malformed fields. The browser rejects unknown dashboard/acknowledgement fields, impossible aggregates, and acknowledgements that do not match the submitted session, subject, and event.

The rendered workspace is now titled an account-protection screening ledger. It states explicitly that recommended actions do not perform step-up, denial, suspension, or revocation, and it exposes the persistence, retention, erasure, and request-only input boundary. The route map distinguishes its one live route from four documented-only routes. Controls meet the 44 px touch-target floor, and narrow layouts retain containment.

text
# exact request/response contract, no-store policy, malformed input, and scope
pnpm --dir apps/oshun/bff exec vitest run \
  src/__tests__/admin-isis-account-protection-route.test.ts \
  --pool=forks --maxWorkers=1 --no-file-parallelism
  1 file passed; 9/9 tests passed

# strict dashboard/ack parser, route map, page wiring, and UI behavior
pnpm --dir apps/oshun/web exec vitest run \
  src/components/__tests__/StudioIsisAccountProtectionPage.test.tsx \
  src/components/__tests__/StudioIsisAccountProtectionRouteMap.test.ts \
  src/components/__tests__/StudioIsisAccountProtectionWorkspace.integration.test.tsx \
  src/components/__tests__/StudioIsisAccountProtectionWorkspace.test.tsx \
  --pool=forks --maxWorkers=1 --no-file-parallelism
  4 files passed; 8/8 tests passed

# source BFF + web + real PostgreSQL/Redis: hard gate, exact live GET/POST/400,
# durable commit/reload, inflated payload rejection, outage/scope behavior,
# desktop/mobile containment, touch targets, and applicable axe analysis
pnpm --dir apps/oshun/web exec playwright test \
  e2e/studio-isis-account-protection.spec.ts \
  --config=playwright.config.ts --workers=1
  8/8 tests passed; all 32 current migrations applied

pnpm --dir apps/oshun/bff exec vitest run \
  src/isis/account-protection-store.spec.ts \
  src/auth/login-account-screening.test.ts \
  --pool=forks --maxWorkers=1
  2 files passed; 13/13 tests passed

OSHUN_V1_DATABASE_URL=<disposable-database> \
pnpm --dir apps/oshun/bff exec vitest run \
  -c vitest.integration.config.ts \
  src/isis/account-protection-store-durability.integration.spec.ts \
  --pool=forks --maxWorkers=1
  1 file passed; 1/1 test passed

pnpm --dir apps/oshun/web typecheck
pnpm exec eslint <affected BFF/web source, test, and E2E paths>
git diff --check
  web typecheck, affected lint, and whitespace checks passed

NODE_OPTIONS=--max-old-space-size=6144 \
node tools/typecheck/ratchet.mjs \
  --app apps/oshun/bff --tsconfig tsconfig.typecheck.json
  reached only the same two unrelated current-main errors in
  autonomous-content-metrics-store.ts and autonomy-route.test.ts

pnpm --dir apps/oshun/bff run build
pnpm --dir apps/oshun/bff run verify:production-artifact
  migrated-database production-artifact smoke passed;
  36,097,671-byte entry bundle;
  SHA-256 08e5db98d4ac3a3a1d570d8f6cbe48fdb579d228db2dd9a5862f00b50249bb98

The durability proof covers restart survival, cross-replica idempotency, insert-versus-erasure ordering, exact-subject removal, adjacent-subject preservation, resurrection fencing, normal expiry, and hold-aware retention. Its first run shared two older browser-fixture rows with the retention sweep; after those disposable account-protection rows were isolated, the same test passed 1/1. The disposable database was then removed. The web production build was not run because the 15 GiB host is below the repository's 32 GiB hard gate and no user approval was provided. The source commit used the documented typecheck-only hook bypass after all affected verification passed; hook lint, formatting, convention, asset, and documentation checks passed. This follow-up does not claim enforcement or close the parent all-store item.

Isis artifact-detection durability, privacy, retention, and browser verification#

The artifact-detection implementation source is bce1e432032d95a8570ea989505b88db2674c53a, published directly on origin/main after a clean rebase over non-overlapping Aphrodite/shared live-media work. Verification completed on 2026-07-20 UTC with the repository-pinned toolchain. The user-owned pnpm-lock.yaml remained outside the commit at worktree blob a37431842e330b3a06b030947c25bebdc72bc2b1; the permanent preservation stash remained 9c4ddf4f7fd4c205d1f083cdbfb9d4a1ee5ce320 at stash@{0}.

The former production authority was a process-local map initialized with four synthetic reports. A restart erased operator-authored history, replicas could independently accept the same queue item, and the POST body supplied createdBy. Production now starts empty and requires two normalized PostgreSQL tables: one append-only row per defect report and one SHA-256 operator-digest lifecycle row. The queue-item primary key is the cross-replica idempotency boundary. The lifecycle row is the serialization point between report creation and account erasure and remains as a permanent pseudonymous resurrection fence after the report package is physically removed.

The administrator route now derives operator attribution exclusively from the validated auth context and rejects any caller-supplied createdBy. Queue, asset, provider, model, failure-code, severity, benchmark-category, timestamp, and operator values are bounded and taxonomy checked in the application; the SQL migration independently constrains canonical identifiers, control characters, digests, JSON shape/length/vocabulary, severity/category vocabulary, lifecycle ordering, indexes, and the restricted foreign key. Asset, provider, and model values are explicitly opaque operational identifiers. No customer owner is inferred from them and no DSAR claim is made for those fields.

Report acknowledgement is transaction bound. The insert, persisted-row projection, and dashboard input read happen inside one transaction; a response cannot report storage failure after silently committing the report. The real PostgreSQL failure-injection test forces that post-insert projection to throw and then proves both the report and newly created operator lifecycle row remain absent. GET and POST fail closed with controlled 503 when durability is unbound or unavailable. POST returns controlled 400, 409, and 410 for invalid input, a duplicate queue item, and an erased operator respectively.

These reports are minimized internal, non-exportable review_package quality evidence. Signed profile erasure pseudonymizes the exact authenticated operator in every retained report and marks the digest lifecycle row deleted/redacted in the same transaction. Adjacent operators remain unchanged and later writes by the erased principal are rejected before and after physical purge. The shared retention executor now admits asynchronous normalized candidates; startup and the supervised periodic run apply the canonical 2,555-day review-package window, block physical removal for an active exact-subject legal hold or exact-category retention exception, delete due reports, and retain only the digest fence plus purge time.

The existing restrained Studio Isis operations workspace was preserved rather than redesigned. It now gives specific guidance for deleted-account and persistence failures, including the acknowledgement-safe “Nothing was recorded” message. The mandatory frontend workflow and first real Chromium run exposed 26.5px inputs; all five inputs/selects and the submit control now have a 44px minimum height. The final live-browser journey checks the boundary guard, absence of the four legacy synthetic IDs, caller-spoof rejection, authenticated attribution, three-report cluster promotion, durable browser-authored reload, duplicate rejection, payload minimization, touch targets, controlled 410/503 states, and automatic WCAG 2.1 AA axe analysis.

text
# focused store and shared retention behavior
pnpm --dir apps/oshun/bff exec vitest run \
  src/isis/artifact-detection-store.spec.ts \
  src/privacy/compliance-retention-executor.spec.ts \
  --pool=forks --maxWorkers=1 --no-file-parallelism
  2 files passed; 13/13 tests passed

# authenticated admin route, honest empty state, taxonomy, clustering,
# duplicate, spoof, erased-subject, and unavailable-persistence behavior
pnpm --dir apps/oshun/bff exec vitest run \
  src/__tests__/admin-isis-artifact-detection-route.test.ts \
  --pool=forks --maxWorkers=1 --no-file-parallelism
  1 file passed; 8/8 tests passed

# deterministic schema and SQL invariants
pnpm --dir libs/oshun/persistence exec vitest run \
  src/artifact-detection-schema.spec.ts \
  --pool=forks --maxWorkers=1 --no-file-parallelism
  1 file passed; 2/2 tests passed

pnpm --dir libs/oshun/persistence exec prisma validate \
  --schema prisma/schema.prisma
pnpm --dir libs/oshun/persistence exec prisma migrate status \
  --schema prisma/schema.prisma
  schema valid; 17 migrations found; disposable database up to date

pnpm exec tsx \
  libs/oshun/persistence/scripts/generate-contract-persistence-schema.ts
  generated schema remained byte-identical
  schema SHA-256 1e119704d60ed4ff46f9bf1388893d38afd169a77ea3204f8f5e395f653e002d

# two independent handles, restart, replica duplicate, insert/erasure race,
# exact pseudonymization, adjacent subject, legal hold, purge/fence, and
# acknowledgement-projection rollback against real PostgreSQL
pnpm --dir apps/oshun/bff exec vitest run \
  -c vitest.integration.config.ts \
  src/isis/artifact-detection-store-durability.integration.spec.ts \
  --pool=forks --maxWorkers=1 --no-file-parallelism
  1 file passed; 2/2 tests passed

# rendered workspace/component/route-map behavior
pnpm --dir apps/oshun/web exec vitest run \
  src/components/__tests__/StudioIsisArtifactDetectionWorkspace.integration.test.tsx \
  src/components/__tests__/StudioIsisArtifactDetectionPage.test.tsx \
  src/components/__tests__/StudioIsisArtifactDetectionRouteMap.test.ts \
  --pool=forks --maxWorkers=1 --no-file-parallelism
  3 files passed; 7/7 tests passed

# isolated current-code web/BFF stack, real migrated PostgreSQL, Chromium + axe
E2E_BASE_URL=http://127.0.0.1:<isolated-web-port> \
E2E_BFF_URL=http://127.0.0.1:<isolated-bff-port> \
pnpm --dir apps/oshun/web exec playwright test \
  e2e/studio-isis-artifact-detection.spec.ts \
  --config=playwright.config.ts --project=chromium --workers=1 --retries=0
  4/4 tests passed

NODE_OPTIONS=--max-old-space-size=8192 node tools/typecheck/ratchet.mjs \
  --app apps/oshun/bff --tsconfig tsconfig.typecheck.json
NODE_OPTIONS=--max-old-space-size=8192 node tools/typecheck/ratchet.mjs \
  --app apps/oshun/web --tsconfig tsconfig.typecheck.json
pnpm --dir libs/oshun/persistence exec tsc -p tsconfig.lib.json --noEmit
  BFF backlog 0; web backlog 0; changed persistence library passed

pnpm exec eslint <affected BFF/web/persistence TypeScript paths> \
  --no-warn-ignored --max-warnings=0
pnpm exec prettier --check <affected hand-authored TypeScript paths>
git diff --check
  lint, formatting, and whitespace checks passed

pnpm --dir apps/oshun/bff run build
  server.js 34,945,612 bytes
  source map 81,661,580 bytes
  server SHA-256 dbfab05e45835f50d3f9aae64ce4cd33a48ce77b7d95af169a3403508b38a163

# against the migrated 17-migration database and local Redis
pnpm --dir apps/oshun/bff run verify:production-artifact
  Production artifact smoke check passed

The package-wide persistence tsc --noEmit and the commit hook both reached the same two current-main TS7016 failures: missing pg declarations in bootstrap-admin-snapshot-store.ts and validate-explain-checks.ts. Neither script changed here. The exact changed-library tsconfig.lib.json check, generated-schema proof, Prisma validation/status, migration execution, and real database suite passed. The hook's documented SKIP_TYPECHECK=1 override was used only after both zero-backlog application ratchets and that library check; all hook lint, formatting, asset, convention, and documentation gates passed.

The web production build compiled successfully in 3.2 minutes and finished its TypeScript phase in 60 seconds. Static generation then stopped on the unrelated current-main /profile/persona page because an existing projection read undefined.join. The artifact-detection page had already compiled, rendered, and passed the isolated live Playwright/axe flow. This evidence does not turn that unrelated failure into a green build claim.

This closes the connected artifact-detection operational partition only. It does not claim external provider remediation, model retraining, automatic release blocking, asset-owner DSAR semantics, or a quality-policy authoring workflow. The parent all-store V1-002 row remains open.

Isis 3D-benchmarking durability, integrity, privacy, retention, and browser verification#

The benchmarking implementation source and published tip is b4623dfe0e8ed9a6e9e776260f054cf7e602a4a0. It was rebased cleanly over two non-overlapping Aphrodite/shared live-media commits and published on origin/main. Verification completed on 2026-07-21 UTC with the repository- pinned toolchain. The user-owned pnpm-lock.yaml remained outside the commit at worktree blob a37431842e330b3a06b030947c25bebdc72bc2b1; the permanent preservation stash remained 9c4ddf4f7fd4c205d1f083cdbfb9d4a1ee5ce320 at stash@{0}.

The former production authority was a seeded process-local map. Restart erased operator-authored regression history, separate replicas could accept the same case id, the request body supplied evaluator attribution, and production mixed two synthetic examples into apparently real quality evidence. Production now starts empty and requires one normalized PostgreSQL row per benchmark case plus one SHA-256 operator-digest lifecycle row. The global case-id primary key is the cross-replica idempotency boundary. Updating the lifecycle row serializes case creation against exact operator erasure; that row remains a permanent pseudonymous resurrection fence after the retained case package is purged.

The authenticated administrator route derives evaluatedBy only from the validated principal and rejects caller-supplied evaluatedBy or createdBy. Case ids, labels, evaluator ids, timestamps, thresholds, vector cardinality, vector components, and calculated metrics are bounded. Reference and candidate embeddings must be non-empty, finite, equal dimensional, no larger than 4,096 components, and within the component magnitude limit. The SQL migration independently constrains canonical identifiers, lifecycle ordering, array NULL, NaN, infinity, cardinality, equal dimensions, component magnitude, metric ranges, verdict consistency, indexes, and the restricted lifecycle foreign key.

Acknowledgement is transaction bound. Operator-state creation, the case insert, and the dashboard projection used by the 201 response complete in one transaction. The real PostgreSQL failure-injection test makes that projection throw after insertion and proves that neither the case nor a new lifecycle row commits. Persisted rows are schema checked and both cosine and CLIP metrics are recalculated before reads are served, so database drift cannot silently become quality evidence. GET and POST fail closed with controlled 503 when the durable repository is absent or unavailable; writes return controlled 400, 409, and 410 for invalid input, a duplicate case id, and a deleted operator.

Benchmark rows are minimized, internal, non-exportable review_package evidence. Labels and numeric embeddings are operational measurements; the implementation does not infer customer ownership from them. Signed profile erasure pseudonymizes the exact authenticated evaluator and marks the digest lifecycle deleted/redacted in the same transaction. Adjacent operators remain unchanged, and later writes by the erased principal are rejected before and after physical purge. The shared compliance-retention executor applies the canonical seven-year review-package window, blocks physical removal for an active exact-subject legal hold or exact-category retention exception, deletes due cases, and retains only the digest fence plus purge time.

The existing restrained Studio Isis operations workspace remains intact. It now renders honest empty durable history, validates vectors without silently dismissing malformed tokens, prevents unequal-dimension submission, validates successful response projections before rendering, and gives specific duplicate, invalid-input, deleted-operator, and storage-unavailable guidance. The latter explicitly says that nothing was recorded. All five inputs and the submit button meet the 44px target. The live browser journey proves hard boundary protection, absence of legacy seed ids, caller-spoof rejection, authenticated attribution, durable submit/reload, duplicate rejection, exact vector transport, unequal- dimension blocking, controlled 410/503 states, touch targets, and automatic WCAG 2.1 AA axe analysis.

text
# focused store, authenticated route, and shared-retention behavior
pnpm --dir apps/oshun/bff exec vitest run \
  src/isis/benchmark-store.spec.ts \
  src/__tests__/admin-isis-benchmarking-route.test.ts \
  src/privacy/compliance-retention-executor.spec.ts \
  --pool=forks --maxWorkers=1 --no-file-parallelism
  3 files passed; 20/20 tests passed

# deterministic generated schema and SQL invariants
pnpm --dir libs/oshun/persistence exec vitest run \
  src/benchmark-schema.spec.ts \
  --pool=forks --maxWorkers=1 --no-file-parallelism
  1 file passed; 2/2 tests passed

pnpm --dir libs/oshun/persistence exec prisma validate \
  --schema prisma/schema.prisma
pnpm exec tsx \
  libs/oshun/persistence/scripts/generate-contract-persistence-schema.ts
  schema valid; generated schema remained byte-identical
  schema SHA-256 b4e15461cd8da1978821ef9253ea3fe27ca62b5fa56adb059cfcb675aa9d8ef2

# fresh disposable database, all 18 migrations, two independent handles,
# restart, replica duplicate, insert/erasure race, exact pseudonymization,
# adjacent subject, legal hold, purge/fence, and acknowledgement rollback
pnpm --dir apps/oshun/bff exec vitest run \
  -c vitest.integration.config.ts \
  src/isis/benchmark-store-durability.integration.spec.ts \
  --pool=forks --maxWorkers=1 --no-file-parallelism
  1 file passed; 2/2 tests passed

# rendered workspace, base component, page, and route-map behavior
pnpm --dir apps/oshun/web exec vitest run \
  src/components/__tests__/StudioIsisBenchmarkingWorkspace.integration.test.tsx \
  src/components/__tests__/StudioIsisBenchmarkingWorkspace.test.tsx \
  src/components/__tests__/StudioIsisBenchmarkingPage.test.tsx \
  src/components/__tests__/StudioIsisBenchmarkingRouteMap.test.ts \
  --pool=forks --maxWorkers=1 --no-file-parallelism
  4 files passed; 11/11 tests passed

# isolated current-code web/BFF stack, fresh 18-migration PostgreSQL,
# Chromium, rendered boundary/submit/reload/failure states, and axe
E2E_BASE_URL=http://127.0.0.1:<isolated-web-port> \
E2E_BFF_URL=http://127.0.0.1:<isolated-bff-port> \
node apps/oshun/web/scripts/run-playwright.mjs test \
  -c apps/oshun/web/playwright.config.ts \
  apps/oshun/web/e2e/studio-isis-benchmarking.spec.ts \
  --project=chromium --workers=1
  4/4 tests passed in 44.7 seconds

node tools/typecheck/ratchet.mjs \
  --app apps/oshun/bff --tsconfig tsconfig.typecheck.json
node tools/typecheck/ratchet.mjs \
  --app apps/oshun/web --tsconfig tsconfig.typecheck.json
pnpm --dir libs/oshun/persistence exec tsc -p tsconfig.lib.json --noEmit
  BFF backlog 0; web backlog 0; changed persistence library passed

pnpm exec eslint <affected BFF/web/persistence source paths>
pnpm exec prettier --check <affected hand-authored TypeScript paths>
git diff --check
  affected source lint, formatting, and whitespace checks passed

pnpm --dir apps/oshun/bff run build
  server.js 34,975,361 bytes
  source map 81,712,527 bytes
  server SHA-256 c4c646227952dc972d02ca74968fd75791fea34724dfa17cb02306a141c67aa6

# against a fresh migrated 18-migration database and local Redis
pnpm --dir apps/oshun/bff run verify:production-artifact
  Production artifact smoke check passed

The package-wide persistence tsc --noEmit and the commit hook reached the same two current-main TS7016 failures: missing pg declarations in bootstrap-admin-snapshot-store.ts and validate-explain-checks.ts. Neither script changed in this slice. The exact changed-library tsconfig.lib.json check, generated-schema proof, Prisma validation, fresh migration execution, and real-database suite passed. The hook's documented SKIP_TYPECHECK=1 override was used only after both zero-backlog application ratchets and that focused library check; all hook lint, formatting, asset, convention, and documentation gates passed.

The web production build compiled successfully in 3.4 minutes and finished its TypeScript phase in 67 seconds. Static generation then stopped at 346 of 692 pages on the unrelated current-main /profile/persona page because an existing projection reads undefined.join. The changed benchmarking page had compiled, typechecked, rendered, and passed the isolated live Playwright/axe flow. This evidence does not represent the unrelated failure as a green build.

This closes the connected Isis 3D-benchmarking operational partition only. It does not claim benchmark-corpus governance, external provider/model remediation, automatic release gating, customer ownership of labels or embeddings, or a benchmark policy-authoring workflow. The parent all-store V1-002 row remains open.

Isis feedback-evaluation durability, integrity, privacy, retention, and browser verification#

The feedback-evaluation implementation source and published tip is 6998eb4883bd8437c3bf5b414b7ee0fbb7551552. It was rebased cleanly over five non-overlapping Tara, Yemaya, and shared-lifecycle commits and published on origin/main. Verification completed on 2026-07-21 UTC with the repository- pinned toolchain. The user-owned pnpm-lock.yaml remained outside the commit at worktree blob a37431842e330b3a06b030947c25bebdc72bc2b1; the permanent preservation stash remained 9c4ddf4f7fd4c205d1f083cdbfb9d4a1ee5ce320 at stash@{0}.

The former production authority was a seeded process-local map. Restart erased operator-authored evaluation history, separate replicas could accept the same sample id, the request body supplied evaluator attribution, and production mixed synthetic exact/partial examples into apparently real quality evidence. Production now starts empty and requires one normalized PostgreSQL row per evaluation sample plus one SHA-256 operator-digest lifecycle row. The global sample-id primary key is the cross-replica idempotency boundary. Updating the lifecycle row serializes sample creation against exact operator erasure; that row remains a permanent pseudonymous resurrection fence after the retained review package is physically purged.

The authenticated administrator route derives evaluatedBy only from the validated principal and rejects caller-supplied evaluatedBy or createdBy. Sample ids and evaluator ids are canonical and bounded, predicted/reference text is nonblank and limited to 16,000 characters, unsafe control characters are rejected, maxNgram is an integer from one through four, and timestamps and metrics are bounded and finite. The SQL migration independently constrains identifier and text bounds, safe controls, lifecycle ordering, digest shape, n-gram and metric ranges, indexes, and the restricted lifecycle foreign key.

Acknowledgement is transaction bound. Operator-state creation, the sample insert, and the dashboard projection used by the 201 response complete in one transaction. The real PostgreSQL failure-injection test makes that projection throw after insertion and proves that neither the sample nor a new lifecycle row commits. Persisted rows are schema checked and BLEU plus ROUGE-1, ROUGE-2, and ROUGE-L are recalculated before reads are served, so database drift cannot silently become quality evidence. GET and POST fail closed with controlled 503 when the durable repository is absent or unavailable; writes return controlled 400, 409, and 410 for invalid input, a duplicate sample id, and a deleted operator.

Samples are approved, de-identified internal review_package evidence. This route has no customer provenance and therefore does not fabricate customer ownership, accept customer feedback, or claim customer-data DSAR semantics. Signed profile erasure pseudonymizes the exact authenticated evaluator and marks the digest lifecycle deleted/redacted in the same transaction. Adjacent operators remain unchanged, and later writes by the erased principal are rejected before and after physical purge. The shared compliance-retention executor applies the canonical seven-year review-package window, blocks physical removal for an active exact-subject legal hold or exact-category retention exception, deletes due text and scores, and retains only the digest fence plus purge time.

The restrained Studio Isis operations workspace now states its data boundary: approved, de-identified internal review text only, never customer feedback or personal data. It labels BLEU/ROUGE as diagnostic evidence rather than automatic release authority. The browser accepts a successful write only when a complete, bounded server sample and aggregate pass the response contract and the sample is bound to the submitted id and text. It renders honest empty history plus specific duplicate, invalid-input, deleted-operator, malformed-acknowledgement, and storage- unavailable guidance. Inputs and the submit button meet the 44px target. The live browser journey proves hard boundary protection, absence of legacy seed ids, caller-spoof rejection, authenticated attribution, durable submit/reload, duplicate rejection, controlled 410/503 states, touch targets, and automatic WCAG 2.1 AA axe analysis.

text
# focused store and authenticated-route behavior
pnpm --dir apps/oshun/bff exec vitest run \
  src/isis/feedback-eval-store.spec.ts \
  src/__tests__/admin-isis-feedback-eval-route.test.ts \
  --pool=forks --maxWorkers=1 --no-file-parallelism
  2 files passed; 11/11 tests passed in 82.41 seconds

# shared legal-hold/retention-exception executor
pnpm --dir apps/oshun/bff exec vitest run \
  src/privacy/compliance-retention-executor.spec.ts \
  --pool=forks --maxWorkers=1 --no-file-parallelism
  1 file passed; 8/8 tests passed

# deterministic generated schema and SQL invariants
pnpm --dir libs/oshun/persistence exec vitest run \
  src/feedback-eval-schema.spec.ts \
  --pool=forks --maxWorkers=1 --no-file-parallelism
  1 file passed; 2/2 tests passed

pnpm --dir libs/oshun/persistence exec prisma validate \
  --schema prisma/schema.prisma
pnpm exec tsx \
  libs/oshun/persistence/scripts/generate-contract-persistence-schema.ts
  schema valid; generated schema remained byte-identical
  schema SHA-256 9a6c927a6d069e45065c401969eddf3c9043be1c5a9c866538c893266fd6bc62

# fresh disposable database, all 19 migrations, two independent handles,
# restart, replica duplicate, insert/erasure race, exact pseudonymization,
# adjacent subject, legal hold, purge/fence, and acknowledgement rollback
pnpm --dir apps/oshun/bff exec vitest run \
  -c vitest.integration.config.ts \
  src/isis/feedback-eval-store-durability.integration.spec.ts \
  --pool=forks --maxWorkers=1 --no-file-parallelism
  1 file passed; 2/2 tests passed in 11.11 seconds

# rendered workspace, page, and route-map behavior
pnpm --dir apps/oshun/web exec vitest run \
  src/components/__tests__/StudioIsisUserFeedbackLoopWorkspace.integration.test.tsx \
  src/components/__tests__/StudioIsisUserFeedbackLoopPage.test.tsx \
  src/components/__tests__/StudioIsisUserFeedbackLoopRouteMap.test.ts
  3 files passed; 7/7 tests passed

# isolated current-code web/built-BFF stack, fresh 19-migration PostgreSQL,
# Chromium, rendered boundary/submit/reload/failure states, and axe
E2E_BASE_URL=http://127.0.0.1:<isolated-web-port> \
E2E_BFF_URL=http://127.0.0.1:<isolated-bff-port> \
pnpm --dir apps/oshun/web run e2e -- \
  e2e/studio-isis-user-feedback-loop.spec.ts \
  --project=chromium --workers=1
  4/4 tests passed in 34.3 seconds

node tools/typecheck/ratchet.mjs \
  --app apps/oshun/bff --tsconfig tsconfig.typecheck.json
node tools/typecheck/ratchet.mjs \
  --app apps/oshun/web --tsconfig tsconfig.typecheck.json
pnpm --dir libs/oshun/persistence exec tsc -p tsconfig.lib.json --noEmit
  BFF backlog 0; web backlog 0; changed persistence library passed

pnpm exec eslint <affected BFF/web/persistence source paths>
git diff --check
  affected source lint and whitespace checks passed

pnpm --dir apps/oshun/bff run build
  server.js 35,004,862 bytes
  source map 81,764,033 bytes
  server SHA-256 bce7ad7e02a1985a3066fbb5630294bc3ed87032531ec5176de92ba92bd898bc

# against a fresh migrated 19-migration database and local Redis
pnpm --dir apps/oshun/bff run verify:production-artifact
  Production artifact smoke check passed

The final evidence sources rendered 3,116 docs-center files. pnpm docs:center:verify reported zero structural broken links and zero dead source paths, while continuing to surface the 111 documented non-blocking imported- content links; pnpm docs:center:check reported every generated file fresh, and the V5 documentation validator passed. The docs generator regression suite retained the exact current-main baseline: 47 tests passed and the same three unrelated route-matrix/Metis source-shape assertions failed. No feedback- evaluation path appears in those failures.

The package-wide persistence tsc --noEmit and the first commit attempt reached the same two current-main TS7016 failures: missing pg declarations in bootstrap-admin-snapshot-store.ts and validate-explain-checks.ts. Neither script changed in this slice. The exact changed-library tsconfig.lib.json check, generated-schema proof, Prisma validation, fresh migration execution, and real-database suite passed. The hook's documented SKIP_TYPECHECK=1 override was used only after both zero-backlog application ratchets and that focused library check; all hook lint, formatting, asset, convention, and documentation gates passed.

The final web production build compiled successfully in 3.5 minutes and finished its TypeScript phase in 63 seconds. Static generation then stopped at 346 of 692 pages on the unrelated current-main /profile/persona page because an existing projection reads undefined.join. The changed feedback-evaluation page had compiled, typechecked, rendered, and passed the isolated live Playwright/axe flow. This evidence does not represent the unrelated failure as a green build.

This closes the connected Isis feedback-evaluation operational partition only. It does not claim customer-feedback ingestion, automatic model release or training authority, provider/model remediation, customer ownership of internal review pairs, or a quality-policy authoring workflow. The parent all-store V1-002 row remains open.

Isis model-quality assessment durability, integrity, privacy, retention, and browser verification#

The model-quality assessment implementation source and published tip is d1bbb3ca0f14fa8d913239dd4f86887cea463b28. It was rebased over the latest non-overlapping origin/main, its generated Prisma client was regenerated from the merged canonical schema, and it was published on origin/main. Verification completed on 2026-07-21 UTC with the repository-pinned toolchain. The user-owned pnpm-lock.yaml remained outside the commit at worktree blob a37431842e330b3a06b030947c25bebdc72bc2b1; the permanent preservation stash remained 9c4ddf4f7fd4c205d1f083cdbfb9d4a1ee5ce320 at stash@{0}.

The former production authority was a seeded process-local map. Restart erased operator-authored assessments, separate replicas could accept the same assessment id, the request body supplied assessor attribution, and synthetic examples appeared as production history. Production now starts empty and requires one normalized PostgreSQL row per assessment plus one SHA-256 operator- digest lifecycle row. The global assessment-id primary key is the cross-replica idempotency boundary. Updating the lifecycle row serializes assessment creation against exact operator erasure; the row remains a permanent pseudonymous resurrection fence after the retained review package is physically purged.

The authenticated administrator route derives assessedBy only from the validated principal and rejects caller-supplied assessedBy, evaluatedBy, or createdBy. Assessment ids, operator ids, timestamps, evaluator revision, encoded JSON size, counts, scores, failure-code vocabulary, use cases, and every nested delivery-signal field are bounded. Unknown envelope and nested signal fields, unsafe control characters, non-finite numbers, duplicate failure codes, and reserved redaction identities are rejected. The SQL migration independently constrains canonical identifiers, digest and lifecycle shape, timestamps, evaluator revision, JSON object/size bounds, indexes, and the restricted lifecycle foreign key.

Acknowledgement is transaction bound. Operator-state creation and assessment insertion complete in one transaction before the route returns 201. The real PostgreSQL failure-injection test makes the insert fail and proves that neither the assessment nor a newly created lifecycle row commits. Persisted signals, stored evaluator revision, and the complete evaluator projection are schema checked; the projection is recalculated from the stored signals before reads are served, so corrupted or stale database results fail closed rather than silently becoming quality evidence. A Prisma uniqueness error is reported as a duplicate only after the assessment id is confirmed to exist. GET and POST return controlled 503 when the durable repository is absent or unavailable; writes return controlled 400, 409, and 410 for invalid input, a duplicate assessment id, and a deleted operator.

Assessments are minimized, internal, non-exportable review_package evidence. Signals are operational measurements rather than source assets; the implementation neither accepts customer identifiers nor infers customer ownership from assessment ids. Signed profile erasure pseudonymizes the exact authenticated assessor and marks the digest lifecycle deleted/redacted in the same transaction. Adjacent operators remain unchanged, and later writes by the erased principal are rejected before and after physical purge. The shared compliance-retention executor applies the canonical seven-year review-package window, blocks physical removal for an active exact-subject legal hold or exact- category retention exception, deletes due signals and projections, and retains only the digest fence plus purge time.

The restrained Studio Isis operations workspace now states that this surface is for diagnostic quality evidence only, does not authorize release, and must not receive customer ids or personal information. Its response contract validates profiles, templates, assessments, the complete submitted signal projection, and the returned evaluator result before treating a write as acknowledged. It renders honest empty history plus specific invalid-input, duplicate, deleted- operator, malformed-acknowledgement, and storage-unavailable guidance without a stale reload dependency. Inputs and the submit button meet the 44px target. The live browser journey proves the hard Studio boundary, absence of legacy seed ids, caller-spoof rejection, authenticated attribution, durable submit/reload, duplicate rejection, controlled 410/503 states, touch targets, and automatic WCAG 2.1 AA axe analysis.

text
# focused store, authenticated route, and shared retention behavior
pnpm --dir apps/oshun/bff exec vitest run \
  src/isis/model-quality-store.spec.ts \
  src/__tests__/admin-isis-model-quality-route.test.ts \
  src/privacy/compliance-retention-executor.spec.ts \
  --pool=forks --maxWorkers=1 --no-file-parallelism
  3 files passed; 22/22 tests passed in 91.31 seconds

# deterministic generated schema and SQL invariants
pnpm --dir libs/oshun/persistence exec vitest run \
  src/model-quality-schema.spec.ts \
  --pool=forks --maxWorkers=1 --no-file-parallelism
  1 file passed; 2/2 tests passed

pnpm --dir libs/oshun/persistence exec prisma validate \
  --schema prisma/schema.prisma
pnpm exec tsx \
  libs/oshun/persistence/scripts/generate-contract-persistence-schema.ts
  schema valid; generated schema remained byte-identical after rebase
  schema SHA-256 41b537bf99226c97b9215617424c7f99c4287be37d19651fe8f949eaa0568dc8

# fresh disposable database, all 20 migrations, independent handles, restart,
# replica duplicates, insert/erasure race, exact pseudonymization, adjacent
# subject, hold/retention purge and fence, corruption, and rollback
pnpm --dir apps/oshun/bff exec vitest run \
  -c vitest.integration.config.ts \
  src/isis/model-quality-store-durability.integration.spec.ts \
  --pool=forks --maxWorkers=1 --no-file-parallelism
  1 file passed; 2/2 tests passed in 11.64 seconds

# rendered workspace, page, legacy fixture, and route-map behavior
pnpm --dir apps/oshun/web exec vitest run \
  src/components/__tests__/StudioIsisModelQualityAssessmentWorkspace.integration.test.tsx \
  src/components/__tests__/StudioIsisModelQualityAssessmentWorkspace.test.tsx \
  src/components/__tests__/StudioIsisModelQualityAssessmentPage.test.tsx \
  src/components/__tests__/StudioIsisModelQualityAssessmentRouteMap.test.ts \
  --pool=forks --maxWorkers=1 --no-file-parallelism
  4 files passed; 11/11 tests passed

# isolated current-code web/BFF stack, fresh 20-migration PostgreSQL, Chromium,
# rendered boundary/submit/reload/failure states, touch targets, and axe
E2E_BASE_URL=http://127.0.0.1:<isolated-web-port> \
E2E_BFF_URL=http://127.0.0.1:<isolated-bff-port> \
pnpm --dir apps/oshun/web exec playwright test \
  e2e/studio-isis-model-quality-assessment.spec.ts \
  --config=playwright.config.ts --project=chromium --workers=1 --retries=0
  4/4 tests passed in 32.9 seconds

node tools/typecheck/ratchet.mjs \
  --app apps/oshun/bff --tsconfig tsconfig.typecheck.json
node tools/typecheck/ratchet.mjs \
  --app apps/oshun/web --tsconfig tsconfig.typecheck.json
pnpm --dir libs/oshun/persistence exec tsc -p tsconfig.lib.json --noEmit
  BFF backlog 0; web backlog 0; changed persistence library passed

pnpm exec eslint <affected BFF/web/persistence source paths> \
  --max-warnings=0
pnpm exec prettier --check <affected hand-authored source paths>
git diff --check
  affected source lint, formatting, and whitespace checks passed

pnpm --dir apps/oshun/bff run build
  server.js 35,062,216 bytes
  server SHA-256 8afe89f270c87e20db61a54dbd01ec6de0af1882b944908c4f1ae0a781e1520f

# against a fresh migrated 20-migration database and local Redis
pnpm --dir apps/oshun/bff run verify:production-artifact
  Production artifact smoke check passed

The final evidence sources rendered 3,116 docs-center files. pnpm docs:center:verify reported zero structural broken links and zero dead source paths while continuing to surface the same 111 documented non-blocking imported-content links. pnpm docs:center:check reported every generated file fresh; Prettier, whitespace validation, and the V5 documentation validator passed. The Docs Center generator regression suite retained the exact current-main baseline: 47 tests passed and the same three unrelated route-matrix and Metis source-shape assertions failed. No model-quality assessment path appears in those failures.

The web production build was deliberately not run. This 15 GiB host is below the repository's 32 GiB hard memory-safety gate, has no user approval for a Next production build, and the affected web typecheck plus live Chromium/axe flow already passed. The latest observed unrelated current-main web-build baseline compiled and typechecked before failing during /profile/persona prerender on an existing undefined.join; that historical observation is not represented as a result from this slice.

This closes the connected Isis model-quality assessment operational partition only. It does not claim provider/model release enforcement, automatic release authorization, customer-owned assessment records, source-asset validation, remediation execution, or a quality-policy authoring workflow. The parent all- store V1-002 row remains open.

Isis texture-quality diagnostic durability, integrity, privacy, retention, and browser verification#

The texture-quality diagnostic implementation source and published tip is b0728341aa7a065968e9f90eaf9d040501bb4732. It was rebased over the latest non-overlapping origin/main, its generated Prisma client was regenerated from the merged canonical schema, and it was published on origin/main. Verification completed on 2026-07-21 UTC with the repository-pinned toolchain. The user-owned pnpm-lock.yaml remained outside the commit at worktree blob a37431842e330b3a06b030947c25bebdc72bc2b1; the permanent preservation stash remained 9c4ddf4f7fd4c205d1f083cdbfb9d4a1ee5ce320 at stash@{0}.

The former production implementation kept seeded fixtures and submitted evaluations in a process-local map. Restart erased operator-authored evidence, separate replicas could accept the same batch id, and request bodies could supply evaluator attribution. Production now starts empty and requires one normalized PostgreSQL batch row, ordered fixture rows, and one SHA-256 operator- digest lifecycle row. The batch primary key is the cross-replica idempotency boundary. Updating the lifecycle row serializes evaluation against exact operator erasure and concurrent retention purge; it remains a permanent pseudonymous resurrection fence after the review-package rows are deleted.

The authenticated administrator route derives evaluatedBy only from the validated principal and rejects caller-supplied evaluatedBy, assessedBy, or createdBy. Batch, fixture, and operator ids, timestamps, thresholds, scores, fixture count/order/uniqueness, evaluator revision, and the complete request and response envelopes are strictly bounded. Reserved redaction identities, unsafe control characters, non-finite values, malformed timestamps, duplicate fixture ids, and unknown fields are rejected. The SQL migration independently constrains identifier, digest, lifecycle, score, threshold, timestamp, revision, fixture-order, and foreign-key shape.

Acknowledgement is transaction bound. Operator-state creation, batch insertion, and every ordered fixture commit before the route returns 201. The real PostgreSQL failure-injection test proves a failed fixture insert commits neither the batch nor a newly created lifecycle row. Stored scalar projections and the complete returned fixture projection are schema checked. Reads rerun the versioned worst-fixture evaluator from the ordered rows and fail closed on projection, score, evaluator-revision, or operator-digest drift. A Prisma uniqueness error is reported as a duplicate only after confirming that the batch id exists. GET and POST return controlled 503 when durability is absent or unavailable; writes return controlled 400, 409, and 410 for invalid input, duplicates, and a deleted operator.

The rows are minimized, internal, non-exportable review_package evidence. Fixture and batch ids are opaque operational identifiers; the workflow rejects customer ids, personal information, and source assets rather than inferring customer ownership. Signed profile erasure pseudonymizes the exact authenticated evaluator and marks the digest lifecycle deleted/redacted in one transaction. Adjacent operators remain unchanged, and later writes by the erased principal are rejected before and after physical purge. The shared compliance-retention executor applies the canonical seven-year review-package window, blocks removal for an active exact-subject legal hold or exact-category retention exception, deletes each due batch and its cascading fixture rows, and retains only the digest fence and purge time.

The restrained Studio Isis workspace identifies the result as diagnostic-only internal evidence with no customer, asset, or release-authority semantics. Its response contract validates the complete batch acknowledgement and returned fixture projection before showing success, without depending on a stale reload. It renders honest boundary, empty-history, invalid-input, duplicate, deleted- operator, malformed-acknowledgement, and storage-unavailable states. Controls meet the 44px target. Live browser coverage proves the hard Studio boundary, absence of legacy seed ids, spoof rejection, authenticated attribution, durable submit/reload, duplicate and controlled failure states, viewport containment, touch targets, and WCAG 2.1 AA axe analysis.

text
# focused store and authenticated route behavior
pnpm --dir apps/oshun/bff exec vitest run \
  src/isis/texture-quality-store.spec.ts \
  src/__tests__/admin-isis-texture-quality-route.test.ts \
  --pool=forks --maxWorkers=1 --no-file-parallelism
  2 files passed; 12/12 tests passed

# deterministic generated schema, SQL invariants, and persistence types
pnpm exec vitest run \
  --config libs/oshun/persistence/vitest.config.ts \
  libs/oshun/persistence/src/texture-quality-schema.spec.ts \
  --pool=forks --maxWorkers=1 --no-file-parallelism
  1 file passed; 2/2 tests passed

pnpm --dir libs/oshun/persistence exec prisma validate \
  --schema prisma/schema.prisma
pnpm --dir libs/oshun/persistence exec tsc -p tsconfig.lib.json --noEmit
pnpm exec tsx \
  libs/oshun/persistence/scripts/generate-contract-persistence-schema.ts
  schema valid; persistence typecheck passed; generated schema remained fresh

# fresh disposable database, all 22 migrations, independent handles, restart,
# replica duplicates, insertion/erasure serialization, exact pseudonymization,
# adjacent subject, hold/exception-aware purge and fence, corruption, rollback
OSHUN_ADMIN_DATABASE_URL=postgresql://[redacted]/<fresh-database> \
pnpm --dir apps/oshun/bff exec vitest run \
  -c vitest.integration.config.ts \
  src/isis/texture-quality-store-durability.integration.spec.ts \
  --pool=forks --maxWorkers=1 --no-file-parallelism
  1 file passed; 2/2 tests passed

# rendered workspace, page, legacy fixture, and route-map behavior
pnpm --dir apps/oshun/web exec vitest run \
  src/components/__tests__/StudioIsisTextureEnhancementWorkspace.integration.test.tsx \
  src/components/__tests__/StudioIsisTextureEnhancementWorkspace.test.tsx \
  src/components/__tests__/StudioIsisTextureEnhancementPage.test.tsx \
  src/components/__tests__/StudioIsisTextureEnhancementRouteMap.test.ts \
  --pool=forks --maxWorkers=1 --no-file-parallelism
  4 files passed; 10/10 tests passed

# isolated current-source web/BFF stack, fresh 22-migration PostgreSQL,
# desktop Chromium, rendered boundary/submit/reload/failure states, and axe
E2E_BASE_URL=http://127.0.0.1:<isolated-web-port> \
E2E_BFF_URL=http://127.0.0.1:<isolated-bff-port> \
pnpm --dir apps/oshun/web exec playwright test \
  e2e/studio-isis-texture-enhancement.spec.ts \
  --config=playwright.config.ts --project=chromium --workers=1 --retries=0
  4/4 tests passed

# exact production BFF bundle, Pixel 7 viewport, touch targets, containment, axe
E2E_BASE_URL=http://127.0.0.1:<isolated-web-port> \
E2E_BFF_URL=http://127.0.0.1:<production-bff-port> \
pnpm --dir apps/oshun/web exec playwright test \
  e2e/studio-isis-texture-enhancement.spec.ts \
  --config=playwright.config.ts --project="Pixel 7" --workers=1 --retries=0 \
  --grep="mobile"
  1/1 test passed

node tools/typecheck/ratchet.mjs \
  --app apps/oshun/bff --tsconfig tsconfig.typecheck.json
node tools/typecheck/ratchet.mjs \
  --app apps/oshun/web --tsconfig tsconfig.typecheck.json
  BFF backlog 0; web backlog 0

pnpm exec eslint <affected BFF/web/persistence source paths> \
  --max-warnings=0 --no-ignore
pnpm exec prettier --check <affected hand-authored source paths>
git diff --check
  affected source lint, formatting, and whitespace checks passed

pnpm --dir apps/oshun/bff run build
  production server.js bundle built successfully (33.5 MiB)

# against a fresh migrated 22-migration database and local Redis
pnpm --dir apps/oshun/bff run verify:production-artifact
  Production artifact smoke check passed

The final evidence sources rendered 3,116 Docs Center files. pnpm docs:center:verify reported zero structural broken links and zero dead source paths across 3,485 entities while surfacing 112 documented non-blocking links inside imported content. pnpm docs:center:check reported every generated file fresh, and pnpm docs:center:pytest passed all 52 generator regression tests. Prettier, whitespace validation, and the V5 documentation validator also passed.

The web production build was deliberately not run. This 15 GiB host is below the repository's 32 GiB hard memory-safety gate and no user approval was provided. The affected web typecheck plus live desktop and mobile Chromium/axe flows passed instead; this evidence does not represent a Next production build as green.

This closes the connected Isis texture-quality diagnostic operational partition only. It does not claim upstream asset scoring, provider/model release enforcement, automatic release authorization, customer-owned diagnostic records, source-asset validation, remediation execution, or a quality-policy authoring workflow. The parent all-store V1-002 row remains open.

Isis content-safety diagnostic durability, integrity, privacy, retention, and browser verification#

The content-safety diagnostic implementation source and published tip is 181979d868d606715a4d71179f16e1df827efad2. It was rebased over the latest non-overlapping origin/main, then its generated Prisma client was regenerated from the combined Tara + Content Safety canonical schema after a later remote persistence update. The final source commit is present on origin/main. Verification completed on 2026-07-21 UTC with the repository-pinned toolchain. The user-owned pnpm-lock.yaml remained outside the commit at worktree blob a37431842e330b3a06b030947c25bebdc72bc2b1; the permanent preservation stash remained 9c4ddf4f7fd4c205d1f083cdbfb9d4a1ee5ce320 at stash@{0}.

The former production implementation kept two seeded examples and subsequent operator submissions in a process-local map. Restart erased submitted evidence, separate replicas could accept the same screen id, raw source messages could not be recovered for projection verification, and request bodies could supply no trustworthy evaluator attribution. Production now starts empty and requires one normalized PostgreSQL screen row, its ordered source-message rows, its ordered evaluator-issue rows, and one SHA-256 operator-digest lifecycle row. The screen primary key is the cross-replica idempotency boundary. Updating the lifecycle row serializes evaluation against exact operator erasure and concurrent retention purge; it remains a permanent pseudonymous resurrection fence after the review-package rows are deleted.

The authenticated administrator route derives screenedBy only from the validated principal and rejects caller-supplied screenedBy, evaluatedBy, assessedBy, or createdBy. The request permits only screenId and 1–64 ordered { role, content } messages, with a fixed role vocabulary, per-message and aggregate text bounds, canonical ids, and no control characters. Unknown top-level or nested fields—including customer/source metadata—are rejected. Screen ids, operator ids, timestamps, token counts, quality scores, issue count, issue type/severity/text, evaluator revision, sort order, aggregate counts, and the complete request/response envelopes are strictly bounded. The SQL migration independently constrains identifier, digest, lifecycle, role, content, issue vocabulary, score, timestamp, ordinal, foreign-key, index, and cascade shape.

Acknowledgement is transaction bound. Operator-state creation, screen insertion, and every nested message/issue row commit before the route returns 201. The real PostgreSQL failure-injection test proves a failed nested insert commits neither the screen nor a newly created lifecycle row. A Prisma uniqueness error is reported as a duplicate only after confirming that the screen id exists. Every database read reconstructs the ordered messages and issues, reruns the versioned validateSample evaluator, and fails closed on token, quality, flagged-verdict, issue projection, evaluator-revision, ordering, or operator- digest drift. GET and POST return controlled 503 when durability is absent or unavailable; writes return controlled 400, 409, and 410 for invalid input, duplicates, and a deleted operator.

The rows are minimized, internal, non-exportable review_package evidence. Input is limited to approved de-identified internal fixtures; customer content, customer ids, source assets, and personal information are prohibited rather than being assigned invented customer ownership. Signed profile erasure pseudonymizes every screen attached to the exact authenticated evaluator digest and marks the lifecycle deleted/redacted in one transaction. The digest/FK is the privacy authority, so even a corrupted display attribution cannot obstruct erasure; ordinary reads still reject that corruption. Adjacent operators remain unchanged, and later writes by the erased principal are rejected before and after physical purge. The shared compliance-retention executor applies the canonical seven-year review-package window, blocks removal for an active exact- subject legal hold or exact-category retention exception, deletes each due screen and its cascading message/issue rows, and retains only the digest fence and purge time.

The restrained Studio Isis workspace labels the result as diagnostic-only internal evidence with no runtime-moderation, customer, asset, or release- authority semantics. Its response contract validates the complete screen acknowledgement, evaluator attribution/revision, issue/verdict consistency, newest-first uniqueness, and exact recomputed aggregate before showing success. It inserts the acknowledged screen immediately without depending on a stale GET and proves the result survives reload. It renders honest boundary, empty- history, duplicate, deleted-operator, malformed-response/acknowledgement, and storage-unavailable states. Controls meet the 44px target, and long identifiers remain contained. Live browser coverage proves the hard Studio boundary, absence of legacy seed ids, spoof/customer-field rejection, authenticated attribution, durable submit/reload, controlled failures, desktop and Pixel 7 containment, touch targets, and WCAG 2.1 AA axe analysis.

text
# focused store and authenticated route behavior
pnpm --dir apps/oshun/bff exec vitest run \
  src/isis/content-safety-store.spec.ts \
  src/__tests__/admin-isis-content-safety-route.test.ts \
  --pool=forks --maxWorkers=1 --no-file-parallelism
  2 files passed; 12/12 tests passed

# deterministic generated schema, SQL invariants, and persistence types
pnpm exec vitest run \
  --config libs/oshun/persistence/vitest.config.ts \
  libs/oshun/persistence/src/content-safety-schema.spec.ts \
  --pool=forks --maxWorkers=1 --no-file-parallelism
  1 file passed; 2/2 tests passed

pnpm exec prisma validate \
  --schema libs/oshun/persistence/prisma/schema.prisma
pnpm --dir libs/oshun/persistence exec tsc -p tsconfig.lib.json --noEmit
pnpm exec prisma generate \
  --schema libs/oshun/persistence/prisma/schema.prisma
  merged schema valid; persistence typecheck and client generation passed

# fresh disposable database, all 24 migrations, independent handles, restart,
# replica duplicates, same-operator concurrency, evaluation/erasure and purge
# serialization, exact pseudonymization including corrupted attribution,
# adjacent subject, hold/exception-aware purge and fence, corruption, rollback
OSHUN_ADMIN_DATABASE_URL=postgresql://[redacted]/<fresh-database> \
pnpm --dir apps/oshun/bff exec vitest run \
  -c vitest.integration.config.ts \
  src/isis/content-safety-store-durability.integration.spec.ts \
  --pool=forks --maxWorkers=1 --no-file-parallelism
  1 file passed; 2/2 tests passed

# rendered workspace, page, route-map, and strict acknowledgement behavior
pnpm --dir apps/oshun/web exec vitest run \
  src/components/__tests__/StudioIsisContentSafetyWorkspace.integration.test.tsx \
  src/components/__tests__/StudioIsisContentSafetyWorkspace.test.tsx \
  src/components/__tests__/StudioIsisContentSafetyPage.test.tsx \
  src/components/__tests__/StudioIsisContentSafetyRouteMap.test.ts \
  --pool=forks --maxWorkers=1 --no-file-parallelism
  4 files passed; 10/10 tests passed

# isolated current-source web/BFF stack, fresh 23-migration PostgreSQL at the
# time of the browser run; desktop Chromium + Pixel 7, live durable
# submit/reload, controlled failures, containment, touch targets, and axe
E2E_BASE_URL=http://127.0.0.1:<isolated-web-port> \
E2E_BFF_URL=http://127.0.0.1:<isolated-bff-port> \
E2E_WEB_ONLY=1 \
pnpm --dir apps/oshun/web exec playwright test \
  e2e/studio-isis-content-safety.spec.ts \
  --config=playwright.config.ts \
  --project=chromium --project=mobile-chrome --workers=1
  5/5 tests passed

node tools/typecheck/ratchet.mjs \
  --app apps/oshun/bff --tsconfig tsconfig.typecheck.json
node tools/typecheck/ratchet.mjs \
  --app apps/oshun/web --tsconfig tsconfig.typecheck.json
  BFF backlog 0; web backlog 0

pnpm exec eslint <affected BFF/web/persistence source paths> \
  --max-warnings=0 --no-ignore
pnpm exec prettier --check <affected hand-authored source paths>
git diff --check
  affected source lint, formatting, and whitespace checks passed

pnpm --dir apps/oshun/bff run build
  production server.js bundle built successfully (33.5 MiB)

# final merged tree, fresh migrated 24-migration database, and local Redis
pnpm --dir apps/oshun/bff run verify:production-artifact
  Production artifact smoke check passed

The pre-commit hook's redundant Nx affected-typecheck step failed while its shared daemon could not process the project graph; it did not report a source type error. The hook's documented SKIP_TYPECHECK=1 escape was used only after the exact BFF/web zero-backlog ratchets and persistence typecheck above passed on the staged tree. All lint-staged, asset-lock, source-policy, and V5 documentation checks in the commit hook passed.

The final evidence sources rendered 3,116 Docs Center files. The integrity gate reported zero structural broken links and zero dead source paths across 3,485 entities; it also surfaced 112 pre-existing, non-blocking broken links inside imported content. The final freshness check and generator regression suite passed, including all 54 Python tests.

The web production build was deliberately not run. This 15 GiB host is below the repository's 32 GiB hard memory-safety gate and no user approval was provided. The affected web typecheck plus live desktop and mobile Chromium/axe flows passed instead; this evidence does not represent a Next production build as green.

This closes the connected Isis content-safety diagnostic operational partition only. It does not claim runtime moderation, provider/model release enforcement, automatic release authorization, customer-owned diagnostic records, source- asset validation, remediation execution, or a safety-policy authoring workflow. The parent all-store V1-002 row remains open.

Isis resource-recommendation durability, integrity, privacy, retention, and browser verification#

The resource-recommendation implementation source and published tip is e1a7ae32087b1b17cd3d37cef9df7a3afd791dd7. It was rebased over the latest non-overlapping origin/main, passed the complete source commit policy, and is present on origin/main. Verification completed on 2026-07-21 UTC with the repository-pinned toolchain. The user-owned pnpm-lock.yaml remained outside the commit at worktree blob a37431842e330b3a06b030947c25bebdc72bc2b1; the permanent preservation stash remained 9c4ddf4f7fd4c205d1f083cdbfb9d4a1ee5ce320 at stash@{0}.

The former production surface mixed five deploy-time model examples with a process-local recommendation map. Restart erased operator decisions, separate replicas could accept the same recommendation id, history was pre-seeded rather than observed, and neither stored downgrade math nor caller attribution had a durable integrity boundary. Production now separates an immutable, revision-labelled five-model catalog from an initially empty normalized PostgreSQL history. The recommendation primary key is the cross-replica idempotency boundary. A SHA-256 operator lifecycle row serializes writes against exact-subject erasure and retention purge, then remains as a pseudonymous resurrection fence after the recommendation rows are physically deleted.

The catalog revision is exactly isis-resource-recommendation-catalog-v1. Its prices and quality scores are explicit configured estimates, not current provider telemetry, invoices, or a live pricing authority. The route records an internal recommendation only: it does not switch a model, reserve or reconcile budget, enforce a fallback, authorize publication, or claim provider availability. The authenticated admin POST accepts only canonical recommendationId, catalog currentModel, and one fixed reason. It derives recommendedBy from the validated principal and rejects caller-supplied attribution, customer ids, source assets, content, and all other unknown fields. The migration independently constrains ids, operator digests, model/reason vocabulary, complete-or-null downgrade projections, percentage bounds, exact catalog revision, attribution, timestamps, foreign keys, and the indexes used for ordering, attribution, and retention.

Acknowledgement is transaction bound. Operator-state creation and the complete recommendation projection commit before POST returns 201; a failed insert leaves neither a recommendation nor a newly created lifecycle row. Independent connections prove duplicate races resolve to one durable winner, while same-operator writes serialize correctly with erasure and purge. Every PostgreSQL read validates the canonical row, recomputes the downgrade from the immutable catalog inputs, and fails closed on projection, revision, attribution digest, timestamp, or vocabulary drift. GET also recomputes the exact newest- first history and aggregate rather than trusting client math. Production composition requires the durable repository before traffic; unavailable reads or writes return controlled 503, and invalid, duplicate, or erased-operator writes return controlled 400, 409, or 410.

These rows are minimized, internal, non-exportable review_package evidence. The surface prohibits customer/source/content/PII fields instead of inventing a customer owner for operational model-cost notes. Signed profile erasure finds rows by the exact authenticated operator digest, replaces their display attribution with a digest-derived redaction label, and marks the lifecycle deleted/redacted in one transaction. This remains effective when display attribution is corrupt; ordinary reads fail closed on the same corruption. Adjacent operators remain unchanged, and the erased principal cannot recreate history before or after purge. The shared review-package executor applies the canonical seven-year window, honors an exact-subject legal hold or exact- category retention exception, physically removes due recommendation rows, and retains only the lifecycle digest fence and purge time.

The restrained Studio Isis workspace presents the catalog as a cost-governance worksheet with the fallback ladder as its visual anchor. It labels all numbers as configured estimates, prohibits customer ids/assets/content/PII, and states that the surface is recommendation-only. Its strict response contract independently recomputes projection math, catalog metadata, newest-first uniqueness, attribution, and aggregate totals before rendering success. A transaction-bound acknowledgement is inserted immediately and survives reload; there is no synthetic seed history. Honest empty-history, malformed response, malformed acknowledgement, duplicate, erased-operator, and storage-unavailable states are covered independently. Desktop and Pixel-class browser coverage proves authenticated attribution, spoof/customer-field rejection, durable submit/reload, controlled failures, long-content containment, 44px touch targets, and the repository's WCAG 2.1 AA axe serious/critical scan.

text
# focused store and authenticated route behavior
pnpm --dir apps/oshun/bff exec vitest run \
  src/isis/resource-recommendation-store.spec.ts \
  src/__tests__/admin-isis-resource-recommendations-route.test.ts \
  --pool=forks --maxWorkers=1 --no-file-parallelism
  2 files passed; 12/12 tests passed

# deterministic SQL/schema invariants and package-local persistence types
pnpm exec vitest run \
  --config libs/oshun/persistence/vitest.config.ts \
  libs/oshun/persistence/src/resource-recommendation-schema.spec.ts \
  --pool=forks --maxWorkers=1 --no-file-parallelism
  1 file passed; 2/2 tests passed

pnpm exec prisma validate \
  --schema libs/oshun/persistence/prisma/schema.prisma
pnpm exec prisma generate \
  --schema libs/oshun/persistence/prisma/schema.prisma
pnpm --dir libs/oshun/persistence exec tsc --noEmit
  schema valid; generated client stable; persistence typecheck passed
  schema SHA-256 33b24482de95405e2a0585377bc3261d28a67c19526bbca46fb04173fff8746a
  generated tree SHA-256 59bc60211bf3405ba341d264007a483ff66915f87ec97bf1ebb20206295d146c

# fresh disposable database; all 27 migrations; independent handles; restart,
# replica duplicates, same-operator concurrency, erasure and purge races,
# adjacent isolation, hold/exception, corrupted projection/attribution, rollback
OSHUN_ADMIN_DATABASE_URL=postgresql://[redacted]/<fresh-database> \
pnpm --dir apps/oshun/bff exec vitest run \
  -c vitest.integration.config.ts \
  src/isis/resource-recommendation-store-durability.integration.spec.ts \
  --pool=forks --maxWorkers=1 --no-file-parallelism
  1 file passed; 2/2 tests passed

# rendered workspace, page, route-map, and strict transaction acknowledgement
pnpm --dir apps/oshun/web exec vitest run \
  src/components/__tests__/StudioIsisResourceRecommendationsWorkspace.integration.test.tsx \
  src/components/__tests__/StudioIsisResourceRecommendationsWorkspace.test.tsx \
  src/components/__tests__/StudioIsisResourceRecommendationsPage.test.tsx \
  src/components/__tests__/StudioIsisResourceRecommendationsRouteMap.test.ts \
  --pool=forks --maxWorkers=1 --no-file-parallelism
  4 files passed; 11/11 tests passed

# isolated current-source web/BFF stack and fresh migrated PostgreSQL; desktop
# Chromium + Pixel-class mobile, durable reload, failure contracts, containment,
# touch targets, and repository auto-axe serious/critical analysis
E2E_BASE_URL=http://127.0.0.1:<isolated-web-port> \
E2E_BFF_URL=http://127.0.0.1:<isolated-bff-port> \
E2E_WEB_ONLY=1 \
pnpm --dir apps/oshun/web exec playwright test \
  e2e/studio-isis-resource-recommendations.spec.ts \
  --config=playwright.config.ts \
  --project=chromium --project=mobile-chrome --workers=1
  8/8 tests passed

node tools/typecheck/ratchet.mjs \
  --app apps/oshun/bff --tsconfig tsconfig.typecheck.json
node tools/typecheck/ratchet.mjs \
  --app apps/oshun/web --tsconfig tsconfig.typecheck.json
pnpm --dir libs/oshun/persistence exec tsc --noEmit
  BFF backlog 0; web backlog 0; persistence typecheck passed

pnpm exec eslint <affected BFF/web/persistence source paths> \
  --max-warnings=0 --no-ignore
pnpm exec prettier --check <affected hand-authored source paths>
git diff --check
  affected source lint, formatting, and whitespace checks passed

# direct production-entry compilation and current-source runtime smoke
pnpm exec esbuild apps/oshun/bff/src/server.ts \
  --bundle --platform=node --format=esm --outfile=<temporary-server.js>
  production entry compiled successfully (34.2 MiB)

OSHUN_ADMIN_DATABASE_URL=postgresql://[redacted]/<fresh-database> \
  <current-source BFF process + authenticated GET/POST/restart readback>
  empty GET, committed POST, and durable readback passed

The full pre-commit policy passed after correcting two repository integrity defects it exposed: the Isis token-budget library now has its existing type:lib Nx tag, and the persistence package has a package-local typed pg boundary for its already tracked maintenance scripts. Lint-staged formatting and ESLint, asset locking, convention ratchets, V5 documentation validation, and all four affected Nx typecheck targets passed. The source commit was then rebased without conflict over a non-overlapping Tara web change and pushed.

The production entry compiled, but no exact bundled-artifact runtime claim is made. Artifact smoke investigation exposed existing BFF bundle ownership issues around dynamic pg loading and the native sharp loader; current-source BFF runtime against fresh PostgreSQL proved this route instead. The web production build was deliberately not run: this 15 GiB host is below the repository's 32 GiB hard memory-safety gate, and no user approval was provided. The affected web typecheck plus live desktop/mobile Chromium and axe coverage passed; this evidence does not represent a Next production build as green.

This closes the connected Isis resource-recommendation operational partition only. It does not claim live provider pricing, invoice reconciliation, model routing/execution, budget enforcement, runtime fallback, release authorization, customer-owned records, or provider health. The parent all-store V1-002 row remains open.

Isis intelligent-routing durability, integrity, privacy, retention, and browser verification#

The intelligent-routing implementation source and published tip is 1f90b287735cf6087e64aec76a999b4317891036. It was rebased without conflict over the latest non-overlapping origin/main, passed the complete source commit policy, and is present on origin/main. Verification completed on 2026-07-21 UTC with the repository-pinned toolchain. The user-owned pnpm-lock.yaml remained outside the commit at worktree blob a37431842e330b3a06b030947c25bebdc72bc2b1; the permanent preservation stash remained 9c4ddf4f7fd4c205d1f083cdbfb9d4a1ee5ce320 at stash@{0}.

The former production surface coupled deploy-time routing examples to a process-local mutable history. Restart lost decisions, replicas could accept the same route id independently, the browser was trusted to report aggregate and downgrade values, and caller-provided operator attribution had no durable identity boundary. Production now separates the immutable shared fallback catalog from an initially empty normalized PostgreSQL routing history. The route primary key is the cross-replica idempotency boundary. A SHA-256 operator lifecycle row serializes route creation against exact-subject erasure and purge, then persists as a pseudonymous resurrection fence after history is physically deleted.

The catalog revision is exactly isis-resource-recommendation-catalog-v1. Its cost and quality values are explicit configured estimates, not current provider prices, invoices, health, availability, or execution telemetry. A recorded route is an internal cost-governance decision: it does not switch a live model, reserve or reconcile budget, execute a fallback, authorize release, or mutate customer content. The authenticated admin POST accepts only canonical routing inputs. It derives routedBy from the validated principal and rejects caller attribution, customer ids, source assets, content, and unknown fields. The migration independently constrains ids, operator digests, catalog vocabulary and revision, complete projections, signed percentage bounds from -100 through 100, attribution, timestamps, foreign keys, and read/retention indexes.

Acknowledgement is transaction bound. Operator-state creation and the complete route projection commit before POST returns success; rollback leaves neither a route nor a newly created lifecycle row. Independent connections prove duplicate route races converge on one durable winner while same-operator writes serialize with erasure and purge. Every PostgreSQL read validates the canonical row and recomputes the projection from immutable catalog inputs. It fails closed on projection, revision, attribution digest, timestamp, ordering, vocabulary, or aggregate drift. Production composition requires the durable repository before traffic, and unavailable or invalid operations return controlled responses instead of synthetic history.

These minimized rows are internal, non-exportable review_package evidence. The API excludes customer/source/content/PII fields instead of manufacturing a customer owner for an operational routing note. Signed profile erasure finds rows through the exact authenticated operator digest, replaces display attribution with a digest-derived redaction label, and marks the lifecycle deleted and redacted in one transaction. Adjacent operators remain byte-for-byte unchanged, and the erased operator cannot recreate history before or after physical purge. The shared review-package executor enforces the canonical seven-year retention window, defers deletion for an exact-subject legal hold or exact-category retention exception, physically removes due routes, and retains only the lifecycle digest fence and purge time.

The restrained Studio Isis worksheet keeps the fallback ladder as its visual anchor, labels values as configured estimates, and states that the action records a recommendation rather than performing live routing. Its strict response parser independently recomputes catalog projection, revision, newest-first ordering, attribution, and aggregate totals before rendering success. A transaction-bound optimistic acknowledgement appears immediately and survives reload; no seeded history is shown. Honest empty-history, malformed response, failed write, auth, and storage-unavailable states are covered. The route map marks the primary intelligent-routing page as mounted and four adjacent destinations as documented-contract, explicitly stating that no page is mounted for them. Desktop and Pixel-class automation covers authenticated attribution, spoof/customer-field rejection, durable submit/reload, containment, mobile interaction, and the repository's WCAG 2.1 AA serious/critical axe scan.

text
# focused store and authenticated route behavior
pnpm --dir apps/oshun/bff exec vitest run \
  src/isis/intelligent-routing-store.spec.ts \
  src/__tests__/admin-isis-intelligent-routing-route.test.ts \
  --pool=forks --maxWorkers=1 --no-file-parallelism
  2 files passed; 12/12 tests passed

# deterministic SQL/schema invariants and package-local persistence types
pnpm exec vitest run \
  --config libs/oshun/persistence/vitest.config.ts \
  libs/oshun/persistence/src/intelligent-routing-schema.spec.ts \
  --pool=forks --maxWorkers=1 --no-file-parallelism
  1 file passed; 2/2 tests passed

pnpm exec prisma validate \
  --schema libs/oshun/persistence/prisma/schema.prisma
pnpm exec prisma generate \
  --schema libs/oshun/persistence/prisma/schema.prisma
pnpm --dir libs/oshun/persistence exec tsc --noEmit
  schema valid; generated client stable; persistence typecheck passed

# fresh disposable database; all 28 migrations; independent handles; restart,
# replica duplicates, same-operator concurrency, erasure and purge races,
# adjacent isolation, hold/exception, corruption, and failed-write rollback
OSHUN_ADMIN_DATABASE_URL=postgresql://[redacted]/<fresh-database> \
pnpm --dir apps/oshun/bff exec vitest run \
  -c vitest.integration.config.ts \
  src/isis/intelligent-routing-store-durability.integration.spec.ts \
  --pool=forks --maxWorkers=1 --no-file-parallelism
  1 file passed; 2/2 tests passed

# rendered workspace, strict response contract, and honest route map
pnpm --dir apps/oshun/web exec vitest run \
  src/components/__tests__/StudioIsisIntelligentRoutingWorkspace.integration.test.tsx \
  src/components/__tests__/StudioIsisIntelligentRoutingWorkspace.test.tsx \
  src/components/__tests__/StudioIsisIntelligentRoutingRouteMap.test.ts \
  --pool=forks --maxWorkers=1 --no-file-parallelism
  3 files passed; 10/10 tests passed

# isolated current-source web/BFF stack and fresh migrated PostgreSQL; desktop
# Chromium + Pixel-class mobile, empty history, durable reload, spoof rejection,
# failure contracts, containment, and auto-axe serious/critical analysis
E2E_BASE_URL=http://127.0.0.1:<isolated-web-port> \
E2E_BFF_URL=http://127.0.0.1:<isolated-bff-port> \
E2E_BFF_PORT=<isolated-bff-port> \
E2E_WEB_PORT=<isolated-web-port> \
E2E_SKIP_STUDY=1 \
pnpm --dir apps/oshun/web exec playwright test \
  e2e/studio-isis-intelligent-routing.spec.ts \
  --config=playwright.config.ts \
  --project=chromium --project=mobile-chrome --workers=1
  8/8 tests passed

node tools/typecheck/ratchet.mjs \
  --app apps/oshun/bff --tsconfig tsconfig.typecheck.json
node tools/typecheck/ratchet.mjs \
  --app apps/oshun/web --tsconfig tsconfig.typecheck.json
pnpm --dir libs/oshun/persistence exec tsc --noEmit
  BFF backlog 0; web backlog 0; persistence typecheck passed

pnpm exec eslint <affected BFF/web/persistence source paths> \
  --max-warnings=0 --no-ignore
pnpm exec prettier --check <affected source paths>
git diff --check
  affected source lint, formatting, and whitespace checks passed

# direct production-entry compilation
pnpm exec esbuild apps/oshun/bff/src/server.ts \
  --bundle --platform=node --format=esm \
  --outfile=/tmp/oshun-intelligent-routing-server.js
node --check /tmp/oshun-intelligent-routing-server.js
  compilation and syntax check passed; 35,880,273 bytes

The source pre-commit policy passed lint-staged ESLint and formatting, convention and asset checks, and all four affected Nx typecheck targets: @oshun/bff, @oshun/persistence, @oshun/web, and @oshun/prompt-injection-evals. The source commit was then rebased without a content conflict over non-overlapping BFF package, Tara, Aphrodite, and Yemaya changes and pushed to origin/main.

The production entry compiled and passed Node syntax validation, but no exact bundled-artifact runtime smoke claim is made. The web production build was deliberately not run: this 15 GiB host is below the repository's 32 GiB hard memory-safety gate, and no user approval was provided. The affected web typecheck plus live desktop/mobile Chromium and axe coverage passed; this evidence does not represent a Next production build as green.

Evidence publication regenerated 3,116 docs-center files across 54 domains. pnpm docs:center:check found every generated file fresh, pnpm docs:center:verify found zero structural broken links and zero dead source paths, and pnpm docs:center:pytest passed 54/54 generator regressions. The integrity report also surfaced 112 pre-existing broken links inside imported content as its explicitly non-blocking category; they are not represented here as resolved by this routing slice. The V5 documentation validator passed.

This closes the connected Isis intelligent-routing operational partition only. It does not claim current provider price or health, invoice reconciliation, model execution, budget enforcement, runtime fallback, release authorization, customer-owned routing records, or mounted pages for the four documented adjacent destinations. The parent all-store V1-002 row remains open.

Isis cost-tracking durability, integrity, privacy, retention, and browser verification#

The cost-tracking implementation source is 8bab273a22d48801748efc21c7ed062166824288. It was rebased over the latest non-overlapping origin/main, passed the complete source commit policy, and is present on origin/main. A two-field Tara compatibility correction exposed by the final-tree BFF type ratchet was independently tested and published through verification tip ae490aa4fb500ad0c6e471999eb5ed70b2f34727. Verification completed on 2026-07-21 UTC with the repository-pinned toolchain. The user-owned pnpm-lock.yaml remained outside both commits at worktree blob a37431842e330b3a06b030947c25bebdc72bc2b1; the permanent preservation stash remained 9c4ddf4f7fd4c205d1f083cdbfb9d4a1ee5ce320 at stash@{0}.

The former surface rendered a hard-coded pricing table without a durable operational history. Production now separates an immutable 12-model configured pricing catalog, revision isis-token-budget-pricing-v1, from an initially empty normalized PostgreSQL cost history. Record ids are strict opaque machine tokens and cross-replica idempotency keys. A SHA-256 operator lifecycle row serializes record creation against exact-subject erasure and purge, then remains as a pseudonymous resurrection fence after history is physically deleted.

The catalog rates and computed costs are explicitly configured estimates, not live provider prices, invoices, availability, health, or execution telemetry. The authenticated admin POST accepts only canonical model and token inputs, derives recordedBy from the validated principal, and rejects caller attribution, customer ids, source assets, content, precomputed rates or costs, catalog metadata, digests, and unknown fields. The migration independently constrains ids, operator digests, catalog vocabulary and revision, token and rate bounds, exact cost attribution, timestamps, foreign keys, and read/retention indexes.

Acknowledgement is transaction bound: the lifecycle row and complete cost record commit before POST returns success, and rollback leaves neither a record nor a newly created lifecycle row. Independent connections prove duplicate-id races converge on one durable winner while same-operator writes serialize with erasure and purge. Every PostgreSQL read validates canonical fields and recomputes rates, costs, catalog revision, attribution digest, ordering, and rollup totals. Invalid or corrupted state fails closed. Production composition requires the durable repository before traffic and returns controlled unavailable responses rather than seeded or synthetic history.

These minimized rows are internal, non-exportable review_package evidence. They deliberately contain no customer/source/content identity. Signed profile erasure finds rows through the exact authenticated operator digest, replaces display attribution with a digest-derived redaction label, and marks the lifecycle deleted and redacted atomically. Adjacent operators remain unchanged, and the erased operator cannot recreate history before or after physical purge. The shared review-package executor enforces the canonical seven-year retention window, defers deletion for exact-subject legal holds or exact-category retention exceptions, physically removes due records, and keeps only the digest-only lifecycle fence and purge time.

The restrained Studio Isis cost-governance worksheet makes the catalog and estimate boundary explicit, shows honest empty history, and records configured estimates rather than implying provider billing or enforcement. Its strict response parser independently recomputes catalog projections, revision, newest-first ordering, attribution, individual costs, and aggregate totals before rendering success. A transaction-bound acknowledgement survives reload; malformed responses, failed writes, authentication failures, and unavailable storage fail closed. The route map marks the primary cost-tracking page as mounted and four adjacent destinations as documented-contract, explicitly stating that they have no mounted page. Desktop and Pixel-class automation covers authorization, attribution, spoof and unknown-model rejection, idempotency, durable submit/reload, containment, touch interaction, and the repository's WCAG 2.1 AA serious/critical axe scan.

text
# focused durable store and authenticated route behavior
pnpm --dir apps/oshun/bff exec vitest run \
  src/isis/cost-tracking-store.spec.ts \
  src/__tests__/admin-isis-cost-tracking-route.test.ts \
  --pool=forks --maxWorkers=1 --no-file-parallelism
  2 files passed; 14/14 tests passed

# deterministic SQL/schema invariants and package-local persistence types
pnpm exec vitest run \
  --config libs/oshun/persistence/vitest.config.ts \
  libs/oshun/persistence/src/cost-tracking-schema.spec.ts \
  --pool=forks --maxWorkers=1 --no-file-parallelism
  1 file passed; 2/2 tests passed

pnpm exec prisma validate \
  --schema libs/oshun/persistence/prisma/schema.prisma
pnpm exec prisma generate \
  --schema libs/oshun/persistence/prisma/schema.prisma
pnpm --dir libs/oshun/persistence exec tsc --noEmit
  schema valid; generated client stable; persistence typecheck passed

# fresh disposable database; all 30 migrations; independent handles; restart,
# replica duplicates, same-operator races, erasure/purge, adjacent isolation,
# hold/exception, corruption, attribution recomputation, and rollback
OSHUN_ADMIN_DATABASE_URL=postgresql://[redacted]/<fresh-database> \
pnpm --dir apps/oshun/bff exec vitest run \
  -c vitest.integration.config.ts \
  src/isis/cost-tracking-store-durability.integration.spec.ts \
  --pool=forks --maxWorkers=1 --no-file-parallelism
  1 file passed; 2/2 tests passed

# rendered workspace, strict response contract, and honest route map
pnpm --dir apps/oshun/web exec vitest run \
  src/components/__tests__/StudioIsisCostTrackingWorkspace.integration.test.tsx \
  src/components/__tests__/StudioIsisCostTrackingWorkspace.test.tsx \
  src/components/__tests__/StudioIsisCostTrackingRouteMap.test.ts \
  --pool=forks --maxWorkers=1 --no-file-parallelism
  3 files passed; 9/9 tests passed

# isolated current-source web/BFF stack and fresh migrated PostgreSQL; desktop
# Chromium + Pixel-class mobile, empty history, durable reload, spoof rejection,
# fail-closed contracts, containment, touch targets, and auto-axe analysis
E2E_BASE_URL=http://127.0.0.1:<isolated-web-port> \
E2E_BFF_URL=http://127.0.0.1:<isolated-bff-port> \
E2E_BFF_PORT=<isolated-bff-port> \
E2E_WEB_PORT=<isolated-web-port> \
E2E_SKIP_STUDY=1 \
pnpm --dir apps/oshun/web exec playwright test \
  e2e/studio-isis-cost-tracking.spec.ts \
  --config=playwright.config.ts \
  --project=chromium --project=mobile-chrome --workers=1
  8/8 tests passed

node tools/typecheck/ratchet.mjs \
  --app apps/oshun/bff --tsconfig tsconfig.typecheck.json
node tools/typecheck/ratchet.mjs \
  --app apps/oshun/web --tsconfig tsconfig.typecheck.json
pnpm --dir libs/oshun/persistence exec tsc --noEmit
  BFF backlog 0; web backlog 0; persistence typecheck passed

pnpm exec eslint <affected BFF/web/persistence source paths> \
  --max-warnings=0 --no-ignore
pnpm exec prettier --check <affected source paths>
git diff --check
  affected source lint, formatting, and whitespace checks passed

# direct production-entry compilation
pnpm exec esbuild apps/oshun/bff/src/server.ts \
  --bundle --platform=node --format=esm \
  --outfile=/tmp/oshun-cost-tracking-server.js
node --check /tmp/oshun-cost-tracking-server.js
  compilation and syntax check passed; 35,987,898 bytes;
  SHA-256 4e021928bfb668ed28f8220f7c8bc51c07e49d0ee31a4b7a43ac8b802f476fa2

The source pre-commit policy passed lint-staged ESLint and formatting, convention and asset checks, V5 documentation validation, and all four affected Nx typecheck targets: @oshun/bff, @oshun/persistence, @oshun/web, and @oshun/prompt-injection-evals. After publication, the final-tree ratchet found an independently introduced required Tara concept field omitted at two construction sites. The minimal targetPublishDate: null compatibility fix passed 109 route tests with one intentional skip, the BFF ratchet returned to zero backlog, and that fix was rebased and published before the final cost E2E run.

The production entry compiled and passed Node syntax validation. The web production build was deliberately not run: this 15 GiB host is below the repository's 32 GiB hard memory-safety gate, and no user approval was provided. The affected web typecheck plus live desktop/mobile Chromium and axe coverage passed; this evidence does not represent a Next production build as green.

Evidence publication regenerated 3,116 docs-center files across 54 domains. pnpm docs:center:check found every generated file fresh, pnpm docs:center:verify found zero structural broken links and zero dead source paths, and pnpm docs:center:pytest passed 54/54 generator regressions after reconciling two newly added Tara routes and the transaction-bound Nisaba notebook-authoring audit seam. The integrity report also surfaced 112 pre-existing broken links inside imported content as its explicitly non-blocking category; they are not represented here as resolved by this cost-tracking slice. The V5 documentation validator passed.

This closes the connected Isis cost-tracking operational partition only. It does not claim live provider pricing, invoice reconciliation, provider health or availability, model execution, budget enforcement, runtime fallback, release authorization, customer-owned records, or mounted pages for the four documented adjacent destinations. The parent all-store V1-002 row remains open.

Isis cost-optimization ephemeral-loss, privacy, contract, and browser verification#

The cost-optimization disposition source and published tip is 9dc92a2905b182d4e4bcca11393ca1b0b0e6d43e. It was rebased without conflict over non-overlapping Tara, Yemaya, and study-contract changes, passed the complete source commit policy, and is present on origin/main. Verification completed on 2026-07-21 UTC with the repository-pinned toolchain. The user-owned pnpm-lock.yaml remained outside the commit at worktree blob a37431842e330b3a06b030947c25bebdc72bc2b1; the permanent preservation stash remained 9c4ddf4f7fd4c205d1f083cdbfb9d4a1ee5ce320 at stash@{0}.

The former singleton seeded two fabricated optimization runs and retained prompt-derived previews in a process-local map. Restart erased the apparent history, replicas disagreed on duplicate ids, and the UI presented that volatile state as stored operational runs. Production now exposes the frozen real token-budget technique catalog and an exact disposition: ephemeral_recomputable, persistence none, retention request_lifetime, catalog revision isis-token-budget-optimizer-v1, and authoritativeState: false. GET always returns an empty history. POST applies the real deterministic optimizer and returns its preview directly without writing input, output, correlation id, or derived metrics anywhere. A new instance produces the same result for the same input, and loss of any process cannot discard authority, evidence, lineage, approvals, provider effects, or learning state because none is created by this seam.

Both GET and successful POST use Cache-Control: no-store. The authenticated admin route requires a strict 1-128 character machine-token correlation id, a catalog technique, 1-20,000 characters of content, and valid optional token or ratio bounds. It rejects unknown fields rather than accepting customer identity or unmodeled attribution. Reusing an id is intentionally safe because the id is request correlation, not an idempotency or persistence key. Sensitive input and the derived preview exist only during computation and in the response; a subsequent read contains neither.

Following the frontend skill's restrained cost-governance worksheet direction, the browser now leads with the no-record boundary instead of a fabricated history. It retains only the latest preview in React state, labels that state as current-tab-only, and visibly clears it on reload. Its strict response parser requires the exact no-retention disposition, an empty server history, a complete bounded result, and matching correlation id before rendering derived text. Malformed retained-history or partial-success responses fail closed. Inputs, selects, the action, and quick links meet the 44 px target minimum. The primary route is marked mounted while four adjacent destinations are honest documented-contract entries with no page or implied export, revision, approval, budget, or release authority.

text
# authenticated route, real optimizer math, strict input, privacy, and loss proof
pnpm --dir apps/oshun/bff exec vitest run \
  src/__tests__/admin-isis-cost-optimization-route.test.ts \
  --pool=forks --maxWorkers=1 --no-file-parallelism
  1 file passed; 8/8 tests passed

# strict browser contract, current-tab rendering, route honesty, and page wiring
pnpm --dir apps/oshun/web exec vitest run \
  src/components/__tests__/StudioIsisCostOptimizationEngineWorkspace.test.tsx \
  src/components/__tests__/StudioIsisCostOptimizationEngineWorkspace.integration.test.tsx \
  src/components/__tests__/StudioIsisCostOptimizationEngineRouteMap.test.ts \
  src/components/__tests__/StudioIsisCostOptimizationEnginePage.test.tsx \
  --pool=forks --maxWorkers=1 --no-file-parallelism
  4 files passed; 9/9 tests passed

# isolated current-source web/BFF stack and fresh migrated PostgreSQL; desktop
# Chromium + Pixel-class mobile, live compute, reload loss, safe recomputation,
# malformed contracts, auth, containment, touch targets, and auto-axe analysis
E2E_BASE_URL=http://127.0.0.1:<isolated-web-port> \
E2E_BFF_URL=http://127.0.0.1:<isolated-bff-port> \
E2E_BFF_PORT=<isolated-bff-port> \
E2E_WEB_PORT=<isolated-web-port> \
E2E_SKIP_STUDY=1 \
pnpm --dir apps/oshun/web exec playwright test \
  e2e/studio-isis-cost-optimization.spec.ts \
  --config=playwright.config.ts --workers=1
  7/7 tests passed; all 32 current migrations applied

node tools/typecheck/ratchet.mjs \
  --app apps/oshun/bff --tsconfig tsconfig.typecheck.json
node tools/typecheck/ratchet.mjs \
  --app apps/oshun/web --tsconfig tsconfig.typecheck.json
  BFF backlog 0; web backlog 0

pnpm exec eslint <affected BFF/web source paths> --max-warnings=0
pnpm exec eslint apps/oshun/web/e2e/studio-isis-cost-optimization.spec.ts \
  --max-warnings=0 --no-ignore
pnpm exec prettier --check <affected source paths>
git diff --check
  affected source lint, formatting, and whitespace checks passed

# direct production-entry compilation and syntax validation
pnpm exec esbuild apps/oshun/bff/src/server.ts \
  --bundle --platform=node --format=esm \
  --outfile=/tmp/oshun-cost-optimization-server.js
node --check /tmp/oshun-cost-optimization-server.js
  35,985,040 bytes;
  SHA-256 8e0d832b830ecd320e6f12283f3301e1fcf39a4cb82bb6879d595764df11c31a

The source pre-commit policy passed lint-staged ESLint and formatting, convention and asset checks, V5 documentation validation, and all three affected Nx typecheck targets: @oshun/bff, @oshun/web, and @oshun/prompt-injection-evals. The web production build was deliberately not run: this 15 GiB host is below the repository's 32 GiB hard memory-safety gate, and no user approval was provided. Live desktop/mobile Chromium and axe coverage passed; this evidence does not represent a Next production build as green.

Evidence publication regenerated 3,117 docs-center files across 54 domains after rebasing over the newly published Tara and V10 documentation. The freshness check passed, structural verification found zero broken links and zero dead source paths, and the generator regression suite passed 54/54. The verifier also surfaced the same 112 pre-existing broken links inside imported content in its explicitly non-blocking category; this slice does not represent those links as resolved.

This closes the connected process-local Isis cost-optimization map by proving the computation is safely ephemeral and recomputable. It does not claim live provider pricing, invoice reconciliation, provider health, model execution, budget enforcement, durable optimization history, learning, release authority, customer-owned records, or mounted pages for the four documented adjacent destinations. The parent all-store V1-002 row remains open.

Isis prompt-preview ephemeral-loss, privacy, contract, and browser verification#

The prompt-template preview disposition source and published tip is b876a5ce0e393ef732ea32a7af899e9daf9cef5a. It was rebased without conflict over non-overlapping V10 mobile, Tara, study-contract, and accessibility-policy changes, passed the complete source commit policy, and is present on origin/main. Verification completed on 2026-07-21 UTC with the repository- pinned toolchain. The user-owned pnpm-lock.yaml remained outside the commit at worktree blob a37431842e330b3a06b030947c25bebdc72bc2b1; the permanent preservation stash remained 9c4ddf4f7fd4c205d1f083cdbfb9d4a1ee5ce320 at stash@{0}.

The former singleton seeded two fabricated rendered templates and retained operator prompt source, variables, rendered output, and derived metrics in a process-local map. Restart erased that apparent reusable history, replicas disagreed about duplicate keys, and the UI described volatile previews as saved templates. Production now exposes an exact ephemeral_recomputable disposition: persistence none, retention request_lifetime, engine revision isis-prompt-template-preview-v1, and authoritativeState: false. GET always returns an empty history. POST uses the real prompt-engineering engine and returns the derived preview directly without writing source, variables, rendered output, correlation key, or metrics. A new instance returns the same preview for the same input; process loss cannot discard a reusable template, approval, evidence, lineage, provider effect, or learning state because this seam creates none.

Both GET and successful POST use Cache-Control: no-store. The authenticated admin route requires a strict 1-128 character machine-token correlation key, a bounded name and prompt, and a bounded JSON variable object. It rejects unknown fields, caller identity, retention flags, more than 100 top-level keys, more than 20,000 serialized characters, depth above eight, more than 1,000 value nodes, non-finite values, prototype-control keys, and prototype references in template expressions. Accepted objects are recursively copied into null- prototype records before the engine sees them. Reusing a key is intentionally safe because it correlates a request rather than identifies a durable write. Sensitive input and derived output exist only during computation and in the response; a subsequent read contains neither.

Following the frontend skill's restrained worksheet direction, the browser now leads with the no-record boundary instead of fabricated history. It retains only the latest preview in React state, labels it current-tab-only, and visibly loses it on reload. Its strict response parser requires the exact disposition, an empty server history, a complete bounded result, and the matching correlation key before rendering derived text. Retained-history claims and partial success responses fail closed. Primary controls meet the 44 px target minimum. The primary route is marked mounted while four adjacent destinations are honest documented-contract entries with no page or implied saved template, export, revision, approval, provider execution, or release authority.

text
# authenticated route, real render engine, strict input, privacy, and loss proof
pnpm --dir apps/oshun/bff exec vitest run \
  src/__tests__/admin-isis-prompt-templates-route.test.ts \
  --pool=forks --maxWorkers=1 --no-file-parallelism
  1 file passed; 8/8 tests passed on the published tree

# strict browser contract, current-tab rendering, route honesty, and page wiring
pnpm --dir apps/oshun/web exec vitest run \
  src/components/__tests__/StudioIsis3DPromptEngineeringWorkspace.test.tsx \
  src/components/__tests__/StudioIsis3DPromptEngineeringWorkspace.integration.test.tsx \
  src/components/__tests__/StudioIsis3DPromptEngineeringRouteMap.test.ts \
  src/components/__tests__/StudioIsis3DPromptEngineeringPage.test.tsx \
  --pool=forks --maxWorkers=1 --no-file-parallelism
  4 files passed; 9/9 tests passed on the published tree

# isolated current-source web/BFF stack and fresh migrated PostgreSQL; desktop
# Chromium + Pixel-class mobile, live render, reload loss, safe recomputation,
# malformed contracts, auth, containment, touch targets, and auto-axe analysis
E2E_BASE_URL=http://127.0.0.1:<isolated-web-port> \
E2E_BFF_URL=http://127.0.0.1:<isolated-bff-port> \
E2E_BFF_PORT=<isolated-bff-port> \
E2E_WEB_PORT=<isolated-web-port> \
E2E_SKIP_STUDY=1 \
pnpm --dir apps/oshun/web exec playwright test \
  e2e/studio-isis-3d-prompt-engineering.spec.ts \
  --config=playwright.config.ts --workers=1
  final full run 8/8 tests passed; all 32 current migrations applied
  post-input-hardening live render/invalid-field subset 2/2 passed

node tools/typecheck/ratchet.mjs \
  --app apps/oshun/bff --tsconfig tsconfig.typecheck.json
node tools/typecheck/ratchet.mjs \
  --app apps/oshun/web --tsconfig tsconfig.typecheck.json
  BFF backlog 0; web backlog 0

pnpm exec eslint <affected BFF/web source paths> --max-warnings=0
pnpm exec eslint <affected test and E2E paths> --max-warnings=0 --no-ignore
pnpm exec prettier --check <affected source paths>
git diff --check
  affected source/test lint, formatting, and whitespace checks passed

# direct production-entry compilation and syntax validation
pnpm exec esbuild apps/oshun/bff/src/server.ts \
  --bundle --platform=node --format=esm \
  --outfile=/tmp/oshun-prompt-preview-server.js
node --check /tmp/oshun-prompt-preview-server.js
  36,093,443 bytes;
  SHA-256 c3e0456b478310ecadca18ffcd3fdb68d2af4d62ce7c7cddc2d35b67a9e46f34

The source pre-commit policy passed lint-staged ESLint and formatting, convention and asset checks, V5 documentation validation, and all three affected Nx typecheck targets: @oshun/bff, @oshun/web, and @oshun/prompt-injection-evals. The web production build was deliberately not run: this 15 GiB host is below the repository's 32 GiB hard memory-safety gate, and no user approval was provided. Live desktop/mobile Chromium and axe coverage passed; this evidence does not represent a Next production build as green.

Evidence publication regenerated 3,117 docs-center files across 54 domains on the published source tree. The freshness check passed, structural verification found zero broken links and zero dead source paths, and the generator regression suite passed 54/54. The verifier also surfaced the same 112 pre-existing broken links inside imported content in its explicitly non-blocking category; this slice does not represent those links as resolved.

This closes the connected process-local prompt-template map by proving the existing surface is safely ephemeral and recomputable. It does not create or claim a reusable-template repository, durable prompt history, approvals, lineage, provider execution, learning, release authority, customer-owned records, or mounted pages for the four documented adjacent destinations. A future reusable-template feature would require a separate durable authority, privacy lifecycle, and recovery proof. The parent all-store V1-002 row remains open.

Isis managed-model registry unbound-projection contract and browser verification#

The managed-model registry disposition source and published tip is 5a47c333dd7a5117920a21966b16035dcdd9ef4f. It was rebased without conflict over non-overlapping documentation changes, passed the complete source commit policy, and is present on origin/main. Verification completed on 2026-07-21 UTC with the repository-pinned toolchain. The user-owned pnpm-lock.yaml remained outside the commit at worktree blob a37431842e330b3a06b030947c25bebdc72bc2b1; the permanent preservation stash remained 9c4ddf4f7fd4c205d1f083cdbfb9d4a1ee5ce320 at stash@{0}.

The former singleton seeded five fabricated approved model records, including licenses, hashes, recipes, moderation state, and release-like metadata, despite having no production mutation producer or persistence adapter. Production now exposes an exact unbound_empty_projection disposition: persistence none, producer none, retention not_applicable, authority binding not_configured, and authoritativeState: false. Every browse and asset-type projection is structurally empty, including across new store instances and all valid filters. Process loss therefore cannot drop model authority, admission evidence, lineage, approvals, provider effects, or learning state because this seam creates and retains none.

The authenticated admin route emits Cache-Control: no-store, requires an Isis admin scope, accepts only the documented query keys, and strictly bounds query, asset-type, cursor, boolean, and page-size syntax. Unknown fields and malformed cursors fail closed. The browser parser accepts only the exact unbound disposition with zero records, zero asset types, no cursor, and total zero; any retained record or authority claim is treated as a malformed response. The workspace leads with the missing-authority boundary, reports zero admitted models, and hides filters and pagination until an authoritative intake and admission registry is connected. The primary route is marked mounted while four adjacent destinations remain honest documented-contract entries with no mounted page or implied approval, license, provider, recipe, export, or release authority.

text
# authenticated empty projection, strict query contract, and loss proof
pnpm --dir apps/oshun/bff exec vitest run \
  src/__tests__/admin-isis-model-registry-route.test.ts \
  --pool=forks --maxWorkers=1 --no-file-parallelism
  1 file passed; 6/6 tests passed on the final source tree

# strict browser contract, authority-claim rejection, route honesty, and page wiring
pnpm --dir apps/oshun/web exec vitest run \
  src/components/__tests__/StudioIsisModelRegistryWorkspace.test.tsx \
  src/components/__tests__/StudioIsisModelRegistryWorkspace.integration.test.tsx \
  src/components/__tests__/StudioIsisModelRegistryRouteMap.test.ts \
  src/components/__tests__/StudioIsisModelRegistryPage.test.tsx \
  --pool=forks --maxWorkers=1 --no-file-parallelism
  4 files passed; 8/8 tests passed

# isolated current-source web/BFF stack and fresh migrated PostgreSQL; desktop
# Chromium + Pixel-class mobile, live empty projection, strict query rejection,
# fabricated-authority rejection, auth, containment, touch targets, and auto-axe
E2E_BASE_URL=http://127.0.0.1:<isolated-web-port> \
E2E_BFF_URL=http://127.0.0.1:<isolated-bff-port> \
E2E_BFF_PORT=<isolated-bff-port> \
E2E_WEB_PORT=<isolated-web-port> \
E2E_SKIP_STUDY=1 \
pnpm --dir apps/oshun/web exec playwright test \
  e2e/studio-isis-model-registry.spec.ts \
  --config=playwright.config.ts --workers=1
  8/8 tests passed; all 32 current migrations applied

node tools/typecheck/ratchet.mjs \
  --app apps/oshun/bff --tsconfig tsconfig.typecheck.json
node tools/typecheck/ratchet.mjs \
  --app apps/oshun/web --tsconfig tsconfig.typecheck.json
  BFF backlog 0; web backlog 0

pnpm exec eslint <affected BFF/web source paths> --max-warnings=0
pnpm exec eslint <affected test and E2E paths> --max-warnings=0 --no-ignore
pnpm exec prettier --check <affected source paths>
git diff --check
  affected source/test lint, formatting, and whitespace checks passed

# exact underlying production build command, run without Nx's 319-task fan-out
pnpm --dir apps/oshun/bff exec esbuild src/server.ts \
  --bundle --platform=node --format=esm --target=node22 \
  --outfile=dist/server.js --sourcemap
node --check apps/oshun/bff/dist/server.js
  36,333,874-byte entry bundle;
  SHA-256 b2040f174d504c828362f7686a353530f4c1ea8e29685b2bc5c6207c0bde6ecc

The source pre-commit policy passed lint-staged ESLint and formatting, convention and asset checks, V5 documentation validation, and all three affected Nx typecheck targets: @oshun/bff, @oshun/web, and @oshun/prompt-injection-evals. The web production build was deliberately not run: this 15 GiB host is below the repository's 32 GiB hard memory-safety gate, and no user approval was provided. Live desktop/mobile Chromium and axe coverage passed; this evidence does not represent a Next production build as green.

Evidence publication regenerated 3,118 docs-center files across 54 domains on the published source tree. The freshness check passed, structural verification found zero broken links and zero dead source paths, and the generator regression suite passed 54/54. The verifier also surfaced the same 112 pre-existing broken links inside imported content in its explicitly non-blocking category; this slice does not represent those links as resolved.

This retires the fabricated local managed-model catalog by proving that the existing BFF has no registry producer, persistence, or authority to lose. It does not create or claim model intake, admission review, license verification, artifact hash validation, provider availability, recipes, approval history, customer-owned records, or release authority. A future registry feature must bind a durable authoritative adapter and independently prove recovery, privacy, retention, and deletion behavior. The parent all-store V1-002 row remains open.

Isis Civitai intake unbound-projection and disabled-decision verification#

The Civitai intake disposition source and published tip is a2e8e0d69d1fb4bc667c10594b884b27b85f747a. It passed the complete source commit policy and is present on origin/main. Verification completed on 2026-07-21 UTC with the repository-pinned toolchain. The user-owned pnpm-lock.yaml remained outside the commit at worktree blob a37431842e330b3a06b030947c25bebdc72bc2b1; the permanent preservation stash remained 9c4ddf4f7fd4c205d1f083cdbfb9d4a1ee5ce320 at stash@{0}.

The former singleton seeded a searchable candidate and an in-review candidate with invented creator attribution, license tags, hashes, lineage, compatibility notes, preview assets, reviewer identity, and decision history. Its POST route could then acknowledge approval, rejection, conditional, takedown, and denylist transitions in process memory, including a fabricated promotion recipe, despite having no production discovery producer, reviewer directory, admission persistence, or downstream registry binding. Production now exposes the exact unbound_empty_projection disposition: persistence none, producer none, retention not_applicable, authority binding not_configured, decisions unavailable, and authoritativeState: false. Every new instance returns zero queued entries, a null operator, and zero search candidates.

The authenticated GET route emits Cache-Control: no-store. The authenticated decision compatibility endpoint preserves the Isis scope boundary but returns 503 intake_authority_not_configured with the same no-store disposition for every authorized body; it cannot acknowledge a decision or mutate the empty projection. The browser accepts only the exact empty context and disposition. Any candidate, reviewer, history, or decision-authority claim fails closed. The workspace leads with the missing-authority boundary and hides search, filters, candidate metadata, and review actions. The primary route is marked mounted while four adjacent destinations remain honest documented-contract entries with no mounted page or implied intake snapshot, revision, rights decision, license verification, governance approval, or release signoff.

text
# authenticated empty projection, disabled writes, and loss proof
pnpm --dir apps/oshun/bff exec vitest run \
  src/__tests__/admin-isis-civitai-intake-route.test.ts \
  src/__tests__/admin-isis-civitai-intake-decisions-route.test.ts \
  src/isis/seed-data-notice.test.ts \
  --pool=forks --maxWorkers=1 --no-file-parallelism
  3 files passed; 7/7 tests passed

# strict browser contract, authority-claim rejection, route honesty, and page wiring
pnpm --dir apps/oshun/web exec vitest run \
  src/components/__tests__/StudioIsisCivitaiIntegrationWorkspace.test.tsx \
  src/components/__tests__/StudioIsisCivitaiIntegrationWorkspace.integration.test.tsx \
  src/components/__tests__/StudioIsisCivitaiIntegrationRouteMap.test.ts \
  src/components/__tests__/StudioIsisCivitaiIntegrationPage.test.tsx \
  --pool=forks --maxWorkers=1 --no-file-parallelism
  4 files passed; 8/8 tests passed

# isolated current-source web/BFF stack and fresh migrated PostgreSQL; desktop
# Chromium + Pixel-class mobile, live GET/POST, fabricated-authority rejection,
# auth, containment, touch targets, and automatic axe analysis
E2E_BFF_PORT=<isolated-bff-port> \
E2E_WEB_PORT=<isolated-web-port> \
E2E_BFF_URL=http://127.0.0.1:<isolated-bff-port> \
E2E_SKIP_STUDY=1 \
pnpm --dir apps/oshun/web exec playwright test \
  e2e/studio-isis-civitai-integration.spec.ts \
  --config=playwright.config.ts --workers=1
  8/8 tests passed; all 32 current migrations applied

node tools/typecheck/ratchet.mjs \
  --app apps/oshun/bff --tsconfig tsconfig.typecheck.json
node tools/typecheck/ratchet.mjs \
  --app apps/oshun/web --tsconfig tsconfig.typecheck.json
  BFF backlog 0; web backlog 0

pnpm exec eslint <affected BFF/web source, test, and E2E paths> \
  --max-warnings=0 --no-ignore
pnpm exec prettier --check <affected source paths>
git diff --check
  affected source/test lint, formatting, and whitespace checks passed

pnpm --dir apps/oshun/bff exec esbuild src/server.ts \
  --bundle --platform=node --format=esm --target=node22 \
  --outfile=dist/server.js --sourcemap
node --check apps/oshun/bff/dist/server.js
  36,326,165-byte entry bundle;
  SHA-256 9506d12ce42e4d39a1cc640d00673dd40945826631c682c65c2797c5d9e5ab82

The source pre-commit policy passed lint-staged ESLint and formatting, convention and asset checks, V5 documentation validation, and all three affected Nx typecheck targets: @oshun/bff, @oshun/web, and @oshun/prompt-injection-evals. The web production build was deliberately not run: this 15 GiB host is below the repository's 32 GiB hard memory-safety gate, and no user approval was provided. Live desktop/mobile Chromium and axe coverage passed; this evidence does not represent a Next production build as green.

Evidence publication regenerated 3,118 docs-center files across 54 domains on the published source tree. The freshness check passed, structural verification found zero broken links and zero dead source paths, and the generator regression suite passed 54/54. The verifier also surfaced the same 112 pre-existing broken links inside imported content in its explicitly non-blocking category; this slice does not represent those links as resolved.

This retires the fabricated Civitai intake and review authority by proving that the existing BFF has no producer or durable authority to lose and cannot accept a decision. It does not create or claim remote Civitai search, candidate intake, reviewer identity, rights or license verification, hash validation, moderation, preview evidence, promotion recipes, model registration, provider effects, or release authority. A future intake must bind durable admission and reviewer authorities and independently prove recovery, privacy, retention, deletion, and downstream model-registry consistency. The parent all-store V1-002 row remains open.

Isis model-merging unbound-projection and disabled-plan verification#

The model-merging disposition source and published tip is 8dca9a9e33996b791085b663b59d46ddcffbd0a6. It passed the complete source commit policy and is present on origin/main. Verification completed on 2026-07-21 UTC with the repository-pinned toolchain. The user-owned pnpm-lock.yaml remained outside the commit at worktree blob a37431842e330b3a06b030947c25bebdc72bc2b1; the permanent preservation stash remained 9c4ddf4f7fd4c205d1f083cdbfb9d4a1ee5ce320 at stash@{0}.

The former process singleton seeded five invented component records and three fixture sets, assigned them to operator-anon, and retained saved merge plans only in memory. Its POST route could assemble a provenance-shaped bundle and acknowledge a plan despite having no production component catalog, fixture provider, artifact writer, merge executor, durable plan store, or downstream effect. Production now exposes the exact unbound_empty_projection disposition: persistence none, producer none, retention not_applicable, authority binding not_configured, plans unavailable, execution unavailable, and authoritativeState: false. Every new instance returns a null operator, zero candidate components, zero fixture sets, and zero saved plans.

The authenticated GET route emits Cache-Control: no-store. The authenticated plan compatibility endpoint preserves the Isis scope boundary but returns 503 model_merging_authority_not_configured with the same no-store disposition for every authorized body; it cannot acknowledge or retain a plan. The browser accepts only the exact empty context and disposition. Any component, fixture, saved-plan, or execution-authority claim fails closed. The workspace leads with the missing-authority boundary and hides component selection, ratios, fixtures, planning, and execution controls. The primary route is marked mounted while four adjacent destinations remain honest documented-contract entries with no mounted page or implied comparison, provenance, quality, or release authority.

text
# authenticated empty projection, disabled plans, and loss proof
pnpm --dir apps/oshun/bff exec vitest run \
  src/__tests__/admin-isis-model-merging-route.test.ts \
  src/__tests__/admin-isis-model-merging-plans-route.test.ts \
  src/isis/seed-data-notice.test.ts \
  --pool=forks --maxWorkers=1 --no-file-parallelism
  3 files passed; 7/7 tests passed

# strict browser contract, authority-claim rejection, route honesty, and page wiring
pnpm --dir apps/oshun/web exec vitest run \
  src/components/__tests__/StudioIsisModelMergingWorkspace.test.tsx \
  src/components/__tests__/StudioIsisModelMergingWorkspace.integration.test.tsx \
  src/components/__tests__/StudioIsisModelMergingRouteMap.test.ts \
  src/components/__tests__/StudioIsisModelMergingPage.test.tsx \
  --pool=forks --maxWorkers=1 --no-file-parallelism
  4 files passed; 8/8 tests passed

# isolated current-source web/BFF stack and fresh migrated PostgreSQL; desktop
# Chromium + Pixel-class mobile, live GET/POST, fabricated-authority rejection,
# auth, containment, touch targets, and automatic axe analysis on live pages
E2E_BFF_PORT=<isolated-bff-port> \
E2E_WEB_PORT=<isolated-web-port> \
E2E_BFF_URL=http://127.0.0.1:<isolated-bff-port> \
E2E_SKIP_STUDY=1 \
pnpm --dir apps/oshun/web exec playwright test \
  e2e/studio-isis-model-merging.spec.ts \
  --config=playwright.config.ts --workers=1
  7/7 tests passed; all 32 current migrations applied

node tools/typecheck/ratchet.mjs \
  --app apps/oshun/bff --tsconfig tsconfig.typecheck.json
node tools/typecheck/ratchet.mjs \
  --app apps/oshun/web --tsconfig tsconfig.typecheck.json
  BFF backlog 0; web backlog 0

pnpm exec eslint <affected BFF/web source, test, and E2E paths> \
  --max-warnings=0 --no-ignore
pnpm exec prettier --check <affected source paths>
git diff --check
  affected source/test lint, formatting, and whitespace checks passed

pnpm --dir apps/oshun/bff exec esbuild src/server.ts \
  --bundle --platform=node --format=esm --target=node22 \
  --outfile=dist/server.js --sourcemap
node --check apps/oshun/bff/dist/server.js
  36,319,322-byte entry bundle;
  SHA-256 6d7e67f6fc4469f1aff629bfd3f7aeb7432e1cec8a46afd99a5539ca72c2d869

The source pre-commit policy passed lint-staged ESLint and formatting, convention and asset checks, V5 documentation validation, and all three affected Nx typecheck targets: @oshun/bff, @oshun/web, and @oshun/prompt-injection-evals. The web production build was deliberately not run: this 15 GiB host is below the repository's 32 GiB hard memory-safety gate, and no user approval was provided. Live desktop/mobile Chromium and applicable axe coverage passed; this evidence does not represent a Next production build as green.

Evidence publication regenerated 3,119 docs-center files across 54 domains on the published source tree. The freshness check passed, structural verification found zero broken links and zero dead source paths, and the generator regression suite passed 54/54. The verifier also surfaced the same 112 pre-existing broken links inside imported content in its explicitly non-blocking category; this slice does not represent those links as resolved.

This retires the fabricated model-merging catalog and plan authority by proving that the existing BFF has no producer, durable plan authority, merge executor, or downstream effect to lose. It does not create or claim model admission, component integrity, fixture provenance, merge execution, artifact writing, quality comparison, provider effects, approval history, or release authority. A future merge feature must bind durable catalog, plan, execution, and artifact authorities and independently prove recovery, privacy, retention, deletion, and downstream registry consistency. The parent all-store V1-002 row remains open.

Isis voice-cloning unbound-projection and disabled-workflow verification#

The voice-cloning disposition source and published tip is 73d0f24553b3fb596c97d0374973b35542b0490d. It passed the complete source commit policy and is present on origin/main. Verification completed on 2026-07-21 UTC with the repository-pinned toolchain. The user-owned pnpm-lock.yaml remained outside the commit at worktree blob a37431842e330b3a06b030947c25bebdc72bc2b1; the permanent preservation stash remained 9c4ddf4f7fd4c205d1f083cdbfb9d4a1ee5ce320 at stash@{0}.

The former process singleton seeded two invented voice-cloning workflows with named consent acknowledgements, identity-verification timestamps, biometric sample hashes, read-aloud script hashes, naturalness and speaker-similarity scores, watermark attestations, abuse-risk scores, reviewer signoffs, lifecycle history, and a released production profile. Its POST routes could accept consent-shaped text and walk a workflow through identity, samples, scoring, signoff, profile registration, release, rejection, or revocation only in memory. Repository tracing found no production consent ledger, identity verifier, biometric sample store, scoring producer, signer directory, profile registry, provider executor, or downstream TTS release binding.

Production now exposes the exact unbound_empty_projection disposition: persistence none, producer none, retention not_applicable, authority binding not_configured, workflows, transitions, identity verification, biometric samples, scoring, signoffs, and profile registration unavailable, and authoritativeState: false. Every new store instance returns zero records. The authenticated GET route emits Cache-Control: no-store. Both authenticated workflow-creation and lifecycle-transition compatibility routes preserve the Isis scope boundary but return 503 voice_cloning_authority_not_configured with the same no-store disposition for every authorized body; they cannot acknowledge or retain subject, consent, sample, score, signoff, profile, or revocation data.

The browser accepts only the exact empty response and disposition. Any workflow, consent, biometric, signoff, profile, transition, or authoritative-state claim fails closed. The workspace leads with the missing-authority boundary and hides subject identifiers, consent capture, identity verification, sample manifests, scores, watermark and abuse-risk attestations, signoffs, profile registration, and release controls. The primary route is marked mounted while four adjacent destinations remain honest documented-contract entries with no mounted page or implied scene, export, revision, governance, or release authority.

text
# authenticated empty projection, disabled workflows/transitions, and loss proof
pnpm --dir apps/oshun/bff exec vitest run \
  src/__tests__/admin-isis-voice-cloning-route.test.ts \
  src/__tests__/admin-isis-voice-cloning-workflow-route.test.ts \
  src/isis/seed-data-notice.test.ts \
  --pool=forks --maxWorkers=1 --no-file-parallelism
  3 files passed; 7/7 tests passed

# strict browser contract, authority-claim rejection, route honesty, and page wiring
pnpm --dir apps/oshun/web exec vitest run \
  src/components/__tests__/StudioIsisTextToSpeechWorkspace.test.tsx \
  src/components/__tests__/StudioIsisTextToSpeechWorkspace.integration.test.tsx \
  src/components/__tests__/StudioIsisTextToSpeechRouteMap.test.ts \
  src/components/__tests__/StudioIsisTextToSpeechPage.test.tsx \
  --pool=forks --maxWorkers=1 --no-file-parallelism
  4 files passed; 8/8 tests passed

# isolated current-source web/BFF stack and fresh migrated PostgreSQL; desktop
# Chromium + Pixel-class mobile, live GET/two POST boundaries, fabricated
# consent/biometric/profile authority rejection, auth, containment, touch
# targets, and automatic axe analysis on live pages
E2E_BFF_PORT=<isolated-bff-port> \
E2E_WEB_PORT=<isolated-web-port> \
E2E_BFF_URL=http://127.0.0.1:<isolated-bff-port> \
E2E_SKIP_STUDY=1 \
pnpm --dir apps/oshun/web exec playwright test \
  e2e/studio-isis-text-to-speech.spec.ts \
  --config=playwright.config.ts --workers=1
  7/7 tests passed; all 32 current migrations applied

node tools/typecheck/ratchet.mjs \
  --app apps/oshun/bff --tsconfig tsconfig.typecheck.json
node tools/typecheck/ratchet.mjs \
  --app apps/oshun/web --tsconfig tsconfig.typecheck.json
  BFF backlog 0; web backlog 0

pnpm exec eslint <affected BFF/web source, test, and E2E paths> \
  --max-warnings=0 --no-ignore
pnpm exec prettier --check <affected source paths>
git diff --check
  affected source/test lint, formatting, and whitespace checks passed

pnpm --dir apps/oshun/bff exec esbuild src/server.ts \
  --bundle --platform=node --format=esm --target=node22 \
  --outfile=dist/server.js --sourcemap
node --check apps/oshun/bff/dist/server.js
  36,342,561-byte entry bundle;
  SHA-256 523786b2c0cbbf2606d11309f27a1ee2220d7be14e5c589bcfc494d0f23054f7

The source pre-commit policy passed lint-staged ESLint and formatting, convention and asset checks, V5 documentation validation, and all three affected Nx typecheck targets: @oshun/bff, @oshun/web, and @oshun/prompt-injection-evals. The post-rebase BFF type ratchet also passed after incoming shared server wiring was integrated. The web production build was deliberately not run: this 15 GiB host is below the repository's 32 GiB hard memory-safety gate, and no user approval was provided. Live desktop/mobile Chromium and applicable axe coverage passed; this evidence does not represent a Next production build as green.

Evidence publication regenerated 3,122 docs-center files across 54 domains on the published source tree. The freshness check passed, structural verification found zero broken links and zero dead source paths, and the generator regression suite passed 54/54. The verifier also surfaced the same 112 pre-existing broken links inside imported content in its explicitly non-blocking category; this slice does not represent those links as resolved.

This retires the fabricated voice-cloning workflow and release authority by proving that the existing BFF has no authoritative producer or durable state to lose and cannot accept high-risk consent or biometric workflow inputs. It does not create or claim consent validity, identity verification, biometric custody, sample integrity, model scoring, watermark verification, abuse-risk screening, reviewer identity, rights or safety signoff, provider execution, profile registration, revocation propagation, or TTS release authority. A future voice- cloning feature must bind those durable authorities and independently prove recovery, privacy, biometric deletion, retention, consent withdrawal, and downstream profile consistency. The parent all-store V1-002 row remains open.

Isis Analytics and Reporting request-local retry-analysis verification#

The implementation source is 9ac7f3cc0f0013229e6e041055da9f548e3c5bce, published directly to origin/main on 2026-07-22 UTC. Repository tracing found no production analytics producer or reporting store behind this surface. The administrator route accepts caller-supplied retry attempts for the pure analyzeRetryStats helper and caller-supplied parameters for the pure calculateBackoff helper. It does not ingest telemetry, execute an operation, schedule a retry, apply jitter, retain history, create an export, mutate a policy, or make a release decision.

All three successful endpoints return the exact request_local_non_authoritative_retry_analysis disposition with no-store cache policy. It declares no persistence, request-only retention, access-scope-only authority binding, caller-supplied inputs, deterministic source-defined aggregation/backoff preview, no telemetry ingestion, no operation execution, no scheduling, excluded jitter, no reporting history, no export artifact, no mutations, and non-authoritative state. Exact request keys prevent callers from attaching persistence, telemetry, scheduling, or approval claims. The input contract caps attempts at 1,000, operation references at 200 canonical non-control characters, attempt numbers at 10,000, delays at one day, and multipliers at 100.

The browser requires the exact disposition, catalog order, bounds, output shape, and distribution vocabulary. A successful aggregate must match the submitted attempt count, success/failure counts, average delay, attempts-to-success, operations ratio, and every failure/strategy bucket. The backoff response must equal an independent calculation over the submitted strategy, attempt, base, maximum, and multiplier. Unknown or inconsistent success fields fail closed. The restrained worksheet labels its JSON as a caller-supplied editable sample, calls output a preview, states that no delay is scheduled, and marks four aspirational subroutes documented-only.

text
pnpm --dir apps/oshun/bff exec vitest run \
  src/__tests__/admin-isis-analytics-reporting-route.test.ts \
  --pool=forks --maxWorkers=1 --no-file-parallelism
  1 file passed; 6/6 tests passed

pnpm --dir apps/oshun/web exec vitest run \
  src/components/__tests__/StudioIsisAnalyticsAndReportingWorkspace.test.tsx \
  src/components/__tests__/StudioIsisAnalyticsAndReportingWorkspace.integration.test.tsx \
  src/components/__tests__/StudioIsisAnalyticsAndReportingRouteMap.test.ts \
  src/components/__tests__/StudioIsisAnalyticsAndReportingPage.test.tsx \
  --pool=forks --maxWorkers=1 --no-file-parallelism
  4 files passed; 8/8 tests passed

# source BFF + web + disposable fully migrated PostgreSQL/Redis
OSHUN_V1_DATABASE_URL=<disposable-database> \
E2E_BFF_PORT=<isolated-bff-port> \
E2E_WEB_PORT=<isolated-web-port> \
E2E_BFF_URL=http://127.0.0.1:<isolated-bff-port> \
E2E_SKIP_STUDY=1 \
pnpm --dir apps/oshun/web exec playwright test \
  e2e/studio-isis-analytics-and-reporting.spec.ts \
  --config=playwright.config.ts --workers=1
  8/8 tests passed with applicable axe analysis; all 32 migrations applied

pnpm --dir apps/oshun/web typecheck
pnpm exec eslint <affected BFF/web source, test, and E2E paths> \
  --max-warnings=0 --no-ignore
pnpm exec prettier --write <affected source paths>
git diff --check
  web typecheck, affected lint, formatting, and whitespace checks passed

NODE_OPTIONS=--max-old-space-size=6144 \
node tools/typecheck/ratchet.mjs \
  --app apps/oshun/bff --tsconfig tsconfig.typecheck.json
  reached only the same two unrelated current-main errors in
  autonomous-content-metrics-store.ts and autonomy-route.test.ts

pnpm --dir apps/oshun/bff run build
pnpm --dir apps/oshun/bff run verify:production-artifact
  migrated-database production-artifact smoke passed;
  36,100,449-byte entry bundle;
  SHA-256 31d4c9edca2bae238ef1718d7cb013e9d616f8169b2c42b70001e25702a86f8e

The first browser command was intentionally discarded because the invocation set E2E_BASE_URL, which tells the repository config to skip managed server startup. The corrected command then exposed the known default oshun_dev missing-account-protection-table startup blocker. The final valid run used a disposable database created from all 32 current migrations, passed 8/8, and the database was removed after production-artifact smoke. Neither invalid harness attempt is represented as product verification. The web production build was not run because the 15 GiB host is below the repository's 32 GiB hard gate and no approval was provided. The source commit used the documented typecheck-only hook bypass after affected verification passed; hook lint, formatting, convention, asset, and documentation checks passed. This closes the request-local calculator boundary, not the parent all-store item or any live analytics/reporting authority.

Isis 3D Editing browser-local and repair-simulation verification#

The implementation source is f7c89cc85db1f1641911a3384b00ed99af7ff13f, published directly to origin/main on 2026-07-22 UTC. Repository tracing found two separate, unconnected mechanisms behind the surface. The browser editor operates on seeded geometry and keeps sculpt history, previews, and last-export state only in the current tab; it can create a browser download but has no project store, collaboration authority, server upload, archive, or durable artifact identity. The BFF accepts a separate caller-supplied indexed mesh and invokes the pure @isis/3d-post-pipeline manifold-repair helper. It is not bound to the browser editor and returns topology analysis rather than repaired mesh bytes.

GET and successful POST return the exact no-store request_local_non_authoritative_mesh_repair_analysis disposition. It declares no persistence, request-only retention, caller-supplied geometry, deterministic source-defined simulation, no browser-editor binding, no repaired-mesh output, no export or pipeline admission, no artifact output, no mutations, and non- authoritative state. Exact parsing rejects unknown top-level and option fields. Position and index arrays are capped at 30,000 values, must contain complete triples, and must use finite bounded coordinates and safe in-range indices.

The browser independently validates the exact catalog, disposition, input contract, both topology snapshots, actions, all seven metrics, warnings, blockers, and topologyReady. It binds the input vertex/triangle counts to the acknowledgement and rejects catalogs or acknowledgements that claim repaired geometry, export admission, or other authority. The rendered workspace labels the editor as a browser-local demo, labels its download as a browser download, states that repair analysis uses an independent editable sample and returns no repaired geometry, and marks five adjacent routes documented-only.

text
pnpm --dir apps/oshun/bff exec vitest run \
  src/__tests__/admin-isis-3d-editing-route.test.ts
  1 file passed; 7/7 tests passed

pnpm --dir apps/oshun/web exec vitest run \
  src/components/__tests__/StudioIsis3DEditingManifoldRepairLane.live.test.tsx \
  src/components/__tests__/StudioIsis3DEditingWorkspace.test.tsx \
  src/components/__tests__/StudioIsis3DEditingRouteMap.test.ts \
  src/components/__tests__/StudioIsis3DEditingPage.test.tsx \
  src/components/__tests__/StudioIsis3DEditingWorkspace.integration.test.tsx
  5 files passed; 18/18 tests passed

pnpm --dir libs/isis/3d-post-pipeline exec vitest run
  1 file passed; 4/4 tests passed

# real production BFF artifact + direct Next dev server + disposable fully
# migrated PostgreSQL/Redis; retries disabled
E2E_BASE_URL=http://127.0.0.1:<isolated-web-port> \
E2E_BFF_URL=http://127.0.0.1:<isolated-bff-port> \
pnpm --dir apps/oshun/web exec playwright test \
  e2e/studio-isis-3d-editing-boundary.spec.ts \
  --config=playwright.config.ts --workers=1 --retries=0
  8/8 tests passed with applicable axe analysis; all 32 migrations applied

pnpm --dir apps/oshun/web typecheck
pnpm exec eslint <affected BFF/web source, test, and E2E paths>
git diff --check
  web typecheck, affected lint/formatting, and whitespace checks passed

NODE_OPTIONS=--max-old-space-size=6144 \
node tools/typecheck/ratchet.mjs \
  --app apps/oshun/bff --tsconfig tsconfig.typecheck.json
  reached only the same two unrelated current-main errors in
  autonomous-content-metrics-store.ts and autonomy-route.test.ts

pnpm --dir apps/oshun/bff run build
pnpm --dir apps/oshun/bff run verify:production-artifact
  migrated-database production-artifact smoke passed;
  36,103,182-byte entry bundle;
  SHA-256 b7a3bdcb8fea7a939bcee418b9da37546c12d1d978568d72f84201dff33cf15e

The managed Playwright rerun was discarded before tests because the Nx-based BFF web-server command exceeded its bounded startup window while constructing the project graph. A first direct-server diagnostic run was also discarded because the manually launched web process omitted the repository's explicit Studio E2E bypass and correctly returned the hard 404. The final valid run used the exact feature-gated environment, the real built BFF, retries disabled, and passed 8/8; neither discarded harness attempt is represented as product verification. The disposable database was removed after artifact smoke. The web production build was not run because the 15 GiB host is below the repository's 32 GiB hard gate and no approval was provided. This closes the browser-local loss and request-local repair-simulation boundary, not the parent all-store item or any durable editing, collaboration, repaired-mesh, export, artifact, pipeline, governance, or release authority.

Isis 3D Generation request-local prompt-preview verification#

The implementation source is 45f1a952fa76045ddafc3210f2ee60cf7431fe89, published directly to origin/main on 2026-07-22 UTC. Repository tracing found that the administrator route is the only production consumer of the pure @isis/3d-product-parity structured-prompt builder. It accepts caller-supplied text and vocabulary fields and concatenates a deterministic prompt. It does not create a generation request, execute a provider, submit a queue item, retain a project or revision, export a file, write an artifact, record governance, or make a release decision.

GET and successful POST return the exact no-store request_local_non_authoritative_structured_prompt_preview disposition. It declares no persistence, request-only retention, access-scope-only authority, caller-supplied inputs, deterministic source-defined assembly, and no generation admission, provider execution, queue submission, export admission, artifact output, mutations, or authoritative state. Requests accept exactly the one required subject and six optional source-defined fields. Subject text is capped at 1,000 characters, optional text at 500, control characters and supplied empty values are rejected, and topology/export values use closed vocabularies.

The browser requires exact catalog and acknowledgement shapes and independently reconstructs both the canonical prompt and ordered fields-used list from the submitted values. Extra authority fields, a mismatched prompt, or a disposition claiming generation/export admission fails closed. The restrained worksheet labels export target as a phrase, states that it creates no 3D asset or export, meets the 44-pixel control floor, remains contained on mobile, and marks the primary preview plus the independently mounted browser turntable viewer while leaving five nonexistent shapes documented-only.

text
pnpm --dir apps/oshun/bff exec vitest run \
  src/__tests__/admin-isis-3d-generation-route.test.ts \
  --pool=forks --maxWorkers=1 --no-file-parallelism
  1 file passed; 6/6 tests passed

pnpm --dir apps/oshun/web exec vitest run \
  src/components/__tests__/StudioIsis3DGenerationWorkspace.test.tsx \
  src/components/__tests__/StudioIsis3DGenerationWorkspace.integration.test.tsx \
  src/components/__tests__/StudioIsis3DGenerationRouteMap.test.ts \
  src/components/__tests__/StudioIsis3DGenerationPage.test.tsx
  4 files passed; 9/9 tests passed

pnpm --dir libs/isis/3d-product-parity exec vitest run \
  src/structured-prompt-builder.test.ts src/index.test.ts
  2 files passed; 2/2 tests passed

# real production BFF artifact + direct Next dev server + disposable fully
# migrated PostgreSQL/Redis; retries disabled
E2E_BASE_URL=http://127.0.0.1:<isolated-web-port> \
E2E_BFF_URL=http://127.0.0.1:<isolated-bff-port> \
pnpm --dir apps/oshun/web exec playwright test \
  e2e/studio-isis-3d-generation-boundary.spec.ts \
  --config=playwright.config.ts --workers=1 --retries=0
  8/8 tests passed with applicable axe analysis; all 32 migrations applied

pnpm --dir apps/oshun/web typecheck
pnpm exec eslint <affected BFF/web source, test, and E2E paths>
git diff --check
  web typecheck, affected lint/formatting, and whitespace checks passed

NODE_OPTIONS=--max-old-space-size=6144 \
node tools/typecheck/ratchet.mjs \
  --app apps/oshun/bff --tsconfig tsconfig.typecheck.json
  reached only the same two unrelated current-main errors in
  autonomous-content-metrics-store.ts and autonomy-route.test.ts

pnpm --dir apps/oshun/bff run build
pnpm --dir apps/oshun/bff run verify:production-artifact
  migrated-database production-artifact smoke passed;
  36,105,735-byte entry bundle;
  SHA-256 5b1bbf47f6e10c3da822db25186e20ea09b5d9d213cb029d75399edd81537bf5

The first eight-scenario run had seven passing scenarios and one cold-compile timeout: Next required 71 seconds to compile the route while the test retained the generic 60-second budget. The scenario received the repository's explicit slow-test allowance, and the complete clean rerun passed 8/8 with retries disabled. This startup-only discarded run is not represented as product verification. The disposable database was removed after artifact smoke. The web production build was not run because the 15 GiB host is below the repository's 32 GiB hard gate and no approval was provided. This closes the request-local prompt-preview boundary, not the parent all-store item or any 3D generation, provider/queue execution, project, revision, export, artifact, governance, or release authority.

Isis Auto-Rigging browser-demo and bone-map-analysis verification#

The implementation source is 55f36ce86cf9d0fb8f263b070e5c69bc4e5196e8, published directly to origin/main on 2026-07-23 UTC. Repository tracing found two distinct capabilities on the route. The large recovery workspace is built from source-defined sample sessions and React state that exists only in the current tab. Its apparent landmark, correction, skin-weight, validation, and motion-application actions have no project, collaboration record, server-side rig mutation, animation application, export, artifact, governance record, or release connection. The administrator endpoint separately accepts only caller-supplied bone names and invokes the pure deterministic humanoid-name membership helper. It receives no mesh, detected skeleton, rig identity, or artifact identity.

GET and successful POST now return the exact no-store request_local_non_authoritative_humanoid_bone_map_analysis disposition. It declares no persistence, request-only retention, access-scope-only authority, caller-supplied name production, deterministic source-defined membership analysis, and no mesh binding, skeleton detection, rig mutation, retarget admission, animation application, export admission, artifact output, mutations, or authoritative state. POST accepts exactly bones; the list is nonempty and capped at 256 unique entries, while each case-sensitive name must be trimmed, control-character-free, and no longer than 100 characters. Additional mutation/admission fields fail with 400.

The browser requires the exact disposition, input contract, required catalog, and optional catalog. It independently recomputes every required-name presence row, missing/optional/extra list, coverage value, completeness boolean, and summary count from the submitted names. A catalog claiming rig authority or a successful acknowledgement with invented completeness fails closed. The route leads with both honest boundaries, labels one mounted route and four nonexistent shapes documented-only, provides a 44-pixel analysis control, and reflows its previously fixed-minimum stage grids without horizontal overflow at 390 pixels.

text
pnpm --dir apps/oshun/bff exec vitest run \
  src/__tests__/admin-isis-auto-rigging-route.test.ts
  1 file passed; 5/5 tests passed

pnpm --dir apps/oshun/web exec vitest run \
  src/components/__tests__/StudioIsisAutoRiggingSkeletonLane.live.test.tsx \
  src/components/__tests__/StudioIsisAutoRiggingWorkspace.test.tsx \
  src/components/__tests__/StudioIsisAutoRiggingWorkspace.integration.test.tsx \
  src/components/__tests__/StudioIsisAutoRiggingPage.test.tsx \
  src/components/__tests__/StudioIsisAutoRiggingRouteMap.test.ts
  5 files passed; 27/27 tests passed

# real built BFF artifact + direct Next dev server + disposable fully migrated
# PostgreSQL/Redis; retries disabled
E2E_BASE_URL=http://127.0.0.1:<isolated-web-port> \
E2E_BFF_URL=http://127.0.0.1:<isolated-bff-port> \
pnpm --dir apps/oshun/web exec playwright test \
  e2e/studio-isis-auto-rigging-boundary.spec.ts \
  --config=playwright.config.ts --workers=1 --retries=0
  8/8 tests passed with applicable axe analysis; all 32 migrations applied

node tools/typecheck/ratchet.mjs \
  --app apps/oshun/web --tsconfig tsconfig.typecheck.json
pnpm --dir apps/oshun/web exec eslint <affected web source paths>
git diff --check
  web typecheck, affected lint/formatting, and whitespace checks passed

NODE_OPTIONS=--max-old-space-size=6144 \
node tools/typecheck/ratchet.mjs \
  --app apps/oshun/bff --tsconfig tsconfig.typecheck.json
  reached only the same two unrelated current-main errors in
  autonomous-content-metrics-store.ts and autonomy-route.test.ts

pnpm --dir apps/oshun/bff run build
pnpm --dir apps/oshun/bff run verify:production-artifact
  migrated-database production-artifact smoke passed;
  36,107,416-byte entry bundle;
  SHA-256 0c9de0daca5094217454ce4a9901ae2c837e99d3107435135240720df5edfd88

The first full browser run intentionally failed closed because the manually started production-mode BFF rejected unsigned development tokens and the web process omitted the explicit local-only Studio bypass. After correcting the harness, the first valid run passed 7/8 and exposed a real 390-pixel overflow in legacy fixed-minimum stage grids. Descendant-bounds diagnostics guided the responsive-grid fix; a clean full rerun then passed 8/8 with retries disabled. The discarded harness and defect-discovery runs are not represented as passing verification. The disposable database was removed after testing. The web production build was not run because the 15 GiB host is below the repository's 32 GiB hard gate and no approval was provided. This closes the browser-demo loss and request-local bone-name-analysis boundary, not the parent all-store item or real skeleton detection, rig mutation, retargeting, animation application, project persistence, collaboration, export, artifacts, governance, or release authority.

Isis InstantID alias-analysis verification#

The implementation source is 359b8063613466a8891e23dcb9d5aa4eb5609574, published directly to origin/main on 2026-07-23 UTC. Repository tracing found that the shared ControlNet endpoint receives only a caller-supplied domain and mode string, then invokes the pure source-defined @isis/job-envelope alias normalizer and legacy-name mapper. The endpoint receives no face, image, identity, embedding, conditioning input, job identity, provider response, or artifact identity. It has no connection to conditioning execution, generation, job admission, provider execution, persistence, export, governance, or release.

GET and successful POST now return the exact no-store request_local_non_authoritative_control_mode_alias_analysis disposition. It declares no persistence, request-only retention, access-scope-only authority, caller-supplied string production, deterministic source-defined alias normalization, and no image binding, identity extraction, conditioning execution, job admission, provider execution, artifact output, mutations, or authoritative state. GET returns an exact source-defined catalog and input contract without a generated timestamp. POST accepts exactly domain and mode; the domain must be one of the three catalog values and the mode must be a trimmed, control-character-free string of at most 100 characters. Additional execution or admission fields fail with 400.

The InstantID browser requires the entire exact catalog and disposition rather than trusting a partial mode array. It independently recomputes the canonical InstantID and legacy-workflow names from the submitted alias and accepts a successful acknowledgement only when every field agrees exactly. Incomplete or authority-inflated catalogs, invented execution fields, and semantically false successful mappings fail closed. The restrained route leads with the string-normalization boundary, labels successful output as an alias description with no admitted job, preserves 44-pixel controls, and identifies one mounted route plus four documented-only shapes instead of presenting scenes, exports, revisions, governance records, or release signoff as implemented.

text
pnpm --dir apps/oshun/bff exec vitest run \
  src/__tests__/admin-isis-controlnet-route.test.ts
  1 file passed; 6/6 tests passed

pnpm --dir apps/oshun/web exec vitest run \
  <ControlNet, IP-Adapter, and InstantID component/page/route-map tests>
  12 files passed; 20/20 tests passed

# exact built BFF artifact + direct Next dev server + disposable fully migrated
# PostgreSQL/Redis; retries disabled
E2E_BASE_URL=http://127.0.0.1:<isolated-web-port> \
E2E_BFF_URL=http://127.0.0.1:<isolated-bff-port> \
pnpm --dir apps/oshun/web exec playwright test \
  e2e/studio-isis-instantid.spec.ts \
  --config=playwright.config.ts --workers=1 --retries=0
  10/10 tests passed with applicable axe analysis; all 32 migrations applied

node tools/typecheck/ratchet.mjs \
  --app apps/oshun/web --tsconfig tsconfig.typecheck.json
pnpm --dir apps/oshun/web exec eslint <affected web source paths>
git diff --check
  web typecheck, affected source lint/formatting, and whitespace checks passed

NODE_OPTIONS=--max-old-space-size=6144 \
node tools/typecheck/ratchet.mjs \
  --app apps/oshun/bff --tsconfig tsconfig.typecheck.json
  reached only the same two unrelated current-main errors in
  autonomous-content-metrics-store.ts and autonomy-route.test.ts

pnpm --dir apps/oshun/bff run build
pnpm --dir apps/oshun/bff run verify:production-artifact
  migrated-database production-artifact smoke passed;
  36,108,864-byte entry bundle;
  SHA-256 50e4a00c3ff930b33eac2d338d49c8d3623891b49e30a263441f0da3822be5ad

The browser suite proves the Studio hard block, anonymous redirect, exact live GET/POST/400/422 no-store contracts, three valid alias mappings, pending-submit lockout, unresolved input, malformed and authority-inflated response rejection, catalog and network failures, scope denial, route honesty, touch targets, and descendant-level mobile containment at 390 pixels. The disposable database was removed after testing. The web production build was not run because this 15 GiB host is below the repository's 32 GiB hard gate and no approval was provided. This closes the InstantID request-local alias-analysis consumer and establishes the shared backend disposition, not the still-unhardened IP-Adapter or ControlNet browser consumers and not identity extraction, image processing, conditioning, generation, job admission, provider execution, persistence, export, artifacts, governance, or release authority.

Isis IP-Adapter alias-analysis verification#

The consumer implementation source is 8fa00ff094c0a38f74da1635c52d8b08d8dcb1cb, published directly to origin/main on 2026-07-23 UTC. The shared BFF disposition and exact no-store contract were established in the immediately preceding InstantID slice at 359b8063613466a8891e23dcb9d5aa4eb5609574; this slice does not change or expand that backend authority. Repository tracing confirms that the IP-Adapter route sends only domain: ipadapter and a caller-supplied mode string. It sends no image, embedding, extracted style or identity, conditioning input, job, provider response, or artifact identity.

The browser now consumes a single shared exact catalog definition with the InstantID consumer instead of maintaining a weaker partial shape. It requires the full request_local_non_authoritative_control_mode_alias_analysis disposition and exact catalog/input contract. For every submitted IP-Adapter alias it independently recomputes the expected canonical mode and legacy workflow name. A partial or authority-inflated catalog, invented conditioning field, wrong domain/input echo, unsupported canonical value, or semantically false successful mapping fails closed.

The restrained route leads with the string-normalization boundary: no reference image or embedding is inspected, no style or identity is extracted, no conditioning runs, no job is admitted, and no provider result, artifact, export, governance record, or release decision exists. Successful output is labelled an alias description with no admitted job. Controls retain the 44-pixel floor, and the route map now reports one mounted analyzer plus four documented-only shapes rather than presenting scenes, exports, revisions, governance records, or signoff as implemented.

text
pnpm --dir apps/oshun/web exec vitest run \
  <ControlNet, IP-Adapter, and InstantID component/page/route-map tests>
  12 files passed; 22/22 tests passed

# exact previously built shared-contract BFF artifact + direct Next dev server
# + disposable fully migrated PostgreSQL/Redis; retries disabled
E2E_BASE_URL=http://127.0.0.1:<isolated-web-port> \
E2E_BFF_URL=http://127.0.0.1:<isolated-bff-port> \
pnpm --dir apps/oshun/web exec playwright test \
  e2e/studio-isis-ip-adapter.spec.ts \
  --config=playwright.config.ts --workers=1 --retries=0
  10/10 tests passed with applicable axe analysis; all 32 migrations applied

node tools/typecheck/ratchet.mjs \
  --app apps/oshun/web --tsconfig tsconfig.typecheck.json
pnpm --dir apps/oshun/web exec eslint <affected web source paths>
git diff --check
  web typecheck, affected source lint/formatting, and whitespace checks passed

The browser suite proves the Studio hard block, anonymous redirect, exact live GET/POST/400/422 no-store contracts, three valid IP-Adapter alias mappings, pending-submit lockout, unresolved input, malformed and authority-inflated response rejection, catalog and network failures, scope denial, route honesty, touch targets, and descendant-level mobile containment at 390 pixels. The disposable database was removed after testing. No BFF source or bundle changed; the shared route's focused tests, source build, migrated-database production-artifact smoke, and 36,108,864-byte bundle digest remain recorded in the immediately preceding InstantID evidence. The web production build was not run because this 15 GiB host is below the repository's 32 GiB hard gate and no approval was provided. This closes the IP-Adapter request-local alias-analysis consumer, not the still-unhardened ControlNet browser consumer and not image or embedding analysis, style or identity extraction, conditioning, generation, job admission, provider execution, persistence, export, artifacts, governance, or release authority.

Isis ControlNet alias-analysis verification#

The final shared-consumer implementation source is 0ebba001c2d5a38ef38081db1ee5dd69759ab1f2, published directly to origin/main on 2026-07-23 UTC. The exact no-store BFF contract remains the shared backend established at 359b8063613466a8891e23dcb9d5aa4eb5609574; this consumer-only slice does not add backend authority. Repository tracing confirms that the ControlNet browser submits only a selected catalog domain and caller-supplied mode string. It submits no control image, detector result, preprocessor map, conditioning graph, job, provider response, or artifact identity.

The shared browser contract now contains the complete source-defined alias and legacy-name semantics for ControlNet, IP-Adapter, and InstantID. All three consumers use that one exact catalog and semantic resolver. The ControlNet browser requires the full request_local_non_authoritative_control_mode_alias_analysis disposition and independently recomputes every successful response from the submitted domain and mode. Partial or authority-inflated catalogs, wrong echoes, cross-domain mappings, unsupported canonical values, false legacy names, and invented preprocessing or execution fields fail closed.

The restrained route leads with the string-only boundary: no control image is inspected, no detector or preprocessor runs, no conditioning graph executes, no job is admitted, and no provider result, artifact, export, governance record, or release decision exists. Successful output is labelled an alias description with no admitted job. Controls retain the 44-pixel floor, and the route map reports one mounted analyzer plus four documented-only shapes rather than presenting scenes, exports, revisions, governance records, or signoff as implemented.

text
pnpm --dir apps/oshun/web exec vitest run \
  <ControlNet, IP-Adapter, and InstantID component/page/route-map tests>
  12 files passed; 24/24 tests passed

# exact previously built shared-contract BFF artifact + direct Next dev server
# + disposable fully migrated PostgreSQL/Redis; retries disabled
E2E_BASE_URL=http://127.0.0.1:<isolated-web-port> \
E2E_BFF_URL=http://127.0.0.1:<isolated-bff-port> \
pnpm --dir apps/oshun/web exec playwright test \
  e2e/studio-isis-controlnet.spec.ts \
  --config=playwright.config.ts --workers=1 --retries=0
  10/10 tests passed with applicable axe analysis; all 32 migrations applied

node tools/typecheck/ratchet.mjs \
  --app apps/oshun/web --tsconfig tsconfig.typecheck.json
pnpm --dir apps/oshun/web exec eslint <affected web source paths>
git diff --check
  web typecheck, affected source lint/formatting, and whitespace checks passed

The browser suite proves the Studio hard block, anonymous redirect, exact live GET/POST/400/422 no-store contracts, semantic resolution across all three domains, pending-submit lockout, unresolved input, malformed and authority-inflated response rejection, catalog and network failures, scope denial, route honesty, touch targets, and descendant-level mobile containment at 390 pixels. The disposable database was removed after testing. No BFF source or bundle changed; the shared route's focused tests, source build, migrated-database production-artifact smoke, and 36,108,864-byte bundle digest remain recorded in the preceding InstantID evidence. The web production build was not run because this 15 GiB host is below the repository's 32 GiB hard gate and no approval was provided. This closes the ControlNet request-local alias analyzer and completes the three mounted consumers of that shared contract, not control-image analysis, detection, preprocessing, conditioning, generation, job admission, provider execution, persistence, export, artifacts, governance, or release authority.

Remaining work for full V1-002 closure#

The remaining V1-002 implementation must finish the operational-store inventory outside the now-hardened autonomy, run-authority, generation, operator-audit, Studio, central-admin, and customer-deletion-lifecycle boundaries. Every remaining store needs an explicit durable-or-recomputable disposition, with restart/failed-write/race proof for durable state and ephemeral-loss proof for caches. The final audit must implement and prove deletion/privacy/retention fanout for every other newly durable user-scoped partition. profile and session are now mapped. Account-protection screening is now acknowledgement- bound in normalized PostgreSQL rows, exact-subject DSAR-visible under session, physically erasable behind a digest-only fence, and purged after the canonical legal-hold-aware 90-day window. Its login producer remains explicitly fail-open and does not enforce a high-risk verdict. The local Metis academic-record partition now replaces the former structural-absence path with a real evidence_pack export/eraser and has a 730-day legal-hold/retention-exception-aware physical expiry path. Its named canonical V1 evidence/verdict-table DSAR gaps now close when OSHUN_V1_DATABASE_URL is configured and remain explicit without that binding. Until the remaining cross-store and fanout proof lands, the final all-store box remains open. Local calendar OAuth connections are now acknowledgement-bound, restart-safe, secret-free in profile DSAR, and physically removed with a persistent subject fence during signed profile erasure. Google, Apple, and Microsoft provider-side grant revocation remains explicitly open. The reminder schedule, delivered ledger/ownership, and inbox partition is now closed. The three connected BFF reminder-source projections for due assignments, upcoming sessions, and scheduled content drops are also acknowledgement-bound, restart-safe, exact-owner DSAR-visible under continuity_state, physically erased behind independent subject fences, and purged strictly after their 30-day terminal continuity window. Their owning services' complete per-recipient event production remains outside that projection claim. Arete weekly-review closures, living-offering decisions, and coach decisions are now acknowledgement-bound, restart-safe, exact-owner DSAR-visible under continuity_state, and physically erased behind three persistent subject fences; their lifecycle-bound product-history retention ends at signed account erasure. Nyx saved objects, event reminders, and minimized per-member search counts are now acknowledgement-bound in one restart-safe snapshot, exact-owner DSAR-visible under continuity_state, and physically erased behind a persistent subject fence; query strings are never retained. Nisaba-local saved flags and study reminders are also closed with independent durable category fences. Authenticated client-state slots are now acknowledgement-bound, exact-owner DSAR-visible under continuity_state, physically erased behind a persistent subject fence, and automatically purged after 30 days of inactivity through startup and daily retention execution. Only workspace-layout has a demonstrated web producer today; the other allow-listed slots remain API capacity rather than claimed connected UI flows. Authenticated Psyche dialogue sessions are now acknowledgement-bound across both HTTP and WebSocket mutation paths, exact-owner DSAR-visible under conversation_history, physically erased behind a persistent subject fence, and purged after the canonical 30-day creation-time window unless exact admin legal-hold or category-exception authority blocks physical deletion. The four authenticated Studio world- configuration, story-graph, quest, and timeline authoring-record partitions are also acknowledgement-bound, restart-safe, exact-owner DSAR-visible under continuity_state, physically erased behind independent persistent subject fences, and purged after 30 days of inactivity. They have no demonstrated first-party web consumer, and their four whole-snapshot queues remain per process. Mentor Presence rendered performances are now acknowledgement-bound, restart-safe, exact-owner DSAR-visible under generated_artifact, physically erased behind a persistent subject fence, and purged after the canonical 365-day creation-time window unless an active legal hold or category retention exception blocks physical deletion. Expired held media is withheld from reads; its whole-snapshot queue remains per process, has bounded inline-media capacity, and has no object-store offload or demonstrated listing/revocation UI. The separate Lilith Studio Tara scene-publish receipt is now acknowledgement-bound, restart-safe, exact-owner DSAR-visible under generated_artifact, physically erased behind a persistent subject fence, and purged after the canonical legal-hold-aware 365-day creation-time window. The first-party editor submits the exact manifest and its Playwright journey reaches the durable receipt, but the per-process whole-snapshot queue lacks distributed compare-and-swap and the receipt remains disconnected from editorial approval, audit, supersede, customer publication, and natural browser token propagation. The separate cross-process conversation-turn transcript store and the authenticated shell-assistant producer are now acknowledgement-bound, exact-owner DSAR-visible under conversation_history, physically erased behind a persistent subject fence, and purged after the same canonical legal-hold-aware 30-day creation-time window. The shell assistant's separate session-continuity checkpoint is now acknowledgement-bound, exact-owner DSAR-visible under continuity_state, physically erased behind a persistent subject fence, and purged after the engine's 30-minute creation-time lifetime; its full raw transcript remains excluded in favor of the separate authority. The connected BFF Iris memory partition is now acknowledgement-bound across its working and archival tiers, exact-owner DSAR-visible under memory_scope, and physically erased and fenced before the independent canonical signed receipt is accepted. It is purged after 365 days of inactivity through startup and supervised retention execution, with normal reads durably refreshing last access. The canonical Iris service remains the independent remote authority; its receipt is still required, and this local closure does not close that service or the wider inventory. Notification preferences and notification read/dismiss state are now closed through profile and continuity_state. Personalization vectors and active-persona selections are now closed together through personalization_vector. Customer message history, delivery receipts, opt-outs, and delayed dispatches are now closed through continuity_state. Device push-token credentials are now closed through session. Customer email, SMS, and WhatsApp bindings are now closed through profile. Per-user Telegram captures and profile state are now closed through saved_claim_passage and profile. Celestial ritual schedules are now closed through continuity_state. The BFF wearable-health store is now durable and composes into ritual_completion, but its actual HealthKit/Google Fit production adapters and live provider receipts remain absent. Its DSAR section, and the morning-capture journal_entry section, now query their canonical V1 rows when the shared database is configured and otherwise report the gaps explicitly. Customer data-export request metadata and exact bundle bytes are now acknowledgement-bound; short-lived bundles compose into generated_artifact, while compliance-retained request metadata is now pseudonymized during account erasure, durably anchored for seven years, and physically purged by the shared legal-hold/retention-exception-aware executor. Canonical customer-consent current state, complete retained decision evidence/history, expiry, policy revision, and DSAR export are now acknowledgement-bound. Full-account erasure pseudonymizes that compliance-retained consent_record ledger, minimizes its caller-supplied text and evidence references, anchors it for seven years, and connects it to the same legal-hold/retention-exception-aware physical purge. The BFF customer-billing and Fiat Stripe operational stores are now acknowledgement-bound, restart-safe, DSAR-visible, and locally pseudonymized on account deletion. Both pseudonym sets now have durable seven-year anchors and are connected to the legal-hold/retention-exception-aware physical purge. The bound Stripe Customer is deleted and confirmed before local pseudonymization; Stripe-retained financial/compliance records remain explicitly excluded from a total-purge claim. Apple/Google merchant-side purchase-record deletion is now dispositioned as unsupported on their documented APIs. Authenticated client subscription-cancellation guidance and the optional secret-safe Google manager seam are now implemented; production manager credentials/client injection, live provider proof, and native-device execution remain open. Customer feedback submissions and operator triage are now acknowledgement-bound, restart-safe, DSAR-visible support_case records and are locally pseudonymized during account deletion. Their five-year retention is now physically enforced by the legal-hold/retention-exception-aware purge executor with a durable anchor and irreversible recreation fence. Authenticated Themis moderation-appeal case outcomes are now acknowledgement-bound, restart-safe, DSAR-visible in the same support_case category, and locally pseudonymized with appellant-authored narrative/evidence removal plus a persistent account fence. Their five-year retention is now physically enforced by the legal-hold/retention-exception-aware purge executor with a durable anchor and irreversible recreation fence. Pre-account verification deliveries, codes, resend authority, signup velocity, and challenge bindings are now acknowledgement-bound and bounded-retention; safe metadata is DSAR-visible and email-owned state composes into profile erasure before the auth identity is removed. Imported member cards/FSRS learning state, citations, captures, followed stories, passage collections, mastery targets, and collection sharing authority are now acknowledgement-bound, restart-safe, DSAR-visible, and compose into saved_claim_passage and collection erasure with persistent subject fences. Recent authenticated queries are now acknowledgement-bound, restart-safe, bounded to 90 days, DSAR-visible, and compose into conversation_history erasure with a persistent subject fence. The activity-summary seam is now code-enforced as a stateless empty production projection; Sky Tonight and privacy receipts now fail closed without deploy-bound canonical sources. All three mutable synthetic stores require explicit injection. Scene tip accruals, settlements, and counsel-authority history are now acknowledgement-bound, restart-safe, and DSAR-visible under billing_receipt; profile erasure pseudonymizes retained financial rows and persists a subject fence. Those records now have seven-year billing_history anchors and shared legal-hold/retention-exception-aware expiry. Expiry irreversibly unlinks the due pseudonym while preserving the adjacent counterparty's exact financial evidence and the ledger's settlement arithmetic. One-per-viewer scene appreciations and the active UTC-day velocity authority are now acknowledgement-bound, restart-safe, DSAR-visible under continuity_state, and compose into its exact signed erasure with a persistent subject fence. Follow relationships and creator-owned premiere allocation/lifecycle state are now acknowledgement-bound, restart-safe, and DSAR-visible under continuity_state; they compose into exact two-role erasure with a persistent subject fence. Follow blocklists, notification preferences, and weekly delivery counts are now removed from that authority; follow creation and premiere fan-out fail closed without complete deploy-bound canonical projections. Notification preferences, including quiet-hours and digest cadence, use their separate acknowledgement-bound, restart-safe, DSAR/erasure-fenced canonical store. The shared group-practice lifecycle and participant-private leave reasons are now acknowledgement-bound in one atomic snapshot, bounded to 30 days, restart-safe, DSAR-visible under continuity_state, and compose into exact host/participant erasure with a persistent subject fence; raw invite bearer tokens are never persisted. Admin achievement-evaluation outcomes are now acknowledgement-bound, restart-safe, strictly catalog-validated, and physically bounded to 90 days; raw progress/unlock inputs and subject identity are not persisted, and the opaque idempotency key is restricted to machine-token syntax rather than a free-form text field. Public living-scene abuse-report intake and operator triage are now acknowledgement-bound, restart-safe, DSAR-visible under support_case, and compose into two-role compliance redaction with a persistent subject fence; unauthenticated reporter-id spoofing is closed. These cases require the same five-year legal-hold/retention-exception-aware purge executor. BFF DMCA notices, ownership mappings, counter-notices, restoration decisions, and uploader strikes are now acknowledgement-bound in one restart-safe statutory snapshot. Authenticated uploader DSAR excludes third-party claimant identity; account erasure scrubs uploader content, pseudonymizes the retained case/strike ledger, and installs a subject fence; and the shared five-year support_case executor physically purges due records unless blocked. Actual external content removal, notification delivery, a production ownership-registration caller, and an unauthenticated claimant rights workflow remain outside that local-record claim. The local DSA statement/reporting-pair and MAR authority is now acknowledgement-bound, restart-safe, affected-account-redactable, fenced, and connected to seven-year review_package retention. The separately durable Themis customer intake now has a three-reviewer operator lifecycle and a replayable pending projection into those appeal rows, so the previously named local appeal-outcome reporting seam is closed. Push notification, external provider-side reversal, and external transparency-database submission remain outside that claim. The general operator-inbox review partition is now acknowledgement-bound, restart-safe, exact-reviewer pseudonymized and fenced on signed account erasure, and connected to seven-year hold-aware purge. Its queue is still fixture-backed: these verdicts do not mutate canonical incident, citation, retraction, or republication authority, and its free-form assignee label is not an operator-directory identity. The citation-drift terminal- resolution and per-source-classification partitions are now acknowledgement- bound, restart-safe, exact-reviewer pseudonymized and fenced on signed account erasure, and connected to seven-year hold-aware purge. Terminal work uses a durable pending intent plus exact incident-authority reconciliation to close the cross-store crash window without claiming an atomic transaction. Authenticated Metis ingest jobs and derived outlines are now acknowledgement-bound, restart- safe, exact-owner DSAR-visible under saved_claim_passage, physically erased behind a persistent subject fence, and retained for the active account lifecycle. Raw pasted source text is not stored; URL credentials/query/fragment and PDF path components are removed before persistence. URL fetching and PDF byte extraction remain deploy-bound rather than being reported as completed processing. The BFF Metis BYO-material operator-decision review_package is now acknowledgement-bound, restart-safe, exact-reviewer pseudonymized and fenced on signed account erasure, and connected to seven-year legal-hold/retention-exception-aware physical purge. It remains an internal non-exportable governance record, and the fixture-backed queue is not connected to real ingest/course-build state or an authoritative learner-owner mapping. Living Scene kept artifacts, exact share media, links, audit/takedown state, and deletion fences are now acknowledgement-bound, restart-safe, DSAR-visible under generated_artifact, physically erasable, and bounded-retention artifacts are purged by an awaited startup/periodic executor. Reissuable 15-minute download grants are explicitly ephemeral. The collector exports the exact-owner BFF generation-jobs/catalog/operator-gallery partitions and, when the production composition root has an explicit ISIS_DATABASE_URL, the exact-owner canonical Isis generated-output rows with private lineage and secret-safe provenance. Without that binding it reports the canonical view as an honest gap. The continuing inventory must disposition any other still-unclassified user-scoped store and bind the dedicated Isis reader in each deployment. The stored bucket/key generated-artifact boundary is now closed for configured S3/MinIO stores. The separate Isis resource-recommendation, intelligent-routing, and cost-tracking histories are now acknowledgement-bound, restart-safe, exact-operator pseudonymized and fenced on signed profile erasure, and connected to seven-year legal-hold/retention-exception-aware review_package purge. Their immutable catalogs are explicitly configured, estimate-only governance inputs, not evidence of live prices, invoices, provider health, budget enforcement, model execution, fallback, or release authority. The separate Isis cost- optimization seam is now explicitly ephemeral_recomputable: it creates no history or authority, retains input and derived preview only for the request or current browser tab, and safely accepts repeat correlation ids because no write occurs. It therefore has no deletion or retention fanout to claim unless a future implementation begins persisting runs. The separate Isis prompt-template endpoint is now likewise explicitly a request-lifetime render preview, not a reusable-template repository. It creates no history or authority, retains prompt source, variables, and derived output only for the request/current browser tab, and has no deletion or retention fanout unless a future implementation begins persisting templates or previews. The final inventory must still identify any provider-native remote asset that lacks such a deletion identity, bind its real provider eraser where it exists, and fail the signed receipt whenever that purge cannot be confirmed.

OIDC pending-login cross-process authority#

The implementation source is 99344f4c9be62aaeb8810c77874984325bc86d8d, published from the V1-002 operational-store audit on 2026-07-26 UTC.

Finding and disposition#

The live SP-initiated OIDC route retained state, nonce, connection identity, safe post-login redirect, and issuance time in a module-global Map. A callback could complete only in the process that issued the redirect. Process replacement discarded every outstanding login, while replicas had independent single-use views and could each accept the same state if traffic reached different processes.

This is short-lived pre-authentication authority, not a recomputable cache: losing it breaks an in-flight identity proof, and consuming it more than once weakens replay protection. Production therefore uses a shared Redis authority:

  • the browser state is SHA-256-digested before it enters a Redis key;
  • issuance is SET ... PX 600000 NX, so collisions never overwrite authority;
  • the stored document has an exact closed schema and immutable ten-minute lifetime;
  • callback consumption uses one Redis script that reads and deletes the record atomically;
  • expired, implausibly future-issued, malformed, partially shaped, unknown, and replayed records cannot mint a session;
  • Redis issuance or consumption failure returns 503 sso_login_state_unavailable instead of falling back to process memory; and
  • the deployable binds the unavailable fail-closed store when Redis is absent.

Direct development and tests retain an explicitly injected in-memory implementation. It has the same digest-keyed, expiry-pruned, single-use semantics, but the production composition root never selects it. Redirect capture also rejects scheme-relative //host values instead of retaining an open-redirect-shaped path.

The record exists before claims map to an Oshun account, contains no asserted email or subject identity, expires after ten minutes, and is physically deleted on use. It therefore creates no user-addressable DSAR or long-term retention partition. The resulting customer account, session, and device session remain in their separately durable and deletion-governed authorities.

Adversarial and recovery proof#

The focused suites prove:

  • a valid cryptographic OIDC callback completes after the issuing Fastify process is closed and replaced;
  • two independent Redis clients racing the same state produce exactly one successful consumption;
  • callback replay returns no record;
  • an issuance collision does not overwrite the first record;
  • Redis keys do not contain raw browser state;
  • TTL and NX arguments are exact;
  • expired and future-issued records return no authority;
  • malformed durable JSON and partial schemas fail loud;
  • Redis read/write failures produce the explicit route-level 503; and
  • the development implementation remains single-use.

Verification#

The host was Linux x86-64 with 15 GiB RAM, 31 GiB swap, Node v24.14.1, and pnpm 10.25.0. Verification ran sequentially because another agent had long-lived web/accessibility processes in the same checkout.

text
pnpm --dir apps/oshun/bff exec vitest run \
  src/auth/sso-login-state-store.spec.ts \
  src/auth/sso-login-routes.test.ts \
  --pool=forks --maxWorkers=1 --no-file-parallelism
  2 files passed; 9/9 tests passed

OSHUN_BFF_IT_REDIS_URL=redis://127.0.0.1:6379 \
pnpm --dir apps/oshun/bff exec vitest run \
  --config vitest.integration.config.ts \
  src/auth/sso-login-state-store.integration.spec.ts \
  --pool=forks --maxWorkers=1 --no-file-parallelism
  1 file passed; 1/1 test passed against Redis 7

pnpm exec eslint <all seven affected production/test TypeScript files> \
  --no-warn-ignored
pnpm exec prettier --write <affected hand-authored TypeScript files>
git diff --check
  passed

pnpm --dir apps/oshun/bff run build
  server.js: 36,457,876 bytes
  source map: 85,414,168 bytes
  server SHA-256:
  15e565ef88a6fb950f0a6453ea15f75e4ab9f467500b4b9cdeb3ae3efb189979

# exact disposable PostgreSQL database created from an empty catalog
pnpm --dir libs/oshun/persistence exec prisma migrate deploy \
  --config prisma.config.ts
  all 32 migrations applied

# built artifact, fresh 32-migration database, and local Redis
pnpm --dir apps/oshun/bff run verify:production-artifact
  Production artifact smoke check passed.

The BFF type ratchet completed and reported five current-main errors outside the affected files: the incoming Isis CLI test, autonomous-content metrics, two autonomy-route test assignments, and tenant-content graph test fixture. None originated in this slice, so they were not represented as a passing typecheck and the pre-commit typecheck was explicitly skipped after the full diagnostic run. The pre-commit formatter, ESLint, conventions ratchet, V2 asset lock, and V5 documentation gates passed. The disposable database was deleted after smoke verification. No user-facing UI, mobile UI, or Unreal surface changed, so Playwright, mobile automation, frontend-skill work, screenshots, and Unreal verification were inapplicable.

Artifact identities#

Artifact SHA-256
apps/oshun/bff/src/auth/sso-login-state-store.ts a889d0104ac95417fccfed11347077fe84dfb463842a416670d2d3df64042974
apps/oshun/bff/src/auth/sso-login-routes.ts 86f1d8edf8673a5db3b690cd68766b4d1d69f16eb4b90aca14f2023b5c245d20
apps/oshun/bff/dist/server.js 15e565ef88a6fb950f0a6453ea15f75e4ab9f467500b4b9cdeb3ae3efb189979

This closes only the pre-authenticated OIDC state/nonce partition. It does not claim a live external IdP receipt, SAML execution, provider-side identity deletion, or closure of the parent V1-002 all-store inventory.

Tenant LMS pending-login and managed-connector durability#

The implementation source is fab8ac2b074e9aa31d003e3c9ad2757b0d3b7f34, published from the continuing V1-002 operational-store audit on 2026-07-26 UTC.

Finding and bounded disposition#

The live tenant LMS composition previously created two authoritative in-process stores at boot:

  • an InMemoryLtiLoginStateStore held the LTI 1.3 state, nonce, issuer, and client binding needed to complete a cryptographically verified launch; and
  • InMemoryTenantLmsConnectorAdminStore acknowledged managed connector creation, overrides, deletion, and environment-connector tombstones even though all mutations disappeared on process replacement.

Neither partition is a recomputable cache. Losing pending login state interrupts an in-flight identity proof and weakens replica-wide replay protection. Losing a managed connector or tombstone changes which institution configuration can initiate launches.

Production now binds pending LTI login state to shared Redis. It hashes browser state before key construction, writes the exact closed-schema payload with PX 600000 NX, atomically reads and deletes through one Redis script, and rejects expired, future-issued, malformed, unknown, or replayed records. Redis errors return 503 lti_login_state_store_unavailable; the composition root binds an unavailable fail-closed authority when Redis is not configured. Direct tests retain an explicitly injected digest-keyed in-memory implementation.

Managed connector overrides and environment tombstones now restore from and write through DurableSnapshotStore under tenant-lms-connector-admin-v1. Each mutation constructs a detached candidate, awaits its PostgreSQL snapshot commit, and only then reconciles the live framework. A failed save cannot make a connector or tombstone visible. Mutations are ordered within the production process, snapshots are canonical and sorted, duplicate or invalid descriptors/tombstones fail hydration, and a production runtime with no bound snapshot rejects admin mutation with 503 tenant_lms_connector_store_unavailable. Version-controlled environment connectors remain deploy-defined; durable managed overrides take precedence and durable tombstones keep an environment connector disabled across restart.

The login-state record is pre-account, contains no asserted learner subject, expires after ten minutes, and is physically deleted on consumption, so it creates no long-term user DSAR partition. Connector documents are institution-level configuration containing public LTI endpoints and identifiers, not provider access tokens or learner data.

This is deliberately not a claim that the entire LMS framework is now durable. LmsConnectorFramework still holds normalized LTI launch sessions and SCORM runtime/learning sessions in process-local maps; those are separate operational/learning partitions that remain in the V1-002 inventory. The snapshot-backed connector store also does not claim cross-replica concurrent writer serialization or automatic read refresh; this slice proves ordered single-writer acknowledgement and restart recovery only.

Adversarial and recovery proof#

The focused suites prove:

  • Redis keys and values do not contain raw browser state;
  • TTL and NX issuance arguments are exact and collisions cannot overwrite;
  • two independent clients racing one state yield exactly one consumer;
  • replay, expiry, future issuance, malformed JSON, and partial schemas fail closed;
  • route-level Redis issue/consume failures return the controlled 503;
  • managed connector overrides and environment tombstones restore into a fresh framework after process replacement;
  • snapshot failure leaves the candidate connector absent from the live framework;
  • concurrent in-process mutations persist and publish in acknowledgement order;
  • missing required connector persistence returns 503 without publishing; and
  • malformed or duplicate snapshots do not replace the current authority.

Verification#

The host had 15 GiB RAM, 31 GiB swap, and 15 GiB free disk. Checks ran sequentially because another agent retained long-lived low-memory web/accessibility and development-server processes in the same checkout.

text
pnpm --dir apps/oshun/bff exec vitest run \
  src/tenant-console/lti-login-state-store.spec.ts \
  src/tenant-console/lms-connector-admin-store.spec.ts \
  src/tenant-console/lms-route.test.ts \
  src/tenant-console/lms-admin-route.test.ts
  4 files passed; 34/34 tests passed

OSHUN_BFF_IT_REDIS_URL=redis://127.0.0.1:6379 \
pnpm --dir apps/oshun/bff exec vitest run \
  -c vitest.integration.config.ts \
  src/tenant-console/lti-login-state-store.integration.spec.ts
  1 file passed; 1/1 test passed against Redis 7

OSHUN_ADMIN_DATABASE_URL=<local PostgreSQL> \
pnpm --dir apps/oshun/bff exec vitest run \
  -c vitest.integration.config.ts \
  src/tenant-console/lms-connector-admin-store.integration.spec.ts
  1 file passed; 1/1 test passed against PostgreSQL

pnpm exec eslint <all affected production TypeScript files>
pnpm exec prettier --write <all affected hand-authored TypeScript files>
git diff --check
node --check apps/oshun/bff/dist/server.js
  passed

node apps/oshun/bff/scripts/build.mjs
  dist/server.js: 34.8 MiB
  dist/server.js.map: 81.5 MiB

# exact disposable database created from an empty catalog
pnpm --dir libs/oshun/persistence exec prisma migrate deploy \
  --config prisma.config.ts
  all 32 migrations applied

# exact built artifact, fresh database, and local Redis
node apps/oshun/bff/scripts/verify-production-artifact.mjs
  Production artifact smoke check passed.

The BFF type ratchet completed and reported five current-main errors outside the affected files: the incoming Isis CLI surface test, autonomous-content metrics, two autonomy-route test assignments, and the tenant-content graph fixture. No LMS file appeared in the diagnostic, so the check is not represented as passing and the commit hook's type stage was explicitly skipped after the full run. A dependency-expanded Nx build was also stopped after unrelated current-main failures in @nyx/constants (TypeScript-6 baseUrl deprecation) and @oshun/tracing (implicit-any callbacks); the BFF's exact artifact builder passed. The pre-commit formatter, ESLint, stub scan, conventions ratchet, V2 asset lock, and V5 documentation gates passed. The freshly migrated disposable database was dropped after artifact smoke. No user-facing web/mobile UI or Unreal surface changed, so frontend-skill, Playwright, mobile automation, screenshots, and Unreal verification were inapplicable.

Artifact identities#

Artifact SHA-256
apps/oshun/bff/src/tenant-console/lti-login-state-store.ts e0ef75457d0859c3ec9902cdc65f716c8243e7040c1beb0e7f70de925ae9b40a
apps/oshun/bff/src/tenant-console/lms-route.ts 85677a7d6198b32981a04d77c913fbe001b00dd60f8065f65b87d7fe3397bc39
apps/oshun/bff/dist/server.js dc7e93a675592801281bf7729d0184c956fa6228e905c4d1816b5b6521ca3657

This closes only the LTI pending-login and managed-connector/tombstone partitions. It does not close the LTI launch-session, SCORM runtime/learning session, live provider receipt, or parent V1-002 all-store inventories.

Tenant LMS volatile session-map disposition#

The implementation source is cf6a834163bb785f5df6f8b01629a5b6888aa74d, published from the continuing V1-002 operational-store audit on 2026-07-26 UTC.

Producer/consumer tracing#

Repository-wide symbol tracing found that LmsConnectorFramework retained two additional maps:

  • normalized LTI launch sessions containing the complete verified claim set; and
  • SCORM launch sessions containing the learner/course identifiers, raw runtime token, launch URL, and mutable learning state.

Every Deep Linking, Names and Roles, Assignment and Grade, and stored-session lookup outside the framework itself was in lms.spec.ts. The production BFF exposes no follow-up endpoint keyed by the returned LTI session id. Its launch route uses the normalized session only to form the current response. Retaining full claims after that response was therefore not recoverable authority; it was unused process-lifetime sensitive data.

The SCORM map was different: its HTTP update route did consume stored state and claimed mutable progress. Tracing found no durable SCORM repository, no authenticated mapping between the request's arbitrary LMS learnerId and an Oshun deletion subject, no tenant-scoped erasure path, and no retention/legal- hold authority. Persisting that map as-is would turn a restart defect into an unowned learner-data privacy defect.

Disposition#

LmsConnectorFramework now has two explicit retention controls. Its reusable library behavior remains backwards-compatible: both default to retained for callers that actually compose follow-up services. The production tenant LMS factory instead:

  • sets retainLtiLaunchSessions: false;
  • sets retainScormSessions: false; and
  • uses UUID-backed launch identifiers so returned request correlations do not reset or collide across process replacement.

The verified LTI route still returns the exact normalized launch projection, but complete launch claims are request-lifetime and loss after the response cannot drop an approval, side effect, learning record, or later API authority because no such production consumer exists.

SCORM launch/update accepts an injected TenantScormRuntimeStore. Direct route and shared-framework tests explicitly use the framework-backed in-memory adapter. Production binds only unavailableTenantScormRuntimeStore: a valid package can be evaluated request-locally, but the route returns 503 tenant_scorm_runtime_store_unavailable before exposing the generated runtime token or acknowledging progress. The update route returns the same controlled 503 without consulting a volatile map. The production startup log states this boundary instead of claiming SCORM runtime is live.

This is a disabled/unbound product boundary, not a claim of SCORM completion. A future implementation must supply one production authority that atomically persists learning updates across replicas, stores no raw runtime secret, authenticates and maps the institutional learner identity, supports exact tenant/learner export and erasure with resurrection fencing, applies bounded legal-hold-aware retention, and proves restart/concurrency recovery before the composition root may inject it.

Loss and fail-closed proof#

The focused tests prove:

  • disabling LTI retention still returns the normalized verified launch;
  • the returned LTI id cannot resolve a later Deep Linking call when retention is disabled;
  • disabling SCORM retention still permits request-local validation and launch URL construction inside the reusable framework, but creates no stored session and rejects later mutation;
  • the deploy factory binds no process-local SCORM authority by default;
  • production-style SCORM launch returns 503 and never exposes the generated runtime token;
  • production-style update returns 503 for every session id rather than reading volatile state; and
  • explicitly injected test composition retains the original token authorization and learning-state behavior.

Verification#

text
pnpm --dir libs/shared/inbound-integrations exec vitest run src/lms.spec.ts
  1 file passed; 9/9 tests passed

pnpm --dir apps/oshun/bff exec vitest run \
  src/tenant-console/lms-route.test.ts \
  src/tenant-console/lms-admin-route.test.ts \
  src/tenant-console/lti-login-state-store.spec.ts \
  src/tenant-console/lms-connector-admin-store.spec.ts
  4 files passed; 36/36 tests passed

pnpm --dir libs/shared/inbound-integrations run typecheck
  passed application and spec TypeScript checks

pnpm exec eslint <affected production TypeScript files>
pnpm exec prettier --check <all affected hand-authored TypeScript files>
git diff --check
node --check apps/oshun/bff/dist/server.js
  passed

node apps/oshun/bff/scripts/build.mjs
  exact production artifact built

# exact disposable database created from an empty catalog
pnpm --dir libs/oshun/persistence exec prisma migrate deploy \
  --config prisma.config.ts
  all 32 migrations applied

# exact built artifact, fresh database, and local Redis
node apps/oshun/bff/scripts/verify-production-artifact.mjs
  Production artifact smoke check passed.

The shared library's standalone ESM bundle completed, but its declaration bundler stopped on the repository-wide TypeScript-6 baseUrl deprecation. The BFF type ratchet again reported only the same five current-main errors outside the LMS files, so neither failure is represented as passing and the commit hook's type stage was explicitly skipped after the diagnostics. The exact BFF artifact builder passed. Pre-commit formatting, ESLint, stub scanning, conventions, V2 asset locking, and V5 documentation validation passed. The freshly migrated database was dropped after artifact smoke. No user-facing web/mobile UI or Unreal surface changed, so frontend-skill, Playwright, mobile, screenshot, and Unreal verification were inapplicable.

Artifact identities#

Artifact SHA-256
libs/shared/inbound-integrations/src/lms.ts 220883e102db5da87657d8601f82980c02bdf0832776610810090cce65da2146
apps/oshun/bff/src/tenant-console/lms-route.ts 6a2ee8b1720f09040a952d9f2b902f697cd6329196789304a11665e8b0dc9b78
apps/oshun/bff/dist/server.js 6f36a0dca14f02552d1b0eb1c4c9852f25ccfc3d8ca79277bfa22c1484522f5d

This closes both production process-local LMS session maps by request-lifetime or fail-closed disposition. It does not claim a live Deep Linking/NRPS/AGS follow-up surface, a live SCORM runtime, an institutional learner-identity mapping, or closure of the parent V1-002 all-store inventory.

Living Scenes render-budget authority#

The implementation source is 4e0876107bf0421f7ee20995e6636beb3594e601, published from the continuing V1-002 operational-store audit on 2026-07-26 UTC.

Operational classification and disposition#

The authenticated Living Scenes PNG route formerly enforced its CPU/cost boundary with a module-global Map keyed by raw user id. Its one-render-in- flight lease and six-renders-per-minute counter therefore reset on process replacement and differed between replicas. That map did not contain an approval, artifact, publication receipt, learning record, or user-authored state, so copying it into long-term application persistence would be the wrong privacy and retention model. It is short-lived operational abuse-control state, but it must be shared and atomic to protect the render service.

Production now injects RedisLivingSceneRenderBudgetGate. One Lua acquisition script atomically checks the active lease, enforces the fixed-window count, creates an ownership token with bounded expiry, increments the count, and sets the first-count expiry. Release is a second ownership-checked Lua script, so a stale renderer cannot delete a replacement lease. Count and lease keys contain only a SHA-256 user digest and share an explicit Redis Cluster hash tag. The count expires after 60 seconds and the crash-recovery lease after 30 minutes; raw user ids and render payloads are not stored.

The deployable starts with an unavailable authority and replaces it only when the shared Redis client is configured. Missing, malformed, or failed Redis authority returns controlled 503 render_budget_unavailable; it never falls back to restart-resettable process memory. An explicitly named in-memory gate remains only as the direct route/unit-test default and models the same ownership, cap, window, and lease-expiry behavior.

This partition is not a DSAR source of truth: it is pseudonymous, contains no render content, and expires automatically within the operational window. A failed release can temporarily deny another render but cannot over-admit one; the bounded lease recovers after a crashed renderer. The actual generated PNG response remains request-local and is outside this budget-state disposition.

Concurrency, failure, and recovery proof#

The focused and live tests prove:

  • two gate instances sharing Redis admit exactly one concurrent render for one account;
  • lease release requires the exact winning ownership token;
  • the six-render count survives process/instance replacement and the seventh request is denied;
  • different accounts retain independent budgets;
  • Redis keys omit raw user ids and both Lua keys use the same cluster hash tag;
  • malformed Redis responses and Redis failures fail closed;
  • the in-memory test adapter recovers an expired lease without allowing an old owner to release its replacement; and
  • route composition returns 503 before rendering when its authority is unavailable.

Verification#

The host had 15 GiB RAM, 31 GiB swap, and 15 GiB free disk. Checks ran sequentially while long-lived low-memory development/accessibility processes continued elsewhere on the host.

text
pnpm --dir apps/oshun/bff exec vitest run \
  src/living-scenes/render-budget-gate.spec.ts \
  src/living-scenes/render-route.test.ts
  2 files passed; 10/10 tests passed

OSHUN_BFF_IT_REDIS_URL=redis://127.0.0.1:6379 \
pnpm --dir apps/oshun/bff exec vitest run \
  -c vitest.integration.config.ts \
  src/living-scenes/render-budget-gate.integration.spec.ts
  1 file passed; 1/1 test passed against live Redis

pnpm exec eslint <all affected production TypeScript files>
pnpm exec prettier --check <all affected hand-authored TypeScript files>
git diff --check
node --check apps/oshun/bff/dist/server.js
  passed

node apps/oshun/bff/scripts/build.mjs
  dist/server.js: 34.8 MiB
  dist/server.js.map: 81.5 MiB

# exact disposable database created from an empty catalog
pnpm --dir libs/oshun/persistence exec prisma migrate deploy \
  --config prisma.config.ts
  all 32 migrations applied

# exact built artifact, fresh database, and local Redis
node apps/oshun/bff/scripts/verify-production-artifact.mjs
  Production artifact smoke check passed.

The direct BFF TypeScript process first exhausted its default 4 GiB heap. A supervised 8 GiB diagnostic completed with only transitive workspace errors and no error in the affected files. The authoritative BFF app-own ratchet then completed and reported the same five current-main errors outside this slice: the Isis CLI surface test, autonomous-content metrics, two autonomy-route test assignments, and the tenant-content graph fixture. The check is not represented as passing, and the commit hook's type stage was skipped only after those full diagnostics. The pre-commit formatter, ESLint, stub scan, conventions ratchet, V2 asset lock, and V5 documentation gates passed. Both freshly migrated disposable databases were dropped after artifact smoke. No user-facing web/mobile UI or Unreal surface changed, so frontend-skill, Playwright, mobile, screenshot, and Unreal verification were inapplicable.

Artifact identities#

Artifact SHA-256
apps/oshun/bff/src/living-scenes/render-budget-gate.ts b639eb33e7be007fb485eaffb5fb2170afc6118412030af67262f3a1989d17aa
apps/oshun/bff/src/living-scenes/render-route.ts 98c28210ccd3fbde618d9522730753c4dc7ce5325d2c217a8baa1a058ccf0670
apps/oshun/bff/dist/server.js b48810ad2917f0d1db7d809593a09871130f18d143dd0ccb2fedc7a1fff8fcaa

This closes the production Living Scenes render-budget map by replacing it with shared, atomic, bounded operational authority. It does not claim durable render artifacts, provider-backed Living Scenes generation, or closure of the parent V1-002 all-store inventory.

Notification preference shadow-store disposition#

The implementation source is 6f696261d7cb2abeaa96004572c0773f5c25bf41, published from the continuing V1-002 operational-store audit on 2026-07-26 UTC.

Producer/consumer tracing and canonical authority#

Repository-wide import and symbol tracing found no caller of notifications/quiet-hours.ts or notifications/digest.ts. Those legacy modules nevertheless exposed raw-user-keyed mutable maps for quiet-hours configuration, digest configuration, and last-delivery time. They were not registered in the BFF composition root, imported by a route, included in the production artifact, connected to persistence, or connected to account export, erasure, or retention.

The live authenticated preference routes already use notificationPreferencesStore. Its canonical document includes the complete quiet-hours and digest configurations, acknowledges mutations only after an ordered DurableSnapshotStore write, hydrates before production traffic, and returns controlled 503 without publishing a failed candidate. Exact-subject erasure physically removes the preference record, persists a deletion fence, rejects stale recreation after restart, and preserves adjacent subjects.

The two orphan modules are now deleted rather than being made into a second durable authority. No delivery receipt was migrated from lastDigestDelivery: tracing proved there was no producer or consumer, and inventing durable historical receipts for an uncomposed engine would create a false delivery claim. Any future digest dispatcher must use its actual durable, idempotent delivery/outbox authority; the canonical preference store owns only the member's scheduling choice.

Loss, privacy, and recovery proof#

Focused proof now explicitly writes a member's quiet-hours window, timezone, active days, digest frequency, delivery time, and include-read choice through the canonical durable mutation, restores a new store instance, and verifies the exact projection and revision. The live PostgreSQL test repeats that process-replacement proof and then proves exact-subject erasure, durable resurrection refusal, and adjacent-subject preservation.

The authenticated HTTP suite proves the live route seeds, reads, and mutates the same quiet-hours and digest fields, applies related notification filtering, and returns 503 when persistence fails. Repository-wide search after deletion finds no reference to either removed BFF module. On the same source tree, the production bundle was byte-identical before and after their deletion, proving the shadow maps were absent from the runtime graph.

Verification#

text
pnpm --dir apps/oshun/bff exec vitest run \
  src/__tests__/notification-preferences-store.test.ts \
  src/__tests__/notifications-preferences-route.test.ts \
  src/notifications/state-durability.test.ts
  3 files passed; 25/25 tests passed

OSHUN_ADMIN_DATABASE_URL=<local PostgreSQL> \
pnpm --dir apps/oshun/bff exec vitest run \
  -c vitest.integration.config.ts \
  src/notifications/state-durability.integration.test.ts
  1 file passed; 1/1 test passed against PostgreSQL

pnpm exec eslint <affected tests>
pnpm exec prettier --check <affected tests>
git diff --check
node --check apps/oshun/bff/dist/server.js
  passed

node apps/oshun/bff/scripts/build.mjs
  dist/server.js: 34.8 MiB
  dist/server.js.map: 81.6 MiB

# exact disposable database created from an empty catalog
pnpm --dir libs/oshun/persistence exec prisma migrate deploy \
  --config prisma.config.ts
  all 32 migrations applied

# exact built artifact, fresh database, and local Redis
node apps/oshun/bff/scripts/verify-production-artifact.mjs
  Production artifact smoke check passed.

The BFF app-own type ratchet completed and reported only the same five current-main errors outside the notification files: the Isis CLI surface test, autonomous-content metrics, two autonomy-route test assignments, and the tenant-content graph fixture. The check is not represented as passing, and the commit hook's type stage was skipped only after the full diagnostic. The pre-commit formatter, ESLint, stub scan, conventions ratchet, V2 asset lock, and V5 documentation gates passed. Remote-main integration occurred twice; the focused 25/25 suite and live PostgreSQL test passed after the first integration, and the 7/7 durability suite, live PostgreSQL test, exact build, and artifact smoke passed again after the final integration. Each disposable database was dropped. No user-facing web/mobile UI or Unreal surface changed, so frontend-skill, Playwright, mobile, screenshot, and Unreal verification were inapplicable.

Artifact identities#

Artifact SHA-256
apps/oshun/bff/src/notifications/preferences-store.ts 4d2f08e70a9301d08bbf0398e4ec97037b99600a57df4993f24a4077a3e6d04b
apps/oshun/bff/src/notifications/state-durability.test.ts c6b7e7a8c35ee0fa38f8b7a8f09eff83635d412e85da7c24a6a667444df295e7
apps/oshun/bff/src/notifications/state-durability.integration.test.ts f6702bfe32ed98bb755a235fffeb5cf4960082989781f25029213b63b10207e8
apps/oshun/bff/dist/server.js 2114612e2b77698ff48b7cba307b270ea49469827c3ff3f0c7f40ca736494a54

This closes three uncomposed notification shadow maps by deletion and points quiet-hours/digest preference authority exclusively at the already durable, erasable canonical store. It does not claim a live digest dispatcher or a durable digest-delivery receipt/outbox and does not close the parent V1-002 all-store inventory.

Achievement read-refresh cache disposition#

The implementation source is fb671e9fd4910c3a66bb353433817ecd8b00c800, published from the continuing V1-002 operational-store audit on 2026-07-26 UTC.

Classification and bounded implementation#

The achievement summary route refreshes live cross-domain statistics before idempotently evaluating unlock criteria. Its former module-global debounce map stored raw user ids without a capacity bound. The timestamp was not achievement authority: losing it merely allowed one additional live read/evaluation, while the actual unlocked achievement record belongs to the separately durable achievement store. It is therefore correctly classified as an ephemeral_recomputable read-throttle cache rather than a persistence target.

AchievementReadRefreshCache now stores only SHA-256 subject digests, expires a claim after 30 seconds, prunes expired claims opportunistically, and enforces a hard 10,000-entry ceiling by oldest-entry eviction. Empty identities are rejected. The production route uses one bounded instance; its reset seam exists only to model total process/cache loss in tests.

This cache contains no progress, unlock, approval, learning, or publication record and is not a DSAR source of truth. Loss can increase domain-read load once but cannot suppress an unlock: the next summary read reclaims the cache entry, refreshes authoritative inputs, and runs the same idempotent evaluator.

Loss and capacity proof#

The focused tests prove:

  • raw user ids never appear in retained cache keys;
  • repeated reads within 30 seconds are suppressed;
  • expiry permits a fresh refresh;
  • expired entries are pruned;
  • the oldest digest is evicted at the hard capacity boundary; and
  • clearing the entire cache between two real summary-route reads repeats the refresh but leaves the durable unlocked-achievement count exactly unchanged.

Verification#

text
pnpm --dir apps/oshun/bff exec vitest run \
  src/achievements/read-refresh-cache.spec.ts \
  src/__tests__/achievements-route.test.ts
  2 files passed; 9/9 tests passed

pnpm exec eslint <affected production TypeScript files>
pnpm exec prettier --check <all affected hand-authored TypeScript files>
git diff --check
node --check apps/oshun/bff/dist/server.js
  passed

node apps/oshun/bff/scripts/build.mjs
  dist/server.js: 34.8 MiB
  dist/server.js.map: 81.6 MiB

# exact disposable database created from an empty catalog
pnpm --dir libs/oshun/persistence exec prisma migrate deploy \
  --config prisma.config.ts
  all 32 migrations applied

# exact built artifact, fresh database, and local Redis
node apps/oshun/bff/scripts/verify-production-artifact.mjs
  Production artifact smoke check passed.

The BFF app-own type ratchet completed and again reported only the same five current-main errors outside the affected files. The check is not represented as passing, and the commit hook's type stage was skipped only after the full diagnostic. Pre-commit formatting, ESLint, stub scanning, conventions, V2 asset locking, and V5 documentation validation passed. After integrating three non-overlapping remote commits, the 9/9 focused proof, exact build, and fresh-database artifact smoke passed again. Both disposable databases were dropped. No user-facing web/mobile UI or Unreal surface changed, so frontend-skill, Playwright, mobile, screenshot, and Unreal verification were inapplicable.

Artifact identities#

Artifact SHA-256
apps/oshun/bff/src/achievements/read-refresh-cache.ts 3971bee27e6d8d095369cf13756744a7a5c0f661ad4f2727766ba258af6db8b2
apps/oshun/bff/src/routes/achievements.ts fbadc28dbd68c5fadf5c2534d4ce99c4f5c71980caefb4dfe81e022ad3b3cc18
apps/oshun/bff/src/__tests__/achievements-route.test.ts fc348465e170749385f09b1d328c5e98407d02301df64b9693d56b47f9ba18f2
apps/oshun/bff/dist/server.js 822e2cfff554a60fd2937d2c0a4fedeee23620a2a9eb32169164b40a0ef25483

This closes the unbounded achievement read-refresh map through an explicit bounded/recomputable disposition. It does not alter achievement persistence or close the parent V1-002 all-store inventory.

Agentic governance adapter run-local map disposition#

The disposition was verified on the published main tip 20d944fd9a3cd4bfb5b386040ce9ddbd5a368eeb on 2026-07-26 UTC.

Repository-wide symbol tracing found that createAgenticStudioGovernanceGate is referenced only by its own focused test. No BFF composition root, route, worker, or production orchestration path constructs it. Its envelope and meter maps are also not module globals: a new pair is created inside each factory call from the caller-supplied starting budget list and remains reachable only through that returned run gate.

The maps are therefore request_run_local evaluation state, not a current operational store and not a durability gap. They contain caller-supplied budget ids/envelopes and the meter values advanced while one in-memory route-plan execution runs. They own no persisted run, approval, artifact, effect, or learning record in the production BFF because there is no production consumer. There is no user DSAR partition or retention obligation for an uncomposed constructor-local test adapter.

The focused 5/5 tests prove the intended bounded execution semantics: family kill switches terminate matching nodes, supplied cost meters advance across dispatches and terminate at exhaustion, terminal runs are refused, and the real orchestrator router honors both denial and admission. This does not prove restart-safe budget enforcement. If a future production composition injects this adapter, that work must supply durable run checkpoints and an atomic shared budget meter (or explicitly constrain the whole plan to one non-resumable request) before the path can claim cross-replica or restart-safe cost authority.

text
pnpm --dir apps/oshun/bff exec vitest run \
  src/agentic/agentic-governance-gate.test.ts
  1 file passed; 5/5 tests passed

rg createAgenticStudioGovernanceGate apps/oshun/bff/src \
  --glob '!agentic-governance-gate.ts' \
  --glob '!agentic-governance-gate.test.ts'
  no production references

This closes the two constructor-local maps in the operational-store inventory without deleting the tested adapter or falsely promoting it to a live runtime. It does not claim a production agentic-studio governance composition and does not close the parent V1-002 all-store inventory.

Veritas personal-retraction acknowledgement authority#

The implementation source and published tip is 44e733459bd13b60dbffea5b5c64dedc2430220c, integrated on 2026-07-26 UTC.

Classification, authority, and acknowledgement boundary#

The authenticated personal-retraction route previously stored the reader's acknowledgement in a module-global Map<string, string>. A successful HTTP response therefore claimed “do not show this correction letter again” before any durable write, rolling restarts made the letter reappear, different replicas could disagree, and the raw-user-keyed state was absent from DSAR and account erasure.

This state is an account-scoped profile preference rather than a 30-day continuity cache: it records that one named correction notice must remain suppressed for the life of the account/notice. The replacement PersonalRetractionAcknowledgementStore is the sole BFF authority and retains only canonical {userId, noticeId, acknowledgedAt} records. Production requires and hydrates its schema-v1 DurableSnapshotStore partition before traffic. Acknowledgement mutations are serialized, build a detached candidate, validate and persist it, and publish only after the save succeeds. Duplicate concurrent acknowledgements return the first committed timestamp and do not perform a second write.

The partition is bounded to 100,000 acknowledgements and 100,000 deletion fences. Missing persistence, failed saves, and exhausted capacity return a controlled 503 veritas_retraction_acknowledgement_persistence_unavailable; no volatile candidate is exposed. The read route also fails closed while production durability is unavailable instead of presenting an already-acknowledged letter as new.

Privacy, export, and erasure#

The default profile data-export collector now returns only the exact reader's notice ids and acknowledgement timestamps; it does not repeat the raw subject id or expose adjacent readers. The signed profile deletion fanout removes every acknowledgement for the exact subject, preserves adjacent subjects, and commits a domain-separated SHA-256 subject fence. The raw subject id is absent from the fence set. Reads for a fenced subject return the same honest not-found result as an absent notice, and delayed acknowledgement writes cannot recreate erased state.

Strict hydration rejects unknown/missing fields, noncanonical identities or timestamps, duplicate entries/fences, noncanonical ordering, capacity overflow, and any snapshot that combines a subject record with its deletion fence. Failed restore and failed mutation candidates leave the previously committed view unchanged.

Loss, recovery, and deletion proof#

The focused store suite proves write-before-publish, failed-save rollback and retry, ordered duplicate admission, exact-subject export, adjacent-subject isolation, idempotent deletion, pseudonymous fencing, resurrection refusal, strict snapshot validation, and unbound-production fail closure. The route suite proves authenticated notice/acknowledgement semantics plus controlled read and write 503s. The complete export-bundle suite proves the profile DSAR projection and its exact erasure.

A real PostgreSQL process-replacement test writes target and adjacent records, hydrates through a fresh client/store, exports only the target, erases it through the composed profile deleter, hydrates again, preserves the adjacent record, and rejects stale recreation from the durable fence.

Verification#

text
pnpm --dir apps/oshun/bff exec vitest run \
  src/veritas/personal-retraction-acknowledgement-store.spec.ts \
  src/__tests__/veritas-route.test.ts
  2 files passed; 23/23 tests passed

pnpm --dir apps/oshun/bff exec vitest run \
  src/data-export/bundle-builder.test.ts
  1 file passed; 41/41 tests passed

OSHUN_ADMIN_DATABASE_URL=<local PostgreSQL> \
pnpm --dir apps/oshun/bff exec vitest run \
  -c vitest.integration.config.ts \
  src/veritas/personal-retraction-acknowledgement-durability.integration.spec.ts
  1 file passed; 1/1 test passed against PostgreSQL

pnpm exec eslint <all affected TypeScript files>
pnpm exec prettier --write <all affected TypeScript files>
git diff --check
node --check apps/oshun/bff/dist/server.js
  passed

node apps/oshun/bff/scripts/build.mjs
  dist/server.js: 34.8 MiB
  dist/server.js.map: 81.6 MiB

# exact disposable database created from an empty catalog
pnpm --dir libs/oshun/persistence exec prisma migrate deploy \
  --config prisma.config.ts
  all 32 migrations applied

# exact built artifact, fresh database, and local Redis
node apps/oshun/bff/scripts/verify-production-artifact.mjs
  Production artifact smoke check passed.

The BFF app-own type ratchet completed with an 8 GiB compiler heap and reported only the same five current-main errors outside the affected files: the Isis CLI surface test, autonomous-content metrics, two autonomy-route test assignments, and the tenant-content graph fixture. The check is not represented as passing, and the commit hook's type stage was skipped only after the full diagnostic. Pre-commit formatting, ESLint, stub scanning, conventions, V2 asset locking, and V5 documentation validation passed.

Five non-overlapping Yemaya commits reached origin/main before publication. The scoped commit rebased cleanly; the exact production artifact then rebuilt byte-identically and passed a fresh 32-migration startup smoke again. Every disposable verification database was force-dropped. No user-facing web/mobile layout or interaction contract changed, so frontend-skill, Playwright, mobile, screenshot, and Unreal verification were inapplicable.

Artifact identities#

Artifact SHA-256
apps/oshun/bff/src/veritas/personal-retraction-acknowledgement-store.ts e57a7132f32a629389b3530ac0c9c2e8012c6f09a90e5b002ea64414c24d932a
apps/oshun/bff/src/routes/veritas.ts 90fe5063d50ac52f430f501108b095c889ed5f320abb4b015e68724ca235c4b1
apps/oshun/bff/src/data-export/bundle-builder.ts 9d08d9a19fc5c0677a48a518572db0103ef92662a17bfa4bbc135b3f3a1e81a2
apps/oshun/bff/src/server.ts 905d92be66084a0efc846509d18d5165b8e15f72a4103b547bd10a8f3703fccd
apps/oshun/bff/dist/server.js 00feaa8ad0677f583b1dbf045e12c39c90722e2c91fdc02ea43a4eb01f557fa4

This closes the module-global Veritas personal-retraction acknowledgement map with a bounded, acknowledgement-bound, restart-safe, exportable, and erasable profile authority. It does not convert the static launch-fixture notice into a general retraction-cascade inbox and does not close the parent V1-002 all-store inventory.

Tara procedural ambient-WAV cache disposition#

The implementation source and published tip is 6d185b90dc7d93ddf02af9e1e93e507067f15675, integrated on 2026-07-26 UTC.

Classification and bounded implementation#

The authenticated Tara sitting route derives a procedural ambient plan solely from the requested session id and clamped duration, then renders a deterministic mono PCM WAV. The former module-global cache was already capped at 32 entries, but it retained raw session ids and its entry-only bound allowed approximately 254 MiB of 180-second buffers. It owned no session, listening, completion, generation, approval, publication, or learning record.

The cache is therefore explicitly classified as ephemeral_recomputable, not a persistence target. AmbientWavCache now uses only domain-separated SHA-256 digests of canonical session-id/duration tuples. It enforces both a 32-entry LRU ceiling and a 64 MiB aggregate byte ceiling. Oldest entries are evicted until both limits hold; a single buffer larger than the complete byte budget is served but never retained. Capacities, empty session ids, and non-positive/non-integral durations are rejected at the cache boundary.

The cache exposes no application route, durable record, DSAR partition, or account-erasure obligation. Losing it only repeats deterministic local synthesis. The authenticated route contract, WAV bytes, cache headers, and procedural root metadata are unchanged.

Loss, privacy, and capacity proof#

Focused tests prove digest-only retained keys, entry-bound LRU ordering, multi-eviction byte accounting, oversized-buffer bypass, invalid-boundary rejection, and complete cache clearing followed by byte-identical recomputation. The live Fastify route test repeats the loss drill using the real 30-second synthesizer and verifies exact response-byte equality after the singleton cache is cleared.

Verification#

text
pnpm --dir apps/oshun/bff exec vitest run \
  src/tara/ambient-wav-cache.spec.ts \
  src/tara/ambient-audio.test.ts
  2 files passed; 11/11 tests passed

pnpm exec eslint <all affected TypeScript files> --no-warn-ignored
pnpm exec prettier --write <all affected TypeScript files>
git diff --check
node --check apps/oshun/bff/dist/server.js
  passed

node apps/oshun/bff/scripts/build.mjs
  dist/server.js: 34.8 MiB
  dist/server.js.map: 81.6 MiB

# exact disposable database created from an empty catalog
pnpm --dir libs/oshun/persistence exec prisma migrate deploy \
  --config prisma.config.ts
  all 32 migrations applied

# exact built artifact, fresh database, and local Redis
node apps/oshun/bff/scripts/verify-production-artifact.mjs
  Production artifact smoke check passed.

The BFF app-own type ratchet completed with an 8 GiB compiler heap and reported only the same five current-main errors outside the affected files: the Isis CLI surface test, autonomous-content metrics, two autonomy-route test assignments, and the tenant-content graph fixture. The check is not represented as passing, and the commit hook's type stage was skipped only after the full diagnostic. Pre-commit formatting, ESLint, stub scanning, conventions, V2 asset locking, and V5 documentation validation passed.

One non-overlapping Yemaya commit reached origin/main before publication. The scoped commit rebased cleanly; the exact artifact then rebuilt byte-identically and passed a second fresh 32-migration startup smoke. Both disposable databases were force-dropped. No user-facing layout or interaction contract changed, so frontend-skill, Playwright, mobile, screenshot, and Unreal verification were inapplicable.

Artifact identities#

Artifact SHA-256
apps/oshun/bff/src/tara/ambient-wav-cache.ts 7866f92c374c259355c0691ae8b526b1ed5d1436e25f5d173bd005ebfef108de
apps/oshun/bff/src/tara/ambient-audio-routes.ts e9e4285b9290c3d4220441ec95ecf9573e0bb4cc4db151537e3bab4c059c8ee0
apps/oshun/bff/src/tara/ambient-audio.test.ts a8458f5bdabd16828a43593aaa7c54ca2561233fc45a0db0bd77beb6df81c5ca
apps/oshun/bff/dist/server.js ca4c87658ff618a62ed58c4561b835bface0219502689bef9002e2eb65f5f730

This closes the Tara module-global ambient-WAV map through an explicit, privacy-minimized, dual-bounded, recomputable-cache disposition. It does not claim provider-generated music, retained session audio, or closure of the parent V1-002 all-store inventory.

V3 regional-waitlist unbound collection disposition#

The implementation source commit is 29228d13b6, published to origin/main on 2026-07-26 UTC.

Classification and fail-closed implementation#

The public V3 launch router previously accepted an email address without authentication or an explicit consent contract, stored it in a module-global map, returned a predictable sequential record id, and exposed the raw address through an unauthenticated record lookup. The public web form did not call that endpoint at all; it rendered a fabricated “saved” confirmation locally. No durable lead authority, delivery provider, double-opt-in flow, owner mapping, DSAR/erasure path, or retention policy existed.

The route now declares V3_REGIONAL_WAITLIST_DISPOSITION.mode = unbound-disabled-collection. Valid POST attempts are abuse-protected and return 503 regional_waitlist_not_configured, emailStored: false, persistence: none, and cache-control: no-store without echoing the address. Invalid addresses return a non-echoing 400. The legacy lookup is retained only as a fixed no-store 404, so guessed ids cannot enumerate a record. Launch decisions explicitly report enabled: false, acceptingSignups: false, and the unavailable reason.

The V3 marketing page preserves its existing image-led layout and interaction hierarchy while changing the contract: the regional form calls the real endpoint, disables its button while checking, and reports either the explicit no-collection disposition or an honest unverifiable/network-failure state. Even an arbitrary 2xx response cannot produce a saved confirmation. The default invite form likewise stops claiming an invite was staged. This application of the frontend skill kept the visual thesis intact and confined UI changes to truthful status copy, disabled/loading behavior, and the real request boundary.

The V3 region rollout drill, feature documentation, release-gate verifier, and product checklist no longer claim records persist. The region router and safe no-collection behavior remain verified, while the actual signup checkbox is reopened until consent, delivery, durable owner mapping, privacy, retention, and recovery proof exist.

Verification#

text
pnpm --dir apps/oshun/bff exec vitest run \
  src/__tests__/v3-lilith-launch-route.test.ts
  1 file passed; 4/4 tests passed

pnpm --dir apps/oshun/web exec vitest run \
  src/components/lilith/V3MarketingLanding.test.tsx
  1 file passed; 4/4 tests passed

pnpm verify:v3 region-rollout-compliance
  V3 region rollout compliance verification passed.

E2E_WEB_ONLY=1 E2E_BFF_PORT=4111 E2E_WEB_PORT=3111 \
  pnpm --dir apps/oshun/web e2e \
  e2e/v3-marketing-public-web.spec.ts --workers=1
  3/3 tests passed; the first cold Next-development navigation timed out once,
  then passed on the configured retry; regional flow and scoped axe passed
  first attempt

pnpm --dir apps/oshun/bff exec eslint \
  src/routes/v3-lilith-launch.ts
pnpm --dir apps/oshun/web exec eslint \
  src/components/lilith/V3MarketingLanding.tsx
node --check scripts/v3/verify-v3-region-rollout-compliance.mjs
node --check apps/oshun/bff/dist/server.js
git diff --check
  passed

NODE_OPTIONS='--max-old-space-size=8192' \
  node tools/typecheck/ratchet.mjs \
  --app apps/oshun/web --tsconfig tsconfig.typecheck.json
  no new app-own errors; backlog 0

node apps/oshun/bff/scripts/build.mjs
  dist/server.js: 34.8 MiB
  dist/server.js.map: 81.6 MiB

# exact disposable database created from an empty catalog
pnpm --dir libs/oshun/persistence exec prisma migrate deploy \
  --config prisma.config.ts
  all 32 migrations applied

# exact built artifact, fresh database, and local Redis
node apps/oshun/bff/scripts/verify-production-artifact.mjs
  Production artifact smoke check passed.

The full BFF type ratchet was also run with an 8 GiB compiler heap. It reported only the same five unrelated current-main errors in the Isis CLI surface test, autonomous-content metrics, two autonomy-route test assignments, and the tenant-content graph fixture; it is not represented as passing. Pre-commit formatting, ESLint, stub scans, conventions, V2 asset locking, and V5 documentation validation passed. The host has 15 GiB RAM and therefore the hard resource gate prohibited a Next production build without explicit user approval; targeted Vitest, Playwright, lint, and clean web typecheck supplied the applicable UI coverage instead.

The initial full Playwright service-stack attempt timed out during its repository-defined BFF/database boot at 180 seconds. The isolated web-only run then exercised all three page flows and scoped accessibility checks. Its first cold Next-development navigation timed out and passed on the configured retry; the affected regional flow passed first attempt. Both fresh artifact-smoke databases were force-dropped. Two non-overlapping Yemaya commits arrived during publication; both rebases were clean, and focused tests plus the region verifier passed after the first integration. The second remote change touched only the Yemaya study workspace.

Artifact identities#

Artifact SHA-256
apps/oshun/bff/src/routes/v3-lilith-launch.ts 69e501a49a49cbda94884a1b116b5748a9fad16b11e47b0bb5888a220a575a8d
apps/oshun/bff/src/__tests__/v3-lilith-launch-route.test.ts 8389373f3cb948328fdd0c4a6f79ca2e0cd74805e97e3629a63681f3fb9f5496
apps/oshun/web/src/components/lilith/V3MarketingLanding.tsx 8dbf2a90dcd197f12a611671a04628b5fb3c433a3737850735a99b9048a7c880
apps/oshun/web/src/components/lilith/V3MarketingLanding.test.tsx 8c292e0d79bb360e5c201099554099ff4773d934f3f7e41d5053557ebe5dc421
apps/oshun/web/e2e/v3-marketing-public-web.spec.ts 0f79d4d3d880b1ee689e1275a7d33414d21145f8ec6f637449b027a8f107c8b3
scripts/v3/verify-v3-region-rollout-compliance.mjs d53905e1244a667a3871c45246ccf7b4274e3961c85580ee173c26e33a982b9e
apps/oshun/bff/dist/server.js e18c5a580dc832e69428bfdb1287729af02abcfc47a25d766cd33fbd1cb5d37a

This closes the unsafe module-global waitlist-map classification by deleting the store and refusing collection. It does not claim a live regional waitlist product or close the parent V1-002 all-store inventory.

V6 authenticated Steward continuity state#

The implementation source commit is 8708bc2c3e4b3d5280d09eeaf3f64a70dd7cfc27, published to origin/main on 2026-07-26 UTC.

Store classification and persistence contract#

V6BffStateStore previously retained authenticated user state in one process-local map. Objective creation, squad-comms messages, Crossroads counsel, homestead settings, visit invites, account preferences, and tier-routing decision evidence disappeared on restart. The same state was absent from DSAR export and deletion, reads silently materialized fixture state into the map, and the histories were unbounded.

The store now declares a durable-subject-continuity-authority disposition backed by the existing PostgreSQL admin snapshot table. Production marks durability required, hydrates and fully schema-validates snapshot version 1 before accepting traffic, and refuses to publish a mutation until the candidate snapshot has committed. Mutations share one reusable promise tail, so concurrent requests inside the process cannot lose an update or reuse a revision. A failed write leaves both the prior in-memory record and its durable snapshot unchanged; V6 routes return 503 v6_state_persistence_unavailable.

Raw authenticated subject ids are not snapshot keys. The store uses a domain-separated SHA-256 digest, caps the combined retained/fenced subject population at 100,000, caps every history independently, and rejects records larger than 2 MiB. Startup rejects unknown schema versions, malformed digests, duplicate records or fences, record/fence resurrection conflicts, contract- invalid nested records, and over-capacity arrays. Fixture-only reads are pure: they return the static bootstrap projection without creating a retained or exportable user record.

The snapshot adapter gives this path durable process-restart recovery and ordered in-process mutation. Its disposition explicitly sets crossProcessMutationSerialization: false; this evidence does not claim multi-replica same-subject serialization or read refresh. That is a bounded remaining deployment seam, not hidden behind a stronger durability label.

Privacy lifecycle and route behavior#

The default continuity_state collector now emits an exact v6_steward_continuity_state partition only for subjects with retained state. The signed continuity deletion fan-out invokes the V6 eraser. Erasure removes only the exact digest, persists a one-way fence even for a zero-row subject, and preserves adjacent ids. A restarted store loads that fence, exports no deleted record, and rejects stale or recreated mutations with 409 v6_state_subject_deleted.

Every V6 state-changing route now awaits persistence, including the tier-router decision event that was formerly fire-and-forget. Successful responses are resolved from the schema-validated record that was actually committed. The V6 product checklist now states this persistence, recovery, failure, DSAR, and erasure boundary instead of the former ambiguous claim that the BFF merely “persists” selected arrays.

Verification#

text
pnpm --dir apps/oshun/bff exec vitest run -c vitest.config.ts \
  src/v6/state.spec.ts src/data-export/bundle-builder.test.ts
  2 files passed; 49/49 tests passed

pnpm --dir apps/oshun/bff exec vitest run \
  -c vitest.integration.config.ts \
  src/__tests__/v6-routes.integration.test.ts
  1 file passed; 6/6 tests passed

OSHUN_ADMIN_DATABASE_URL=<local-postgresql> \
  pnpm --dir apps/oshun/bff exec vitest run \
  -c vitest.integration.config.ts \
  src/v6/state-durability.integration.spec.ts
  1 file passed; 1/1 real-PostgreSQL restart/erasure test passed

pnpm exec eslint --no-warn-ignored <all eight changed TypeScript files>
pnpm exec prettier --write <all changed source, test, and documentation files>
git diff --check
  passed

node apps/oshun/bff/scripts/build.mjs
node --check apps/oshun/bff/dist/server.js
  dist/server.js: 34.8 MiB
  dist/server.js.map: 81.6 MiB

# exact disposable database created from an empty catalog
pnpm --dir libs/oshun/persistence exec prisma migrate deploy \
  --config prisma.config.ts
  all 32 migrations applied

# exact built artifact, fresh database, and local Redis
node apps/oshun/bff/scripts/verify-production-artifact.mjs
  Production artifact smoke check passed.

The BFF app-own type ratchet completed repeatedly with an 8 GiB compiler heap. Its final run reported only the same five current-main errors outside the affected files: the Isis CLI surface test, autonomous-content metrics, two autonomy-route test assignments, and the tenant-content graph fixture. The check is not represented as passing, and the commit hook's type stage was skipped only after the full diagnostic. Pre-commit formatting, ESLint, stub scanning, conventions, V2 asset locking, and V5 documentation validation passed.

Nine non-overlapping Yemaya commits reached origin/main before publication. The scoped implementation rebased cleanly and was then pushed. No user-facing layout or interaction contract changed, so frontend-skill, Playwright, mobile UI automation, screenshots, and Unreal verification were inapplicable.

Artifact identities#

Artifact SHA-256
apps/oshun/bff/src/v6/state.ts 5b7e20f026afe8ea0dae5f3ffd26a0c476e67f6419ea14d53eabe6546e9dd9e9
apps/oshun/bff/src/routes/v6.ts 2274aa5b98125385e3d41fde861fd67be8b02179fb094abd56fd5cd10ac05aca
apps/oshun/bff/src/v6/state.spec.ts 22a66ba9cf10f8166991fa944f784fc121aca4021a8490cd6cc3541a82129a81
apps/oshun/bff/src/v6/state-durability.integration.spec.ts 25e90f3bddf0770bfe33be99f8321ea22cde5f25a78047dc77b1d64532c6ac13
apps/oshun/bff/src/data-export/bundle-builder.ts 88b323f61260cc6d54ed2c88ead10893a1dbe8aa362ff2acde7d1869131d0ee6
apps/oshun/bff/src/server.ts b8571987f8bd778f06e9204baf960f46206d0c3423abe29b7984e0a06f99ba7f
apps/oshun/bff/dist/server.js c91100a455d1bb4c5c940beace322516a7b00bdcbc32ee521c9daf2a63821d93

This closes the V6 authenticated Steward module-global map within its declared single-writer snapshot boundary. It does not close cross-replica mutation coordination, live V6 provider/runtime operation, or the parent V1-002 all-store inventory.

Admin reminder-production no-store preview#

The implementation source commit is 3cba2649419a40e3c749692551651e6e2e3b5d6e, published to origin/main on 2026-07-26 UTC.

Store audit and disposition#

reminder-producer-store.ts retained ProducedBatch values, including recipient contact data and every generated reminder, in an unbounded module-global map. POST /v1/admin/reminders/produce returned 201 as though it had created a resource, duplicate ids returned 409 as though the process map were a restart-safe idempotency authority, and GET exposed that process-local history.

Repository-wide tracing found no production caller beyond the admin route, no live domain-state reader, no cron or worker, no scheduler/outbox handoff, no delivery effect, and no consumer of a produced batch. Persisting that map would therefore have promoted an operator-submitted preview into a false operational authority. The store was deleted and replaced by a pure request projection with this machine-readable disposition:

text
mode: request-local-non-authoritative-preview
persistence: none
retention: request-lifetime
source: operator-submitted-domain-slices
liveDomainProducer: false
deliveryScheduled: false
idempotencyAuthority: none
authoritativeState: false

The route still evaluates the real four pure reminder producers, but now returns 200, retained: false, deliveryScheduled: false, the disposition, and cache-control: no-store; repeated batch ids are independent previews and the catalog contains no batch history. Because no contact-bearing state is retained, this boundary creates no DSAR, erasure, retention-job, or recovery partition.

This change does not close historical gap G-MSG-1. A complete implementation still needs a live producer that queries authoritative session, streak, assignment, and content-drop state and durably schedules delivery through a recoverable, idempotent outbox or equivalent authority.

Boundary hardening#

The preview refuses unknown top-level and trigger fields, non-canonical timestamps, non-HTTPS or credential-bearing URLs, invalid channel/contact bindings, empty trigger sets, unsafe streak counts, individually oversized trigger arrays, and a combined payload over 1,000 trigger items. Identifiers, titles, URLs, timestamps, contact fields, and serialized recipients have explicit length or byte ceilings. Recipient objects are cloned before producer evaluation.

Verification#

text
pnpm --dir apps/oshun/bff exec vitest run \
  -c vitest.config.ts \
  src/__tests__/admin-reminders-produce-route.test.ts
  1 file passed; 7/7 tests passed

pnpm exec eslint --no-warn-ignored \
  apps/oshun/bff/src/reminders/reminder-production-preview.ts \
  apps/oshun/bff/src/routes/admin-reminders-produce.ts \
  apps/oshun/bff/src/__tests__/admin-reminders-produce-route.test.ts
pnpm exec prettier --write <the same three TypeScript files>
git diff --check
  passed

node apps/oshun/bff/scripts/build.mjs
node --check apps/oshun/bff/dist/server.js
  dist/server.js: 34.8 MiB
  dist/server.js.map: 81.6 MiB

# exact disposable database created from an empty catalog
pnpm --dir libs/oshun/persistence exec prisma migrate deploy \
  --config prisma.config.ts
  all 32 migrations applied

# exact built artifact, fresh database, and local Redis
node apps/oshun/bff/scripts/verify-production-artifact.mjs
  Production artifact smoke check passed.

The BFF app-own type ratchet completed with an 8 GiB compiler heap and reported only the same five current-main errors outside the affected files: the Isis CLI surface test, autonomous-content metrics, two autonomy-route test assignments, and the tenant-content graph fixture. It is not represented as passing. Pre-commit formatting, ESLint, stub scanning, conventions, V2 asset locking, and V5 documentation validation passed.

Two non-overlapping remote updates reached origin/main during publication. Both rebases were conflict-free. The focused 7/7 route suite and BFF build were re-run after the first integration; the second update did not touch BFF, messaging-channel, or persistence paths.

No user-facing UI, mobile flow, Unreal asset, or browser contract changed, so frontend-skill, Playwright, mobile UI automation, screenshots, and Unreal verification were inapplicable.

Artifact identities#

Artifact SHA-256
apps/oshun/bff/src/reminders/reminder-production-preview.ts 5825c7bcc7181385697d777c72746169693ce937616ce21b5fd6a1ca75abaa66
apps/oshun/bff/src/routes/admin-reminders-produce.ts 51adf4f67970ae0a5864637ea239d6b38d0971985b357daeb38201e4d9a0b2ba
apps/oshun/bff/src/__tests__/admin-reminders-produce-route.test.ts 060932b8648c3bbd2caa80628ec5f8c5847f151054289b74a1c16183a5d3947f
apps/oshun/bff/dist/server.js 62df533b373f7651fa8e61d7e5c27dceb1976923ac3902a929d320cf665b3f49

This closes the misleading module-global reminder-batch map within its explicit request-local no-store boundary. It does not close live reminder production, durable scheduling/delivery, or the parent V1-002 all-store inventory.

Shared authenticated route-response cache disposition#

The implementation source commit is d77d5b60418cd32a07d979779edc2242710703f6, published to origin/main on 2026-07-26 UTC.

Cache audit and bounded-loss contract#

createRouteResponseCache backs 25 process-local cache instances across 17 BFF route modules, including home, domain, activity, search, recommendation, notification, library, Nisaba, Veritas, Nyx, Arete, and admin projections. The cache keys already use SHA-256 over tenant, residency, authenticated subject, sorted scopes, route, request URL, entitlement headers, and route-specific parts, so raw subject ids were not map keys. The retained values can still contain authenticated response data.

The former implementation had a TTL but deleted an expired entry only when that same key was read. It never swept expired entries on unrelated traffic and had no entry ceiling. An authenticated client varying query, cursor, tenant, route, or other cache-key inputs could therefore retain response projections for the process lifetime despite their nominal TTL.

The shared factory now publishes this explicit disposition:

text
mode: bounded-ephemeral-recomputable
persistence: none
authoritativeState: false
lossEffect: cache-miss-and-recompute
defaultMaxEntriesPerCache: 1000
maximumTtlMs: 300000

Every cache prunes all expired entries before a write and when its size is inspected. Hits refresh access order, and writes evict the least-recently-used entry until the configured ceiling holds. Invalid TTLs fall back to one second, finite TTLs are clamped between one second and five minutes, and invalid capacities fall back to 1,000 entries. Existing production callers use TTLs of 15–60 seconds, beneath the absolute ceiling.

The cache has no durable sink by design. It owns no domain state, write receipt, idempotency decision, user history, or recovery checkpoint. Clearing an entire instance produces only a cache miss followed by recomputation through the existing authoritative route adapters. It therefore creates no DSAR, erasure, retention-job, or recovery partition beyond the enforced in-process TTL/LRU boundary.

Verification#

text
pnpm --dir apps/oshun/bff exec vitest run \
  -c vitest.config.ts \
  src/__tests__/response-controls.test.ts
  1 file passed; 7/7 tests passed

pnpm --dir apps/oshun/bff exec vitest run \
  -c vitest.config.ts \
  src/__tests__/domains-route.test.ts \
  src/__tests__/notifications-route.test.ts \
  src/__tests__/search-suggestions-route.test.ts \
  src/__tests__/nisaba-route.test.ts \
  src/__tests__/admin-route.test.ts
  5 files passed; 84/84 tests passed

pnpm exec eslint --no-warn-ignored \
  apps/oshun/bff/src/routes/response-controls.ts \
  apps/oshun/bff/src/__tests__/response-controls.test.ts
pnpm exec prettier --write <the same two TypeScript files>
git diff --check
  passed

node apps/oshun/bff/scripts/build.mjs
node --check apps/oshun/bff/dist/server.js
  dist/server.js: 34.8 MiB
  dist/server.js.map: 81.6 MiB

# exact disposable database created from an empty catalog
pnpm --dir libs/oshun/persistence exec prisma migrate deploy \
  --config prisma.config.ts
  all 32 migrations applied

# exact built artifact, fresh database, and local Redis
node apps/oshun/bff/scripts/verify-production-artifact.mjs
  Production artifact smoke check passed.

The direct proof covers LRU order, hard capacity, complete expired-entry pruning on an unrelated write, size-time pruning, invalid configuration, and total cache loss followed by recomputation. The representative route suites preserve cache-hit behavior, cursor pagination, tenant isolation, failure envelopes, and authenticated scope enforcement across five different cache consumers.

The BFF app-own type ratchet completed with an 8 GiB compiler heap and reported only the same five current-main errors outside the affected files: the Isis CLI surface test, autonomous-content metrics, two autonomy-route test assignments, and the tenant-content graph fixture. It is not represented as passing. Pre-commit formatting, ESLint, stub scanning, conventions, V2 asset locking, and V5 documentation validation passed.

No user-facing layout or interaction, mobile flow, Unreal asset, schema, external provider, or persistent record changed. Frontend-skill, Playwright, mobile UI automation, screenshots, Unreal verification, provider tests, and store migration tests were therefore inapplicable. Startup was still verified against a freshly migrated database because the shared BFF artifact changed.

Artifact identities#

Artifact SHA-256
apps/oshun/bff/src/routes/response-controls.ts ab99be0e2373eb5eabfcd93b5be441d285e28945e090b993099a8d2f2990573d
apps/oshun/bff/src/__tests__/response-controls.test.ts 8c6f42277aa2bce9c6cdfd0342fc94117f2a7c0cde07daee8f021ae14cff8c27
apps/oshun/bff/dist/server.js 4b8d9035facb624bca85f46db78bc54a5a2203f54fce091acddeddcfdded2a35

This closes the shared route-response maps within their explicit bounded, ephemeral, loss-safe boundary. It does not close the parent V1-002 all-store inventory or prove freshness of the authoritative data sources behind every route.

Mentor Presence aggregate analytics durability and access boundary#

The implementation source commit is a7e03be1803a7648b0e864e1dc4ae20118c6e12e, published to origin/main on 2026-07-26 UTC.

Store audit and durable aggregate contract#

MentorPresenceAnalyticsStore held opt-in/out, presence attachment, fallback, crisis-collapse, sit-start, and sit-completion counters in one module-global object with two maps. The fallback-reason map had a 32-key ceiling, but every counter reset on process replacement. A consented event still received recorded: true before any durable write because no write existed, and any authenticated customer could read the global summary. Arbitrary client reason strings up to 64 characters were retained and echoed as summary keys.

Production now requires and hydrates the isolated mentor-presence-analytics schema-v1 snapshot before traffic. Each event is applied to a detached candidate through one reusable promise tail; the complete bounded aggregate commits before publication. A pending save is invisible, a failed save leaves the prior summary and revision unchanged, and a later retry starts from that committed state. Missing or failed persistence returns 503 mentor_presence_analytics_persistence_unavailable from both intake and operator summary routes, and never reports the event as recorded.

Hydration accepts only the exact root, counter, rung, and reason schema. It rejects unknown versions or fields, missing or duplicate categories, unsafe or negative counts, unknown reason buckets, documents over 64 KiB, revision/event count mismatches, and fallback-reason totals that differ from fallback-rung totals. Serialization emits all four rung counters in canonical order and reason buckets in lexical order.

The aggregate intentionally retains no subject id, tenant id, event payload, timestamp, event log, session id, or raw fallback text. The finite canonical fallback-reason taxonomy includes the known product failure codes; every other non-empty, at-most-128-character reason is irreversibly counted as other. This makes the retained snapshot a global aggregate rather than a user-scoped DSAR or erasure partition. Revoking analytics consent stops future intake through the already-durable consent authority; an individual cannot be subtracted from a global counter because no subject linkage is retained.

Event payloads now have exact kind-specific fields. Intake is authenticated, consent-authorized, and protected by the standard abuse prehandler. Summary reads require admin:*, admin:studio, or admin:workspace:observability and return cache-control: no-store; an ordinary domain-authenticated customer receives 403.

Verification#

text
pnpm --dir apps/oshun/bff exec vitest run \
  -c vitest.config.ts \
  src/mentor-presence/analytics.spec.ts \
  src/__tests__/mentor-presence-route.test.ts
  2 files passed; 25/25 tests passed

OSHUN_ADMIN_DATABASE_URL=<local-postgresql> \
  pnpm --dir apps/oshun/bff exec vitest run \
  -c vitest.integration.config.ts \
  src/mentor-presence/analytics-durability.integration.spec.ts
  1 file passed; 1/1 real-PostgreSQL replacement-recovery test passed

pnpm exec eslint --no-warn-ignored <all six changed TypeScript files>
pnpm exec prettier --write <all six changed TypeScript files>
git diff --check
  passed

node apps/oshun/bff/scripts/build.mjs
node --check apps/oshun/bff/dist/server.js
  dist/server.js: 34.9 MiB
  dist/server.js.map: 81.6 MiB

# exact disposable database created from an empty catalog
pnpm --dir libs/oshun/persistence exec prisma migrate deploy \
  --config prisma.config.ts
  all 32 migrations applied

# exact final built artifact, fresh database, and local Redis
node apps/oshun/bff/scripts/verify-production-artifact.mjs
  Production artifact smoke check passed.

The adversarial unit proof covers pending-save invisibility, failed-save rollback and clean retry, 50 concurrent ordered mutations without lost counts, strict restart decoding, unknown/expanded/mismatched snapshot rejection, missing required persistence, and irreversible bucketing of client-supplied private text. Route coverage proves durable consent, strict event validation, operator-only no-store summaries, persistence-failure translation, and no publication on failure in addition to the existing governed render/media coverage. The real PostgreSQL test writes two acknowledged counters through the production snapshot adapter, constructs a replacement store and connection, and recovers exact aggregates without the submitted arbitrary reason text.

The BFF app-own type ratchet completed with an 8 GiB compiler heap and reported only the same five current-main errors outside the affected files: the Isis CLI surface test, autonomous-content metrics, two autonomy-route test assignments, and the tenant-content graph fixture. It is not represented as passing. Pre-commit formatting, ESLint, stub scanning, conventions, V2 asset locking, and V5 documentation validation passed.

One non-overlapping remote integration reached origin/main before publication. The source rebased without conflict; the remote delta did not touch BFF or shared dependency paths. No user-facing layout or interaction, mobile flow, Unreal asset, schema migration, external provider, or generated media algorithm changed, so frontend-skill, Playwright, mobile UI automation, screenshots, Unreal verification, and provider/model tests were inapplicable.

Artifact identities#

Artifact SHA-256
apps/oshun/bff/src/mentor-presence/analytics.ts b1a237f46443a4dc3f4e349836d70c720f87956499b891c13b4ad43af0cfc5b9
apps/oshun/bff/src/mentor-presence/analytics.spec.ts 9fb1fd1476ec2629685d946a2d302c21ed98c63ee03d048e044f66f347b42462
apps/oshun/bff/src/mentor-presence/analytics-durability.integration.spec.ts c0a6750edc3e990ee0ee4ddb09df1ee6e00080fcdd2da1f38c63559603bd471f
apps/oshun/bff/src/routes/mentor-presence.ts a15022dd7c72adb1ba12cad6d61a2bdb08cb2d3f461f2f0bfc5ec9bfc54ed0bd
apps/oshun/bff/src/__tests__/mentor-presence-route.test.ts 959ed0a303e6436822afea382b8f1d368bd3e47e014871783649a0f710248c83
apps/oshun/bff/src/server.ts cfe0d5b81abc7fb66bda610366ac0ee0c70d54e15067c8e9439ff4998b8f7cf9
apps/oshun/bff/dist/server.js 4e936aa65dc831e1c225cc3d432b28dec5f451350f3d41eba2d13938c726f81d

This closes the Mentor Presence aggregate process map within its declared single-process ordered snapshot boundary. It does not establish event idempotency, distributed cross-replica mutation serialization, server-observed outcomes, statistical validity, or the parent V1-002 all-store inventory.

CTIA SMS suppression durability and outbound enforcement — 2026-07-26#

The implementation source commit is 3be16ee88908562540297214e5411ba5380cff2d, published to origin/main on 2026-07-26 UTC.

Store and delivery-path audit#

SmsSuppressionStore was a module-global array. A signed Twilio STOP webhook updated that array and immediately returned confirmation TwiML, but process replacement erased the decision. START had the same restart-volatile behavior. The store's isSuppressed lookup was referenced only by tests: the production reminder scheduler proceeded to the Twilio delivery seam without consulting it. Thus the old code neither provided a durable acknowledgement boundary nor enforced its local opt-out state on the only repository production SMS sender.

Production now requires and hydrates the isolated sms-suppressions schema-v1 snapshot before traffic. A STOP or START constructs a detached whole-store candidate on one reusable promise tail, saves it, and only then publishes it. Pending state is invisible. A failed save preserves the prior projection and revision, and a later mutation retries from that committed state. Missing, failed, or capacity-exhausted persistence returns 503 sms_suppression_unavailable without confirmation TwiML; this permits the provider to retry instead of turning a volatile decision into a false acknowledgement.

The snapshot is capped at 250,000 records and 64 MiB. Hydration accepts exact root and record fields only and rejects unknown schema versions, invalid or duplicate recipient digests, unknown reasons or scope, invalid timestamps, invalid provider receipt ids, excessive records, and oversized documents. Serialization is canonical by recipient digest. A subscriber has at most one complete all-SMS-class decision: STOP replaces it, while authenticated START removes exactly that digest without disturbing an adjacent subscriber.

The durable representation never stores the raw E.164 number. It stores a domain-separated SHA-256 digest plus the finite compliance reason, effective time, provider message id, and all-SMS scope. The digest is a stable lookup key, not an anonymity or non-enumerability claim. The store reconstructs the recipient-bearing SmsSuppressionEntry only after a caller supplies the exact phone number for lookup.

The reminder scheduler propagates a synchronous lookup from the hydrated BFF authority through the environment-provider adapter to deliverDispatchedMessage. The SMS branch checks it after confirming a recipient exists and before configuration or any Twilio request. A match returns the typed suppressed / sms-stop-or-compliance result and makes zero provider calls. The independently governed in-app reminder is still allowed; if it delivers, that reminder is not reported as an external-channel failure or sent again after a later START.

Retention and boundary disposition#

STOP/START is a delivery-compliance authority, not an account-profile history. Removing its stable lookup on ordinary account erasure could re-enable an external send, so this change does not attach the singleton compliance snapshot to account DSAR deletion. The local record remains until a signed START changes the decision or a separately authorized carrier/manual compliance process replaces it. An owned retention schedule, carrier/provider-native state reconciliation, and operational manual-removal evidence remain inventory gaps. The snapshot itself exposes no raw phone or account/tenant mapping.

The candidate/save/publish queue serializes one process. The shared whole-snapshot adapter does not provide cross-replica compare-and-swap or a distributed lease, so this evidence does not claim safe concurrent mutation from multiple BFF replicas. It also cannot recall messages the provider delivered before STOP, prove carrier-side suppression, or cover senders outside the repository's reminder path.

Verification#

text
pnpm exec vitest run \
  libs/oshun/messaging-channels/src/delivery.test.ts \
  libs/oshun/messaging-channels/src/reminder-scheduler.test.ts
  2 files passed; 35/35 tests passed

pnpm --dir apps/oshun/bff exec vitest run \
  -c vitest.config.ts \
  src/channel-ops/sms-suppression-store.spec.ts \
  src/routes/sms-inbound.test.ts \
  src/reminders/reminders-route.test.ts
  3 files passed; 28/28 tests passed

OSHUN_ADMIN_DATABASE_URL=<local-postgresql> \
  pnpm --dir apps/oshun/bff exec vitest run \
  -c vitest.integration.config.ts \
  src/channel-ops/sms-suppression-store-durability.integration.spec.ts
  1 file passed; 1/1 real-PostgreSQL STOP/START replacement-recovery test passed

pnpm exec nx run @oshun/messaging-channels:typecheck --parallel=1
  passed

pnpm exec eslint --no-warn-ignored <all twelve changed TypeScript files>
pnpm exec prettier --write <all twelve changed TypeScript files>
git diff --check
  passed with zero ESLint errors; sms-inbound retained three existing
  nullish-coalescing preference warnings

node apps/oshun/bff/scripts/build.mjs
node --check apps/oshun/bff/dist/server.js
  dist/server.js: 36,562,911 bytes
  dist/server.js.map: 85,645,978 bytes

# exact disposable database created from an empty catalog
pnpm --dir libs/oshun/persistence exec prisma migrate deploy \
  --config prisma.config.ts
  all 32 migrations applied

# exact final built artifact, fresh database, and local Redis
node apps/oshun/bff/scripts/verify-production-artifact.mjs
  Production artifact smoke check passed.

The focused proof covers pending-save invisibility, rollback and retry after a failed save, exact START removal with adjacent-subscriber isolation, strict restart decoding, missing required persistence, and raw-phone exclusion. The signed-webhook suite proves no state change for missing configuration or bad signatures, durable STOP and START semantics, empty handling for non-keywords, strict payload rejection, and 503 without confirmation or publication when a STOP cannot commit. Delivery and scheduler tests prove that the lookup reaches the provider seam and that a suppressed number creates no Twilio request. The real PostgreSQL test commits STOP through the production adapter, reconstructs both connection and store, observes suppression, commits START, reconstructs again, and observes exact removal.

The BFF app-own type ratchet completed with an 8 GiB compiler heap and reported only the same five current-main errors outside the affected files: the Isis CLI surface test, autonomous-content metrics, two autonomy-route test assignments, and the tenant-content graph fixture. It is not represented as passing. Pre-commit formatting, ESLint, stub scanning, conventions, V2 asset locking, and V5 documentation validation passed.

One non-overlapping Yemaya integration reached origin/main before publication. The source rebased without conflict; the remote delta did not touch the BFF or messaging-channel paths. The exact rebased artifact was rebuilt and smoked again. No user-facing layout or interaction, mobile flow, Unreal asset, schema migration, external provider call, or generated media algorithm changed, so frontend-skill, Playwright, mobile UI automation, screenshots, Unreal verification, and live provider/model tests were inapplicable.

Artifact identities#

Artifact SHA-256
apps/oshun/bff/src/channel-ops/sms-suppression-store.ts 1d81c6a17a3598e7b648b7010be420a15c18d0860961516aa14fbfc7f9ebb2e5
apps/oshun/bff/src/channel-ops/sms-suppression-store.spec.ts 75bbf3f8d293f02e24ca8180ed0eba930156b202dd0fe8602470f5165a683773
apps/oshun/bff/src/channel-ops/sms-suppression-store-durability.integration.spec.ts 3007448a9a7493f551a4c77cec435a2d4671fe02d33612b989c7cc7e668c7ac0
apps/oshun/bff/src/reminders/reminders-route.ts 7052e97915f311c9094e4d06a982ee8ed70c6b002875ab3cb5152aeb2ad972ae
apps/oshun/bff/src/routes/sms-inbound.test.ts 23fb2ac13df3e147111cdf064ed8d40d23cddd9d231a3f33eb60fcae00c1475f
apps/oshun/bff/src/routes/sms-inbound.ts eec64963c24d8b7d24a28e8c59b45b46349e2816ef4f04f5991b7cd7384d37d2
apps/oshun/bff/src/server.ts 1c028f1c4ebb5894b0a76582002798b4556fa9326c0de93f1db2fc9d35fb95bd
libs/oshun/messaging-channels/src/delivery.test.ts a960d4567a7f194bba2413b1974cfb0a84036361a42d92a9605be0e2e7f6e7f1
libs/oshun/messaging-channels/src/delivery.ts 1c91b830c7675ac6e9cad78ddfeed402b2daac3f9d654a2669e68149ee96677d
libs/oshun/messaging-channels/src/provider-config-env.ts fde9cbb827dc1eb74e57115c7eff0db306a97b1fbd42e43ddcdad50066d9bbef
libs/oshun/messaging-channels/src/reminder-scheduler.test.ts 5f204e9c05b93ed3a5501574e1d28396389067f97c8e540d0f155c2cf5efb8e5
libs/oshun/messaging-channels/src/reminder-scheduler.ts 5834fb81afb28a01c8804241e5208f75bbb32ee2e3772677a45a914c23f57606
apps/oshun/bff/dist/server.js 1b820eb2b2e6cb97f924cc8168b510c6d9f40f830c36a76037f4481c356cd8ae

This closes the local restart-volatile SMS suppression map and its missing reminder-delivery enforcement within the declared single-process boundary. It does not close G-MSG-1's live authoritative producer/outbox requirement or the parent V1-002 all-store inventory.

Customer Trust & Safety report authority — 2026-07-26#

The implementation source commit is 934d697bc9d663a91648d2e3a0ac21baf890f492, published to origin/main on 2026-07-26 UTC.

Store, review, and lifecycle audit#

Live customer user reports were held in a module-global AdminUserReportRecord[] beside the large fixture-backed admin workspace. A valid submission incremented a process-local serial, prepended a record, and returned 202 without any persistence. A moderator mutated that same object and returned 200; restart erased both the report and decision. At 201 reports, the old code silently truncated the oldest record. The terminal decision reason was not part of the report authority, so only the notification/audit projections carried it. Reporter rationale, target details, and reviewer identity were absent from the customer export, deletion fanout, and compliance-retention inventory.

Production now requires and hydrates the isolated customer-user-reports schema-v1 snapshot before traffic. Intake, terminal decision, subject redaction, and retention purge run through one reusable promise tail. Each mutation applies to a detached candidate, validates and saves the complete snapshot, and publishes only after the save acknowledges. Pending state is invisible. A failed save leaves records, serial, revision, redaction state, notification store, and decision audit unchanged; a later request starts from the committed state. Missing, failed, or capacity-exhausted persistence returns 503 user_report_persistence_unavailable.

The snapshot has a 10,000-record and 32 MiB hard ceiling. Capacity exhaustion fails closed instead of silently deleting an older safety case. Hydration accepts exact root and record fields only and rejects unknown schema versions or fields, malformed ids, categories, targets, states, outcomes, priorities, timestamps, decision shapes, duplicate report ids or redaction entries, noncanonical retention order, stale serials, unowned pseudonyms, and fenced subject resurrection. Reports serialize newest first; retention entries serialize by subject digest.

The durable record includes the terminal decision reason and timestamp. Repeating the exact terminal state is primary-state idempotent; a different outcome, reason, reviewer, or related-content id returns 409 user_report_already_decided rather than overwriting the first terminal decision. Reporter notification and the existing admin-audit adapter run only after that primary commit. If the primary decision save fails, neither side effect is invoked. A later notification failure remains explicitly represented by the route's existing notification status and does not roll back the already committed safety decision.

Signed-in reporters can read only their own cases. The real data-export bundle now includes those records under support_case / customer_trust_safety_reports, including the stored terminal reason. A user named as the target cannot export the reporter's confidential rationale merely because the report concerns them. Create, own-receipt, and moderator-decision responses all carry cache-control: no-store; authentication, moderator scopes, strict body validation, and abuse protection remain in force.

Deletion and retention disposition#

Signed account deletion invokes exact-subject redaction for all roles a subject can occupy: reporter, user target, and assigned reviewer. The store replaces direct identities with domain-separated SHA-256 pseudonyms, removes display names and authored private text, and scrubs exact subject-id occurrences from every remaining text or identifier field. The digest is a stable deletion fence, not an anonymity or non-enumerability claim. It prevents a deleted reporter or reviewer from recreating direct state and immediately minimizes any later report that names a fenced target.

The reporter owns the DSAR view before deletion; after redaction that direct view is empty while an adjacent reporter remains intact. Redacted cases enter the existing compliance-retention executor as support_case records with a five-year window. Active legal holds or applicable retention exceptions block purge. When due and unblocked, reporter-authored cases are removed; surviving cases replace target/reviewer pseudonyms with generic non-linkable markers. Later reports about an already purged target use the same generic marker rather than recreating the expired pseudonym. The permanent digest fence remains to reject resurrection, matching the repository's other compliance-redaction authorities.

Verification#

text
pnpm --dir apps/oshun/bff exec vitest run \
  -c vitest.config.ts \
  src/admin/customer-user-report-store.spec.ts \
  src/__tests__/user-reports-route.test.ts
  2 files passed; 22/22 tests passed

pnpm --dir apps/oshun/bff exec vitest run \
  -c vitest.config.ts \
  src/data-export/bundle-builder.test.ts
  1 file passed; 42/42 tests passed

OSHUN_ADMIN_DATABASE_URL=<local-postgresql> \
  pnpm --dir apps/oshun/bff exec vitest run \
  -c vitest.integration.config.ts \
  src/admin/customer-user-report-store-durability.integration.spec.ts
  1 file passed; 1/1 real-PostgreSQL replacement/redaction test passed

pnpm exec eslint --no-warn-ignored <new authority, route, export, server, and test paths>
pnpm exec prettier --write <all nine changed TypeScript files>
git diff --check
  passed

node apps/oshun/bff/scripts/build.mjs
node --check apps/oshun/bff/dist/server.js
  dist/server.js: 36,597,024 bytes
  dist/server.js.map: 85,707,416 bytes

# exact disposable database created from an empty catalog
pnpm --dir libs/oshun/persistence exec prisma migrate deploy \
  --config prisma.config.ts
  all 32 migrations applied

# exact final rebased artifact, fresh database, and local Redis
node apps/oshun/bff/scripts/verify-production-artifact.mjs
  Production artifact smoke check passed.

The authority suite covers commit-before-publication, failed-save rollback and retry, 50 concurrent ordered intakes without duplicate ids or lost reports, terminal-reason restart recovery, conflicting decisions, strict malformed and resurrection snapshot rejection, reporter/target/reviewer minimization, adjacent-subject preservation, post-redaction and post-purge admission, reporter-only export, five-year timing, legal-hold blocking, purge, and required persistence. Route coverage proves authentication and moderation scope, canonical validation, no-store, shared admin visibility, exact reporter read-back, notification delivery, controlled persistence failures, zero secondary side effects on primary failure, and terminal-conflict behavior. The full export-bundle suite proves the new partition alongside every existing local support-case partition and verifies an empty direct view after redaction. The real PostgreSQL test commits two reports and a terminal reason through the production adapter, reconstructs connection and store, verifies exact reporter export, commits subject redaction, reconstructs again, and verifies raw-subject absence with adjacent preservation.

The BFF app-own type ratchet completed with an 8 GiB compiler heap and reported only the same five current-main errors outside the affected files: the Isis CLI surface test, autonomous-content metrics, two autonomy-route test assignments, and the tenant-content graph fixture. It is not represented as passing. Pre-commit formatting, ESLint, stub scanning, conventions, V2 asset locking, and V5 documentation validation passed.

Several non-overlapping Yemaya and audio-workbench commits reached origin/main before publication. The source rebased without conflict; no remote file overlapped these nine paths. The remote ESLint ignore and package-script inventory changes were reviewed, affected lint was rerun under the rebased configuration, and the exact rebased artifact was rebuilt and smoked again. No user-facing layout or interaction, mobile flow, Unreal asset, schema migration, external provider call, or generated media algorithm changed, so frontend-skill, Playwright, mobile UI automation, screenshots, Unreal verification, and live provider/model tests were inapplicable.

Artifact identities#

Artifact SHA-256
apps/oshun/bff/src/admin/customer-user-report-store.ts f41acf91bb8c3eb1585f183e2329a1ffbfa20997aa2d48349a6c27e42dfe50a6
apps/oshun/bff/src/admin/customer-user-report-store.spec.ts f500de631d87dc46dd0374575677a5a45934ce7858b3650fe6642ca7e69cfe87
apps/oshun/bff/src/admin/customer-user-report-store-durability.integration.spec.ts 19f1612cfa1f80be89cad42c06aaa3b23cca01504f7e95e2b845d6d71bbac6d1
apps/oshun/bff/src/admin/state.ts f5bb3dd60c1907bc0a97139025f477088a50987091a2d98c01afd196fea001c0
apps/oshun/bff/src/routes/user-reports.ts edc63a6b593a21895dc65010198f2744ac40c89407c4ad992d4e5c6925fcb59d
apps/oshun/bff/src/__tests__/user-reports-route.test.ts c37a16c065bf54f10eb5ec527b021b8b1c2978a13aff4ae16f6700d0234d8180
apps/oshun/bff/src/data-export/bundle-builder.ts a25d0b2603d4c0fd70cb8131bbc3db95ba9bf857893c7ee614cafd404f18e8c0
apps/oshun/bff/src/data-export/bundle-builder.test.ts 6b59dd6e23d81288e0b5aa1246d08d459e2ff33ffec6ddd5d16857e2249c3120
apps/oshun/bff/src/server.ts 68d1488f80baf7c2cb48bf0627f2517f40b1ed5b8ecbff7b9b6560f3af4dd1ba
apps/oshun/bff/dist/server.js 49a88c7fe5f180486f2264be9eee11e3d7747c8bf6c9a55a1b63039ae9e048ed

This closes the shared customer Trust & Safety report process array within its declared single-process durable-authority and privacy-lifecycle boundary. It does not establish cross-replica mutation serialization, atomicity across the primary report, message center, and audit stores, provider-side enforcement, or the parent V1-002 all-store inventory.

Orphan Isis seed-data notice retirement — 2026-07-26#

Source and published implementation: 42b225eb86ca3a872a0f094155b4fa4cb4176de0.

Reachability and disposition#

apps/oshun/bff/src/isis/seed-data-notice.ts held a module-global Set<string> named consolesWithRealRecords. Its comments promised that an operator-created record would mark the corresponding console as real and remove a seedDataNotice from subsequent GET responses. Exact symbol, import, route, and response-field searches found no production consumer:

  • markConsoleHasRealRecords, consoleSeedNotice, and resetSeedDataNoticesForTests were imported only by the colocated seed-data-notice.test.ts;
  • no production source imported seed-data-notice.ts;
  • no production Isis route or response used the seedDataNotice field from this module; and
  • the server's deployable entry therefore had no path to read or mutate the set.

The helper was not an operational authority, cache, idempotency record, or customer-data partition. Its state was unreachable self-test scaffolding for a contract that production could not fulfill. Adding persistence would have converted dead state into a new false authority, so the correct all-store disposition was deletion of both the 40-line helper and its 25-line self-referential test.

This retirement does not remove the independently implemented seed disclosure in AdminIntegrationsRegistryStore. That store derives seedDataNotice from its actual durable registry contents and drops the notice only after a real record commits. Its existing focused suite verifies seeded disclosure, durable auto-drop, failure rollback, and restart behavior.

Verification#

text
# exact production-reference scan after deletion
rg -n \
  "seed-data-notice|consoleSeedNotice|markConsoleHasRealRecords|\
resetSeedDataNoticesForTests|consolesWithRealRecords" \
  apps/oshun/bff/src --glob '*.ts'
  no matches

# independent live seed-disclosure authority
pnpm --dir apps/oshun/bff exec vitest run \
  -c vitest.config.ts \
  src/admin/admin-integrations-registry-store.test.ts
  1 file passed; 19/19 tests passed

NODE_OPTIONS='--max-old-space-size=8192' \
  node tools/typecheck/ratchet.mjs \
    --app apps/oshun/bff \
    --tsconfig tsconfig.typecheck.json
  only the same five current-main errors outside the deleted files

node apps/oshun/bff/scripts/build.mjs
node --check apps/oshun/bff/dist/server.js
  dist/server.js: 36,597,024 bytes
  dist/server.js.map: 85,707,416 bytes
  SHA-256:
    49a88c7fe5f180486f2264be9eee11e3d7747c8bf6c9a55a1b63039ae9e048ed

git diff --check
  passed

The rebuilt artifact is byte-identical to the exact Trust & Safety artifact that had already passed syntax validation and production startup against Redis plus a fresh database with all 32 migrations. That identity proves the deleted module and test were absent from the bundled server, rather than merely unexercised during a smoke request.

Before publication, origin/main advanced with four non-overlapping Yemaya study-workspace files. The deletion rebased without conflict, the protected user lockfile was restored unchanged, the integrations-registry suite passed again, and the exact artifact identity was reconfirmed before push. No user-facing UI, API behavior, customer record, persistence schema, provider call, model pipeline, mobile flow, or Unreal content changed, so frontend-skill, Playwright, mobile, migration, live-provider/model, and Unreal automation were inapplicable.

This closes one false-positive module-global candidate by negative reachability. It does not assert that the legacy seeded Isis consoles are live provider-backed workflows, and it does not close the parent V1-002 all-store inventory.

Production mock-domain adapter exclusion — 2026-07-26#

Implementation commits: 1625bc1d8387edfce49d447d4f5be0704cd3b227 and 79aa5ce43e31bc3386466fa514b444c6f26e6662, both published to origin/main.

Reachability and failure mode#

createApp uses createDefaultDomainAdapters() when the caller does not inject an adapter set. That is the production server's path. The resolver accepted USE_MOCK_ADAPTERS=true for every domain and OSHUN_VERITAS_ADAPTER=mock|outage for Veritas without checking the runtime environment. A deployment misconfiguration could therefore return fixture journalism, claims, courses, sessions, health, and other domain payloads as ordinary authenticated responses.

The mock Veritas adapter also held followed topics in one module-global nested map keyed by raw user id. Every mock adapter factory shared that state. It had no subject or topic ceiling, survived across multiple app instances in the same process, and was neither durable nor part of deletion/export. This was acceptable only as explicitly ephemeral development scaffolding, but the unguarded production switches made that disposition false.

Closed boundary#

The default resolver now invokes a pure production-safety assertion before selecting any adapter. Values are trimmed and case-normalized. If either NODE_ENV=production or the repository's own OSHUN_ENV=production signal is present, full mock mode plus the Veritas mock and outage modes fail app construction with unsafe_production_domain_adapter_configuration:<unsafe switches>. Multiple unsafe switches are reported together. Real/default HTTP and in-process adapters remain allowed.

The production server.ts does not inject domain adapters, so it necessarily passes through this guard. createApp({ domainAdapters }) deliberately remains available as an explicit programmatic test/composition seam; the closure does not claim that arbitrary code importing the app factory is prevented from injecting its own adapter implementation.

For local development and automated journeys, the Veritas follow map now lives inside each createMockDomainServiceAdapters() call. Two app factories cannot observe each other's mutations. The disposable state retains at most 1,000 subjects and 100 topics per subject, evicting the oldest partition/item when the mock ceiling is reached. It remains intentionally restart-lossy: mock follows are not customer authority, are unavailable through the deploy-bound production configuration, and therefore do not create a new DSAR, deletion, or retention partition.

Verification#

text
# normalized NODE_ENV and OSHUN_ENV matrices, combined unsafe-mode reporting,
# real-production modes, instance isolation, and both hard ceilings
pnpm --dir apps/oshun/bff exec vitest run \
  -c vitest.config.ts \
  src/adapters/domain-adapter-runtime-safety.spec.ts \
  src/adapters/mock-domain-service-adapters.spec.ts \
  src/__tests__/domain-adapter-production-safety.spec.ts
  3 files passed; 18/18 tests passed

# existing authenticated briefing, outage, mock override, follow/unfollow,
# persistence-failure, scope, and canonical adapter routes
pnpm --dir apps/oshun/bff exec vitest run \
  -c vitest.config.ts \
  src/__tests__/veritas-route.test.ts
  1 file passed; 16/16 tests passed

pnpm exec eslint --no-warn-ignored <six changed production/test paths>
pnpm exec prettier --write <six changed production/test paths>
git diff --check
  passed

NODE_OPTIONS='--max-old-space-size=8192' \
  node tools/typecheck/ratchet.mjs \
    --app apps/oshun/bff \
    --tsconfig tsconfig.typecheck.json
  only the same five current-main errors outside the affected files

node apps/oshun/bff/scripts/build.mjs
node --check apps/oshun/bff/dist/server.js
  dist/server.js: 36,600,390 bytes
  dist/server.js.map: 85,715,535 bytes

# exact disposable database created from an empty catalog
pnpm --dir libs/oshun/persistence exec prisma migrate deploy \
  --config prisma.config.ts
  all 32 migrations applied

# exact final artifact, fresh database, and local Redis
node apps/oshun/bff/scripts/verify-production-artifact.mjs
  Production artifact smoke check passed.

The first implementation publication rebased over non-overlapping Yemaya study-workspace work. The follow-up OSHUN_ENV guard rebased over a second remote tranche that changed repository ESLint and package configuration but no affected BFF source. Scoped lint, all 18 direct safety/isolation tests, the build, and the exact artifact hash were rerun under that final configuration. The final artifact SHA-256 is 9cbed2016431661e4a4f277fbc5f2084e6b5298b4309250123c6ae6bd423b0ce, identical to the artifact that passed the fresh-database startup smoke.

Artifact identities#

Artifact SHA-256
apps/oshun/bff/src/adapters/domain-adapter-runtime-safety.ts 500259dbbfb64002979454ff4dffa4925949f5d1d22a4d2256f2cbec0c32e5d4
apps/oshun/bff/src/adapters/domain-adapter-runtime-safety.spec.ts 4b94d400fb2562b475be2b476aa37a14c3a57f7ea6c1df248468aaff479a70d6
apps/oshun/bff/src/adapters/mock-domain-service-adapters.ts 0a0255a5ee9704ee7ee38c82a4192183141f13979dc15b2b915da8ffaf9b027c
apps/oshun/bff/src/adapters/mock-domain-service-adapters.spec.ts e2152a5372f4ff4e023f1975b94ac87dddb3024e6f77be8d81ac969f97beab64
apps/oshun/bff/src/__tests__/domain-adapter-production-safety.spec.ts 9d0f3732cd069e30b8e42d921f2460cec976e6f7a19efab6da547a67a7b12fdc
apps/oshun/bff/src/app.ts 54075af278159ffe082a869e46a637856b734b97d5786224b1710e7c0f4f5c60
apps/oshun/bff/dist/server.js 9cbed2016431661e4a4f277fbc5f2084e6b5298b4309250123c6ae6bd423b0ce

No UI, mobile flow, API schema, database schema, provider call, model execution, customer export, deletion fanout, or Unreal asset changed, so frontend-skill, Playwright, mobile, migration, live-provider/model, and Unreal automation were inapplicable. This closes the production reachability and mutable mock-map classification only. It does not prove the live downstream domain adapters, their content quality, or the parent V1-002 all-store inventory.

Orphan analytics warehouse buffer retirement — 2026-07-26#

Source and published implementation: de34f0c5d26a854e9687a2462604b75e3df65089.

Producer, source, and sink audit#

WarehouseEventStore owned an unbounded module-global WarehouseEventInput[]. Its comment described the array as a buffer of emitted customer analytics awaiting an admin warehouse export. Exact production symbol and mutation tracing found:

  • no production caller of record or seed;
  • only GET /v1/admin/analytics/warehouse-export read the singleton;
  • every populated-store use was an injected unit-test instance;
  • the production app registered the route without a warehouse sink; and
  • no web, mobile, admin client, scheduler, worker, or other service referenced the endpoint or store.

The default production route therefore read an empty process array and then returned 503 warehouse_sink_not_configured. It could not deliver a row, and a composition that injected only a sink would have treated process-local state as the apparent source of truth.

The existing durable AnalyticsEventsStore is not a truthful drop-in source. Its privacy contract retains server-authoritative owner identity, event/domain, platform, payload, and receive/occur times. WarehouseEventInput instead requires the member's emit-time analytics-consent decision, a pre-hashed member identifier, tenant, and a taxonomy surface. Fabricating those fields, deriving them from current consent, or re-hashing the retained owner at export time would change historical consent/identity semantics and could misroute or disclose analytics. No adapter was invented.

Disposition#

The 47-line warehouse-event-store.ts module, including its singleton, array, mutators, reset, and test seeding seam, is deleted. No production or test reference remains.

The authenticated admin endpoint remains as an integration boundary. Its options now accept the minimal read-only WarehouseEventSource interface plus the existing WarehouseSink. After validating authentication, admin scope, and the requested time window, a missing source returns 503 warehouse_event_source_not_configured before building a batch or touching the sink. An injected authoritative source still flows through the existing taxonomy mapping, emit-time consent gate, canonical-row SHA-256 manifest, sink receipt, and 502 sink-error behavior.

This is a fail-loud integration seam, not a new store. Production currently injects neither source nor sink, so warehouse delivery remains unavailable and is not represented as complete. The separately durable analytics intake, subject deletion, retention, and export lifecycle are unchanged.

Verification#

text
# missing-source fail loud, missing sink, auth/scope/window validation,
# injected consent/taxonomy/digest delivery, and sink failure
pnpm --dir apps/oshun/bff exec vitest run \
  -c vitest.config.ts \
  src/routes/analytics-warehouse.test.ts \
  src/__tests__/v1-feature-pack-boot.test.ts
  2 files passed; 7/7 tests passed

# authoritative durable intake acknowledgement and privacy regression
pnpm --dir apps/oshun/bff exec vitest run \
  -c vitest.config.ts \
  src/analytics/events-ingest.test.ts
  1 file passed; 6/6 tests passed

# taxonomy mapping, consent accounting, canonical digest, and sink contract
pnpm --dir libs/oshun/analytics exec vitest run \
  src/warehouse/warehouse.test.ts
  1 file passed; 21/21 tests passed

rg -n \
  "warehouse-event-store|warehouseEventStore|WarehouseEventStore" \
  apps/oshun/bff/src --glob '*.ts'
  no matches

pnpm exec eslint --no-warn-ignored \
  apps/oshun/bff/src/routes/analytics-warehouse.ts \
  apps/oshun/bff/src/routes/analytics-warehouse.test.ts
pnpm exec prettier --write <the two retained changed TypeScript files>
git diff --check
  passed

NODE_OPTIONS='--max-old-space-size=8192' \
  node tools/typecheck/ratchet.mjs \
    --app apps/oshun/bff \
    --tsconfig tsconfig.typecheck.json
  only the same five current-main errors outside the affected files

node apps/oshun/bff/scripts/build.mjs
node --check apps/oshun/bff/dist/server.js
  dist/server.js: 36,600,983 bytes
  dist/server.js.map: 85,716,151 bytes

# exact disposable database created from an empty catalog
pnpm --dir libs/oshun/persistence exec prisma migrate deploy \
  --config prisma.config.ts
  all 32 migrations applied

# exact final rebased artifact, fresh database, and local Redis
node apps/oshun/bff/scripts/verify-production-artifact.mjs
  Production artifact smoke check passed.

One non-overlapping contracts/Yemaya comparison-set tranche reached origin/main before publication. The source rebased without conflict. Because the contract delta changed the bundled artifact even though it did not overlap the warehouse files, the route/boot suites and direct build were rerun, then the exact new artifact was smoked against another fresh database. The final artifact SHA-256 is 1455bde8ce2342b976071e12873a33c1c0789cc44cbddf770ec5f12fe1ad9b43.

Artifact identities#

Artifact Identity
deleted apps/oshun/bff/src/channel-ops/warehouse-event-store.ts former Git blob 489e08c5eae7dfe46dc1ed6c5afafe6b9d9c7943
apps/oshun/bff/src/routes/analytics-warehouse.ts SHA-256 398de40903781bb5c29d3c79ee1b80a6b5d783f9f7c4a6763236e02099a02677
apps/oshun/bff/src/routes/analytics-warehouse.test.ts SHA-256 88d6c50f0fcccfef8361c9e490ffdc53d0d30e333fa193bd17c5e326014f234b
apps/oshun/bff/dist/server.js SHA-256 1455bde8ce2342b976071e12873a33c1c0789cc44cbddf770ec5f12fe1ad9b43

No user-facing UI, mobile flow, API schema, database schema, provider call, model execution, customer deletion/export partition, or Unreal asset changed, so frontend-skill, Playwright, mobile, migration, live-provider/model, and Unreal automation were inapplicable. This closes the false process-buffer authority only. A real authoritative source, deploy-bound sink, delivery recovery/idempotency, privacy review of the source contract, and the parent V1-002 all-store inventory remain open.

False admin residency-audit singleton retirement — 2026-07-26#

Source implementation: e2d1cb280718b475ed05d3763ed496fa66eb91e2. Awaited durable-source follow-up and published tip: e9b47d94f5a6cf6115bb4df1d9d56f9864e140ac.

Reachability and authority audit#

adminResidencyAuditStore was a module-global bounded ring of canonical platform-audit-shaped events. Its route and module comments claimed that the V1-PRIV-018 residency enforcer fed it and that the admin route therefore read a canonical residency audit store.

Restricted production symbol, import, and constructor tracing found the opposite:

  • the singleton was imported only by admin-residency-audit.ts;
  • no production BFF route instantiated createResidencyGuard or ResidencyEnforcementService;
  • no production publisher, worker, server wiring, or other module called the store's publish;
  • the BFF composition root registered the admin route with no source; and
  • every populated-store path was an explicitly composed route or region-aware test.

The deployable endpoint consequently returned 200 with an empty audit log after every process start. That empty response was not evidence that no residency transfers occurred; it was evidence that an unwired process-local projection had no events.

The durable admin operator-audit store is not a safe substitute: it uses a different admin-event contract rather than CanonicalPlatformAuditEvent. @oshun/audit-platform supplies the correct canonical contract and ingest service, but its repository implementation is currently in-memory. No database adapter, conversion, or residency event was fabricated to claim a durable source.

Disposition#

The exported global singleton is removed. AdminResidencyAuditStore remains only as an explicit bounded process-local adapter for tests and deliberately composed development runtimes; its documentation now forbids treating it as the deployable default.

The route owns a minimal read-only AdminResidencyAuditSource. Its list may return either canonical events directly or a promise, so a future database- backed authority can be awaited without another API redesign. createApp threads an explicitly supplied source to the route. Production currently supplies none.

The handler preserves security and input-validation ordering:

  1. authentication;
  2. privacy-admin scope;
  3. filter validation;
  4. source availability; and
  5. awaited source read, projection, filtering, counts, and truncation.

An authorized, valid request without a source now returns 503 residency_audit_source_not_configured. Invalid filters still return 400 before source disclosure. Explicit synchronous and asynchronous sources retain the existing V1-PRIV-019 projection behavior.

This is a fail-loud source seam, not a durability claim. A durable canonical audit repository, publisher wiring from actual residency-enforced production paths, retention/privacy controls for that repository, and live operational verification remain open.

Verification#

text
# auth/scope, fail-loud source ordering, synchronous and awaited source reads,
# enforcement-to-audit projection, filters, truncation, and zone/class counts
pnpm --dir apps/oshun/bff exec vitest run \
  src/routes/admin-residency-audit.spec.ts \
  src/__tests__/region-aware-regression.spec.ts
  2 files passed; 46/46 tests passed

pnpm exec eslint \
  apps/oshun/bff/src/admin/residency-audit-state.ts \
  apps/oshun/bff/src/routes/admin-residency-audit.ts \
  apps/oshun/bff/src/routes/admin-residency-audit.spec.ts \
  apps/oshun/bff/src/__tests__/region-aware-regression.spec.ts \
  apps/oshun/bff/src/app.ts
git diff --check
  passed

NODE_OPTIONS='--max-old-space-size=8192' \
  node tools/typecheck/ratchet.mjs \
    --app apps/oshun/bff \
    --tsconfig tsconfig.typecheck.json
  only the same five current-main errors outside the affected files:
  admin-isis-cli-surface-route.test.ts:58
  autonomous-content-metrics-store.ts:89
  agentic/autonomy-route.test.ts:200
  agentic/autonomy-route.test.ts:491
  tenant-content-graph-store.spec.ts:88

# the affected pre-commit sweep additionally reached an unrelated package
nx affected --target=typecheck <the five initial implementation files>
  @oshun/prompt-injection-evals failed at
  libs/shared/tracing/src/genai.ts:365 on a V7 contract-union mismatch
  @oshun/bff reported the same five errors above
  commit used the hook's documented SKIP_TYPECHECK=1 path after focused checks

node apps/oshun/bff/scripts/build.mjs
node --check apps/oshun/bff/dist/server.js
  dist/server.js: 36,602,565 bytes
  dist/server.js.map: 85,720,052 bytes

# exact disposable database created from an empty catalog
pnpm --dir libs/oshun/persistence exec prisma migrate deploy \
  --config prisma.config.ts
  all 32 migrations applied

# exact final artifact, fresh database, and local Redis
node apps/oshun/bff/scripts/verify-production-artifact.mjs
  Production artifact smoke check passed.

Two non-overlapping Yemaya commits reached origin/main before the initial implementation publication. The source rebased without conflict. Focused tests, scoped lint, direct build, syntax validation, and a fresh-database smoke were rerun after the rebase. The awaited-source follow-up then reran 46/46 focused tests, lint, build, and another fresh-database smoke. The final artifact SHA-256 is 926e7a7c7c03b644a59f25ae3adbe86a2485d6a77d22e2fab329ee1115673ea6.

Artifact identities#

Artifact SHA-256
apps/oshun/bff/src/admin/residency-audit-state.ts a61a8c8b8297132f0d8df7bc1abd91ca728d13a05a7491353ec02a3c96928df3
apps/oshun/bff/src/routes/admin-residency-audit.ts 43b8550fd513cd52c7414ba15ec77d1ef44c6ca760406b2b882e5d91c2bd19c3
apps/oshun/bff/src/routes/admin-residency-audit.spec.ts d68157a17fef102dc198fdf574f59ca4f7c842a6da4b63e3cca11ea6acb3ad58
apps/oshun/bff/src/__tests__/region-aware-regression.spec.ts e229b514bac45a18ceb48ef3f1425f8a5648dd1a5b924b39129d8b07dc66f1ff
apps/oshun/bff/src/app.ts 90d00e01772839c0197488058084ff700b0240142edcf18b76d795aa1562feff
apps/oshun/bff/dist/server.js 926e7a7c7c03b644a59f25ae3adbe86a2485d6a77d22e2fab329ee1115673ea6

No user-facing UI, mobile flow, OpenAPI schema, database schema, provider/model call, customer data partition, deletion/export fanout, or Unreal asset changed, so frontend-skill, Playwright, mobile, schema/migration, live-provider/model, privacy-fanout, and Unreal automation were inapplicable. This closes the false singleton authority only; it does not close V1-PRIV-018 production enforcement or V1-002's parent all-store inventory.

Durable admin collaboration authority — 2026-07-26#

Source implementation and published origin/main commit: 9d7754ca7996834161959bcfd49abcd54c1f931f.

Reachability and authority audit#

The Studio quest, story-graph, timeline, and world-configuration registries were initially included in this audit because they expose authoring-shaped state. They already use the deploy-required Studio authoring-record authority: startup hydration, acknowledged persistence, restart recovery, subject export, signed deletion, and resurrection fences are covered by their existing lifecycle suites. No duplicate Studio store was added.

Two connected admin collaboration stores were different:

  • adminCrossLinkStore retained each operator's explicit links in a module-global nested map;
  • adminEntityCommentsStore retained shared comment threads in another module-global map;
  • the mutation routes returned success immediately from those maps;
  • buildDurableAdminStores did not include either store;
  • deployable startup injected neither store into their routes; and
  • investigation bundles read the same volatile singletons while describing the resulting cross-links and comments as independently persisted.

Restart therefore erased acknowledged operator work. Separate replicas could show different threads and investigation bundles. The empty state after a restart was indistinguishable from an authoritative empty result.

Durable disposition#

Both base stores now expose deterministic schema-v1 snapshot export/import. Hydration rejects malformed contracts, duplicate identities, inconsistent thread order/parent depth, impossible revisions, stale subject data covered by a deletion fence, and data above hard global or per-entity bounds. Tombstones count against comment capacity, preventing create/delete churn from growing a thread without limit.

createDurableBackedAdminCrossLinkStore and createDurableBackedAdminEntityCommentsStore serialize mutations using an ordered candidate/save/publish barrier:

  1. clone the last acknowledged state;
  2. apply and validate the mutation to the candidate;
  3. persist the full candidate to PostgreSQL; and
  4. publish it to readers only after the save succeeds.

A rejected save returns AdminCollaborationPersistenceError and leaves the last durable view unchanged. The two stable snapshot keys are admin-cross-links and admin-entity-comments.

buildDurableAdminStores constructs and hydrates both stores before accepting traffic. The cross-link routes, comment routes, and investigation-bundle store receive those exact instances. In deployable mode, a missing injected collaboration store yields:

  • 503 admin_cross_link_persistence_unavailable; or
  • 503 admin_entity_comment_persistence_unavailable.

Authentication, admin scope, entity parameters, and request-shape validation remain ahead of authority disclosure. Mutations await persistence before their success response. Comment creation still writes its operator audit event after the primary collaboration commit and now awaits an available audit persistence barrier; this is an ordered post-primary audit side effect, not a claimed cross-table transaction.

Privacy lifecycle#

The deploy-bound continuity_state collector receives an exact reference to the durable stores. Its admin_collaboration record contains:

  • explicit cross-links owned by the subject; and
  • comments authored by, mentioning, or resolved by the subject.

The signed continuity-state deletion fanout calls the same durable instances. Deletion:

  • removes all exact-subject explicit cross-links;
  • replaces subject-authored comment text with [deleted];
  • tombstones authored comments;
  • removes raw and @-prefixed subject mentions;
  • replaces author and resolver identities with deleted:<sha256-domain-separated-digest>; and
  • persists a domain-separated digest-only fence in each store.

The operation is idempotent. Hydration preserves the fences, stale mutation attempts return 410, and snapshot import rejects a raw identity that conflicts with an existing fence. Adjacent operator records remain intact.

Verification#

text
# base-store contracts and bounds, candidate/save/publish failure behavior,
# concurrent mutation ordering, export, deletion, restart fences, routes,
# deployable fail-loud behavior, and investigation-bundle composition
pnpm exec vitest run --config apps/oshun/bff/vitest.config.ts \
  apps/oshun/bff/src/admin/durable-backed-admin-collaboration-stores.spec.ts \
  apps/oshun/bff/src/admin/durable-stores.test.ts \
  apps/oshun/bff/src/__tests__/admin-cross-links.test.ts \
  apps/oshun/bff/src/__tests__/admin-entity-comments.test.ts \
  apps/oshun/bff/src/__tests__/admin-cross-links-route.test.ts \
  apps/oshun/bff/src/__tests__/admin-entity-comments-route.test.ts \
  apps/oshun/bff/src/__tests__/admin-investigation-bundle-store.test.ts \
  apps/oshun/bff/src/__tests__/admin-investigation-bundles-route.test.ts \
  apps/oshun/bff/src/admin/durable-backed-investigation-bundle-store.test.ts
  9 files passed; 84/84 tests passed

pnpm exec eslint --no-warn-ignored <11 affected production TypeScript files>
pnpm exec prettier --check <16 affected TypeScript files>
git diff --check
  passed

NODE_OPTIONS='--max-old-space-size=8192' \
  node tools/typecheck/ratchet.mjs \
    --app apps/oshun/bff \
    --tsconfig tsconfig.typecheck.json
  only the same five current-main errors outside the affected files:
  admin-isis-cli-surface-route.test.ts:58
  autonomous-content-metrics-store.ts:89
  agentic/autonomy-route.test.ts:200
  agentic/autonomy-route.test.ts:491
  tenant-content-graph-store.spec.ts:88

# the affected pre-commit sweep additionally reaches an unrelated package
# failure at libs/shared/tracing/src/genai.ts:365; the commit used the hook's
# documented SKIP_TYPECHECK=1 path after the focused ratchet above

node apps/oshun/bff/scripts/build.mjs
node --check apps/oshun/bff/dist/server.js
  dist/server.js: 36,631,542 bytes
  dist/server.js.map: 85,777,580 bytes

# empty disposable PostgreSQL catalog
pnpm --dir libs/oshun/persistence exec prisma migrate deploy \
  --config prisma.config.ts
  all 32 migrations applied

OSHUN_V1_DATABASE_URL=<fresh-database> \
  pnpm exec vitest run \
    --config apps/oshun/bff/vitest.integration.config.ts \
    apps/oshun/bff/src/admin/durable-stores.integration.test.ts
  1 file passed; 2/2 tests passed

# exact rebased artifact, fresh database, and local Redis
node apps/oshun/bff/scripts/verify-production-artifact.mjs
  Production artifact smoke check passed.

The first push was rejected because origin/main had advanced through five non-overlapping Yemaya/Isis and generated-inventory commits. The implementation rebased without conflict. All 84 focused tests, the direct build, syntax check, fresh 32-migration PostgreSQL restart suite, and production artifact smoke were rerun after the rebase. The exact published artifact SHA-256 is d6ddc728c3fd42507f3cd632b9a35d1828be86667d7692236267b8c69b033f31.

Artifact identities#

Artifact SHA-256
apps/oshun/bff/src/admin/admin-cross-links.ts 5bd34615c20f48f5e656269d207496cc912dac5e2a5becb03ca22c51f573db45
apps/oshun/bff/src/admin/admin-entity-comments.ts 3c01630075f23b66dec5c3a2bb803b6cc1581472ebf8265c38d73103bc652e82
apps/oshun/bff/src/admin/durable-backed-admin-collaboration-stores.ts fbf6460fd12dd52320ce30ee4117f07703864ed10f58d3d842e0b387efc63ba3
apps/oshun/bff/src/admin/admin-collaboration-subject-authority.ts fea6ed400aee3d1e5b24176a9ca221e1906fd7e3fc78fe1a06235955edf37785
apps/oshun/bff/src/admin/durable-stores.ts 8c616a167eacf11035ba54361777693cbfcf4b283ba7cd614e4deccbcee2aae3
apps/oshun/bff/src/routes/admin-cross-links.ts 3d8bea76b805f16f659ac9f6ce6b2d63072952733ba028c5051668ba9b477748
apps/oshun/bff/src/routes/admin-entity-comments.ts 616eb4630b05c632462d81f1423f2667d9d641d5188ad41ed4e5c1364d5c2e11
apps/oshun/bff/src/data-export/bundle-builder.ts b702bf40358752fb1e40b4df96f554b374725aaf6c688312f16cb67d76a17d16
apps/oshun/bff/dist/server.js d6ddc728c3fd42507f3cd632b9a35d1828be86667d7692236267b8c69b033f31

No customer/admin web UI, mobile flow, public contract, database schema, provider/model call, or Unreal asset changed, so frontend-skill, Playwright, mobile, schema-generation, live-provider/model, and Unreal automation were inapplicable. This closes acknowledged restart loss, fail-open empty reads, and the connected privacy lifecycle for these two stores. The existing whole-snapshot persistence model still assumes a single mutation writer per store; multi-replica compare-and-swap/transactional serialization and V1-002's parent all-store inventory remain open.

Aja governance authority boundary — 2026-07-26#

Source implementation and published origin/main commit: e90c1e371b53782196ab648b725e5fb3a4f792d9.

Reachability and authority audit#

The BFF exposed three operator surfaces backed by module-global process-local managers:

  • upload consent at /v1/admin/aja/consent;
  • content-security grants at /v1/admin/aja/content-security; and
  • data-retention policies at /v1/admin/aja/data-retention.

Repository-wide import, symbol, route, and producer/consumer tracing found no production system beyond those routes:

  • no upload, processing, training, or sharing path consumed upload-consent decisions;
  • no delivery, sharing, decrypt, or key path enforced content-security grants; and
  • no storage lifecycle, deletion, or legal-hold executor consumed retention policies or evaluations.

The admin routes and their tests were the only consumers of the singleton instances. A successful mutation therefore changed only one BFF process while presenting an enforcement-shaped result to the operator. Restart erased the state, separate replicas could disagree, and persistence alone would still have created a second unintegrated policy authority.

Fail-closed disposition#

All three singleton exports are removed. ContentSecurityStore, UploadConsentStore, and AjaDataRetentionStore remain deterministic process-local adapters only for explicit test/development composition.

createApp now accepts three deploy-bound authority interfaces. They support synchronous or awaited implementations, and routes await every read, mutation, and decision. The production server binds none. After authentication, scope, path, and payload validation:

  • catalogs remain available with an explicit authority object;
  • the default catalogs report configured: false and a stable reason;
  • retention returns an honest empty policy list rather than volatile state; and
  • valid decisions return one of:
    • 503 aja_upload_consent_authority_not_configured;
    • 503 aja_content_security_authority_not_configured; or
    • 503 aja_data_retention_authority_not_configured.

Invalid bodies remain 400, absent authentication remains 401, and insufficient scope remains 403; the authority boundary does not weaken or reorder those guards. Explicitly injected adapters preserve deterministic functional route coverage without becoming the deploy default.

The Oshun module-boundary declaration now includes scope:aja, matching the existing composition architecture and 216 BFF imports that previously made every touched Aja adapter fail the scoped lint gate.

Honest Studio state#

The frontend-skill governed the UI change. The existing Studio composition, heading hierarchy, and route-map language remain intact. A shared restrained status notice now:

  • renders “Authority not connected” with the exact machine-readable boundary;
  • explains which owning executor is absent;
  • disables every input, select, checkbox, and mutation button;
  • guards callbacks as well as native controls, so programmatic clicks cannot emit a request; and
  • exposes accessible names on every control, including disabled selects.

Connected-authority fixtures preserve the existing grant/check/revoke, grant/check/withdraw, and create/evaluate behaviors. Unbound fixtures prove there is no POST and no optimistic result. The authenticated Playwright flow checks all three real Studio pages at desktop and 390×844 viewports and receives the shared automatic WCAG 2.1 AA serious/critical axe gate on each page.

The first browser pass correctly found a critical unnamed-select defect. The controls were fixed rather than suppressing the rule; the final three-page run passed.

Verification#

text
pnpm --dir apps/oshun/bff exec vitest run \
  src/__tests__/admin-aja-consent-route.test.ts \
  src/__tests__/admin-aja-content-security-route.test.ts \
  src/__tests__/admin-aja-data-retention-route.test.ts \
  --maxWorkers=1
  3 files passed; 22/22 tests passed

pnpm --dir apps/oshun/web exec vitest run \
  src/components/__tests__/StudioAjaConsentManagementWorkspace.integration.test.tsx \
  src/components/__tests__/StudioAjaConsentManagementWorkspace.test.tsx \
  src/components/__tests__/StudioAjaContentSecurityWorkspace.integration.test.tsx \
  src/components/__tests__/StudioAjaContentSecurityWorkspace.test.tsx \
  src/components/__tests__/StudioAjaDataRetentionWorkspace.integration.test.tsx \
  src/components/__tests__/StudioAjaDataRetentionWorkspace.test.tsx \
  --maxWorkers=1
  6 files passed; 15/15 tests passed

E2E_SKIP_STUDY=1 pnpm --dir apps/oshun/web run e2e -- \
  e2e/studio-aja-governance-authority.spec.ts \
  --project=chromium --workers=1
  3/3 passed; automatic WCAG 2.1 AA axe checks passed

pnpm exec eslint <25 scoped implementation/test files> \
  --no-ignore --max-warnings=0
pnpm exec prettier --check <25 scoped implementation/test/docs files>
git diff --check
  passed

NODE_OPTIONS='--max-old-space-size=8192' \
  node tools/typecheck/ratchet.mjs \
    --app apps/oshun/web --tsconfig tsconfig.typecheck.json
  no app-owned errors; backlog 0

NODE_OPTIONS='--max-old-space-size=8192' \
  node tools/typecheck/ratchet.mjs \
    --app apps/oshun/bff --tsconfig tsconfig.typecheck.json
  only the same five current-main errors outside the affected files:
  admin-isis-cli-surface-route.test.ts:58
  autonomous-content-metrics-store.ts:89
  agentic/autonomy-route.test.ts:200
  agentic/autonomy-route.test.ts:491
  tenant-content-graph-store.spec.ts:88

# the affected pre-commit sweep additionally reaches the unrelated
# libs/shared/tracing/src/genai.ts:365 V7-union mismatch; the implementation
# commit used the hook's documented SKIP_TYPECHECK=1 path after the ratchets

# all three affected Markdown walkthroughs, using the canonical renderer
selected docs-center render/check
  3/3 fresh

# The repository-wide docs-center check also ran. It remains blocked by 409
# previously stale generated files across unrelated V3, ADR, audit, compliance,
# proposal, runbook, and training sources. No broad generated-doc rewrite was
# folded into this scoped authority change.

node apps/oshun/bff/scripts/build.mjs
node --check apps/oshun/bff/dist/server.js

# empty disposable PostgreSQL catalog
pnpm --dir libs/oshun/persistence exec prisma migrate deploy
  all 32 migrations applied

OSHUN_ADMIN_DATABASE_URL=<fresh-database> \
OSHUN_REDIS_URL=<local-redis> \
  node apps/oshun/bff/scripts/verify-production-artifact.mjs
  Production artifact smoke check passed.

The initial push was rejected because origin/main advanced through two non-overlapping Yemaya commits. The implementation rebased cleanly. All 22 BFF tests, all 15 web tests, all three Playwright/axe cases, the direct build and syntax check, the fresh 32-migration database, and the production artifact smoke were rerun after rebase.

The exact published artifact is:

text
apps/oshun/bff/dist/server.js
  36,621,482 bytes
  sha256 672fc7b02507c49925dd60c69d9ec401d6aa8a593a7aa7ba718a0fbb597070b3

apps/oshun/bff/dist/server.js.map
  85,766,240 bytes
  sha256 064a89d0006989f187fc21faf1e3fcca7ee12b6a7f9b126f0bd0bb95704be99b

Artifact identities#

Artifact SHA-256
apps/oshun/bff/src/aja/content-security-store.ts fe1e3a86911aa4ccaa210600a4e78121aba39747ccfd577671b7256bd19350a5
apps/oshun/bff/src/aja/upload-consent-store.ts 5879700a2d594d0d6b71e476c18c1b6d3d107cf6b6fffec22bc704d275771541
apps/oshun/bff/src/aja/data-retention-store.ts ddd8ff6532b7b7fe0316037b007b279c7f40d02527c6efb0e04a64e270edfd5f
apps/oshun/bff/src/routes/admin-aja-content-security.ts 8472b378316520354538cf551d17ecec95d593a6334e656de7f41e78bd539c6c
apps/oshun/bff/src/routes/admin-aja-consent.ts 30b87160d0175eec5c28c3dffbee8154f225a2334934374a1753e32f55f710bf
apps/oshun/bff/src/routes/admin-aja-data-retention.ts befdd0a998d120d49de8b3cd1f9993375382f82e961ccfc3c1fbff4bd35c8854
apps/oshun/bff/src/app.ts 03bbead72283e641f2e74779c248047faccd762c0078b737049e3088d01866b9
apps/oshun/web/src/components/studio/_ajaAuthorityStatus.tsx 0427fa207d671bfbe2ab3f0e20ac4a5a869681efc88856a67cec9a616d2e2778
apps/oshun/web/e2e/studio-aja-governance-authority.spec.ts f7436f90012cee3eaab90f3c26ab6ef1df7fc41713c90c0d44b111c7659b5efa
apps/oshun/bff/dist/server.js 672fc7b02507c49925dd60c69d9ec401d6aa8a593a7aa7ba718a0fbb597070b3

No production authority now stores consent, grants, policies, or subject data on these surfaces. A future binding must be the owning service actually consumed by upload/processing, delivery/decrypt/share, and lifecycle/deletion execution; it must bring its own durable multi-replica semantics, exact-subject export/deletion, resurrection fences, legal holds, retention, recovery, and enforcement tests before authority.configured may become true. V1-002's parent all-store inventory remains open.

Admin restore-review authority boundary — 2026-07-26#

Source implementation and published origin/main commit: bccaaba0bf8e9cf91a4a75560b3550e3ea466eb8.

Reachability and authority audit#

The deployed BFF registered a module-global AdminRestoreReviewStore behind:

  • GET /admin/privacy/restore-requests and its /v1 alias;
  • GET /admin/privacy/restore-requests/:requestId and its /v1 alias; and
  • POST /admin/privacy/restore-requests/:requestId/actions and its /v1 alias.

The state store claimed that deployments populated it through background ingestion. Repository-wide import, symbol, route, producer, consumer, and server composition tracing found no such ingestion path. seedRequest was called only by test sources. No canonical restore-request service fed the singleton, no artifact-restoration executor consumed its approvals or completion claims, and the production singleton was constructed without an audit publisher.

The resulting surface was not a merely lossy cache. It was an authority-shaped, process-local queue that:

  • always appeared empty after production start because no producer existed;
  • could diverge between replicas if any indirect caller populated it;
  • would lose requests, consent and identity evidence, operator notes, decisions, and completion claims on restart; and
  • could mark a request complete without invoking or verifying any artifact restoration.

Persisting that isolated state machine would have created a second, unintegrated restore authority rather than connecting the owning system.

Fail-closed disposition#

The module-global singleton is removed. AdminRestoreReviewStore remains a deterministic process-local state-machine adapter only for explicit test/development composition.

createApp now accepts a deploy-bound AdminRestoreReviewAuthority. The authority exposes one coherent operator snapshot and an action method, and the route supports either synchronous or awaited implementations. The production server binds none. For an otherwise valid authenticated request, all six route forms now return:

text
503 restore_review_authority_not_configured

Guard ordering remains fail-safe and testable:

  • missing authentication remains 401;
  • an operator without the privacy scope remains 403;
  • invalid list filters, request identifiers, and action schemas remain 400; and
  • only a valid request reaches the authority-availability boundary.

Detail reads derive the request and revision from the same authority snapshot, avoiding a split-read revision race. Injected adapters preserve the complete eligibility-window, transition, dual-control, denial, completion-count, and canonical audit-event regression proof without becoming the deploy default.

Verification#

The resource gate reported 15 GiB RAM, 31 GiB swap, 13 GiB initially available, 15 GiB free disk, and no competing broad build or test process. The BFF ratchet peaked near 6.7 GiB RSS while available memory stayed above 6.9 GiB.

text
pnpm --dir apps/oshun/bff exec vitest run \
  src/routes/admin-restore-review.spec.ts \
  src/admin-restore/audit-emission.spec.ts \
  src/__tests__/restore-authorization-regression.spec.ts \
  --maxWorkers=1
  3 files passed; 41/41 tests passed

pnpm exec eslint <5 changed source/test files> --no-warn-ignored
pnpm exec prettier --check <5 changed source/test files>
git diff --check
  passed

NODE_OPTIONS='--max-old-space-size=8192' \
  node tools/typecheck/ratchet.mjs \
    --app apps/oshun/bff \
    --tsconfig tsconfig.typecheck.json
  only the same five current-main errors outside the affected files:
  admin-isis-cli-surface-route.test.ts:58
  autonomous-content-metrics-store.ts:89
  agentic/autonomy-route.test.ts:200
  agentic/autonomy-route.test.ts:491
  tenant-content-graph-store.spec.ts:88

# the affected pre-commit sweep additionally reaches the unrelated
# libs/shared/tracing/src/genai.ts:365 V7-union mismatch; the source commit used
# the hook's documented SKIP_TYPECHECK=1 path after the focused ratchet

node apps/oshun/bff/scripts/build.mjs
node --check apps/oshun/bff/dist/server.js

# empty disposable PostgreSQL catalog
pnpm --dir libs/oshun/persistence exec prisma migrate deploy \
  --config prisma.config.ts
  all 32 migrations applied

OSHUN_ADMIN_DATABASE_URL=<fresh-database> \
OSHUN_V1_DATABASE_URL=<fresh-database> \
OSHUN_REDIS_URL=<local-redis> \
  node apps/oshun/bff/scripts/verify-production-artifact.mjs
  Production artifact smoke check passed.

The initial implementation push was rejected because origin/main advanced through non-overlapping Yemaya/Nisaba work. The source commit rebased cleanly. All 41 focused tests, the direct build, syntax check, fresh 32-migration PostgreSQL catalog, and production artifact smoke were rerun after the rebase.

The exact published artifact is:

text
apps/oshun/bff/dist/server.js
  36,606,191 bytes
  sha256 c240e5e5c36727ca571aa881fa28ea5bbe36b33b8d01b4b5024e94455b73923d

apps/oshun/bff/dist/server.js.map
  85,759,009 bytes
  sha256 625865eb9f77bf3d62fa64dd0528d70eea8186203f75916ccaf14a8ff72950a9

Artifact identities#

Artifact SHA-256
apps/oshun/bff/src/admin-restore/state.ts d90ddf02b6f1ef7cfd56c2f210cc700e5a41a5945e9c3f25dde5f48c6a44a396
apps/oshun/bff/src/routes/admin-restore-review.ts 53e2e0531e75ab31292bd10eabb148fb2d292c21c1e5cda83439e6399a1c82c8
apps/oshun/bff/src/app.ts 81b5437ad5a01d3eb8bae3ba04fa31a92fbcb1c03ad357cdb1ddfa38d321c2e5
apps/oshun/bff/src/routes/admin-restore-review.spec.ts 74595de2ab84c046eb2cc48b7523b53eee07de9acd2192c023bc92459d31a3a6
apps/oshun/bff/src/__tests__/restore-authorization-regression.spec.ts 12ca300ce237d73a3b854b482dcdc997a83782e0c3a56f5e95d65dc467468f14
apps/oshun/bff/dist/server.js c240e5e5c36727ca571aa881fa28ea5bbe36b33b8d01b4b5024e94455b73923d

No customer/admin web UI, mobile flow, public contract, database schema, provider/model call, or Unreal asset changed, so frontend-skill, Playwright, mobile, schema-generation, live-provider/model, and Unreal automation were inapplicable. This closes the false empty queue, unaudited process-local decisions, restart ambiguity, and fabricated completion authority. It does not claim a production restore service. A future binding must be the canonical request owner actually connected to artifact restoration and must provide durable multi-replica serialization, audited acknowledgement, idempotent execution, restart recovery, authorization, exact-subject privacy handling, and end-to-end restoration proof. V1-002's parent all-store inventory remains open.

Admin moderation authority boundary — 2026-07-26#

Source implementation and published origin/main commit: 9a37575bcb7a4fa2775579312e4d7655b3a1edf5.

Reachability and enforcement audit#

The BFF exposed a module-global ModerationStore through eight operations:

  • list the moderation queue and statistics;
  • enqueue a caller-supplied scan result;
  • decide a queue item;
  • file and resolve an appeal;
  • issue and revoke a ban; and
  • read a user's ban status.

The adapter runs the real @aja/content-moderation queue, appeal, and ban state machines. That fact did not make it a production authority. Repository-wide import, symbol, route, producer, consumer, and composition tracing found:

  • no production scanner or upload/content pipeline that ingested scan results;
  • no authentication or account service that consulted its bans;
  • no content-delivery or publication service that enforced its decisions;
  • no durable case or appeal repository;
  • no external moderation provider or enforcement effect; and
  • no consumer outside its own admin route and tests.

The admin route itself accepted a scan status and score and then created the queue record. It could therefore fabricate the input it purported to govern, approve or reject that record, adjudicate an appeal, and issue a ban that changed only one BFF process. Restart erased the entire queue, decision history, appeals, and bans. Replicas could disagree, and a successful ban response did not restrict any account or content operation. Persisting this isolated adapter would still have created a second moderation authority disconnected from intake and enforcement.

Fail-closed disposition#

The module-global singleton is removed. ModerationStore remains a deterministic process-local adapter only for explicit test/development composition and still exercises the upstream Aja state machines.

createApp now accepts a deploy-bound AdminModerationAuthority. Its queue, decision, appeal, ban, and status methods may be synchronous or awaited, and the route awaits every operation. The production server binds none. Each of the eight otherwise-valid operations now returns:

text
503 moderation_authority_not_configured

Authentication and scope checks still precede authority disclosure. Each operation validates its path and payload before reporting the missing authority, so malformed inputs retain their existing 400 response and cannot probe or invoke a binding.

The repository's root module-boundary rule also exposed a directly relevant metadata defect: libs/aja/content-moderation was already declared as an Nx library and carried scope:aja, but lacked the required type:lib tag. The project metadata now accurately identifies it as a library. The boundary rule was not disabled or broadened.

Verification#

The resource gate reported 15 GiB RAM, 31 GiB swap, 13 GiB initially available, 14 GiB free disk, and no competing broad build or test process. The BFF ratchet peaked near 6.6 GiB RSS while available memory stayed near 7 GiB.

text
pnpm --dir apps/oshun/bff exec vitest run \
  src/__tests__/admin-moderation-route.test.ts \
  --maxWorkers=1
  1 file passed; 13/13 tests passed

# cwd libs/aja/content-moderation
pnpm exec vitest run -c vite.config.ts --maxWorkers=1
  1 file passed; 39/39 tests passed

NX_DAEMON=false pnpm exec eslint <4 changed BFF source/test files> \
  --no-warn-ignored --no-cache
pnpm exec prettier --check <4 changed BFF files plus project.json>
git diff --check
  passed

NX_DAEMON=false pnpm exec nx lint aja-content-moderation \
  --parallel=1 --skip-nx-cache
  passed with no errors; eight pre-existing prefer-nullish-coalescing warnings

NODE_OPTIONS='--max-old-space-size=8192' \
  node tools/typecheck/ratchet.mjs \
    --app apps/oshun/bff \
    --tsconfig tsconfig.typecheck.json
  only the same five current-main errors outside the affected files:
  admin-isis-cli-surface-route.test.ts:58
  autonomous-content-metrics-store.ts:89
  agentic/autonomy-route.test.ts:200
  agentic/autonomy-route.test.ts:491
  tenant-content-graph-store.spec.ts:88

# the affected pre-commit sweep additionally reaches the unrelated
# libs/shared/tracing/src/genai.ts:365 V7-union mismatch; the source commit used
# the hook's documented SKIP_TYPECHECK=1 path after the focused ratchet

node apps/oshun/bff/scripts/build.mjs
node --check apps/oshun/bff/dist/server.js

# empty disposable PostgreSQL catalog
pnpm --dir libs/oshun/persistence exec prisma migrate deploy \
  --config prisma.config.ts
  all 32 migrations applied

OSHUN_ADMIN_DATABASE_URL=<fresh-database> \
OSHUN_V1_DATABASE_URL=<fresh-database> \
OSHUN_REDIS_URL=<local-redis> \
  node apps/oshun/bff/scripts/verify-production-artifact.mjs
  Production artifact smoke check passed.

The initial implementation push was rejected because origin/main advanced through non-overlapping Isis/Yemaya/mobile-parity work. The source commit rebased cleanly. All 52 focused tests, the direct build, syntax check, fresh 32-migration PostgreSQL catalog, and production artifact smoke were rerun after the rebase.

The exact published artifact is:

text
apps/oshun/bff/dist/server.js
  36,591,754 bytes
  sha256 3da0da76267f9c1153f8e6c0cceaab7b00214c3e6b52fde09c0fdf25ec0c9001

apps/oshun/bff/dist/server.js.map
  85,753,311 bytes
  sha256 28ac7c0a0465d2b50cb4da96666c635aefb3c653f605f0de1e491a232edafb59

Artifact identities#

Artifact SHA-256
apps/oshun/bff/src/moderation/moderation-store.ts 4e73217aa23cd609e0b026db355dc0fe5b644c53bbb6fd2401c7200e8710cb47
apps/oshun/bff/src/routes/admin-moderation.ts da84a76ab18633a51b84374aedcb763554d3d3b419c2a907231115bc8df1a4cb
apps/oshun/bff/src/app.ts 552c392f49b5ecf365ae1646bac004b00cae706479fa0abb393377d6b7e45df1
apps/oshun/bff/src/__tests__/admin-moderation-route.test.ts 32b06f874a96425bd2bc26e8bf00aa83be934e79c1d5416b283bc35812caf953
libs/aja/content-moderation/project.json 60f97885619fcc09c469a79c8efa92b899869ec38e4b89ee200bb66e6ac34df6
apps/oshun/bff/dist/server.js 3da0da76267f9c1153f8e6c0cceaab7b00214c3e6b52fde09c0fdf25ec0c9001

No customer/admin web UI, mobile flow, public contract, database schema, provider/model call, or Unreal asset changed, so frontend-skill, Playwright, mobile, schema-generation, live-provider/model, and Unreal automation were inapplicable. This closes the false queue, fabricated scan admission, process-local decision/appeal history, and unenforced ban claims. It does not claim a production moderation service. A future binding must own canonical scanner intake, durable cases and appeals, authenticated actor attribution, audited acknowledgements, idempotent enforcement effects, restart recovery, account/content privacy handling, and end-to-end enforcement proof. V1-002's parent all-store inventory remains open.

Isis reference-bank authority boundary — 2026-07-26#

Source implementation and published origin/main commit: 3ec98e462988da49aa6d223d27c55204c8443559.

Reachability and authority audit#

The BFF exposed a module-global ReferenceBankAdminStore through four authenticated Isis admin operations:

  • upsert a character, style, voice, or motif entry;
  • list all entries or filter them by kind;
  • read an entry by id; and
  • delete an entry by id.

The adapter wraps the real @isis/workflows reference-bank state machine and enforces its entry schema and kind-specific invariants. It also caps the bank at 500 entries and evicts older entries. Those implementation details did not make the adapter a production authority.

The store's source comment expressly claimed that other BFF code held its underlying ReferenceBankStore for consumers such as resolveShotReferences. Repository-wide import, symbol, route, producer, consumer, and composition tracing disproved that claim:

  • only the admin-ledger route and its tests imported the singleton;
  • no BFF planning or keyframe path received its store;
  • no canon/persona projection or lecture binding received it;
  • no generation, regeneration, media, assembly, or publication path consulted it;
  • there was no database, object-store snapshot, remote reference service, or cross-replica synchronization; and
  • there was no downstream effect proving that an accepted admin mutation constrained any generated or published artifact.

The route could therefore acknowledge canonical-looking identity, style, voice, and motif mutations that affected only one BFF process. Restart erased them, replicas could disagree, and the capacity policy could silently make a prior admin decision unavailable to that process. Persisting this isolated map alone would still have created a second reference authority disconnected from the workflows that are supposed to consume it.

Fail-closed disposition#

The module-global singleton is removed. ReferenceBankAdminStore remains an explicitly constructed deterministic adapter for unit, route, and local development composition; its upstream workflow invariants and bounded-capacity tests remain intact.

createApp now accepts an AdminReferenceBankAuthority. Its put, get, list, and remove methods may be synchronous or awaited, and every route operation awaits the binding. The production server binds none. Each otherwise-valid operation now returns:

text
503 reference_bank_authority_not_configured

Authentication and Isis workspace scope checks still run first. PUT parses the real ReferenceBankEntrySchema before authority lookup, list validates its kind, and item operations validate their path id. Invalid requests retain their existing 400 or 422 response and cannot probe or invoke a binding. Explicitly injected tests retain the full 201/200/404 lifecycle and real kind-invariant behavior.

Verification#

The resource gate reported 15 GiB RAM, 31 GiB swap, 14 GiB free disk, and no competing broad build/test gate. The type ratchet was supervised at 30-second intervals; it remained above the repository's safety thresholds throughout.

text
pnpm exec vitest run \
  --config apps/oshun/bff/vitest.config.ts \
  apps/oshun/bff/src/isis/reference-bank-store.test.ts \
  apps/oshun/bff/src/__tests__/admin-ledgers-route.test.ts
  2 files passed; 17/17 tests passed

NX_DAEMON=false pnpm exec eslint <4 changed BFF source/test files> --no-cache
  production sources passed with zero errors; the configured test ignore emitted
  one informational warning
pnpm exec prettier --check <4 changed BFF files>
git diff --check
  passed

NODE_OPTIONS='--max-old-space-size=8192' \
  node tools/typecheck/ratchet.mjs \
    --app apps/oshun/bff \
    --tsconfig tsconfig.typecheck.json
  only the same five current-main errors outside the affected files:
  admin-isis-cli-surface-route.test.ts:58
  autonomous-content-metrics-store.ts:89
  agentic/autonomy-route.test.ts:200
  agentic/autonomy-route.test.ts:491
  tenant-content-graph-store.spec.ts:88

# the affected pre-commit sweep additionally reaches the unrelated
# libs/shared/tracing/src/genai.ts:365 V7-union mismatch; the source commit used
# the hook's documented SKIP_TYPECHECK=1 path after the focused ratchet

node apps/oshun/bff/scripts/build.mjs
node --check apps/oshun/bff/dist/server.js

# empty disposable PostgreSQL catalog
pnpm --dir libs/oshun/persistence exec prisma migrate deploy \
  --config prisma.config.ts
  all 32 migrations applied

OSHUN_ADMIN_DATABASE_URL=<fresh-database> \
OSHUN_V1_DATABASE_URL=<fresh-database> \
OSHUN_REDIS_URL=<local-redis> \
  node apps/oshun/bff/scripts/verify-production-artifact.mjs
  Production artifact smoke check passed.

The initial implementation push was rejected because origin/main advanced through non-overlapping Yemaya/Nisaba work. The source commit rebased cleanly. All 17 focused tests, the direct build, syntax check, fresh 32-migration PostgreSQL catalog, and production artifact smoke were rerun after the rebase. Both disposable verification catalogs were removed.

The exact published artifact is:

text
apps/oshun/bff/dist/server.js
  36,589,457 bytes
  sha256 270b15bb2c40c9b5a01e2fba82128dcf05d0e39aa0dd39514e534861e6806cca

apps/oshun/bff/dist/server.js.map
  85,753,243 bytes
  sha256 e051dd355610a5f41fd908b67fefcab5b187525ceeb4c4c1f268f6ae2efecd05

Artifact identities#

Artifact SHA-256
apps/oshun/bff/src/isis/reference-bank-store.ts 8c111e8fe0132d905fbc9ee14a4a3cbd6be777fe60e068c30587a8d557a10b68
apps/oshun/bff/src/routes/admin-ledgers.ts 8a62a67fc980dd59309738fdd6606b70843734df4358c24e428ebf7b36f11ce0
apps/oshun/bff/src/app.ts 329fa96db47ea87a3a2c29cae9b0530afc7784ba468826f0d079f8d9d6704e96
apps/oshun/bff/src/__tests__/admin-ledgers-route.test.ts d0e2f825a40265cc11440988bda5749afb1ab43ac73b8e4540379a41db8b0041
apps/oshun/bff/dist/server.js 270b15bb2c40c9b5a01e2fba82128dcf05d0e39aa0dd39514e534861e6806cca

No customer/admin web UI, mobile flow, public contract, database schema, provider/model call, or Unreal asset changed, so frontend-skill, Playwright, mobile, schema-generation, live-provider/model, and Unreal automation were inapplicable. This closes the false process-local reference authority and its fabricated downstream-consumption claim. It does not claim a production reference bank. A future binding must be the canonical durable/shared owner actually consumed by planning, generation, regeneration, and publication, with authenticated actor attribution, audited acknowledgements, idempotent writes, restart recovery, cross-replica serialization, entry lifecycle/retention, privacy controls for reference media, and end-to-end artifact-binding proof. V1-002's parent all-store inventory remains open.

Isis scene/production/lecture ledger authority boundary — 2026-07-26#

Source implementation and published origin/main commit: b6a090c7922f38e9db307e6ec653f89d28c53cea.

Reachability and effect audit#

The BFF exposed one module-global SceneLedgerAdminStore through 17 authenticated Isis admin operations:

  • scene-ledger put, list, read, digest, and delete;
  • production-ledger put, list, read, digest, and delete;
  • lecture-ledger put, list, read, digest, and delete;
  • model-backed lecture authoring followed by a ledger put; and
  • deterministic or model-classified lecture tweak routing from a stored ledger.

The adapter uses the real @isis/workflows parsers, structural-integrity passes, production schema, digest builders, lecture author floors, and tweak router. It clones reads, caps each family at 500 documents, and reports eviction counters. Those library semantics did not turn its process-local maps into product persistence.

Repository-wide import, symbol, endpoint, producer, consumer, and composition tracing found:

  • only the combined admin route and its tests imported the singleton;
  • no planner, generator, keyframe, regeneration, renderer, or media pipeline consumed a scene ledger from it;
  • no assembler or publication path consumed a production ledger from it;
  • no lesson player, course authority, lecture renderer, or publication path consumed a lecture ledger from it;
  • no web/admin client called these endpoints;
  • no database, object-store snapshot, owning service, or cross-replica synchronization backed any family; and
  • no downstream effect proved that an accepted mutation, authored lecture, or tweak route constrained a generated, assembled, or published artifact.

The route could acknowledge complete authoring documents and deletion while changing only one BFF process. Restart erased all three families, replicas could disagree, and the cap could evict earlier operator state. More seriously, the lecture author could invoke a configured model, clear its deterministic floors, and then report success after writing the result only to volatile memory. Persisting these maps in isolation would still have created a shadow ledger plane disconnected from actual planning, generation, assembly, and publication.

Fail-closed disposition#

The module-global singleton is removed. SceneLedgerAdminStore remains an explicitly constructed test/development adapter, preserving its upstream validation, integrity, cloning, digest, capacity, and eviction coverage.

createApp now accepts one AdminLedgerAuthority spanning scene, production, and lecture operations. Every method may be synchronous or awaited, and the route awaits every read, write, presence probe, list, and deletion. Production binds none. Every otherwise-valid ledger operation now returns:

text
503 ledger_authority_not_configured

Authentication and Isis workspace scope checks remain first. PUT routes parse the real scene/production/lecture contracts before authority lookup; list and digest query parameters and ledger ids are also validated first. Malformed requests therefore retain their existing 400 or 422 behavior and cannot probe or invoke a binding.

The model-backed author validates its body and requires the ledger authority before checking or invoking the LLM binding. The unbound-authority proof injects a working scripted provider and asserts zero provider calls. Thus production cannot pay for a model result that it has no owning authority to acknowledge. With an explicit authority, the existing author-floor, structured-output, failure, blocker, digest, and tweak-routing behavior remains unchanged. The production digest's scene-child presence probes now go through the same awaited owning authority rather than a hidden local map.

Verification#

The resource gate reported 15 GiB RAM, 31 GiB swap, 14 GiB free disk, and no competing broad build/test gate. The BFF type ratchet was polled every 30 seconds and remained above the configured safety thresholds.

text
pnpm exec vitest run \
  --config apps/oshun/bff/vitest.config.ts \
  apps/oshun/bff/src/isis/scene-ledger-store.test.ts \
  apps/oshun/bff/src/__tests__/admin-ledgers-route.test.ts \
  apps/oshun/bff/src/__tests__/admin-ledgers-lecture-route.test.ts
  3 files passed; 46/46 tests passed

NX_DAEMON=false pnpm exec eslint <5 changed BFF source/test files> \
  --no-warn-ignored --no-cache
pnpm exec prettier --check <5 changed BFF files>
git diff --check
  passed

NODE_OPTIONS='--max-old-space-size=8192' \
  node tools/typecheck/ratchet.mjs \
    --app apps/oshun/bff \
    --tsconfig tsconfig.typecheck.json
  only the same five current-main errors outside the affected files:
  admin-isis-cli-surface-route.test.ts:58
  autonomous-content-metrics-store.ts:89
  agentic/autonomy-route.test.ts:200
  agentic/autonomy-route.test.ts:491
  tenant-content-graph-store.spec.ts:88

# the affected pre-commit sweep additionally reaches the unrelated
# libs/shared/tracing/src/genai.ts:365 V7-union mismatch; the source commit used
# the hook's documented SKIP_TYPECHECK=1 path after the focused ratchet

node apps/oshun/bff/scripts/build.mjs
node --check apps/oshun/bff/dist/server.js

# empty disposable PostgreSQL catalog
pnpm --dir libs/oshun/persistence exec prisma migrate deploy \
  --config prisma.config.ts
  all 32 migrations applied

OSHUN_ADMIN_DATABASE_URL=<fresh-database> \
OSHUN_V1_DATABASE_URL=<fresh-database> \
OSHUN_REDIS_URL=<local-redis> \
  node apps/oshun/bff/scripts/verify-production-artifact.mjs
  Production artifact smoke check passed.

The initial implementation push was rejected because origin/main advanced through non-overlapping Yemaya/Nisaba work. The source commit rebased cleanly. All 46 focused tests, the direct build, syntax check, fresh 32-migration PostgreSQL catalog, and production artifact smoke were rerun after the rebase. Both disposable verification catalogs were removed.

The exact published artifact is:

text
apps/oshun/bff/dist/server.js
  36,583,215 bytes
  sha256 d834715929c6eca36084dee1aaf4373cd7890189ca9739bb01cd69fc54143be4

apps/oshun/bff/dist/server.js.map
  85,741,064 bytes
  sha256 5881a21d3d0d89111c5f4805433b6df164e97591182456016a8cbfd68bca4f4f

Artifact identities#

Artifact SHA-256
apps/oshun/bff/src/isis/scene-ledger-store.ts dd789e5b3b8524bc8e16ee4e356db9fd7545dc82508483a7d806c68369a93b20
apps/oshun/bff/src/routes/admin-ledgers.ts 7bce9db7ff4f2c56a05aba948fcbf5173bc5b9c446d0abffba78a312d3e50ae8
apps/oshun/bff/src/app.ts 9e4cc67502975144233d2406888595429112acd5717218c9c41e6c73831aa3e5
apps/oshun/bff/src/__tests__/admin-ledgers-route.test.ts 98c18d5ba34c24b876d53d03488a08e1935dd19327f3901f27b68e1fceae42f5
apps/oshun/bff/src/__tests__/admin-ledgers-lecture-route.test.ts 9c4ecf470747fc92358849a9dd87c784e84777ba3f3cb6ef70de02d3d4efda29
apps/oshun/bff/dist/server.js d834715929c6eca36084dee1aaf4373cd7890189ca9739bb01cd69fc54143be4

No customer/admin web UI, mobile flow, public contract, database schema, live-provider/model call, or Unreal asset changed, so frontend-skill, Playwright, mobile, schema-generation, live-provider/model, and Unreal automation were inapplicable. Scripted provider coverage exercised the LLM boundary without external calls.

This closes the false scene/production/lecture persistence claim, the replica-local authoring plane, and the possibility of invoking a model before discovering that no ledger authority exists. It does not claim a production ledger service. A future binding must be the canonical durable/shared owner actually consumed by planning, generation, regeneration, rendering, assembly, and publication, with authenticated actor attribution, audited and idempotent acknowledgements, transactional concurrency, restart recovery, privacy/DSAR handling for authored content and reference URIs, retention/legal holds, and end-to-end artifact-binding proof. V1-002's parent all-store inventory remains open.

Year in Practice activity-summary disposition — 2026-07-26#

Source implementation and published origin/main commit: 8ed2347d86e9a352bdd5d87ca6a885f5a06d7575.

Producer, consumer, and loss audit#

The authenticated /me/year-in-practice and /v1/me/year-in-practice routes build a quarterly or annual artifact through the canonical @oshun/shell-achievements retrospective builder. Their former input was one module-global ActivitySummariesStore, hydrated from the shared admin snapshot table and described as process-durable member history.

Repository-wide symbol, route, producer, consumer, and composition tracing found:

  • only year-in-practice.test.ts called seedSummaries;
  • production had no analytics, Tara, Arete, Nisaba, Nyx, Veritas, or Living Scenes producer for the record shape;
  • no event consumer, scheduled aggregator, or owning database projection wrote the snapshot key;
  • no first-party web, mobile, or admin client called the route; and
  • the route was the only production reader.

Consequently, a production process could hydrate only orphan/legacy snapshot data; current repository behavior could never create a new record. Treating that map as durable member history overstated both its provenance and its freshness. Its loss cannot remove authority, evidence, lineage, approvals, acknowledged effects, or learning state because no production path owns any of those through this seam.

Stateless production disposition#

The production singleton, snapshot schema/key binding, hydration, and fire-and-forget save path are removed. Production now defaults to a frozen ActivitySummariesSource whose exact projection is null for every member and period. The real retrospective builder converts that absence into its explicit quiet-period artifact; the BFF does not fabricate zero-valued rich statistics.

createApp and the route expose a deploy-bound activitySummariesSource injection seam for a future canonical cross-domain projector. The mutable ActivitySummariesStore remains only as an explicitly constructed synthetic test/development adapter. Rich-quarter, member-isolation, and exact share-card coverage all inject it directly. A dedicated default-composition test proves that production returns the quiet artifact without a binding.

The prior delight-activity-summaries snapshot row, if present in an existing database, is intentionally ignored rather than deleted: it is not authoritative and deleting deployment data was unnecessary to close the code path.

Verification#

text
pnpm exec vitest run \
  --config apps/oshun/bff/vitest.config.ts \
  apps/oshun/bff/src/routes/year-in-practice.test.ts
  1 file passed; 5/5 tests passed

NX_DAEMON=false pnpm exec eslint <5 changed BFF source/test files> \
  --no-warn-ignored --no-cache
pnpm exec prettier --check <5 changed BFF files>
git diff --check
  passed

NODE_OPTIONS='--max-old-space-size=8192' \
  node tools/typecheck/ratchet.mjs \
    --app apps/oshun/bff \
    --tsconfig tsconfig.typecheck.json
  only the same five current-main errors outside the affected files:
  admin-isis-cli-surface-route.test.ts:58
  autonomous-content-metrics-store.ts:89
  agentic/autonomy-route.test.ts:200
  agentic/autonomy-route.test.ts:491
  tenant-content-graph-store.spec.ts:88

# the affected pre-commit sweep additionally reaches the unrelated
# libs/shared/tracing/src/genai.ts:365 V7-union mismatch; the source commit used
# the hook's documented SKIP_TYPECHECK=1 path after the focused ratchet

node apps/oshun/bff/scripts/build.mjs
node --check apps/oshun/bff/dist/server.js

# empty disposable PostgreSQL catalog
pnpm --dir libs/oshun/persistence exec prisma migrate deploy \
  --config prisma.config.ts
  all 32 migrations applied

OSHUN_ADMIN_DATABASE_URL=<fresh-database> \
OSHUN_V1_DATABASE_URL=<fresh-database> \
OSHUN_REDIS_URL=<local-redis> \
  node apps/oshun/bff/scripts/verify-production-artifact.mjs
  Production artifact smoke check passed.

The resource gate reported 15 GiB RAM, 31 GiB swap, 14 GiB free disk, and no competing broad build/test gate. The type ratchet was supervised at 30-second intervals and remained above safety thresholds.

The initial implementation push was rejected because origin/main advanced through non-overlapping Yemaya/Nisaba work. The source commit rebased cleanly. All five focused tests, the direct build, syntax check, fresh 32-migration PostgreSQL catalog, and production artifact smoke were rerun after the rebase. Both disposable verification catalogs were removed.

The exact published artifact is:

text
apps/oshun/bff/dist/server.js
  36,580,685 bytes
  sha256 ba7ff7ae43a8ad37fada3405d1a949a530709a1d5bee9b022c5966e75eeb2074

apps/oshun/bff/dist/server.js.map
  85,738,422 bytes
  sha256 79dce31445a8cdb544a5c212b3b3e538e281511833d584ccbabf8d8081fb23a2

Artifact identities#

Artifact SHA-256
apps/oshun/bff/src/delight/activity-summaries-store.ts 6824b6ab49d496c259693c29c4f372374d1d92a722ade55ad28a4ad3d33a98b6
apps/oshun/bff/src/routes/year-in-practice.ts 1cec9e3e0f0a4d43841c73dc1d7af8721406e55a5c2e99cab7e7ab6685ad05a2
apps/oshun/bff/src/routes/year-in-practice.test.ts 3ee4d13beebe85a77833e76a4f4b2d8f1065fb65fd3900fee38c4b88a74ebc4a
apps/oshun/bff/src/app.ts e2d41b59ff5a8eb7d824d842bc1b2220c58a23fabe9753ebdac996c30791e416
apps/oshun/bff/src/server.ts b160921ed6b228eb73693845db70aab883aabc6687118de839a1cfbad3679b84
apps/oshun/bff/dist/server.js ba7ff7ae43a8ad37fada3405d1a949a530709a1d5bee9b022c5966e75eeb2074

No customer/admin web UI, mobile flow, public contract, database schema, provider/model call, or Unreal asset changed. No first-party UI consumes this route. Frontend-skill, Playwright, mobile, schema-generation, live-provider, and Unreal automation were therefore inapplicable.

This closes the orphan activity-summary snapshot as a false durable history claim and proves its production loss harmless. It does not claim a live Year in Practice activity pipeline. A future binding must project canonical acknowledged cross-domain activity with exact-subject privacy/erasure, retention, freshness, and source-version evidence. V1-002's parent all-store inventory remains open.

Nyx Sky Tonight false-state retirement — 2026-07-26#

Source implementation and published origin/main commit: 72e97fd5fdf8f14b3c1b0214e5d259e9424f1ca4.

Producer, consumer, authority, and loss audit#

The authenticated /nyx/sky-tonight/decision and /v1/nyx/sky-tonight/decision routes evaluate one requested followed event at one saved observing site through decideSkyTonightPush from @oshun/domain-nyx. The former input plane was a module-global SkyTonightStore, hydrated from the shared admin snapshot table and described as durable member follow, site, forecast, quiet-hour, and push-history state.

Repository-wide symbol, route, producer, consumer, and composition tracing found:

  • only nyx-sky-tonight.test.ts called seedFollowedEvent, seedSite, recordForecast, setQuietHours, or recordPush;
  • no Nyx scheduler, ephemeris/weather ingester, event consumer, notification bridge, owning service adapter, or BFF route wrote the snapshot key;
  • the decision route itself was the only production reader and had no acknowledged push-history write side effect;
  • no first-party Oshun web, mobile, or admin client called the route; and
  • the production process supplied no canonical source binding.

Consequently, production could only hydrate orphan/legacy rows that current repository behavior could never create or update. Those rows could falsely claim that a member followed an event, saved a site, had a current forecast or quiet-hour preference, or had already received a push. Their loss cannot remove authority, evidence, approvals, acknowledged effects, lineage, or learning state because no production path owns any of those through this seam.

Fail-closed production composition#

The production singleton, snapshot schema/key binding, hydration, and fire-and-forget write path are removed. createApp and the route now expose one atomic, async-capable SkyTonightSource that loads the event, site, forecast, quiet hours, and history for the authenticated member and requested identifiers. Atomic loading avoids mixing independently timed projections in one decision.

Production intentionally binds no source. After authentication and complete required-query plus ISO-instant validation, a valid request returns:

json
{
  "ok": false,
  "reason": "sky_tonight_source_not_configured"
}

with HTTP 503. Returning event_not_followed, site_not_saved, or forecast-unavailable without a binding would assert negative member or forecast knowledge the process does not possess. Bound sources retain the existing exact 404 and Nyx-domain verdict contract. The mutable SkyTonightStore remains only as an explicitly constructed synthetic test/development adapter. Every rich route test uses an awaited async wrapper, proving deploy adapters may perform real I/O without restoring a shadow write plane.

The prior nyx-sky-tonight snapshot row, if present in an existing database, is intentionally ignored rather than deleted: it is not authoritative, and deleting deployment data was unnecessary to close the code path.

Verification#

text
pnpm exec vitest run \
  --config apps/oshun/bff/vitest.config.ts \
  apps/oshun/bff/src/routes/nyx-sky-tonight.test.ts \
  apps/oshun/bff/src/__tests__/v1-feature-pack-boot.test.ts
  2 files passed; 16/16 tests passed

NX_DAEMON=false pnpm exec eslint <5 changed BFF source/test files> \
  --no-warn-ignored --no-cache
pnpm exec prettier --check <5 changed BFF files>
git diff --check
  passed

NODE_OPTIONS='--max-old-space-size=8192' \
  node tools/typecheck/ratchet.mjs \
    --app apps/oshun/bff \
    --tsconfig tsconfig.typecheck.json
  only the same five current-main errors outside the affected files:
  admin-isis-cli-surface-route.test.ts:58
  autonomous-content-metrics-store.ts:89
  agentic/autonomy-route.test.ts:200
  agentic/autonomy-route.test.ts:491
  tenant-content-graph-store.spec.ts:88

# the affected pre-commit sweep additionally reaches the unrelated
# libs/shared/tracing/src/genai.ts:365 V7-union mismatch; the source commit used
# the hook's documented SKIP_TYPECHECK=1 path after the focused ratchet

node apps/oshun/bff/scripts/build.mjs
node --check apps/oshun/bff/dist/server.js

# empty disposable PostgreSQL catalog
pnpm --dir libs/oshun/persistence exec prisma migrate deploy \
  --config prisma.config.ts
  all 32 migrations applied

OSHUN_ADMIN_DATABASE_URL=<fresh-database> \
OSHUN_V1_DATABASE_URL=<fresh-database> \
OSHUN_REDIS_URL=<local-redis> \
  node apps/oshun/bff/scripts/verify-production-artifact.mjs
  Production artifact smoke check passed.

The resource gates reported 15 GiB RAM, 31 GiB swap, 14 GiB free disk, and no competing broad build/test gate. Both type-ratchet runs were supervised at 30-second intervals and remained above the configured safety thresholds.

The initial source push was rejected because origin/main advanced through non-overlapping Isis/Yemaya work. The source commit rebased cleanly. Scoped static checks, all 16 focused/composition tests, the type ratchet, direct build, syntax check, fresh 32-migration PostgreSQL catalog, and production artifact smoke were repeated after that integration. A second push raced another Yemaya-only advance; that rebase was also clean, and the five changed BFF files were byte-identical. Both disposable verification catalogs were removed.

The exact published artifact is:

text
apps/oshun/bff/dist/server.js
  36,575,507 bytes
  sha256 2e02b782204338a3e96f3b9dc848b3c9a1af18621d8716a489fd7f9ca7060e63

apps/oshun/bff/dist/server.js.map
  85,727,024 bytes
  sha256 904b2d01ed200edf42a2ee3625a8026c4b1270cc291f2eb4f8872c5778e94334

Artifact identities#

Artifact SHA-256
apps/oshun/bff/src/delight/sky-tonight-store.ts 1bf948d84638392f0e82f52889030c65662f311707c9602176941ae2f6100890
apps/oshun/bff/src/routes/nyx-sky-tonight.ts 004e6e8202a5aa1fbeeba128eb216759ca7c5c53c5a4a01e52cdcdb477c53c19
apps/oshun/bff/src/routes/nyx-sky-tonight.test.ts e7561c96bbd9a3d53281d71a13d7601cd3fdc9e23ae0c82870676592321e940a
apps/oshun/bff/src/app.ts ed4a9cc88c0a3de9600f9ed928e227afb9370066a950242ea32eea52ec4351b5
apps/oshun/bff/src/server.ts dc5476d0a43f940433ffaf6830a08652a19ede48a9c4de63619a3e6e4b0197f2
apps/oshun/bff/dist/server.js 2e02b782204338a3e96f3b9dc848b3c9a1af18621d8716a489fd7f9ca7060e63

No customer/admin web UI, mobile flow, public schema, database schema, provider/model call, or Unreal asset changed. No first-party UI consumes this route. Frontend-skill, Playwright, mobile, schema-generation, live-provider, and Unreal automation were therefore inapplicable.

This closes the orphan Sky Tonight snapshot as a false durable member-state claim and proves its production loss harmless. It does not claim a live cross-plane decision pipeline. A future binding must project canonical member-scoped follow/site/weather/preference/history state with freshness, privacy/erasure, retention, source-version, and acknowledged push-delivery evidence. V1-002's parent all-store inventory remains open.

Privacy-receipts false-state retirement — 2026-07-26#

Source implementation and published origin/main commit: 24e010e7632b38d49c5188452b428f32aa5db31b.

Producer, consumer, authority, and loss audit#

The authenticated /v1/me/privacy/receipts route projects a member-facing, reverse-chronological feed and standing assurance posture through @oshun/privacy. The former input plane was one module-global PrivacyRecordsStore, hydrated from the shared admin snapshot table and described as durable consent, DSAR, deletion, export, operator-access, retention-purge, current-consent, and audit-coverage state.

Repository-wide symbol, route, producer, consumer, export/erasure, and composition tracing found:

  • only privacy-receipts.test.ts called any of the seven record* methods or setAuditCoverage;
  • no consent workflow, DSAR machine, deletion executor, export producer, operator-access audit, retention worker, event consumer, or scheduled projector wrote the snapshot key;
  • the receipts route was the only production reader;
  • no first-party Oshun web, mobile, or admin client called the route; and
  • the production process supplied no canonical projection binding.

Consequently, production could only hydrate orphan/legacy rows that current repository behavior could never create or update. Those rows could falsely claim a consent transition, statutory request status, completed deletion or export, operator access, purge, active consent, or complete audit coverage. Their loss cannot remove any canonical consent, DSAR, erasure, export, access-audit, retention, authority, evidence, approval, effect, lineage, or learning state because no production path owns any of those through this shadow seam.

Fail-closed atomic production composition#

The production singleton, snapshot schemas/key binding, serialization-specific hydration, and fire-and-forget write path are removed. createApp and the route now expose one async-capable PrivacyReceiptsSource. One source call returns the receipt feed inputs and standing-assurance inputs atomically, preventing an attested auditCoverageComplete value from being combined with a different operator-access snapshot.

Production intentionally binds no source. Authentication, numeric-limit validation, and cursor syntax validation all complete first. A valid request then returns:

json
{
  "ok": false,
  "reason": "privacy_receipts_source_not_configured"
}

with HTTP 503. An empty 200 response was rejected because it would imply that the member has no consent, DSAR, deletion, export, access, or purge records; even a coverage-unknown assurance posture cannot make that receipt-history claim truthful without a source. Bound projections retain the existing exact feed, stable cursor, typed refusal, member-isolation, and assurance contract. The mutable PrivacyRecordsStore remains only as an explicitly constructed synthetic test/development adapter. Every rich route test uses an awaited async wrapper, proving deploy adapters may perform real I/O.

The prior privacy-records snapshot row, if present in an existing database, is intentionally ignored rather than deleted: it is not authoritative, and deleting deployment data was unnecessary to close the code path.

Verification#

text
pnpm exec vitest run \
  --config apps/oshun/bff/vitest.config.ts \
  apps/oshun/bff/src/routes/privacy-receipts.test.ts \
  apps/oshun/bff/src/__tests__/v1-feature-pack-boot.test.ts
  2 files passed; 10/10 tests passed

NX_DAEMON=false pnpm exec eslint <5 changed BFF source/test files> \
  --no-warn-ignored --no-cache
pnpm exec prettier --check <5 changed BFF files>
git diff --check
  passed

NODE_OPTIONS='--max-old-space-size=8192' \
  node tools/typecheck/ratchet.mjs \
    --app apps/oshun/bff \
    --tsconfig tsconfig.typecheck.json
  only the same five current-main errors outside the affected files:
  admin-isis-cli-surface-route.test.ts:58
  autonomous-content-metrics-store.ts:89
  agentic/autonomy-route.test.ts:200
  agentic/autonomy-route.test.ts:491
  tenant-content-graph-store.spec.ts:88

# the affected pre-commit sweep additionally reaches the unrelated
# libs/shared/tracing/src/genai.ts:365 V7-union mismatch; the source commit used
# the hook's documented SKIP_TYPECHECK=1 path after the focused ratchet

node apps/oshun/bff/scripts/build.mjs
node --check apps/oshun/bff/dist/server.js

# empty disposable PostgreSQL catalog
pnpm --dir libs/oshun/persistence exec prisma migrate deploy \
  --config prisma.config.ts
  all 32 migrations applied

OSHUN_ADMIN_DATABASE_URL=<fresh-database> \
OSHUN_V1_DATABASE_URL=<fresh-database> \
OSHUN_REDIS_URL=<local-redis> \
  node apps/oshun/bff/scripts/verify-production-artifact.mjs
  Production artifact smoke check passed.

The resource gate reported 15 GiB RAM, 31 GiB swap, 14 GiB free disk, and no competing broad build/test gate. The type ratchet was supervised at 30-second intervals and remained above the configured safety thresholds.

The source push was rejected because origin/main advanced through one non-overlapping Yemaya evidence change. The source commit rebased cleanly. No BFF source, dependency, test, build, migration, or runtime-smoke input changed; the five affected BFF files and verified artifact were byte-identical after the rebase. The disposable verification catalog was removed.

The exact published artifact is:

text
apps/oshun/bff/dist/server.js
  36,569,712 bytes
  sha256 3fc5cede080189623647e4c02ae2836e01cd18a03b6dd5359b7a46f96570a953

apps/oshun/bff/dist/server.js.map
  85,713,576 bytes
  sha256 b66fba9113744b8fca8d61e490bb116df410e09fdac2f726cf8924d06f297250

Artifact identities#

Artifact SHA-256
apps/oshun/bff/src/delight/privacy-records-store.ts c27cd345e7a8c8222f1ceb011951bc61bdc7797a97f055bb9fb50b33291ece0c
apps/oshun/bff/src/routes/privacy-receipts.ts a6976e85192bdd4452abaf064bd457963e42fcacc4c5ac3283372a915be863ba
apps/oshun/bff/src/routes/privacy-receipts.test.ts c76364297d31787555e7acce676b147ba4c5423519e9b3f22ba84d07136ab608
apps/oshun/bff/src/app.ts 9944d0f840c644781d213889634ebab8f9a9f203c3968e07d22b73fdcf34f10b
apps/oshun/bff/src/server.ts d1318d6ccdf30f3964bb65604c5fc76ae1a72644988efd2072d4336749845068
apps/oshun/bff/dist/server.js 3fc5cede080189623647e4c02ae2836e01cd18a03b6dd5359b7a46f96570a953

No customer/admin web UI, mobile flow, public schema, database schema, provider/model call, or Unreal asset changed. No first-party UI consumes this route. Frontend-skill, Playwright, mobile, schema-generation, live-provider, and Unreal automation were therefore inapplicable.

This closes the orphan privacy-receipts snapshot as a false durable member-history and assurance claim and proves its production loss harmless. It does not claim a live cross-plane receipts projector. A future binding must join canonical acknowledged consent, DSAR, deletion, export, access-audit, retention, and current-consent state with exact-subject privacy/erasure, retention, freshness, source-version, and completeness evidence. V1-002's parent all-store inventory remains open.

Studio workspace-telemetry shadow-buffer retirement — 2026-07-26#

Source implementation and published origin/main commit: 81969832b2d2421779e501172d6a0159610c701d.

Producer, consumer, durability, and loss audit#

The Studio Hathor/Aja workspace telemetry helper emits studio_workspace_mounted, studio_workspace_unmounted, and studio_workspace_interaction. It previously sent a bespoke payload to POST /v1/studio/telemetry/workspace-events. That route returned 200 after appending records to one module-global, 10,000-record array.

Repository-wide tracing found:

  • only studio-workspace-telemetry-route.test.ts read the buffer snapshot, installed its optional forwarder, or reset it;
  • production never installed a collector/warehouse forwarder;
  • synchronous forwarder exceptions and asynchronous rejections were intentionally swallowed while the route still returned success;
  • accepted records disappeared on restart and could diverge across replicas;
  • the bespoke store had no DSAR, erasure, retention, or recovery participation; and
  • the repository already had one acknowledged, restart-safe authenticated analytics-event owner with bounded seven-day retention and signed deletion fanout.

The buffer was therefore neither an intentional loss-safe cache nor a durable authority. Its response falsely described volatile acceptance as successful ingest, and duplicating the existing analytics persistence plane would have created another ownership boundary.

The audit also found that the web helper's source documentation named Hathor as a mounted producer, but StudioHathorEconomyModelingWorkspace did not call the helper. Aja did. The missing Hathor boundary was corrected rather than preserving an inaccurate producer claim.

Canonical transport and compatibility boundary#

The custom web queue/fetch implementation is removed. The Studio helper now uses createSharedAnalyticsSinks(), the same authenticated, buffered, retry-capable transport as other web analytics, and sends canonical event envelopes to /v1/analytics/events.

The old endpoint remains mounted for deployed-client compatibility. It is now a pure validation/translation adapter:

  • authentication and all existing whole-batch validation happen first;
  • each valid legacy event becomes a canonical oshun/web analytics envelope;
  • ownership comes only from the verified server-side auth context;
  • the adapter awaits AnalyticsEventsStore.ingest;
  • success is 202 only after the canonical snapshot commits; and
  • a required or failed durable write returns 503 analytics_persistence_unavailable without making candidate events readable.

The module-global StudioWorkspaceTelemetrySink, capped array, snapshot/reset API, mutable forwarder, and swallowed failure paths are deleted. workspace-telemetry-sink.ts now contains validation only and owns no state. The empty batch remains a truthful 200 { ok: true, accepted: 0 } because it does not claim a write.

The existing canonical analytics proofs apply without duplication: restart hydration and legacy normalization, ordered concurrent writes, response-after- persistence acknowledgement, failed-write rollback, exact-subject deletion, adjacent-owner isolation, required-sink refusal, authenticated attribution, buffered retry token refresh, signed deletion fanout, and seven-day/5,000-event bounding.

The Hathor workspace now emits its documented mount/unmount pair. This is an instrumentation-only customer-web change: no layout, copy, styling, motion, focus behavior, accessibility semantics, or visible interaction changed. The mandatory frontend skill guided the decision to keep the established utility surface unchanged rather than introduce visual work unrelated to the state closure.

Verification#

text
pnpm exec vitest run \
  --config apps/oshun/bff/vitest.config.ts \
  apps/oshun/bff/src/__tests__/studio-workspace-telemetry-route.test.ts \
  apps/oshun/bff/src/analytics/events-ingest-store.test.ts \
  apps/oshun/bff/src/analytics/events-ingest.test.ts
  3 files passed; 23/23 tests passed

# cwd apps/oshun/web
pnpm exec vitest run --config vitest.config.ts \
  src/analytics/studioWorkspaceMountTelemetry.test.ts \
  src/components/__tests__/StudioHathorEconomyModelingWorkspace.test.tsx \
  src/components/__tests__/StudioHathorEconomyModelingWorkspace.integration.test.tsx
  3 files passed; 11/11 tests passed

pnpm exec vitest run \
  --config libs/oshun/analytics/vitest.config.ts \
  libs/oshun/analytics/src/__tests__/buffered-sink.test.ts
  1 file passed; 13/13 tests passed

# cwd apps/oshun/web; retry disabled
E2E_SKIP_STUDY=1 pnpm exec playwright test \
  e2e/studio-hathor-economy-modeling.spec.ts \
  --grep 'workspace mount uses the canonical analytics transport' \
  --project=chromium --workers=1 --retries=0
  1/1 passed

NX_DAEMON=false pnpm exec eslint <8 changed source/test files> \
  --no-warn-ignored --no-cache
pnpm exec prettier --check <8 changed source/test files>
git diff --check
  passed

NODE_OPTIONS='--max-old-space-size=8192' \
  node tools/typecheck/ratchet.mjs \
    --app apps/oshun/web \
    --tsconfig tsconfig.typecheck.json
  passed with no new errors

NODE_OPTIONS='--max-old-space-size=8192' \
  node tools/typecheck/ratchet.mjs \
    --app apps/oshun/bff \
    --tsconfig tsconfig.typecheck.json
  only the same five current-main errors outside the affected files:
  admin-isis-cli-surface-route.test.ts:58
  autonomous-content-metrics-store.ts:89
  agentic/autonomy-route.test.ts:200
  agentic/autonomy-route.test.ts:491
  tenant-content-graph-store.spec.ts:88

# the affected pre-commit sweep additionally reaches the unrelated
# libs/shared/tracing/src/genai.ts:365 V7-union mismatch; the source commit used
# the hook's documented SKIP_TYPECHECK=1 path after both focused ratchets

node apps/oshun/bff/scripts/build.mjs
node --check apps/oshun/bff/dist/server.js

# empty disposable PostgreSQL catalog
pnpm --dir libs/oshun/persistence exec prisma migrate deploy \
  --config prisma.config.ts
  all 32 migrations applied

OSHUN_ADMIN_DATABASE_URL=<fresh-database> \
OSHUN_V1_DATABASE_URL=<fresh-database> \
OSHUN_REDIS_URL=<local-redis> \
  node apps/oshun/bff/scripts/verify-production-artifact.mjs
  Production artifact smoke check passed.

All 47 focused tests, scoped static checks, both type ratchets, direct build, syntax check, fresh 32-migration catalog, production-artifact smoke, and the no-retry Chromium journey were repeated after rebasing over non-overlapping Yemaya source. Both disposable verification catalogs were removed.

The first browser-test draft targeted the documented Hathor producer and correctly found no event. Source inspection identified the missing effect; the component and focused test were corrected. The first cold Next dev-server run then exceeded the repository's 60-second global test timeout during lazy compilation, while its automatic retry passed the actual assertion. The focused test now allows 180 seconds for one-time route compilation but retains a 15-second analytics-flush assertion. Two subsequent runs with retries disabled passed in 21.6 and 25.6 seconds respectively.

The host gate reported 15 GiB RAM, 31 GiB swap, 14 GiB free disk, and no competing broad verification gate. Ratchets were sequential and supervised at 30-second intervals; available memory stayed above the stop threshold. The web production build was not run because this host is below the repository's 32 GiB hard gate and no approval was provided.

The exact published artifact is:

text
apps/oshun/bff/dist/server.js
  36,568,601 bytes
  sha256 c4406e44d87277c7b760ce3ab2218e93fb75df08a1926c960fc687dda62e7fab

apps/oshun/bff/dist/server.js.map
  85,713,366 bytes
  sha256 04952ced48c494c8cb0a0a78e36cd486b09e782fe6b914eec359de6401a134df

Artifact identities#

Artifact SHA-256
apps/oshun/bff/src/studio/workspace-telemetry-sink.ts 1bf8f185cebe83af7f22ff03eb07c4fcc4d6c19d036a61f68474406e03def9d9
apps/oshun/bff/src/routes/studio-workspace-telemetry.ts 5f838b04ad10075348b4bc98a452b088f551c087e5bec91e2c6a00a9aa4a4ae0
apps/oshun/bff/src/__tests__/studio-workspace-telemetry-route.test.ts 5fb0acd32d316241f67d39848aaa64d74254eb6511a20486fab040d4aebe8396
apps/oshun/web/src/analytics/studioWorkspaceMountTelemetry.ts ef0f7907425ae34fe15f60755eff7638fce4a082fe76ea56de3d9433e9a2d08b
apps/oshun/web/src/analytics/studioWorkspaceMountTelemetry.test.ts 99b3ab385e705735fb6bb391f8b8074437117204b79cd071151824a05f9d3ad7
apps/oshun/web/src/components/studio/StudioHathorEconomyModelingWorkspace.tsx c3512a125a98e8280a4548b6a9ea9e2f55fa02c0fe3438f822bcd186e424bab9
apps/oshun/web/src/components/__tests__/StudioHathorEconomyModelingWorkspace.test.tsx 4b42530e4936ecb924cb5407360ecbd987bb39e3f48548dabdc7dfdce8e89510
apps/oshun/web/e2e/studio-hathor-economy-modeling.spec.ts 99e7bb93f1974720534d2c79d2237fb07a06cbe146818cade0b9773c3caf0f0a
apps/oshun/bff/dist/server.js c4406e44d87277c7b760ce3ab2218e93fb75df08a1926c960fc687dda62e7fab

No mobile flow, public contract/schema, database schema, external provider/model call, or Unreal asset changed. Mobile, schema generation, provider/model, and Unreal automation were inapplicable.

This closes the Studio workspace-telemetry shadow singleton and routes its real producer through the already durable, privacy-connected analytics authority. It does not claim delivery to an external warehouse beyond the canonical BFF snapshot boundary. V1-002's parent all-store inventory remains open.

2026-07-26 — Telegram authentication replay and webhook-rate authority#

Source commit 58f74752b0a6dd0b4d602b3ef92211dcca88739a removes the two process-local Telegram security authorities found by the expanded operational state scan. Authentication replay claims are now atomic Redis SET PX NX claims shared across BFF replicas and restarts. Webhook admission now uses one atomic Redis INCR/EXPIRE script, so alternating requests across replicas consume the same 12-per-60-second identity window. Both Redis key families hash Telegram query, user, and chat identifiers rather than storing those identifiers in key names.

The deployable binds both authorities to the already shared idempotency Redis client. Without shared Redis, production leaves the routes registered but fails verified Mini App/Login Widget authentication and webhook admission closed with 503 telegram_security_state_unavailable; it does not fall back to a restart-resettable map. Development and tests retain explicit in-memory adapters. Signature verification precedes the atomic replay claim, while webhook rate admission now precedes Telegram-link mutation and bot effects. Redis errors, malformed counters, invalid TTLs, and missing production bindings cannot acknowledge authentication or a webhook effect.

Verification:

text
pnpm exec vitest run \
  apps/oshun/bff/src/telegram/security-state.spec.ts \
  apps/oshun/bff/src/telegram/webhook.test.ts \
  apps/oshun/bff/src/__tests__/telegram-route.test.ts
  3 files passed; 22/22 tests passed

pnpm exec vitest run \
  libs/oshun/messaging-channels/src/telegram-messaging.test.ts
  1 file passed; 17/17 tests passed

pnpm exec tsc --noEmit
  # cwd: libs/oshun/messaging-channels
  passed

NODE_OPTIONS='--max-old-space-size=8192' \
  node tools/typecheck/ratchet.mjs \
    --app apps/oshun/bff \
    --tsconfig tsconfig.typecheck.json
  passed within the same five unrelated current-main diagnostics

NX_DAEMON=false pnpm exec eslint <11 changed source/test files> \
  --no-warn-ignored --no-cache
pnpm exec prettier --check <11 changed source/test files>
git diff --check
  passed

node apps/oshun/bff/scripts/build.mjs
node --check apps/oshun/bff/dist/server.js

# empty disposable PostgreSQL catalog
pnpm --dir libs/oshun/persistence exec prisma migrate deploy \
  --config prisma.config.ts
  all 32 migrations applied

OSHUN_ADMIN_DATABASE_URL=<fresh-database> \
OSHUN_V1_DATABASE_URL=<fresh-database> \
OSHUN_REDIS_URL=<local-redis> \
  node apps/oshun/bff/scripts/verify-production-artifact.mjs
  Production artifact smoke check passed.

The focused suite passed 39/39. It proves cross-replica replay rejection, cross-replica rate-window accumulation and thirteenth-update blocking, hashed identifier keys, fail-closed Redis/malformed-state behavior, route-level 503s when production security state is unbound, and continued synchronous-adapter compatibility. The disposable database was removed after the smoke. The host gate reported 15 GiB RAM, 31 GiB swap, 14 GiB free disk, and a concurrent BFF type compiler; the artifact build was deferred until that compiler exited and available memory recovered to 13 GiB.

The exact verified artifact is:

text
apps/oshun/bff/dist/server.js
  36,573,298 bytes
  sha256 e4622b2afbcece1047aa4634aee17f3270fa5f0f4c3efb98266fa047c34cab68

apps/oshun/bff/dist/server.js.map
  85,723,613 bytes
  sha256 c9a3a597f143e2dfbd8d4031257c3c58f9e98681aaf8191abd81735d92340ea6

Artifact identities:

Artifact SHA-256
apps/oshun/bff/src/telegram/security-state.ts 171fa8cc0ae6609f9a40cbe0ce112646e18c9565f586b49ea098a740063bd2af
apps/oshun/bff/src/telegram/security-state.spec.ts 86f892a45a402439a4d73f0697175f9189818c4b59d84bd32ea166ccfbdc002f
apps/oshun/bff/dist/server.js e4622b2afbcece1047aa4634aee17f3270fa5f0f4c3efb98266fa047c34cab68

No public schema, database schema, web/mobile UI, model/provider call, media pipeline, or Unreal asset changed, so schema generation, UI automation, provider/model evaluation, media evaluation, mobile automation, and Unreal automation were inapplicable. This closes the two Telegram process-local security seams found by the expanded scan; V1-002's parent all-store inventory remains open pending the checked-in repository-wide disposition registry and drift gate.

2026-07-26 — Machine-enforced operational-state inventory#

Source commit 41d31b78c1ab181def5f2ff6debd72c5e3c455ff replaces the prose-only store audit with an AST-based detector, checked-in disposition registry, and drift test. The detector scans non-test BFF modules for module-scope constructed owners, operational factories, mutable collections, explicit route caches, and every module-scope mutable binding. It refuses new, removed, moved, or undispositioned candidates and requires a reviewed disposition, rationale, and evidence reference for each entry.

The first reviewed snapshot contains 238 candidates: 110 durable authorities, 60 coupled projections inside those durable owners, 43 loss-safe ephemeral bindings, 10 source-controlled stateless catalogs, nine deliberately empty production projections, and six explicit test/development adapters. The audit immediately found three previously missed shadows. Isis generation dispatch and Psyche embodiment sessions no longer default to module-global simulated stores in production; their valid operational routes return 503 isis_generation_authority_unavailable or 503 psyche_embodiment_authority_unavailable until an owning adapter is bound. Customer message-delivery transparency similarly no longer reads a test-seeded global map in production and returns 503 message_delivery_source_unavailable until the delivery projection is bound.

Focused route, adapter, transparency, and inventory coverage passed 36/36 after remote integration. Scoped lint, formatting, syntax, and inventory drift checks passed. The BFF ratchet reported only the same five unrelated current-main diagnostics. The exact artifact applied all 32 migrations to an empty PostgreSQL catalog and passed PostgreSQL/Redis startup smoke; the disposable catalog was removed.

text
apps/oshun/bff/dist/server.js
  36,575,588 bytes
  sha256 83b747f2f195f6e390c1a1e6e6f0c3686e121f5647630f5912be85167a934a5c

apps/oshun/bff/dist/server.js.map
  85,729,143 bytes
  sha256 f1cd44f16b73d75282b8c55af055cb4683b4866e40d4a646cac6e88769637718

No public schema, database schema, UI, provider/model call, media pipeline, mobile flow, or Unreal asset changed. This establishes a repeatable inventory gate, but the first pass did not itself prove every disposition correct.

2026-07-26 — Shell operational-authority correction#

Follow-up source commit ea0bd4e6e18f226641191b684eb0305089517ae5 demonstrates why the registry remains reviewable rather than self-certifying. Manual consumer tracing found four entries incorrectly classified as ephemeral: the achievements, routines, wearable, and desktop shell engines retain and acknowledge unlocks, partnerships, challenge participation, authored routines, active executions, completion history, downstream step effects, devices, push tokens, preferences, reminders, summaries, windows, notifications, and event state.

Production no longer constructs any of those process-local engines by default. App composition exposes four explicit owner seams. Without an injected owner, operational routes fail closed with the domain-specific *_authority_not_configured response; routine and wearable authentication still runs first. Pure source-controlled reads remain available: routine templates, achievement/challenge definitions, desktop deep-link construction, and widget-type definitions. The corrected registry now contains 110 durable authorities, 60 coupled durable projections, 39 loss-safe ephemeral bindings, 10 stateless catalogs, 13 unbound production projections, and six test/development adapters.

Focused production-boundary, achievement, desktop, routine-contract, and inventory coverage passed 18/18. After each non-overlapping remote integration, the inventory test and affected boundary suite passed again; scoped lint and formatting passed. The BFF ratchet returned to only the same five unrelated current-main diagnostics. A rebuilt artifact applied all 32 migrations to a fresh PostgreSQL catalog and passed PostgreSQL/Redis production startup smoke; the disposable catalog was removed.

text
apps/oshun/bff/dist/server.js
  36,580,071 bytes
  sha256 6c169e58b2b34b19293e32f194d20273b098b30770a12f032762ccfe4fbb6717

apps/oshun/bff/dist/server.js.map
  85,738,667 bytes
  sha256 d5f7d0115323225498dd5ccae09965093ce63c78ed381c0e87ab2f4d1ad5697f

No schema, UI, model/provider, media, mobile, or Unreal surface changed. These four false authorities are now honest unbound capabilities, not completed live features. V1-002 remains open while the remaining registry dispositions and cross-store privacy/deletion/recovery proofs are reviewed.

2026-07-26 — Nyx duplicate event-action projection correction#

Source commit 286f70747dfdd1a36d518f2ab308937ff806ee46 corrects another registry review error. The legacy nyxEventActionStateStore had been labeled a durable authority even though it owns only a capped process-local map, has no sink or hydration seam, and duplicates saved/followed/reminder information already governed by the durable NyxMemberStateStore.

Production no longer binds that compatibility singleton. The authenticated aggregate read and mutation routes preserve authentication, Nyx scope, and event-id checks, then return 503 nyx_event_action_authority_not_configured until a canonical owning projection is explicitly injected. Development and direct tests retain the legacy adapter. This does not modify or weaken the existing durable Nyx member authority, exact-subject export, signed erasure, resurrection fence, or recovery behavior.

The corrected 238-entry registry now reports 109 durable authorities, 60 durable coupled projections, 39 loss-safe ephemeral bindings, 10 stateless catalogs, 13 unbound production projections, and seven test/development adapters. The event-action route/store, durable Nyx owner, guarded Nyx routes, and inventory suites passed 21/21. Scoped lint, formatting, inventory drift, and diff checks passed. The BFF ratchet contained only the same five unrelated current-main diagnostics. The rebuilt artifact applied all 32 migrations and passed PostgreSQL/Redis production startup smoke; the disposable database was removed.

text
apps/oshun/bff/dist/server.js
  36,580,853 bytes
  sha256 2fda357c3f09d1640326b2b3bba41e83d560e1cdf7992dbc66ea3001af49f540

apps/oshun/bff/dist/server.js.map
  85,740,612 bytes
  sha256 5aa2c016e34313680ba68ed86414cfba5034caa8bb837a12aa1aff4bf3d50151

No schema, UI, provider/model, media, mobile, or Unreal surface changed. This retires a duplicate volatile projection; it does not claim that a canonical aggregate projector has been implemented.

2026-07-26 — Mutation and startup-composition inventory expansion#

Source commit 80470f8f1ff49ee4738fdd9a389b7cb21c9ad000 expands collection detection beyond lower-camel and explicit cache names. Module-scope uppercase or otherwise nonstandard arrays, objects, maps, sets, and weak collections now enter the registry when the AST observes add, clear, delete, pop, push, set, shift, splice, or unshift. This discovered ADMIN_MUTATION_CHECKPOINTS, a request-lifetime WeakMap used only to restore the prior durable admin snapshot when the matching mutation fails. Its loss cannot acknowledge a mutation, suppress persistence, or delete committed authority. Inventory and admin durability coverage passed 12/12; formatting, lint, syntax, and drift checks passed.

Review then found that module-scope detection still omitted authorities constructed inside deployable startup. Source commit 1ff95429d25a551ce48ebbd703e56c7f63a7567b adds a server.ts main composition scan and a regression test that requires the Redis idempotency, SSO/LTI login, Telegram replay/rate, durable admin audit, Tara workbench, and Prisma Ori owners to remain inventoried. The scan also dispositions the Redis client, abuse/render/generation gates, admin snapshot/store projections, rail stores, Ori consent/service composition, configured asset-store client, and stateless tool/evidence/capability registries.

The current registry contains 263 reviewed candidates:

Disposition Count
Durable authority 123
Durable coupled projection 62
Ephemeral and loss-safe 44
Stateless catalog or policy 14
Unbound production projection 13
Test/development adapter 7

Verification:

text
node apps/oshun/bff/scripts/operational-state-inventory.mjs
  Operational-state inventory passed for 263 candidates.

pnpm --dir apps/oshun/bff exec vitest run \
  src/__tests__/operational-state-inventory.spec.ts
  2/2 passed after integration with current origin/main

ephemeral-loss representative suite
  11 files; 67 passed, 1 provider integration explicitly skipped

deletion-worker and V1 eraser suite
  2 files; 17/17 passed

live Redis deletion/privacy/export integration suite
  3 files; 59/59 passed

release gate and OpenAPI coverage/runtime-drift suite
  3 files; 17/17 passed

BFF type ratchet
  exactly the same five unrelated current-main diagnostics

The Redis integration emitted existing missing-source-map warnings from built shared-library JavaScript; all tests passed. No production runtime, schema, UI, model/provider call, media pipeline, mobile flow, or Unreal asset changed in the detector expansion, so an artifact rebuild and those domain-specific gates were inapplicable.

This evidence does not close the parent checkbox. The registry now covers module-scope state and deployable main composition, but factory-local and route-composition ownership roots outside main still require the same machine-enforced discovery, disposition, and representative loss/recovery review.

2026-07-26 — Calendar sync false-authority retirement#

The nested-construction review found that createCalendarRuntimeFromEnv always installed MemoryCalendarSyncStore, including in production. That store retains imported calendar events, reconciliation watermarks, and import-run evidence. Successful admin import/export responses therefore acknowledged operational state that a deploy or crash erased.

Source commit b00b985cc9621a4d3512054e5e411394b82cff4d makes the ownership boundary explicit. createCalendarRuntimeFromEnv accepts an injected CalendarSyncStore; createApp exposes the corresponding runtime seam. Production runtimes without an injected owner still expose authenticated connector visibility, but import and export authenticate and enforce admin scope first, then return:

json
{
  "error": "calendar_sync_authority_not_configured",
  "reason": "durable_calendar_sync_store_required"
}

The memory store remains available to direct tests and non-production development. No durable calendar-sync implementation is fabricated or claimed; the capability is honestly unbound until deployable composition supplies one.

Verification:

text
calendar-sync-route.test.ts + calendar-two-way-flow.test.ts
  15/15 passed before integration
  15/15 passed after each of two origin/main integrations

operational-state-inventory.mjs
  263-candidate published inventory passed after each integration

scoped Prettier, ESLint, and git diff checks
  passed

BFF type ratchet
  exactly the same five unrelated current-main diagnostics

apps/oshun/bff/dist/server.js
  36,581,478 bytes
  sha256 73314cea8f624cecc018f5d82fff45da2b397685a1f5516f3c5b17e35e0932df

apps/oshun/bff/dist/server.js.map
  85,741,983 bytes
  sha256 4b0c4bb16b76b2a54dcc1f07fbe76892dca0ecbfe6ab1061d534538871cc995a

fresh PostgreSQL catalog
  all 32 migrations applied

PostgreSQL/Redis production artifact smoke
  passed; disposable database dropped

No public schema, database schema, UI, model/provider call, media pipeline, mobile flow, or Unreal asset changed. This retires one factory-local false authority; the parent all-store box remains open while the remaining nested construction candidates are dispositioned and audited.

2026-07-26 — Nested store review and Aja moderation retirement#

Source commit c5277d7c0b47424270e70497659e3fabaca4e992 extends the AST inventory through factory bodies, class fallbacks, hydration candidates, and route-local composition. It detects store-, repository-, registry-, catalog-, ledger-, queue-, limiter-, gate-, state-, and authority-shaped constructors and factories while leaving module-scope and main startup expressions to their existing stable detectors. Regression assertions require both a development-only in-memory generation budget store and an Isis repository fallback to remain visible.

The 282 additional candidates were individually dispositioned by ownership class. Durable factory returns remain authorities; repository/cache objects inside hydrated owners are coupled projections; snapshot drafts and request-local builders are loss-safe; adapter registries are stateless; production-unavailable memory fallbacks are test/development-only. The resulting registry contains:

Disposition Count
Durable authority 146
Durable coupled projection 151
Ephemeral and loss-safe 88
Stateless catalog or adapter 122
Test/development adapter 25
Unbound production projection 13
Total 545

The scan found one further production false authority. The Aja content- moderation route created a fresh in-memory BanManager for every BFF app and acknowledged issue, check, repeat-offense, scoped-ban, and revocation state that could not survive restart. Source commit 07762a54c5440a3fa69055754f6279a107b4c4ab removes that implicit production owner. The source-controlled ban-type/category catalog stays live; valid mutable operations now authenticate and validate first, then return:

json
{
  "ok": false,
  "reason": "aja_content_moderation_authority_not_configured"
}

Direct tests inject createModerationStore() explicitly and retain the complete ban lifecycle. The separate generic moderation queue was already correctly injection-only and fail-closed; its internal queues are classified as test/development adapter state.

Verification:

text
admin-aja-content-moderation-route.test.ts +
admin-moderation-route.test.ts
  21/21 passed

post-integration admin-aja-content-moderation-route.test.ts
  8/8 passed

operational-state-inventory.spec.ts
  3/3 passed after integration
  Operational-state inventory passed for 545 candidates.

scoped Prettier, ESLint, syntax, and diff checks
  passed

BFF type ratchet
  exactly the same five unrelated current-main diagnostics

apps/oshun/bff/dist/server.js
  36,577,566 bytes
  sha256 e27e40dd4b54716d7529c46b79bc47f1fdf5aa32149038ff67b2657d0a5432e6

apps/oshun/bff/dist/server.js.map
  85,714,714 bytes
  sha256 3830dc6a8f45b00ec108a85bf3ea0426f07ce298fb80217454ff97e9bb4af6a3

fresh PostgreSQL catalog
  all 32 migrations applied

PostgreSQL/Redis production artifact smoke
  passed; disposable database dropped

No public schema, database schema, UI, model/provider call, media pipeline, mobile flow, or Unreal asset changed. This completes the store-shaped nested construction review. It does not yet close the parent box: stateful owner families whose names end in manager, engine, coordinator, tracker, service, or similar terms still need the same machine-enforced discovery and disposition pass.

2026-07-26 — Rail TV false-authority retirement#

Source commit 136c89c155a352b3065c21896cb70a997f7e9cba removes the deployable's implicit TvWatchPartyCoordinator. That coordinator owned watch-party session creation, phone pairing tokens, session snapshots, playback commands, and the session boundary used by live chat, but retained all of that state in one BFF process. A restart erased acknowledged sessions and separate replicas could disagree.

Production now requires an explicitly injected owning coordinator on every state-bearing Rail TV route. Authentication and applicable request parsing remain ordered before the availability boundary. A valid unbound request returns:

json
{
  "error": "tv_watch_party_authority_not_configured",
  "reason": "durable_tv_watch_party_coordinator_required"
}

Direct tests inject the coordinator and preserve the full create, pair, poll, command, chat-join, chat-send, and chat-history behavior. No shared or durable watch-party implementation is fabricated or claimed.

Verification:

text
v10-rail-tv.spec.ts
  4/4 passed before integration
  4/4 passed after integration

operational-state-inventory.mjs
  published 545-candidate registry passed after integration

scoped Prettier, ESLint, and git diff checks
  passed

BFF type ratchet
  exactly the same five unrelated current-main diagnostics

apps/oshun/bff/dist/server.js
  36,569,613 bytes
  sha256 755a266d3a64bf1bfa533ccbf48add37a51ad56dece23eabebbd7b472514c575

apps/oshun/bff/dist/server.js.map
  85,710,509 bytes
  sha256 5a8b7143dab3154b41f775542eb28d0ceead5ab3e6ad2f078c4d708c52a70e1f

fresh PostgreSQL catalog
  all 32 migrations applied

PostgreSQL/Redis production artifact smoke
  passed at the integrated source tip; disposable database dropped

No public or database schema, UI, model/provider call, media pipeline, mobile flow, or Unreal asset changed.

2026-07-26 — Stateful owner-family inventory expansion#

Source commit ce41cd5b03170adabb973f81f77921d98d049684 extends the nested construction detector beyond store-shaped names. Constructors and create/build/make/resolve factories ending in manager, engine, coordinator, tracker, service, session, framework, governor, learner, sampler, runtime, or plane now enter the checked-in registry. Regression assertions pin an Aja ban manager and the autonomy preference learner so this vocabulary cannot silently disappear from coverage.

The pass discovered 89 candidates before the Rail TV correction and 88 after it. Every remaining candidate was reviewed. Durable and coupled entries include the file-backed Ori agent runtime; autonomy learner, sampler, governor, usage accounting, and plane views restored through the encrypted durable plane; the academic-integrity replay runtime; account-protection analysis coupled to its repository; the group-session commit candidate; and the LMS connector framework coupled to its snapshot-backed admin owner. Request-local response projections, provider clients, model runtimes, checkout sessions, health hysteresis, and SCORM commit candidates are loss-safe. Deterministic Hathor/Yemaya simulations, daypart evaluators, and judge/assistant engines retain no acknowledged operational authority. Aja, Psyche, calendar, and generic moderation memory managers remain explicit test/development adapters, while achievements, desktop, routines, and wearable engines remain unbound and fail closed in production.

The reviewed registry now contains:

Disposition Count
Durable authority 148
Durable coupled projection 166
Ephemeral and loss-safe 125
Stateless catalog or engine 138
Test/development adapter 39
Unbound production projection 17
Total 633

Verification:

text
node apps/oshun/bff/scripts/operational-state-inventory.mjs
  Operational-state inventory passed for 633 candidates.

operational-state-inventory.spec.ts
  3/3 passed before integration
  3/3 passed after integration

representative owner/recovery/loss-boundary suite
  11 files; 86/86 passed
  autonomy plane, account protection, academic integrity, group sessions,
  LMS connector admin, Ori runtime, health routes, real-time music runtime,
  Psyche production boundary, and Aja content-security/retention

scoped Prettier, ESLint, syntax, drift, and diff checks
  passed

BFF type ratchet
  exactly the same five unrelated current-main diagnostics

apps/oshun/bff/dist/server.js
  36,569,613 bytes
  sha256 755a266d3a64bf1bfa533ccbf48add37a51ad56dece23eabebbd7b472514c575

apps/oshun/bff/dist/server.js.map
  85,710,509 bytes
  sha256 5a8b7143dab3154b41f775542eb28d0ceead5ab3e6ad2f078c4d708c52a70e1f

fresh PostgreSQL catalog
  all 32 migrations applied

PostgreSQL/Redis production artifact smoke
  passed; disposable database dropped

No production runtime changes are introduced by the detector expansion itself. No public or database schema, UI, provider/model call, media pipeline, mobile flow, or Unreal asset changed. The parent all-store checkbox remains open: additional construction vocabularies and anonymous/local collection roots still require the same machine-enforced discovery, and existing deletion, privacy, retention, recovery, and loss-proof requirements continue to apply.

2026-07-26 — Persistence and control-family inventory expansion#

Source commit e1cef3526a13e585726c092ddc547b3fef44160b extends the nested construction detector through sink, breaker, controller, emitter, collector, accountant, director, broker, solver, evaluator, blackboard, aggregator, planner, bridge, processor, analyzer, narrator, reader, resolver, source, and policy owner vocabularies. Regression assertions pin a durable achievement snapshot sink, the domain-service circuit breaker, and a per-run capability broker.

The pass discovered and reviewed 161 candidates:

  • 101 createSnapshotSink constructions plus the startup durable audit sink are write-through views coupled to their owning durable authorities.
  • Autonomy usage accounting and the creative director are serialized through the protected autonomy-plane snapshot.
  • The academic-integrity bridge/gradebook emitters and fiat settlement processor/entitlement emitter publish through their enclosing durable stores.
  • Domain-service circuit breakers, request abort controllers, metrics and health collectors, per-run low/medium-risk capability brokers, provider sources/resolvers, and the Ori narrator are loss-safe request/rebind state.
  • Retention/share/ring policies, simulation solvers/controllers/blackboards, interpolation/upscaling planners, and adapter bridges are deterministic and retain no acknowledged mutable authority.
  • Aja's manager-owned retention-policy construction remains confined to the explicit test/development adapter; the production route requires an injected authority or fails closed.

The reviewed registry now contains:

Disposition Count
Durable authority 148
Durable coupled projection 275
Ephemeral and loss-safe 154
Stateless catalog or engine 160
Test/development adapter 40
Unbound production projection 17
Total 794

Verification:

text
node apps/oshun/bff/scripts/operational-state-inventory.mjs
  Operational-state inventory passed for 794 candidates.

operational-state-inventory.spec.ts
  3/3 passed

durable-snapshot-store.test.ts
  10/10 passed

representative BFF sink/control suite
  8 files; 98/98 passed
  achievement and Iris snapshot durability, autonomy recovery, governed
  capability brokers, academic replay/gradebook coupling, fiat persistence
  and settlement, and health probe state

scoped Prettier, ESLint, syntax, drift, and diff checks
  passed

BFF type ratchet
  exactly the same five unrelated current-main diagnostics

The detector/registry/test change modifies no production runtime, public or database schema, UI, provider/model call, media pipeline, mobile flow, or Unreal asset, so another production artifact build is inapplicable. The parent all-store checkbox remains open for client/provider/adapter vocabularies, anonymous or escaping local collections, and the standing deletion, privacy, retention, recovery, and loss-proof conditions.

2026-07-27 — Durable internal telemetry and feedback acknowledgement#

Source commit 9f7877877b8194db3d15a50d111eec9717c9be5f removes the two module-global console-only analytics clients used by search and cross-domain recommendation telemetry. Server-generated events now enter the existing owner-attributed analytics authority through one atomic internal-ingest path. The authority retains its bounded seven-day snapshot, production-required durability, recovery, and signed account-erasure integration.

Recommendation feedback was a false acknowledgement boundary: the route logged the input and returned ok: true, while cross-domain feedback emission was detached and best effort. The route now awaits durable analytics persistence before returning success. A missing or failed production sink returns 503 with recommendation_feedback_persistence_unavailable; no event is retained and no recordedAt claim is made. Read/search recommendation telemetry remains best effort at its route call sites, where a failed observation does not alter or overstate the served response.

Verification:

text
analytics ingest, telemetry, recommendation, and search suites
  8 files; 49/49 passed

post-integration feedback and telemetry regression suite
  3 files; 12/12 passed

operational-state inventory
  Operational-state inventory passed for 794 candidates.

scoped Prettier, ESLint, syntax, inventory drift, and diff checks
  passed

BFF type ratchet
  exactly the same five unrelated current-main diagnostics

apps/oshun/bff/dist/server.js
  36,568,748 bytes
  sha256 e4a78a419dfaa269592306968578c8d233c2451276070d5df00e0fc82dbc9c71

apps/oshun/bff/dist/server.js.map
  85,707,387 bytes
  sha256 fb71c431302540809ba5240cfe8783204f01f93b4e8790ae31f7abe05645d40d

fresh PostgreSQL catalog
  all 32 migrations applied

PostgreSQL/Redis production artifact smoke
  passed; disposable database dropped

2026-07-27 — Provider, client, adapter, and execution-family inventory#

Source commit 60f35d06ee65700c57bdb2606d3c6e9a1ca6ee50 extends the AST detector through provider, adapter, client, signer, executor, classifier, verifier, watermarker, and bus-shaped constructions. All 139 newly exposed candidates were reviewed:

  • Seven persistent Redis event buses are durable authorities: the crisis and retraction runtimes plus the five replaying server consumers. The request/reply account-deletion bus has persistence disabled and remains explicitly loss-safe because signed attestations, not the bus, are its audit authority.
  • External database, object-storage, billing, provider, model, voice, image, video, and payment clients are reconstructable bindings over external authority.
  • Signers, classifiers, watermarkers, and generation executors retain no acknowledged operational state; losing the binding cannot erase durable effects, evidence, provenance, or learning.
  • Deterministic domain adapters are stateless wrappers over injected owners. Psyche's compatibility embodiment adapters remain restricted to tests and non-production development.
  • The analytics snapshot sink remains a projection coupled to its durable owner.

The reviewed registry now contains:

Disposition Count
Durable authority 155
Durable coupled projection 275
Ephemeral and loss-safe 262
Stateless catalog or engine 180
Test/development adapter 43
Unbound production projection 17
Total 932

Verification:

text
node apps/oshun/bff/scripts/operational-state-inventory.mjs
  Operational-state inventory passed for 932 candidates.

operational-state-inventory.spec.ts
  3/3 passed

durable-snapshot-store.test.ts
  10/10 passed

scoped Prettier, ESLint, syntax, inventory drift, and diff checks
  passed

BFF type ratchet
  exactly the same five unrelated current-main diagnostics

The inventory-only commit changes no runtime, public or database schema, UI, provider/model invocation, media pipeline, mobile flow, or Unreal asset. The parent all-store checkbox remains open for anonymous or escaping local collections and the standing loss, privacy, deletion, retention, and recovery conditions.

2026-07-27 — Escaping closure collection inventory#

Source commit 375773f3147294d446a2a59644f0bf4ab311fd1b extends the AST gate beyond named factories and constructors to mutable Map, Set, array, and object roots captured by returned functions or returned API methods. The detector requires a post-construction mutation from the escaping closure, so ordinary request-local arrays and immediate map/transaction callbacks do not become false operational owners.

All 32 newly exposed roots were reviewed:

  • Twenty-eight record maps, revision maps, deletion fences, pending-operation maps, and serialization tails are projections coupled to their owning durable snapshot authorities. This includes the autonomy editorial publisher, Arete subject authority, calendar OAuth connections, customer messaging, channel bindings, notification state, active personas, and tenant SSO connections.
  • The per-run governance meter, achievement in-flight request coalescer, and bounded route-response cache are explicitly loss-safe. Process loss causes a conservative budget re-evaluation, duplicate read, or cache miss, never a false durable acknowledgement.
  • Nyx event-action closure state remains an explicit test/development adapter; production requires an injected authority and otherwise fails closed.
  • Regression assertions exclude the request-local Nyx channel-deduplication set and fiat transaction-note array, proving that callbacks which complete before their caller returns are not treated as escaping state.

The reviewed registry now contains:

Disposition Count
Durable authority 155
Durable coupled projection 303
Ephemeral and loss-safe 265
Stateless catalog or engine 180
Test/development adapter 44
Unbound production projection 17
Total 964

Verification:

text
node apps/oshun/bff/scripts/operational-state-inventory.mjs
  Operational-state inventory passed for 964 candidates.

operational-state-inventory.spec.ts
  3/3 passed

representative closure owner and loss-boundary suite
  14 files; 135/135 passed

durable-snapshot-store.test.ts
  10/10 passed

scoped Prettier, ESLint, syntax, inventory drift, and diff checks
  passed

BFF type ratchet
  exactly the same five unrelated current-main diagnostics

This detector-only pass changes no runtime, public or database schema, UI, provider/model invocation, media pipeline, mobile flow, or Unreal asset. The parent all-store checkbox remains open for returned collection objects, class-field and anonymous collection roots, and the standing loss, privacy, deletion, retention, and recovery conditions.

2026-07-27 — Class-field and returned collection inventory#

Source commit e80e47e07f67946a4d090eb38af804bf0ac065cf extends the AST gate across two previously explicit blind spots:

  • mutated class fields initialized as Map, Set, WeakMap, WeakSet, arrays, or empty objects; and
  • mutated named Map/Set roots returned by identity or object property, plus anonymous Map/Set instances assigned directly to properties of returned objects.

The mutation and escape requirements deliberately exclude immutable field catalogs, one-shot locals, and collections that never leave their constructing function. All 407 newly exposed roots were reviewed.

Of the 257 class-field roots, 221 record/index/revision/deletion/pending and serialization fields are coupled to their owning durable authorities, five metrics/debounce/media-cache fields are explicitly loss-safe, and 31 fields belong to test/development adapters whose production bindings use durable authority, an empty reader, or a fail-closed unavailable implementation.

Of the 150 returned roots, 116 are candidate snapshots, decoded snapshots, clones, indexes, deletion fences, or mutation views coupled to their durable owner. Twenty-four are one-shot validation, normalization, ranking, geometry, or source-controlled catalog values. Ten belong to the non-production Isis generation-control adapter; production requires an injected authority and fails closed when it is absent. Regression assertions pin representative durable, loss-safe, stateless, and test/development classifications across achievement state, metrics, Iris memory, Lilith policy, Isis generation controls, and living scenes.

The reviewed registry now contains:

Disposition Count
Durable authority 155
Durable coupled projection 640
Ephemeral and loss-safe 270
Stateless catalog or engine 204
Test/development adapter 85
Unbound production projection 17
Total 1,371

Verification:

text
node apps/oshun/bff/scripts/operational-state-inventory.mjs
  Operational-state inventory passed for 1371 candidates.

operational-state-inventory.spec.ts
  3/3 passed

representative Iris, Isis, Lilith, and living-scenes suites
  5 files; 47/47 passed

durable-snapshot-store.test.ts
  10/10 passed

scoped Prettier, ESLint, syntax, inventory drift, and diff checks
  passed

BFF type ratchet
  exactly the same five unrelated current-main diagnostics

This detector-only pass changes no runtime, public or database schema, UI, provider/model invocation, media pipeline, mobile flow, or Unreal asset. The parent all-store checkbox remains open for anonymous collections passed as call arguments, returned array/object roots, aliased field mutations, and the standing loss, privacy, deletion, retention, and recovery conditions.

2026-07-27 — Returned array and object inventory#

Source commit 9c5bd1b0f74bbb042762a6cfd639d50d36b4bea2 extends the direct-return detector from Map/Set families to locally initialized arrays and empty objects. A root is admitted only when its constructing function mutates it and returns it by identity or as an object property. Object member assignments are recognized as mutations; immutable literals and unreturned request locals remain outside the registry.

All 513 newly exposed roots were reviewed:

  • 55 candidate, clone, export, replay, snapshot, and durable-derived result collections are coupled to their owning durable authority. These include administrative audit/state projections, autonomy snapshots, consent evidence, deletion worklists, notification replay results, persistent safety aggregates, device-token snapshots, and customer export views.
  • 454 validation, normalization, ranking, aggregation, geometry, parser, and deterministic engine results are one-shot stateless values. Their functions retain no mutable collection after returning.
  • Four roots belong to the provider-quality, scene-ledger, and Nyx test/development adapters; production uses an injected authority or fails closed.

Regression assertions pin a durable audit clone, a stateless deterministic accessibility result, and the test-only provider-quality snapshot.

The reviewed registry now contains:

Disposition Count
Durable authority 155
Durable coupled projection 695
Ephemeral and loss-safe 270
Stateless catalog or engine 658
Test/development adapter 89
Unbound production projection 17
Total 1,884

Verification:

text
node apps/oshun/bff/scripts/operational-state-inventory.mjs
  Operational-state inventory passed for 1884 candidates.

operational-state-inventory.spec.ts
  3/3 passed

representative audit, accessibility, and provider-quality suites
  3 files; 23/23 passed

durable-snapshot-store.test.ts
  10/10 passed

scoped Prettier, ESLint, syntax, inventory drift, and diff checks
  passed

BFF type ratchet
  exactly the same five unrelated current-main diagnostics

This detector-only pass changes no runtime, public or database schema, UI, provider/model invocation, media pipeline, mobile flow, or Unreal asset. The parent all-store checkbox remains open for anonymous collections passed as call arguments, alias-mediated mutations, and the standing loss, privacy, deletion, retention, and recovery conditions.

2026-07-27 — Anonymous Map/Set argument inventory#

Source commit 5948456fae341e03efa9b90ca1f3c8bca7255ffb extends the AST gate to anonymous Map, Set, WeakMap, and WeakSet instances passed directly to calls or constructors. Stable candidate identities include the callee and argument index. The existing source filter excludes unit/integration test files, so assertion-only new Set(...) values do not enter the operational registry.

All 28 newly exposed production roots were reviewed:

  • Sixteen deletion fences, migrated snapshot components, and nested candidate collections are passed directly to durable snapshot/publish boundaries in channel bindings, Metis ingest, notification preferences/read state, personalization, active personas, device tokens, and appreciation retention. They are coupled to their owning durable authorities.
  • Twelve enum/subject-reference validators, deduplication values, cycle guards, JSON normalization guards, domain-status inputs, and OneRoster preview indexes are one-shot stateless arguments that their callees do not retain.

Regression assertions pin a durable persistCandidate deletion fence and a stateless assistant enum-validation set.

The reviewed registry now contains:

Disposition Count
Durable authority 155
Durable coupled projection 711
Ephemeral and loss-safe 270
Stateless catalog or engine 670
Test/development adapter 89
Unbound production projection 17
Total 1,912

Verification:

text
node apps/oshun/bff/scripts/operational-state-inventory.mjs
  Operational-state inventory passed for 1912 candidates.

operational-state-inventory.spec.ts
  3/3 passed

representative assistant-session and channel-binding suites
  2 files; 30/30 passed

durable-snapshot-store.test.ts
  10/10 passed

scoped Prettier, ESLint, syntax, inventory drift, and diff checks
  passed

BFF type ratchet
  exactly the same five unrelated current-main diagnostics

This detector-only pass changes no runtime, public or database schema, UI, provider/model invocation, media pipeline, mobile flow, or Unreal asset. The parent all-store checkbox remains open for anonymous array/object call arguments, alias-mediated mutations, and the standing loss, privacy, deletion, retention, and recovery conditions.

2026-07-27 — Retained nested array argument inventory#

Source commit 120bee8452cad86ae534f56b6a35d2dfbfb51024 closes the statically provable retained subset of anonymous array/object call arguments. The census found 913 literal array/empty-object call arguments, 886 of which are ordinary schema definitions, SQL parameter lists, cache keys, promise inputs, validation key lists, and deterministic function inputs. Treating all of them as operational owners would erase the inventory's retention signal.

The gate therefore admits array/empty-object arguments only when collection mutation semantics prove retention: the value position of Map.set or the element position of Set.add. All 27 newly exposed retained roots were reviewed:

  • Eight nested arrays in device/signup sessions, billing, group sessions, and tenant invites are candidate or owning durable state and remain coupled to their surrounding durable authority.
  • Twelve arrays are retained only inside one-shot Aja, Bellona, Hathor, studio, notification-deduplication, or Yemaya graph/grouping calculations and are stateless.
  • Seven arrays belong to explicit admin, sky-tonight, provider-quality, or scene projection test/development adapters.

Regression assertions pin one root from each disposition. Non-retaining literal arguments remain intentionally excluded by the machine rule rather than being bulk-labelled as operational state.

The reviewed registry now contains:

Disposition Count
Durable authority 155
Durable coupled projection 719
Ephemeral and loss-safe 270
Stateless catalog or engine 682
Test/development adapter 96
Unbound production projection 17
Total 1,939

Verification:

text
node apps/oshun/bff/scripts/operational-state-inventory.mjs
  Operational-state inventory passed for 1939 candidates.

operational-state-inventory.spec.ts
  3/3 passed

device-session-store-durability.test.ts
  5/5 passed

durable-snapshot-store.test.ts
  10/10 passed

scoped Prettier, ESLint, syntax, inventory drift, and diff checks
  passed

BFF type ratchet
  exactly the same five unrelated current-main diagnostics

This detector-only pass changes no runtime, public or database schema, UI, provider/model invocation, media pipeline, mobile flow, or Unreal asset. The parent all-store checkbox remains open for alias-mediated mutation/escape analysis and the standing loss, privacy, deletion, retention, and recovery conditions.

2026-07-27 — Simple alias-mediated mutation and escape coverage#

Source commit 44ddd9b7d6a48515c7fe89079270434747cff61c teaches the collection detectors to propagate simple lexical aliases before evaluating mutation and escape:

  • locally constructed collection roots are followed through chained variable aliases for returned-closure mutation, direct mutation, and return escape; and
  • collection-valued class fields are followed through local aliases for method mutation and nested property assignment.

The per-source collector is now exported as a pure analysis seam. A synthetic regression proves that a Map mutated and returned only through a local alias is reported, and that a class field mutated only through a local alias is reported. The current production corpus adds no new candidates under this rule, so the reviewed registry remains at 1,939 entries with zero undispositioned roots.

Verification:

text
node apps/oshun/bff/scripts/operational-state-inventory.mjs
  Operational-state inventory passed for 1939 candidates.

operational-state-inventory.spec.ts
  4/4 passed, including synthetic local and class-field alias coverage

durable-snapshot-store.test.ts
  10/10 passed

scoped Prettier, ESLint, syntax, inventory drift, and diff checks
  passed

BFF type ratchet
  exactly the same five unrelated current-main diagnostics

This detector-only pass changes no runtime, public or database schema, UI, provider/model invocation, media pipeline, mobile flow, or Unreal asset. The parent all-store checkbox remains open for reassigned, destructured, parameter, and interprocedural aliases and the standing loss, privacy, deletion, retention, and recovery conditions.

2026-07-27 — Stateless request-engine disposition correction#

Source commit ae2fbf78aad7b5a32e6076dd270502948448d6e0 corrects two reviewed ISIS request engines that had been conservatively labelled as ephemeral state:

  • costOptimizationStore retains no request, optimization preview, history, approval, evidence, effect, or learning state; and
  • promptTemplateStore likewise computes a preview from the current request without retaining the input or result.

Their public disposition contracts and inventory entries now agree on stateless_request_engine / stateless_catalog. Route tests pin that contract and prove deterministic recomputation with empty retained histories. The reviewed registry remains complete with zero undispositioned roots:

Disposition Count
Durable authority 155
Durable coupled projection 719
Ephemeral and loss-safe 268
Stateless catalog or engine 684
Test/development adapter 96
Unbound production projection 17
Total 1,939

Verification:

text
admin-isis-cost-optimization-route.test.ts
admin-isis-prompt-templates-route.test.ts
operational-state-inventory.spec.ts
  20/20 passed

node apps/oshun/bff/scripts/operational-state-inventory.mjs
  Operational-state inventory passed for 1939 candidates.

scoped Prettier, ESLint, diff, and inventory drift checks
  passed

node apps/oshun/bff/scripts/build.mjs
node --check apps/oshun/bff/dist/server.js
  passed
  server.js SHA-256
    5957c574842b7e2daf854a538b31596ac9088f7b3858b334cbf24f7c1b7c1ea5
  server.js.map SHA-256
    24a6eca95abd5a8380553a2f242cd444717fcf23a0ed7be42c7b5988b0ca2fe6

BFF type ratchet
  exactly the same five unrelated current-main diagnostics

The Nx wrapper was also attempted, but its dependency declaration fan-out hit an existing TypeScript 6 baseUrl deprecation outside the BFF target. The target's direct production build command above passed. This correction changes no runtime behavior or schema. The parent all-store checkbox remains open for the remaining retained-ephemeral loss audit and the standing privacy, deletion, retention, and recovery conditions.

2026-07-27 — Per-subject serialization-tail loss proofs#

Source commit 0d81dcc2a51ea634f69c405e9605f6596e0a20ca audits the two module-retained ephemeral maps that serialize operations by subject:

  • generation subjectLifecycleTails; and
  • personalization-vector subjectTails.

Each map contains only in-flight promises. Process loss terminates those operations along with the map; it does not remove committed state. The inventory now binds each loss-safe disposition to concrete restart tests instead of a generic cache rationale:

  • generation snapshots preserve exact-subject erasure after the tail is lost, and recover an interrupted durable provider claim as needs_review without redispatching its external effect; and
  • personalization snapshots preserve adjacent vectors and the erased subject's resurrection fence after the tail is lost, rejecting a stale post-restart upsert.

Verification:

text
generation/jobs-route.test.ts
personalization/personalization-vector-store.test.ts
operational-state-inventory.spec.ts
  50/50 passed

node apps/oshun/bff/scripts/operational-state-inventory.mjs
  Operational-state inventory passed for 1939 candidates.

scoped Prettier, ESLint, inventory drift, and diff checks
  passed

BFF type ratchet
  exactly the same five unrelated current-main diagnostics

This proof-only pass changes no runtime, schema, provider invocation, or effect path. Registry counts remain unchanged. The parent all-store checkbox remains open for the remaining retained-ephemeral cache and process-binding audit and the standing privacy, deletion, retention, and recovery conditions.

2026-07-27 — Shared route-cache loss-proof gate#

Source commit 41e2bba2445a613d7fca6ce12ddae4239247830c advances the operational-state registry to schema version 2 and binds all 25 module-scoped route response caches to one machine-checked loss proof.

Every covered owner is constructed by createRouteResponseCache, has the ephemeral_loss_safe disposition, and shares the tested bounded TTL/LRU implementation. Its total-loss test clears every entry and proves the next read is a miss followed by recomputation. The cache owns no domain state, idempotency decision, user history, evidence, lineage, approval, effect, or learning state.

The registry checker now rejects a shared proof when:

  • the tested factory's owner count changes;
  • any covered owner changes disposition; or
  • the guarantee or executable evidence citation is absent.

A synthetic negative regression proves both count and disposition drift are rejected.

Verification:

text
response-controls.test.ts
operational-state-inventory.spec.ts
  13/13 passed

node apps/oshun/bff/scripts/operational-state-inventory.mjs
  Operational-state inventory passed for 1939 candidates.

scoped Prettier, ESLint, script syntax, inventory drift, and diff checks
  passed

BFF type ratchet
  exactly the same five unrelated current-main diagnostics

This proof-and-gate pass changes no cache runtime or route behavior. Registry counts remain unchanged. The parent all-store checkbox remains open for the remaining retained-ephemeral class-field, closure, and process-binding audit and the standing privacy, deletion, retention, and recovery conditions.

2026-07-27 — Exact retained cache and metrics loss proofs#

Source commit 4b3955a19ce11a30f68da94c997b26e693f0467a extends shared loss-proof selectors to exact owner IDs, allowing one executable proof to cover a singleton and its internal retained fields without sweeping unrelated collections into the same claim.

Three bounded owners, representing eight retained inventory roots, are now machine-bound:

  • the achievement refresh debounce cache: its reset/process-loss proof permits a fresh idempotent refresh, while expiry/capacity/privacy tests prove it keeps only bounded subject digests;
  • the ambient WAV cache: its total-loss proof recomputes byte-identical deterministic output, while capacity/byte/privacy tests prove it keeps only bounded bytes under digest keys; and
  • the BFF metrics collector: its reset and fresh-collector proofs return an empty telemetry window without changing domain state.

The validator rejects missing or duplicate exact owner IDs as well as count or disposition drift. A synthetic missing-ID regression exercises the exact-owner selector.

Verification:

text
read-refresh-cache.spec.ts
ambient-wav-cache.spec.ts
observability/__tests__/metrics.test.ts
operational-state-inventory.spec.ts
  29/29 passed

node apps/oshun/bff/scripts/operational-state-inventory.mjs
  Operational-state inventory passed for 1939 candidates.

scoped Prettier, ESLint, script syntax, inventory drift, and diff checks
  passed

BFF type ratchet
  exactly the same five unrelated current-main diagnostics

This proof-and-gate pass changes no runtime behavior. Registry counts remain unchanged. The parent all-store checkbox remains open for the remaining retained-ephemeral closures and process bindings and the standing privacy, deletion, retention, and recovery conditions.

2026-07-27 — Process-local ID counter removal#

Source commit 279e1c4befc38a7913f0c9af23ce33d8f8d85103 removes the BFF's process-local fallback ID sequence. The Node runtime already provides node:crypto.randomUUID; using it directly eliminates retained state and avoids the fallback's restart collision window.

The operational-state registry drops the removed counter and now contains:

Disposition Count
Durable authority 155
Durable coupled projection 719
Ephemeral and loss-safe 267
Stateless catalog or engine 684
Test/development adapter 96
Unbound production projection 17
Total 1,938

Verification:

text
id.test.ts
operational-state-inventory.spec.ts
  10/10 passed

node apps/oshun/bff/scripts/operational-state-inventory.mjs
  Operational-state inventory passed for 1938 candidates.

scoped Prettier, ESLint, inventory drift, and diff checks
  passed

node apps/oshun/bff/scripts/build.mjs
node --check apps/oshun/bff/dist/server.js
  passed
  server.js SHA-256
    f8eb3a187200c723b187f24bcc29959e202a1c397958896278b829cefaf1f686
  server.js.map SHA-256
    6749b668df23a06b4dca4716b8ecb7331b71d1c3bb08548861a47529dc8bbd9f

BFF type ratchet
  exactly the same five unrelated current-main diagnostics

This change affects only ID suffix generation and the resulting inventory census; no schema or API shape changes. The parent all-store checkbox remains open for the remaining retained-ephemeral closures and process bindings and the standing privacy, deletion, retention, and recovery conditions.

2026-07-27 — Realtime connection-sequence removal#

Source commit 52f50014a7a1ee110dc6a204914da33e24d5a6f4 removes the process-local realtime-music connection counter. WebSocket generation sessions now receive mrt2--prefixed node:crypto.randomUUID identifiers, eliminating retained sequence state and restart-collision risk.

A focused regression generates 25 IDs, proves uniqueness, and validates the UUID v4/variant shape. The operational-state rewrite also re-reviewed two line-shifted, connection-local provider/session candidates as loss-safe; neither owns acknowledged domain state or effects.

The reviewed registry now contains:

Disposition Count
Durable authority 155
Durable coupled projection 719
Ephemeral and loss-safe 266
Stateless catalog or engine 684
Test/development adapter 96
Unbound production projection 17
Total 1,937

Verification:

text
generation/realtime-music-route.test.ts
operational-state-inventory.spec.ts
  12/12 passed; one real-engine test skipped because its optional engine was absent

node apps/oshun/bff/scripts/operational-state-inventory.mjs
  Operational-state inventory passed for 1937 candidates.

scoped Prettier, ESLint, inventory drift, and diff checks
  passed

node apps/oshun/bff/scripts/build.mjs
node --check apps/oshun/bff/dist/server.js
  passed
  server.js SHA-256
    1af4d0bc033a60a4b8a79950456b1d64b3f306ce0adf6644bc1511aa045c2936
  server.js.map SHA-256
    e49ef2c0cc68d61c978f081f5b9b44fcf53cf225556305f7158a91658f5af6cc

BFF type ratchet
  exactly the same five unrelated current-main diagnostics

The parent all-store checkbox remains open for the remaining retained-ephemeral closures and reconstructable process bindings and the standing privacy, deletion, retention, and recovery conditions.

2026-07-27 — Stateless codec and unbound adapter corrections#

Source commit d833fcec0c7f2b623490a7fc385cc690ddf7c9a4 corrects two remaining retained-root dispositions:

  • Aja's motion-watermark payload codec is stateless, not ephemeral. Its production route proves deterministic encoding and lossless decode/encode round trips, and the codec retains no payload, evidence, history, approval, effect, or learning state.
  • The agentic governance-gate meter closure is a test/development adapter, not production ephemeral state. A repository import-graph assertion proves no non-test source imports or composes the adapter; its only functional consumer is its test suite.

The reviewed registry remains at 1,937 entries and now contains 264 loss-safe ephemeral roots, 685 stateless engines/catalogs, and 97 test/development adapters; all other disposition counts are unchanged.

Verification:

text
admin-aja-content-watermarking-route.test.ts
agentic/agentic-governance-gate.test.ts
operational-state-inventory.spec.ts
  19/19 passed

node apps/oshun/bff/scripts/operational-state-inventory.mjs
  Operational-state inventory passed for 1937 candidates.

scoped Prettier, ESLint, inventory drift, and diff checks
  passed

BFF type ratchet
  exactly the same five unrelated current-main diagnostics

This classification pass changes no runtime behavior. The parent all-store checkbox remains open for the remaining retained-ephemeral closures and reconstructable process bindings and the standing privacy, deletion, retention, and recovery conditions.

2026-07-27 — Final retained-ephemeral gate and V1-002 closure#

Source commits 80873ce591e73471090129de651a049605bab858 and 7e7cd0662d2891018d02e6a19ce736fe58f18a1f complete the retained-root audit and convert its result into a permanent inventory invariant.

Exact executable loss proofs now cover the final eight roots:

  • achievement read-refresh coalescing may repeat an idempotent refresh but cannot duplicate durable unlocks;
  • the request-keyed admin WeakMap cannot outlive its response, which awaits the durable workspace checkpoint;
  • PostgreSQL adapter and connection-promise loss closes/reconstructs the client while canonical rows remain durable;
  • internal response-cache entries lose only recomputable projections;
  • payment runtime loss removes capabilities and makes quote creation fail closed before publishing an invoice;
  • the living-scene C2PA signer is reconstructed from deployment configuration (or a deterministic development key) and missing production configuration fails closed;
  • crisis-frame binding loss does not remove per-surface markers from the durable snapshot store.

The final regression derives all module-, closure-, and class-field ephemeral_loss_safe entries from the registry and fails unless every one is covered by a shared/exact loss proof or one of the two separately proven serialization tails. There are zero uncovered retained roots.

Verification:

text
inventory, achievements, response-cache, payments, crisis,
admin workspace, PostgreSQL reconnect, and living-scene C2PA suites
  108/108 passed

live PostgreSQL
  domain-stubs reconnect/canonical persistence: 28/28 passed
  admin workspace restart recovery: 1/1 passed

final operational-state-inventory.spec.ts
  10/10 passed

node apps/oshun/bff/scripts/operational-state-inventory.mjs
  Operational-state inventory passed for 1937 candidates.

scoped Prettier, ESLint, inventory drift, and diff checks
  passed

BFF type ratchet
  exactly the same five unrelated current-main diagnostics

Final reviewed census:

Disposition Count
Durable authority 155
Durable coupled projection 719
Ephemeral and loss-safe 264
Stateless catalog or engine 685
Test/development adapter 97
Unbound production projection 17
Total 1,937

All operationally required retained state is now durable/recoverable or explicitly fail-closed/unbound, and every retained ephemeral owner has executable evidence that loss cannot drop or falsely acknowledge authority, evidence, lineage, approval, effects, or learning state. This closes the final V1-002 checkbox.

2026-07-29 — Isis signed read pagination (I6.5.c closure)#

Source commit 023ac1ecfe introduces the reusable @isis/read-pagination snapshot/keyset contract and wires it to GET /api/v1/outputs/page. Rebased commit ab10c989ea upgrades the existing production GET /api/v1/outputs route and its consumers from offset pagination. Classifier and integration hardening in 1512613f0c and 5949061dec make both source paths explicit in the workload evidence, share one configured signing key, publish the snapshot route in OpenAPI, and run it through the standard package harness:

  • the route accepts only declared filters, four allowlisted sort keys, two sort directions, an opaque cursor, and a page size bounded to 1 through 100;
  • the SQL uses the selected sort column plus unique id in both ORDER BY and a parameterized tuple continuation predicate, with no OFFSET;
  • the cursor is HMAC-SHA-256 signed, verified with a constant-time comparison, requires a deployment key of at least 32 bytes, and is bound to the complete filter, authorization-scope, sort-key, and direction context;
  • invalid, tampered, or context-mismatched cursors fail before any database query, while missing/short deployment keys fail closed;
  • /outputs/page pins a scan-wide creation-time snapshot, while /outputs explicitly promises forward continuation consistency rather than a transaction snapshot;
  • OpenAPI, the TypeScript SDK, CLI, operator Outputs page, and browser flow use the same forward cursor. The UI keeps prior opaque cursors for Previous and clears continuation whenever filters, sorting, or page size change.

Focused verification:

text
shared read-pagination contract/property suite
  54/54 passed

complete output-registry suite, including snapshot route and OpenAPI parity
  116/116 passed

Isis SDK cursor/schema/cross-service contract suites
  8/8 passed

Outputs, comparison-workspace, and API-parity web suites
  72/72 passed

Chromium output continuation/reset flow
  1/1 passed

Isis CLI suite
  3/3 passed

shared pagination and output-registry lint; registry production build;
SDK, web, and CLI lint/typecheck/build gates
  passed (existing warnings only)

V1 Workbench deterministic generator checks
  base inventories and every Isis generator report no drift

Focused base/Isis generator regression suite
  295/295 passed

The regenerated workload census now reports three keyset reads (both output paths and the pre-existing jobs path) alongside 11 remaining limit-offset reads and one remaining deep-page risk. I6.5.c is checked. This does not overwrite the separate findings: I6.5.a still records missing readable record kinds, and I6.5.f still owns first/middle/final/empty, deleted/changed-row, invalid-cursor, and role-tier consumer fixtures.