Install
This is the repository archive. It installs, but the folder name will carry the branch suffix and updates will not flow.
Install straight from GitHub with WP-CLI:
wp plugin install https://github.com/majidhussainqadri1-dot/01-sabri-platform-foundation/archive/refs/heads/main.zipFile 01 — Sabri Platform Foundation 2.0.1
This repository implements File 01-B, the governance/runtime foundation defined by SSH-F01-PLAN-2026-v1.0, the Definitive Master Plan v3.0, the approved Future Foundation v2.0 enhancement set, and later Founder-approved harmonization.
Canonical boundary
File 01 owns the 00–26 governance catalog, module/contract/route registries, dependency readiness, safe activation/upgrade conventions, redacted System Check, release evidence, File 01 privacy lifecycle, legacy reconciliation orchestration, owner-scoped repair, feature-flag governance, event/outbox foundation, and guarded purge governance. It does not own membership identity (File 00), global shell/navigation (File 20), Home/News/feed (File 21), Security Center assurance (File 24), public visual/profile experience (File 25), or search/discovery/ranking truth (File 26).
Release truth
The current repository candidate is software 2.0.1, schema 1.2.0, contract 2.0.0, and Future Foundation 2.0.0. Software, schema and contract versions are intentionally distinct. Historical 1.1.x/1.2.0/2.0.0 review records remain historical evidence and must not be treated as the current package identity.
Version 2.0.1 is a reconciliation-safety patch discovered from live System Check evidence. It closes a Safe Repair bypass so spf_page_map and spf_founder_user_id can no longer be removed outside the guarded SPF_Reconciler workflow. Legacy route cutover remains fail-closed until canonical File 20/File 21 owner plans are accepted and version-matched reversible receipts are returned. Real WordPress/MySQL cross-file QA pins exact File 20/File 21 candidate SHAs and proves guarded plan → apply → quarantine → rollback behavior.
The current source implements versioned/machine-readable 00–26 governance and rollback-aware reconciliation; event schema/version/idempotency/replay/dead-letter/reconciliation with durable privacy classification; fail-closed feature activation requiring dependency readiness plus independently verified migration, health, rollback and gate evidence; and the approved Future Foundation enhancements.
Security and reliability highlights
- Structured, short-lived File 00 authorization claims bound to actor, action, object, purpose and institutional role.
- No generic Administrator release, Founder or purge authority.
- Atomic idempotency reservation, replay/recovery receipts and serialized mutation throttling.
- Audit-chain integrity verification, bounded redaction and fail-closed tamper handling.
- Bounded outbox payloads, privacy classification, stale-lease recovery, retries and dead-letter handling.
- Shadow-table activation/upgrade compensation plus exact required-index verification.
- Bounded immutable contracts/manifests/routes and deterministic dependency rejection.
- Version-bound File 20/21 reconciliation receipts with exact rollback restoration.
- Safe Repair cannot delete reconciliation-owned legacy options or bypass canonical owner acknowledgement.
- Independent backup/restore and File 24 assurance before destructive purge; atomic quarantine and terminal replay.
- One free tier / donation-only governance metadata with no donor advantage.
Staging-Accepted, Live-Deployed, and Operational remain separate external statuses. A green repository/CI/package result is not evidence of the exact deployed Hostinger state. See TRACEABILITY.md, QA-REPORT.md, STAGING-ACCEPTANCE.md, RELEASE-CHECKLIST.md, and the current review record.