All decks
Pocket Business OSATTOH · deck · narration · production guide · generated 9 September 2026
02What it is

The facts, from the register.

ProductPocket Business OS — founder console engine
Register keypocket-business-os
OwnerATTOH LTD (Companies House 14079382) · powered by app-builder
Live atportal.smegrowthteam.com/command.html · HTTP 200 on 9 September 2026
Price£199 a month
Built from10 register parts, 9 live, 7 probe-verified

What it does

The founder console engine: ranked command briefs, phone-to-worker dispatch with evidence echo, critical web push, and a self-healing detect-fix-verify loop.

Runs on

Pocket OS — ranked command brief engine
Pocket OS — phone→worker dispatch + evidence echo
Founder operator OS
Google one-click OS login
Source: estate register (products, product_parts, builder_blocks) · deploy probe 9 September 2026Evidence live
03The frameWhat this buyer's profession checks

We will measure it against the buyer's own change-control.

Three checks a buyer in this field applies, whether or not they name the standard. We use them as the frame for everything that follows.

Check 1

A control between the work and the submission

Check 2

A process fit for this buyer, not a generic one

Check 3

Readiness for the next rule change

Frame chosen by BRG as a summary of the buyer's own change-control. Verify the wording with the body before external use.No accreditation is claimed
04Why it's better · 1 of 6Check 2 · fit for purpose

The job as the register describes it.

A founder cannot run the business from their phone, so everything queues until they are at a laptop.

Source: register pain_pointThe problem, stated plainly
05Why it's better · 2 of 6Check 2 · fit for purpose

What it does instead.

Pocket Business OS — founder console engine exists to solve: A founder cannot run the business from their phone, so everything queues until they are at a laptop.

The founder console engine: ranked command briefs, phone-to-worker dispatch with evidence echo, critical web push, and a self-healing detect-fix-verify loop.

The parts doing the work

Pocket OS — ranked command brief engine verified

get_command_brief(): fuses 9 live sources into a ranked one-tap card feed with urgency weights × 12h decay + ledger suppression. Live-proven 2026-07-0

Pocket OS — phone→worker dispatch + evidence echo verified

claim_phone_tasks() (SKIP LOCKED) + echo_phone_task() (done requires evidence; push_outbox echo) + bridge_phone_tasks_to_handoffs() (pg_cron */10). Li

Founder operator OS verified

founder_os(): every business Craig runs, each with live room+money.

Google one-click OS login verified

os.html + my_os(): Sign in with Google -> founder sees all businesses, partner sees their room.

Source: register purpose, public_blurb, product_parts joined to builder_blocks4 of 10 parts shown
06Why it's better · 3 of 6Check 1 · controls

Proof it exists, not a roadmap.

200

HTTP status of portal.smegrowthteam.com/command.html on 9 September 2026 · healthy

7/10

register parts verified by probe

9

parts wired live

HTTP 200

functional surface probe

Open portal.smegrowthteam.com/command.html during the talk. Anything the deck claims should be visible there.

Source: register deploy_probe_code, deploy_probed_at, product_parts.verified_by_probeProbed, not promised
07Why it's better · 4 of 6Against the market, honestly

Where we lead, and where we don't.

Category: founder operating console. Nearest rivals: Notion, Monday.com, ClickUp, Asana, Airtable; strongest is Notion among founders. Our edge: rivals are blank workspaces that only tell you what you already put in, so the founder still assembles the picture by hand; we surface what needs deciding, what is overdue and what is running without the founder maintaining the board. How we beat them: no configuration project, because the console is populated from the business rather than from the founder's own data entry.

Source: register vs_competitionNamed competitors are the register's, not the presenter's
08Why it's better · 5 of 6Check 2 · fit for purpose

Built for one kind of buyer.

Not in the register yet an audience. This slide stays blank until the register carries it; nothing here is invented.
Source: register audience, serves_nichesOne buyer, not everyone
09Why it's better · 6 of 6Price is part of the scope

What it costs, in one line.

£199 a month

Buying route

Payment on enquiry
software
Scope named on the next slides, so the price has a boundary
Source: register price_gbp, billing_interval, pricing_basis, payment_link_activeNo hidden rate card
10What's inside

The parts, with their verification state.

PartCategoryStateVerified
Pocket OS — ranked command brief enginebackendlive
Pocket OS — phone→worker dispatch + evidence echobackendlive
Founder operator OSbackendlive_wired
Google one-click OS loginfull-stacklive_wired
Truth Graph publisher railintegrationlive_wired
Self-healing detect-fix-verify loopbackendstaged
Pocket OS — critical web-push pipelinefull-stackstaged
Agent Value-Attribution Loopbackendlive_wired
Command decision action ledgerbackendlive
Push Notificationsfull-stackstaged
Source: product_parts joined to builder_blocks · 10 of 10 shown probe-verified   not yet
12Why packaging matters

