Lewati ke isi

RC1 Deployment Prerequisites and Deterministic Tenant Gate

Candidate and current environment truth

  • Golden candidate: FE app 1ffc7160a6521f7d97f4d5731ff43223846d0e11, served docs descendant bd37c5170991aacc8ac0e0bc7b3a12c2cbf29401, app tree eb10f68e…f31a; BE 3d7a213d2c97bb660316b65ccbd74dbe5541e46d, tree 69bd9993…b2e9.
  • FE is ahead 3 of origin/develop; BE is ahead 1 of origin/main.
  • Demo and every listed production tenant currently serve FE 3b7e578040773f5054ba32d63d5fce64a30acc56 and BE 334db599f4fa0ef66e9872aa4cfcbf0f378f2381.
  • Therefore RC1F-006 is open. This audit authorizes no promotion.
Tenant Current FE Current BE Required upgrades before optional use Smoke required RC1 promotion status
Golden bd37c… (candidate app tree) 3d7a… News authoring requires -u scola_news; authoring excluded audit stack passed functional candidate only
Demo 3b7e… 334db… determine exact diff; -u scola_attendance if version/rule absent; -u scola_news before W16 full candidate role/scope/UAT NOT EXACT CANDIDATE
Golden Baby N Tree 3b7e… 334db… same deterministic checks per-tenant authenticated smoke NOT EXACT CANDIDATE
Spansa 3b7e… 334db… same per-tenant authenticated smoke NOT EXACT CANDIDATE
Al-Jabbar 3b7e… 334db… same per-tenant authenticated smoke NOT EXACT CANDIDATE
Rejis 3b7e… 334db… same per-tenant authenticated smoke NOT EXACT CANDIDATE
SDN 1 PGT 3b7e… 334db… same per-tenant authenticated smoke NOT EXACT CANDIDATE

Required sequence

  1. Commit/push the exact FE/BE candidate and current independent audit docs without changing application trees.
  2. Create immutable backend release and exact FE build; rerun isolation guard.
  3. Promote the exact pair to demo only, then verify served SHA/tree/build, module/entitlement profile, role smoke, negative tenant/RPC probes, and logs.
  4. For each existing DB, require explicit module-version/rule/schema checks. Run -u scola_attendance whenever attendance proof is absent. Run -u scola_news only before News authoring is intentionally enabled after W16 certification.
  5. Production needs fresh user authorization, backup, exact demo-candidate equality, one canary tenant, stop-on-first-failure, and per-tenant served-identity/smoke verification.

No git pull, worktree rsync, wildcard DB, bulk restart, or direct worktree-to-production path is acceptable.