🦊 Fred / Jack OSMain Command CentreCanonical dashboardUpdated 2026-05-12 15:05 Dublin

Jack OS Command Centre

One live dashboard for everything active across Pocket Coach, Leacam, Jack OS and related AI/product work. This is now the canonical Cloudflare entry point; sub-pages are linked below.

Pocket Coach

Main priority

Beta stability + controlled launch.

Rules activeRelease cadence open

Leacam

GTM pilot

Property-management wedge + intent-led outreach.

GojiberryBuffer

Jack OS

Ops layer

Fred as front door, tagged lanes, durable files.

Auto-taggingDashboard rule

FORQA

Watch lane

Plans exist; currently lower priority than Pocket Coach/Leacam.

Context parked

Today's Focus Stack

[PC Dev] Lock release control.
Fred reviews all releases using the Pocket Coach CTO skill; Jack approval is required before PR merges/deploys. Still decide exact release cadence and build owner.
[PC GTM] Build the first Pocket Coach proof asset.
Message: “My training plan broke because life got in the way — Pocket Coach fixes that.” Recommended workflow: Figma source mockup + Canva derivatives.
[Leacam] Purchase/configure Gojiberry + Buffer after approval.
Company card available; still approval-gated before purchase, account connection, campaign launch or posting.
[Leacam] Rank the PM target list by live intent signals.
Do not manually choose top 20 yet; deploy intent tooling first, then select the top 20 from the existing PM company list.
[Jack OS] Keep the operating system current automatically.
Fred auto-tags messages and now updates this command centre/sub-pages as part of meaningful project updates.

Outstanding Decisions

Pocket Coach: exact beta/prod release cadence and final build owner.
Pocket Coach: whether first proof asset becomes landing hero, social post, or both.
Leacam: final go-ahead to purchase/connect Gojiberry + Buffer.
Leacam: Mark/Alison acceptance of LinkedIn automation risk and pilot limits.
Jack OS: whether to move later to Telegram Topics/private group for true topic isolation.

Approval gates remain: purchases, account connections, public posts, outreach, code writes, PR merges and deploys all require explicit approval.

Project Status

Area	Status	Next move	Key links
Pocket Coach Dev	GitHub rules verified on `main`; PR quality gate successful; CTO review rule locked.	Decide release cadence/build owner; every release gets CTO review before Jack-approved merge.	Dev/Test implementation plan · AI-native CI/CD
Pocket Coach GTM	Freemium/pricing and endurance wedge agreed; proof-led launch direction set.	Create first proof asset and launch derivatives.	GTM Command Centre
Leacam GTM	Property-management wedge active; Gojiberry + Buffer tooling decision locked; company card available.	Purchase/configure after approval, monitor intent signals, rank top 20 PM accounts.	Leacam Agentic GTM Pilot · GTM Command Centre
Jack OS	Fred front-door model, auto-tagging and dashboard update rule active.	Keep dashboard and sub-pages current after each meaningful update.	This dashboard
FORQA	CTO/GTM review packs and implementation plans exist; not today's primary lane.	Resume when Mark/Jack prioritise FORQA work again.	FORQA Command Centre · Implementation plan

Canonical Sub-Pages

GTM Command CentreShared Leacam + Pocket Coach GTM loop. Leacam Agentic GTM PilotGojiberry + Buffer tooling decision for Mark. Implementation Plans IndexPocket Coach + FORQA implementation plans. AI-Native CI/CD IndexPocket Coach + FORQA SDLC/CI/CD plans. Pocket Coach Dev/Test PlanTechnical implementation detail. FORQA Command CentreFORQA status, CTO/GTM views and plans.

Operating Rules Now Locked

Fred auto-tags: I infer tags like [PC Dev], [PC GTM], [Leacam], [Jack OS], [Admin], [Quick].
Files are memory: meaningful decisions update Jack OS, not just chat.
HTML stays current: this command centre and affected sub-pages should be updated after meaningful project changes.
Release safety: Pocket Coach releases require CTO review; Jack approves before merge/deploy.
External action approval: no purchases, posts, outreach, account connections or code writes without approval.

Current default route: Jack messages Fred directly; Fred classifies, updates files, delegates subagents if needed, and keeps this dashboard current.

Freshness / Source of Truth

Canonical public page: https://jack-os-artifacts.pages.dev/

Source of truth remains the local Jack OS Markdown/CSV/JSON files. This HTML dashboard is the shareable visual layer generated from those files. If in doubt, treat the timestamp above and project docs as the freshness signal.