File 03 — Profiles and Doctors

Canonical profile-domain source for the Sabri Social Homeopathy Platform.

Governing scope

File 03 owns stable public profile identity, profile fields/audiences, Founder official profile presentation, member/doctor presentation records, slug history, profile-media references/deletion ledger, profile reports, private professional proposals, profile timeline federation, privacy export/erasure and File03 operational evidence. Membership truth, doctor verification decisions, directory/ranking, clinic truth, publication records, communication graph, global shell and final visual-system ownership remain with their canonical companion files.

Current repository candidate

• Plugin: 1.2.0-rc18
• Database schema: 1.2.0
• Public contract: 1.4.0
• PHP target matrix: 8.1, 8.3, 8.4
• WordPress baseline: 7.0+
• Latest completed corrective branch (historical): audit/file03-ninth-twenty-round-20260928
• Latest merged repository closure SHA: 6ed5c0ee5b518a62d961a0d12378adc2960871e7
• Ninth-cycle ledger: NINTH-TWENTY-ROUND-SEQUENTIAL-REVIEW-2026-09-28.md
• Ninth-cycle review: 20/20 completed
• Ninth-cycle defect-bearing rounds: 04, 07, 20
• Ninth-cycle clean rounds: 01, 02, 03, 05, 06, 08–19
• R20 pre-correction exact HEAD: 95c90da025d2157b578126d69559fc6bac733918
• Seventh-cycle ledger: SEVENTH-TWENTY-ROUND-SEQUENTIAL-REVIEW-2026-08-29.md
• Seventh-cycle review: 20/20 completed under complete review → consolidated defect ledger → correction → exact-state retest → next round
• Defect-bearing rounds: 03, 04, 05, 06, 07, 08, 11, 14, 15, 17, 19, 20
• Clean rounds: 01, 02, 09, 10, 12, 13, 16, 18
• Totals: 12/20 defect-bearing · 8/20 clean

Ninth-cycle current-companion correction boundary

The ninth review starts from exact main SHA 695329cced81a1b2ee5c59e3b4a92c9809a2564b. Fresh comparison with current File 08 exact HEAD 70541974ce0ffb16aebef557c3016eb7447662f4 proved a transport mismatch: File 08 emits clinic/appointment owner facts through wca_outbox_event, but rc17 did not subscribe to that exact surface. rc18 adds the versioned File 08 outbox consumer and actual current event names, and uses them only to invalidate File 03 cache/reconciliation state. No File 08 truth is copied or mutated.

The candidate is 1.2.0-rc18; DB schema remains 1.2.0 and public contract remains 1.4.0. The complete branch audit is recorded in the ninth-cycle ledger. PR #38 merged as 6ed5c0ee5b518a62d961a0d12378adc2960871e7, and the required exact-head CI/package workflows passed on that resulting main SHA. Staging, deployed artifact parity, live DB/migration state and live verification remain unverified.

Eighth-cycle cross-file correction boundary

The eighth review starts from exact main SHA 88da03fa4b92576384f4542ee7fc17312043bc0f. It closes repository-owned integration gaps discovered by checking the amended File 03 plan, the central plan and current companion contracts: external File 09/File 21/File 08 facts now invalidate File 03 projections without becoming local truth; File 03 has an explicit File 19 sun.event.v1 producer/intake path for user-facing profile/report/moderation notifications; appeal/reopen events are present in the public contract manifest; System Check exposes File 19 compatibility; and latest-plan CI no longer publishes a stale rc1 artifact identity.

The candidate is 1.2.0-rc17; DB schema remains 1.2.0 and public contract remains 1.4.0. This is source/repository evidence only. Exact-head CI, staging, installed-package checksum parity, database/migration state, real provider journeys and live verification remain separate gates.

Seventh-cycle correction boundary

The seventh cycle hardened File 17/File 00/Future provider exception containment, delegated and mutation uncertainty semantics, fail-closed legacy age/contact migration, viewer-authorized timeline projection, immutable Founder identity refresh, Founder/legal-hold erasure safety, and operational retention failure evidence. The final R20 reconciliation also removed a release-identity collision by advancing the source candidate to 1.2.0-rc16, extended the plan lineage through the sixth and seventh twenty-round cycles, and synchronized repository truth/evidence documents and permanent R20 regression coverage.

The DB schema remains 1.2.0; no R20 table/column/index migration is implied by the rc16 source identity. The public contract remains 1.4.0; rc15 manifest extension keys are retained for backward compatibility rather than silently renamed.

Exact repository evidence

Repository closure is valid only for an exact candidate SHA whose Corrective Integrity and File 03 Fresh Eighty-Round Review workflows both complete successfully. The Fresh workflow also performs deterministic double-build ZIP creation, checksum validation, SBOM validation and exact source/package runtime parity. Any later documentation or merge SHA must itself be re-tested before being called the repository closure HEAD.

Historical review ledgers, package inventories, checksums and CI runs remain regression/provenance evidence only. They never substitute for current exact-HEAD verification.

Truthful status

Repository source, CI and deterministic package evidence do not authorize staging or production. Staging reality, exact installed-package checksum parity, live DB/schema/migration state, real companion-provider integration, representative browser/mobile/Urdu-Arabic RTL/WCAG journeys, backup/restore/rollback and Founder acceptance remain separate mandatory gates.

Exact deployed code remains unverified; repository-based diagnosis is provisional for any live incident.

Tenth-cycle current-main re-audit

A fresh twenty-round read-only audit started from exact main SHA 6ed5c0ee5b518a62d961a0d12378adc2960871e7 and current companion heads on 2026-10-03. Rounds 01–19 were clean. Round 20 found stale post-merge release wording that still described the historical review branch as current and the already-successful merge-SHA closure as pending. The correction is evidence/test-only: runtime source, DB schema 1.2.0, and public contract 1.4.0 are unchanged. The permanent gate is tests/tenth-twenty-round-sequential.py; exact-head workflow records, not a self-referential document SHA, remain authoritative.