How OpsStrategyPro Operates Conventions for engagements, references, and the multi-tenant portal stack

Each engagement under 02_active/ uses the same two-track structure: reference/ is canonical AI context (curated, current, single-source-of-truth) and client-files/ is source documents, archives, drafts. workspaces/ are factories that read reference and produce outputs in published/. Promotion flow is one-directional: client-files/temp/ → reference/<area>/<file>.md, with source moved to client-files/archived/.

When a session produces reusable knowledge — a confirmed rate, a new team member, a deal outcome — update the relevant reference/ file before closing. Reference docs are the upstream source for every future session. Stale reference = missing context.

Each client portal (vg, bc, rwp) is a tenant in one shared codebase: portal_index.py generates the sidebar + shell; section-hub.html renders curated card pages; sync_portal.py mirrors Drive → portal repo → Netlify on every change. A new tenant is a config block + two logo files + a content tree under 02_active/<tenant>/published/.