Five things a package does that a price cannot.

1
Scope becomes visible. The parts are named, so nothing is assumed.
2
Boundaries are explicit. What is outside is written down before the first invoice.
3
It is auditable. A package is a documented process, which is what the buyer's own change-control looks for.
4
Buyers compare like for like. A referral needs a defined thing to refer.
5
Switching fear drops. The move is inside the package, not a project bolted on the front.
Source: BRG packaging doctrine; frame from slide 3Packaging = a compliance instrument
13This packageCut by what each part does

Pocket Business OS, as a package.

backend

Pocket OS — ranked command brief engine

get_command_brief(): fuses 9 live sources into a ranked one-tap card feed with urgency weights × 12h decay + l

verified

Pocket OS — phone→worker dispatch + evidence echo

claim_phone_tasks() (SKIP LOCKED) + echo_phone_task() (done requires evidence; push_outbox echo) + bridge_phon

verified

Founder operator OS

founder_os(): every business Craig runs, each with live room+money.

verified

Self-healing detect-fix-verify loop

Staged Phase-0 control plane: off does not detect/act; shadow proposes only; gated live can contain systemic n

staged
full-stack

Google one-click OS login

os.html + my_os(): Sign in with Google -> founder sees all businesses, partner sees their room.

verified

Pocket OS — critical web-push pipeline

push_outbox + queue_critical_pushes()/drain_push_outbox() (pg_cron */5, pg_net → portal-push-send Netlify fn,

staged

Push Notifications

Registered from existing live product_parts during 2026-07-05 Codex register-integrity repair. Products: black

verified
integration

Truth Graph publisher rail

Staged production publisher rail for the canonical live Truth Graph. It refreshes source repos, preserves BRG

verified
Source: product_parts grouped by builder_blocks.category3 groups
14Anatomy of the packageOn one page · 4 items of work left, filed

A package reads like a control document.

Inside the scope

  • Pocket OS — ranked command brief engine
  • Pocket OS — phone→worker dispatch + evidence echo
  • Founder operator OS
  • Google one-click OS login
  • Truth Graph publisher rail

Evidenced, and how

  • Live URL probed: HTTP 200 on 9 September 2026
  • 7 parts probe-verified, latest 9 September 2026
  • Functional surface: HTTP 200
  • Register row updated with every probe

Outside the scope today · work left

  • No build gap recorded in the register
  • 3 parts still to verify by probe
  • 1 register field to fill (audience)

Who signs, and where the work sits

  • ATTOH LTD owns the product and the data layer
  • 0 build packets proposed · 4 management items pending
  • Change log kept in the register
Source: product_parts (inside), deploy and part probes (evidenced), v_deck_work_left (work left; filed to manager_work and build_packets by deck_work_left_sync)One page
15Across the family

Where it hands over.

A1 Elitea1elite.pages.dev
Accounts & Filingattoh.tech/accounts-law/
AddressSnapattoh.digital/snap/addresssnap/
ATTOHPocket Business OSportal.smegrowthteam.com/command.html
AIEmploymentattoh.tech/aiemployment/
AIFreightaifreight.uk
AITransportaitransport.uk
Source: register rows sharing client_key attohOne house, many doors
1 / 16
Arrow keys or space · N narration · P print
Slide 1Narration Words Running total

Production guide

How to turn these sixteen slides into a presentation video. Same structure as every deck in the family, so a crew that has made one can make them all.

1 · Deliverable

ItemSpec
Format16:9, 1920×1080, 25 fps, H.264 MP4 plus WebM. Burned captions and a sidecar SRT.
RuntimeNarration below plus screen captures of the live product; typically 8 to 12 minutes.
Framethe buyer's own change-control. Verify the wording of the three checks with the body before external use.
BrandATTOH family palette as rendered here. Green only for verified and live states; red only for exclusions.
VoiceCalm, exact, never theatrical. Read figures and dates in full. Numbers are the register's, and the register is cited on every slide.

2 · Runtime plan

#SlideNarrationWordsStarts

3 · Screen captures

4 · Full narration

5 · What this deck must not say

  • No numbers that are not on a slide with a register source.
  • No accreditation by the buyer's own change-control; the frame is a lens, not a badge.
  • No named competitor read aloud unless the audience asks; the register's names are on slide 7 for the presenter.
  • No client names, volumes or tenure unless the register carries them.
  • Fields missing from the register for this product: audience. Fill the register, regenerate; do not improvise on stage.

6 · Regenerate

This deck is generated from the estate register. Update the product row, re-run the deck build, redeploy. Do not hand-edit this file.