All decks
SENTINELATTOH · deck · narration · production guide · generated 9 September 2026
02What it is

The facts, from the register.

ProductSENTINEL — border & migration intelligence
Register keysentinel
OwnerATTOH LTD (Companies House 14079382)
Live atattoh.tech/sentinel · HTTP 200 on 9 September 2026
Price£60,000 one-off
Built from4 register parts, 4 live, 4 probe-verified
Listed14 August 2026

What it does

Border and migration intelligence with a sovereign-LLM narrative core, durable in-database scheduling and self-reported health.

Runs on

OSINT durable in-DB scheduler
Sovereign-LLM narrative core (range-wide)
OSINT health self-report (DB-native)
SENTINEL border & migration engine
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.

Border and migration signals are read as isolated events, so the pattern only becomes visible in hindsight.

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

What it does instead.

Better: "Integrates border migration signals with sovereign LLM and schedules in-database analysis." Count:

Border and migration intelligence with a sovereign-LLM narrative core, durable in-database scheduling and self-reported health.

The parts doing the work

OSINT durable in-DB scheduler verified

pg_cron+pg_net scheduler on the blackline Supabase; data-driven off osint_feeds.poll_interval_s; Vault-secret gated; replaces the twice-failed n8n SPO

Sovereign-LLM narrative core (range-wide) verified

Shared degrade-safe model-as-analyst core: single audited egress (nation's GPU in sovereign mode), leads-not-verdicts appended to every product prompt

OSINT health self-report (DB-native) verified

pg_cron-driven hourly health verdict (HEALTHY/DEGRADED/HALTED) over v_osint_feed_health, logged to osint_health_log; independent of the app and of CRO

SENTINEL border & migration engine verified

Corridor displacement-pressure engine: maps origin-region drivers (conflict/famine) onto configured border crossings, scores push + predicts surge; ri

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

Proof it exists, not a roadmap.

200

HTTP status of attoh.tech/sentinel on 9 September 2026 · healthy

4/4

register parts verified by probe

4

parts wired live

100%

readiness, register-computed

Open attoh.tech/sentinel 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: its category. Nearest rivals: Palantir Technologies (Gotham/Foundry), IBM i2 Analyst's Notebook, SAS Institute (e.g., SAS Viya), Recorded Future; strongest is Palantir Technologies. Our edge: SENTINEL offers rights-sensitive corridor and flow analytics over OSINT events, specifically designed for humanitarian capacity and non-refoulement, distinct from enforcement. Its engine and enrichment capabilities are built and tested to 10/10 reliability, providing a focused and ethically-aligned solution. How we beat them: We will target specific UK government departments and agencies focused on humanitarian aid, migration policy, and data analysis (e.g., Home Office, FCDO, relevant analytical units) through direct sales and targeted LinkedIn campaigns for policy advisors and analysts. Our wedge is the explicit rights-sensitive design, focusing on humanitarian capacity and non-refoulement, which directly contrasts with the broader, oft. Source: product_market_analysis, analyst gtm-loop-worker; rivals re-checked against the product's own promise 2026-08-29.

Not independently sourced This verdict was written from an analysis whose only source was the model itself, not scraped competitors (analyst gtm-loop-worker). Treat the competitor names and positions as a working hypothesis until the market research is re-run; do not quote them to a buyer.
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.

£60,000 one-off

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
OSINT durable in-DB schedulerdatalive_wired
Sovereign-LLM narrative core (range-wide)backendlive_wired
OSINT health self-report (DB-native)datalive_wired
SENTINEL border & migration enginebackendlive_wired
Source: product_parts joined to builder_blocks · 4 of 4 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

SENTINEL, as a package.

data

OSINT durable in-DB scheduler

pg_cron+pg_net scheduler on the blackline Supabase; data-driven off osint_feeds.poll_interval_s; Vault-secret

verified

OSINT health self-report (DB-native)

pg_cron-driven hourly health verdict (HEALTHY/DEGRADED/HALTED) over v_osint_feed_health, logged to osint_healt

verified
backend

Sovereign-LLM narrative core (range-wide)

Shared degrade-safe model-as-analyst core: single audited egress (nation's GPU in sovereign mode), leads-not-v

verified

SENTINEL border & migration engine

Corridor displacement-pressure engine: maps origin-region drivers (conflict/famine) onto configured border cro

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

A package reads like a control document.

Inside the scope

  • OSINT durable in-DB scheduler
  • Sovereign-LLM narrative core (range-wide)
  • OSINT health self-report (DB-native)
  • SENTINEL border & migration engine

Evidenced, and how

  • Live URL probed: HTTP 200 on 9 September 2026
  • 4 parts probe-verified, latest 3 July 2026
  • Register row updated with every probe

Outside the scope today · work left

  • No build gap recorded in the register
  • 2 register fields to fill (vs_competition_unsourced, audience)

Who signs, and where the work sits

  • ATTOH LTD owns the product and the data layer
  • 0 build packets proposed · 2 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/
ATTOHSENTINELattoh.tech/sentinel
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.