Group: Technical Capabilities · Status: Demonstrated
Document conventions, multi-tenant publishing, and learning hubs that surface what already exists rather than forcing every piece of knowledge through a single SaaS UI.
The shape of the capability
- Two-track reference.
reference/is canonical AI context (curated, current, single-source-of-truth).client-files/is source documents, archives, drafts. The split lets AI build accurate mental models fromreference/while raw inputs stay accessible. - Promotion workflow.
client-files/temp/→ manual extraction →reference/<area>/<file>.md. Source moves toclient-files/archived/. Approve/deny per-item, not batch — keeps the canonical set deliberate. - Multi-tenant portals as the surface. Each engagement's published HTML is a Netlify-deployed site with password gate. New tenants are a config block, not a new codebase.
- This very portal. RWP is the meta-application: it surfaces what OpsStrategyPro has built across all engagements.
Canonical sources
📎 RWP repo → RWP/CLAUDE.md → Client Engagement Folder Convention
📎 This portal → How-We-Work section
Where to look in the repo
RWP/CLAUDE.md— the convention itself05_library/templates/internal/operations/client-workspace-claude-template.md02_active/vg/— first engagement migrated to convention (2026-05-18)02_active/rwp/— RWP portal source tree (this site)