Sabri Universal Post Composer — File 22

Sabri Universal Post Composer is the role-aware, adapter-driven creation gateway for the Sabri Social Homeopathy Platform. It unifies authorized authoring workflows while preserving every native module as the canonical owner of its content, media, consent, moderation, publication state, durable draft and canonical URL.

One canonical native record; multiple authorized projections. File 22 orchestrates creation and commands but never duplicates the native domain truth.

Current repository candidate — 1.0.0-rc.3

1.0.0-rc.3 is the integrated source candidate for the current consolidated central plan and the current File 22 plan. It deliberately remains an RC identity: stable 1.0.0 is not claimed until staging acceptance, controlled deployment and live re-verification are complete.

Governing ownership

• File 00: identity, verification, suspension and capabilities.
• File 05: Learning content truth.
• File 06: Encyclopedia content truth.
• File 10: Video truth.
• File 11: Reel truth/relationship under its native owner contract.
• File 12: PDF secure storage and document truth.
• File 18: Marketplace record/transaction truth.
• File 19: notification delivery.
• File 20: global shell and Create placement.
• File 21: social/Founder/Doctor/News/Poll/Patient Case publication lifecycle and canonical records.
• File 22: universal authoring surface and command orchestration only.
• File 23: private Founder/Doctor publishing operations dashboard.
• File 24: security/privacy/compliance assurance.
• File 25: public profile/timeline visual experience and canonical visual-token ownership.
• File 26: Search/Discovery/Ranking.

File 22 does not create a duplicate publishing backend, permanent universal post type, search index, notification store, consent vault, media vault, profile backend or moderation ledger.

RC3 source-complete scope

The candidate includes:

• one role/capability-aware Create gateway;
• native-owner adapter registry and no duplicate content database;
• File 00 fail-closed authorization and current-subject binding;
• File 20 Create/shell integration boundary;
• File 21 social publication provider integration and diagnostics;
• Quick and Advanced composer modes with a seven-stage authoring flow;
• native drafts, bounded autosave, recovery, conflict handling, idempotency and partial-failure reconciliation;
• four independent state dimensions: Composer, Review, Publication and Safety/Hold;
• schema-driven fields, validation, private preview and native upload-token orchestration;
• Patient Case anonymization/opaque-consent-reference controls;
• medical-safety, source/evidence and copyright/rights common policy holds;
• native correction/revision/scheduling lifecycle delegation without a duplicate editorial ledger;
• metadata-only projection events to Files 19/23/24/25 and explicit File 26 search/discovery handoff;
• fail-soft Learning, Encyclopedia, Video, Reel, PDF and Marketplace adapter-pack coverage;
• activation wizard, migration/compatibility, rollback, Safe Mode, audit/observability and non-destructive uninstall boundaries;
• no plaintext draft persistence in localStorage, sessionStorage or IndexedDB;
• a File 22-scoped Sabri Green fallback (#087A4E) while File 25 remains the canonical token owner.

Current central-plan business boundary

File 22 contains no Free/Pro/Premium split, PKR 400 core paywall, paid-AI entitlement, donor ranking, donor reach or donor feature/support advantage. Optional donation policy and any finance truth remain outside File 22's authoring authority.

Institutional AI Teacher boundary

The later central plan assigns generation policy to File 16, composer bridge/orchestration to File 22, publication lifecycle to File 21, notification delivery to File 19, operational oversight to File 23, assurance to File 24 and discovery/classification to File 26. File 22 supplies only the authorized adapter/orchestration path; it does not become an AI generation engine, verified-doctor authority or autonomous clinical system.

Technical baseline

• WordPress 6.5 or later
• PHP 8.1–8.3
• Sabri Membership Core plugin 1.2.3 or later
• File 00 database schema 1.2.0 or later
• File 00 contract 1.1.2 or later
• Production HTTPS required
• American English interface baseline with Urdu/Arabic/RTL readiness
• No external runtime CDN or remote fonts

Candidate contract versions:

• plugin 1.0.0-rc.3
• schema 1.0.0
• adapter API 1.0.0
• workflow API 1.0.0
• subject-schema API 1.0.0
• governance API 1.0.0
• lifecycle API 1.0.0
• REST API 1.2.0
• plan contract 1.0.0

Public PHP integration

Native modules register through the existing public adapter API. Full authoring workflows use the versioned workflow contract; optional governance/lifecycle providers add normalized rights/accessibility/translation/correction/scheduling and native lifecycle capabilities. All write authorization is revalidated server-side against the current subject and native owner.

Data and privacy boundary

File 22 stores only bounded orchestration metadata such as session/attempt UUIDs, user ID, adapter identity/version, opaque native reference, state dimensions, lock version, hashes, idempotency identity, retry counters, error codes and timestamps. It does not store draft bodies, patient consent evidence, identity documents, media bytes, clinical records, reviewer notes or native publication history.

Private Create and REST surfaces are authenticated, nonce-protected, owner-scoped, no-store, noindex, bounded and reauthorized on each operation. If the required private response boundary cannot be guaranteed, the browser workflow fails closed.

Current release truth

The authoritative current source-candidate record is:

docs/FILE22-RC3-NEW-PLANS-RELEASE-TRUTH-2026-08-10.md

The current source manifest is:

docs/FILE22-RC3-NEW-PLANS-SOURCE-MANIFEST-2026-08-10.md

Repository source completion does not equal production completion. Exact-head CI/package evidence, Hostinger staging fresh-install/upgrade, real companion/database migration verification, real-role workflows, browser/device/accessibility acceptance, backup/restore, rollback rehearsal, Founder acceptance, controlled production deployment, live smoke tests and parity verification remain separate gates.