Platform / product-development work — the Adam agreement, productizing/standing this system up as a product for Joseph's Arc Consulting Services business, and anything about building the platform-as-a-product — must be tracked and handled in its own dedicated session, separate from Grand County BD-operational work (PWA, leads, deals, outreach, deliverables). Do NOT interleave the two.
Why: Stated by Joseph 2026-05-18. The GC BD system is operational business development; productizing it for Arc Consulting Services is a distinct business venture. Mixing them dilutes focus and creates confusion while the GC system still isn't fully working. He intends to stand up the Arc Consulting platform in a separate session himself, later.
How to apply:
- Until the GC PWA/system is fully functional and verified working, do NOT start, plan, or get sidetracked by platform-dev / Adam-agreement / Arc-productization work. If such items surface mid-GC-work, capture them as a brief note/flag for the separate track and keep going on GC — do not expand scope into them.
- When GC is done and Joseph opens the separate session for the Arc Consulting platform, that is where Adam-agreement and productization belong — not in GC BD sessions.
- This overrides any inclination to "be helpful" by bundling platform/Adam work into current GC tasks.