Advisory OS — What To Do Next

Updated: February 14, 2026

This Week (Before Monday Session with Ruben)

• [ ] Save System Index locally. Open in browser. Bookmark it.
• [ ] Save Architecture Handoff v2. This goes to the architecture chat.
• [ ] Fix Engagement SOP: Pooja check-ins are Thursday, not Wednesday.
• [ ] Verify SOP V3 is ready for Pooja — February close starts March 1.
• [ ] Prep for Monday session: Have constraint brief + any notes ready.

Recurring Weekly (Every Week, Same Order)

Monday — Session Day

• [ ] Session with Ruben (recorded on Otter)
• [ ] After session: drop transcript in raw transcripts folder → Relay handles the rest
• [ ] Verify Relay produced: recap email + JSON file
• [ ] Feed brief + transcript + JSON → Constraint Priority Matrix (Claude Project)
• [ ] Update Client Master Plan from matrix output
• [ ] Send client recap email

Tuesday–Wednesday — Build Days

• [ ] Build deliverables for active constraint (SOPs, templates, tools)
• [ ] Deploy to Pooja as ready

Thursday — Operator Check-in

• [ ] 1pm ET check-in with Pooja
• [ ] Calibrate SOP against reality — what's working, what's friction
• [ ] Update master plan if anything material surfaced

Friday — Intake

• [ ] Receive constraint brief from Ruben (via his ChatGPT Constraint Identifier)
• [ ] File it for Monday processing

Weekly (Your Business) — Flexible Timing

• [ ] Publish one thought leadership piece
• [ ] Set up Lead Shark for hand-raiser posts (~2x)
• [ ] Send weekly email (thought leadership + tools + briefing invite)

Architecture Work (Do in Architecture Chat)

These are decisions, not tasks. Each one needs a working session:

1. Restructure Client Delivery System instructions — currently trying to do too much. Break into scoped pieces. This is the highest-impact fix.
2. Fix terminology drift — "synergy/synergistic" → "Solve Together" across all files, not just Crulliance skills.
3. Stand up a working Ruben client delivery project — one that takes matrix + JSON + transcript and produces updated master plan + project plan + blueprint in a single weekly session.
4. Formalize the folder structure — where does every file type live? Answer once, enforce everywhere.
5. Extract client-agnostic methodology — separate the Crulliance-specific skills into Layer 1 (agnostic) + Layer 3 (client-specific) versions.
6. Clean up Top of Funnel project — tidy instructions, golden examples, stabilize the weekly campaign production.
7. Email list cleanup — remove GetSales-enriched inactive contacts hurting deliverability.

Not Now (But Don't Forget)

• Client Roadmap (client-facing "where are we going" view) — build after Ruben engagement stabilizes
• Solution library packaging for Accounting Manager OS — after Feb + March live closes
• Agnostic SOP template — after Crulliance SOPs prove the pattern
• Additional micro-tool skill files (calculator, diagnostic, comparison, swipe) — build when first tool of each type is produced
• Cadence integration for client project management — test with Ruben's builds when ready

System Index Maintenance

When you add a new project or system: add a card to the index. When something stabilizes: change badge to Complete. When something breaks: add a warning note. When you solve an issue: remove the warning.

Badge definitions:

• Active — in regular use, working
• Evolving — actively being iterated, not stabilized
• Complete — full system, could hand to someone else to run
• Needs Update — works but has known issues
• Building — in progress, not standalone yet