Lewati ke isi

RC1-A Independent Verdict

Verdict

RC1-A — CORE RC1 CERTIFIED

The bounded Scola Core V1 release candidate is certified on the exact source and evidence chain recorded in RC1-canonical-evidence-index.json. There are no open S0 or S1 findings inside this scope.

This verdict supersedes the current status of the earlier chronological RC1-independent-verdict.md (RC1-B). It does not delete or rewrite that historical decision.

Scope of certification

Certified:

  • T0 product/platform, authorization, package, evidence, and DEC-014 foundations;
  • T1 canonical Core navigation/capability/route/UX contract;
  • W01, W02, and W05 per-lesson bounded workflows;
  • exact Golden proof plus the immutable demo candidate and authenticated demo UAT.

Not certified:

  • Daily, RFID, smart, HR attendance, ATTEND+, LMS, CBT, report card, Admissions, Fees, Finance, optional analytics, complaints, messaging/notifications, News authoring, or independent Calendar CRUD;
  • production deployment or tenant-specific operational acceptance.

Environment decision

goldenbabyntree.gcgscola.id is EXCLUDED FROM RC1 CERTIFICATION AND PROMOTION SCOPE. It remains frozen on FE 3b7e5780… / BE 334db599… and was not changed by this closure.

No production promotion is authorized by RC1-A. Any future production rollout requires separate explicit authorization, backup, exact demo candidate, per-tenant canary, served-identity verification, tenant smoke, and stop-on-first-failure.

Final adversarial answers

  1. Can the excluded Daily surface return an apparently successful product response? No; it is backend fail-closed.
  2. Can the validator miss a new or modified top-level backend controller/security file or manifest? No; hostile mutations invalidate the complete tree.
  3. Can a stale immutable release manifest be silently reused? No; release creation rejects a stale application hash.
  4. Do current-tip W01/W02/W05 still pass behind the new global gate? Yes: 64/64, 33/33, 16/16.
  5. Is demo proof only a negative faculty_not_found path? No; linked-faculty open/save/reload passed, followed by verified cleanup.
  6. Is credential/tenant/session evidence current? Yes; E1.2 29/29 and validator PASS.
  7. Is any production tenant, especially GBN, implied to be certified or promoted? No.
  8. Can development proceed beyond RC1 without modifying GBN? Yes; use dev, Golden, and immutable demo under the promotion policy.

Release label

CORE RC1 CERTIFIED — BOUNDED CORE V1 — GOLDEN/DEV/DEMO — GBN EXCLUDED — PRODUCTION NOT AUTHORIZED