🦊 Fred / Jack OSMain Command CentreAction dashboardUpdated 2026-05-13 17:45 Dublin

Jack OS Command Centre

Primary review surface for Jack’s priority actions, decisions and project links. The command centre does not replace the underlying documents — it points to them and keeps the next moves visible.

Pocket Coach

Main priority

Beta stability + brand pack + controlled launch.

Rules activeBrand pack uploaded

Leacam

Now action

LinkedIn posting + Buffer/Gojiberry pilot approval.

Decisions neededDocs linked

Anitech

Final interview

COO presentation prep and deck-change brief for Friday.

Due FridayBrief ready

Jack OS

Ops layer

Fred as front door, dashboard as action surface.

Dashboard rule

Leacam — Priority Next Steps

This is the current action board for the Leacam LinkedIn/Gojiberry launch. Nothing below is authorised for external action yet.

  1. Approve the launch approach.
    Decision: use Buffer for approved LinkedIn posting and Gojiberry for low-volume, intent-signal-led outreach from Mark’s personal account. Open next-steps plan
  2. Confirm LinkedIn ownership/access.
    Need: who has Super Admin access to the Leacam company page; whether Mark is happy to connect his personal profile to Buffer; who approves posts and who handles replies.
  3. Approve Buffer setup.
    Recommendation: Buffer Team/workspace so Jack/Fred/Alison can draft and Mark/Alison can approve. Then connect Mark profile + Leacam company page. Open tooling research
  4. Approve the 8-week LinkedIn content strategy.
    Recommended cadence: Mark profile 3 posts/week; Leacam company page 2 posts/week; theme is practical AI/workflow automation for Irish property-management businesses. Open 8-week strategy
  5. Approve Gojiberry pilot boundaries.
    Need explicit approval for purchase, LinkedIn connection, automation risk, ICP, first 20–30 prospects, message templates and conservative limits: start 10 actions/day, max 15/day in week 2 if no warnings.
  6. Queue first two weeks after approvals.
    Week 1 should be content warm-up only: 3 Mark posts, 2 company-page posts, Mark comments 5–10x/day. Gojiberry launches only after content is live and messages are approved.

Leacam — Key Decisions Required

  • Buffer plan/workspace: approve Team plan or choose cheaper one-user setup. Recommendation: Team because approval workflows matter.
  • LinkedIn access: confirm Super Admin for Leacam company page and Mark personal-profile connection consent.
  • Approval workflow: Mark approves personal posts; Mark/Alison approve company-page posts; Mark approves outreach messages.
  • Gojiberry risk: accept or reject LinkedIn automation risk before purchase/account connection.
  • Campaign scope: approve ICP, first 20–30 prospects, message templates, and reply owner before launch.

Leacam — Core Documents

Next Steps / Launch PlanBuffer setup, Gojiberry setup, approvals, first 2-week execution. Tooling + Cadence ResearchBuffer requirements, Gojiberry findings, LinkedIn cadence and risk notes. 8-Week LinkedIn StrategyTopics, cadence, formats, weekly workflow and metrics. Leacam Pilot OverviewHigh-level Gojiberry + Buffer pilot decision page.
Approval gate: no purchases, account connections, public posts, outreach, campaign launch or CRM/shared-doc writes without explicit approval.

Today’s Focus Stack

  1. [Leacam] Resolve LinkedIn launch decisions.
    Buffer plan/access, Mark/company-page approval workflow, Gojiberry risk and pilot boundaries.
  2. [Anitech] Finalise Friday COO deck.
    Final Claude CoWork deck-change brief is ready; next step is deck build/rehearsal.
  3. [Pocket Coach Dev] Lock release control.
    Fred reviews all releases using the Pocket Coach CTO skill; Jack approval before PR merges/deploys.
  4. [Pocket Coach Brand/GTM] Review Brand Pack v0.1 and decide first proof asset.
    Choose whether first proof asset becomes landing hero, social post, or both.

Outstanding Decisions

  • Leacam: approve/reject Buffer Team setup.
  • Leacam: confirm LinkedIn Page Super Admin + Mark profile connection.
  • Leacam: approve/reject Gojiberry purchase and automation risk.
  • Leacam: approve 8-week content strategy and first 2-week queue.
  • Anitech: build revised deck and rehearse Friday presentation.
  • Pocket Coach: decide release cadence/build owner and approve brand direction.

Project Status

AreaStatusNext moveKey links
Leacam GTMLinkedIn/Gojiberry launch plan, 8-week strategy and tooling/cadence research are now published and linked.Jack/Mark/Alison approve decisions, then connect Buffer channels and queue first 2 weeks.Launch Plan · Research · 8-Week Strategy
Anitech InterviewFinal-round COO presentation prep active; research, guardrails and Claude CoWork deck-change brief ready.Build revised deck, prepare speaking notes, rehearse before Friday.Final deck-change brief
Pocket Coach DevGitHub 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 plan · AI-native CI/CD
Pocket Coach GTM / BrandFreemium/pricing and endurance wedge agreed; Brand Pack v0.1 created and uploaded to Google Drive.Review guidelines/logos/hero images; approve/refine blended Territory 1+2 direction.GTM Command Centre
Jack OSDashboard repositioned as the primary action-review surface, not just a document index.Keep priority actions, decisions and doc links current after meaningful updates.This dashboard

Freshness / Source of Truth

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

Source documents remain in Jack OS. This dashboard is the action layer: priority next steps, decisions, and links to the supporting documents.

Jack OS Command Centre — generated by Fred — 2026-05-13