For: Randall, future hires, future collaborators
This is the OpsStrategyPro internal knowledge hub — a single place to see what's been built across all active client engagements, what's deferred, what's in flight, and how the operation runs.
What it's NOT
- Not a live system. Everything here is a snapshot. The State page tells you what was true at last rebuild — typically within the last 30 minutes, but never live.
- Not a CRM or project tracker. It doesn't capture new work — it
surfaces work that's already captured elsewhere (in
next.mdfiles, in Fathom meeting archives, in the engagement repos). - Not authoritative. Each card links back to its canonical source
(usually a
reference/<area>/<file>.mdsomewhere in02_active/). If the portal disagrees with the source, the source wins.
What it IS
| Section | What it surfaces |
|---|---|
| Start Here | This onboarding tour (you're here) |
| State | Live next-notes across every active engagement |
| Skills | Capabilities the business has demonstrated |
| How-We-Work | The conventions and patterns the engagements share |
| Timeline | Chronological view: git, Fathom, next.md activity |
| Digest | Weekly Ollama-distilled summary |
How to use it
- Open with a goal. "What was deferred last week?" "What can the business do for a flip-project engagement?" "How do new engagements get set up?"
- Use the sidebar to pick a section. The sidebar is flat — no nested accordions, no deep navigation. Click and you're there.
- Follow the canonical-source links when you need depth. The portal cards are summaries; the canonical files in the repo are the truth.
Who built it
This portal — its generators, its content, its sync daemon — is hand-built
in Claude Code across ~2 weeks in May 2026. The full architecture is
documented in 02_active/rwp/CLAUDE.md.