docs(business): delivery goes dual-route, correct the client picture - #443
Conversation
Two CEO decisions from 2026-08-09. Delivery now runs through both JT's own senior Rails contractors (three unallocated, zero bench cost) and the white-label partner, where the docs previously assigned the entire delivery seat to the partner and called it the single point of failure. Updates the accountability chart, the portfolio's reversibility rationale, E3 in the assumptions register (whose kill-criteria could only route partner to fallback partner, never back in-house), the strategy risk section, and the exec-summary rabbit hole. This also reconciles a standing contradiction with the sales copy, which already promised "one senior engineer" and grounded the $7,500 price in JT's own AI-assisted development. JetThoughts is not restarting from zero: two outstaffing contracts run at $18,400/mo revenue and $5,440/mo profit. The exec summary's opener now says the firm needs new clients, which is the actual gap, rather than an empty book. Flag G0 as OS Issue 6 without changing its status: its definition-of-done (paid trial, fallback named, cold-eyes verdict pasted) is unmet and the handoff note is still the empty placeholder, yet A2 pricing was confirmed off it, which operating rule 1 forbids. OKF log records the durable rules; no concept file fits a business-layer decision and none was invented for it. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01AigL3QEB25ux7d6Wdj2emm
|
Warning Review limit reached
Next review available in: 12 minutes You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (7)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
2 participants
Two CEO decisions from 2026-08-09, surfaced while reconciling the PKM vault against this repo's business OS.
Delivery is dual-route, not partner-only
The docs assigned the entire Delivery seat to the white-label partner and called it "the single point of failure." Delivery now runs through both routes: JT's own senior Rails contractors carry the first rescues, the partner carries capacity beyond them.
docs/business/operating-system.md§2docs/business/opportunity-portfolio.mdrescue-sprint/assumptions-register.mdexecutive-summary.mdstrategy.mdThis also reconciles a contradiction the docs never addressed:
offer-one-pager.mdpromises "one senior engineer" and grounds the published price in JT's own AI-assisted development, while the org chart assigned the build to an unnamed third party.Framing corrected
executive-summary.md:10opened with "JetThoughts needs to restart client acquisition." The accurate framing is that the firm needs new clients — a new service line and a new buyer, not an empty book.G0 flagged, not re-scoped
New OS §5 Issue 6. G0 is marked Done on a CEO assertion, but its own definition-of-done is unmet — no paid trial rescue, no fallback partner named, cold-eyes handoff still the empty placeholder — and pricing was confirmed off it anyway, which operating rule 1 forbids. Status left exactly as Paul set it; the runbook card gains a pointer, nothing more. Lower risk now that in-house is a second route, but still open.
Verification
docs/markdown and.okf/log.md— nothemes/,layouts/,*.css, or blog body HTML, so content-only perCLAUDE.md; visual suites correctly skippedgit diff --stat: 7 files, +49/−12🤖 Generated with Claude Code
https://claude.ai/code/session_01AigL3QEB25ux7d6Wdj2emm