KAIROSSIX-STREAM EXECUTION

BLIND SELECTION · BOUNDED RESULT

TERMINAL RESULT · 04 SEP 2026 · REVIEWER-TESTED

One account
observation.
Zero accepted downstream events.

The blind draw produced one 2026-03-15 IOS account row and no accepted subscription, product, support, customer-outcome, lifecycle, economic or exposure event on the routes executed. This is a sparse observability result—not proof that those events never happened.

TERMINAL CLASS

EXECUTION_VERIFIED_WITH_LIMITS. Process PASS: Tris / Fable 5.1 / high / 51 of 51 fixtures. Execution PASS with limits: native Claude Opus 5 / max / sealed read-only verification.

BLIND DRAW1 / 241,540

Zero redraws in the frozen observed root frame.

CASE TOKENCJ6-000014f4f5e0

Pseudonymous reader token; not anonymous.

ATTRIBUTION1 root · 0 downstream

Zero means no accepted edge on the executed paths.

SOURCE DENOMINATOR · 01

Every room accounted for. Not every object exhausted.

Twelve governed rooms were dispositioned. Nine yielded examined content through authenticated live BigQuery reads or retained captures; three were inaccessible. Metadata coverage is not evidence coverage.

12 / 12Governed rooms

Every room received an explicit disposition.

9Rooms examined

Live BigQuery or retained content reached a declared terminal condition.

3Rooms inaccessible

Mysterium business API, GoProxies reporting and Pipedrive.

509Warehouse objects

A name-level denominator, not a content-exhaustion claim.

15,172,214Frozen rows read

All rows across 14 admitted direct physical leaves.

241,540Eligible root IDs

Frozen observed 2026 frame; left-censored, not the account estate.

BIGQUERY DISPOSITION

14 examined + 8 lineage-excluded + 1 prohibited + 486 metadata-only = 509

14 examined8 lineage1 prohibited486 metadata-only

The safe-object metadata sum is 2,983,161,063 rows across mirrors, derived objects and staging. It is non-deduplicated and is not a count of distinct facts, customers or evidentiary coverage.

01

live + retained

BigQuery mysterium-bq

24 datasets · 509 objects · 14 direct leaves examined; 486 objects remain metadata-only.
02

retained

CJ advertiser commissions

205 rows; account census and source retention horizon unproved.
03

retained

impact.com advertiser reporting

1,037 rows across 33 months; selector and UI parity unproved.
04

retained

Omnisend campaigns

16 campaigns; contacts, recipients and raw events outside the perimeter.
05

partial retained

Ahrefs API v3

Aggregate mapping only after a historical 401; no customer identity path.
06

retained

RichAds advertiser reporting

89 daily rows; account, currency, timezone and attribution semantics absent.
07

inaccessible

Mysterium business API

No current recognized credential; no evidence drawn.
08

inaccessible

GoProxies reseller reporting

No current recognized credential; no evidence drawn.
09

retained

Grafana / VictoriaMetrics

152 dashboards · 2,280 panels; live series and alert content not retained.
10

retained

ClickUp MN workspace

7,068 tasks; all comment endpoints attempted, with named body-level omissions.
11

inaccessible

Pipedrive sales CRM

Historical 401; no accepted source objects.
12

derived index

Slack public-channel export

1,085,280 messages; source ZIP and linked bodies are not exhausted.

SELECTED CASE · 02

A journey with one recorded point.

The first trustworthy observation inside the left-censored 2026 root frame is an account row at DATE grain. Person identity, timezone, first-ever status and every later outcome remain unknown.

CASE TOKENCJ6-000014f4f5e0

Recorded: 2026-03-15 · IOS · one account observation

Decision: treat as a missing-observability result; do not personalize, price, entitle or infer performance.

01Account

Recorded root

02Subscription

No accepted event

03Entitlement

No accepted event

04Product attempt

No accepted event

05Support

No accepted event

06Customer outcome

No accepted event

07Lifecycle

No accepted event

08Economics

No accepted event

09Exposure / experiment

No accepted event

TWO VIEWS · DO NOT MERGE THEM

Population capability versus case evidence.

Identity

Account, subscription and contact identity-shaped sources exist.

1attributable root
Product telemetry

App, session, connection, raw analytics and Grafana leaves are named.

0attributable case events
Payments + economics

Subscription events and advertiser aggregates are populated.

0attributable case events
Support

Three Intercom workspaces plus retained ClickUp and Slack evidence are populated.

0attributable case events
Experiments + actions

Campaign, ad, web-event, ClickUp and Slack sources exist.

0attributable case events
Customer evidence

Intercom text, ClickUp comments and Slack messages exist at population scope.

0attributable case events
STREAM \ STAGEAccountSubscriptionEntitlementProduct attemptSupportCustomer outcomeLifecycleEconomicsExposure / experiment
IdentityRECORDEDone rootno accepted eventno accepted eventno accepted eventno accepted eventno accepted eventno accepted eventno accepted eventno accepted event
Product telemetryno accepted eventno accepted eventno accepted eventno accepted eventno accepted eventno accepted eventno accepted eventno accepted eventno accepted event
Payments + economicsno accepted eventno accepted eventno accepted eventno accepted eventno accepted eventno accepted eventno accepted eventno accepted eventno accepted event
Supportno accepted eventno accepted eventno accepted eventno accepted eventno accepted eventno accepted eventno accepted eventno accepted eventno accepted event
Experiments + actionsno accepted eventno accepted eventno accepted eventno accepted eventno accepted eventno accepted eventno accepted eventno accepted eventno accepted event
Customer evidenceno accepted eventno accepted eventno accepted eventno accepted eventno accepted eventno accepted eventno accepted eventno accepted eventno accepted event

LIVE REPLAY + REVIEW · 03

The frozen draw survived a later live read.

The replay re-read only four selected safe BigQuery objects. It did not replace the frozen denominator, and it did not turn changed projections into an explanation.

183 instrumented BigQuery API GETs0 non-GET0 query jobs0 writes0 prohibited-object requestsall terminal pages observed
LIVE LEAFLIVE ROWSROOT INTERSECTIONSELECTED MATCHESDELTA FROM FREEZE
Account root242,703N/A — root self1+1,163
Subscriptions659,88848,0490+414
Subscription events10,853,75548,2350+38,948
VPN contacts884,39740,7670+306
PROCESS

PASS

Fable 5.1 · high effort · 51/51 fixtures · reviewer-tested.

Certifies the process only; it does not certify data-room exhaustion or a customer outcome.
EXECUTION

PASS WITH LIMITS

Claude Opus 5 · max effort · sealed 28-file corpus · read-only native CLI.

All 18 findings were integrated or preserved as dissent; eight cosmetic residues remain recorded.
BOUNDARY

NO OUTCOME CLAIM

No independent provider channel or billing invoice was inspected.

Exact-byte local search did not normalize variants; retained Intercom has a 92,061-part residual.

TARGET SYSTEM MAP · 04

Six views could become one journey.

No single stream answers the whole business question. Connect their source records through evidenced identities and time—without turning missing links into invented certainty.

Open an example evidence envelope. Hover to preview · click or tap to keep open · Enter to open · Esc to close.

GOVERNED CUSTOMER ID + TIME

Full Customer Journey

Every event keeps its source, timestamp, semantic status and confidence.

OUTPUT

Decisions

Fix the right failure. Measure the result. Learn once for everyone.

SYNTHETIC TEACHING MODEL · 05

Watch one fictional fact enter the chain.

This twelve-scene journey is synthetic. The systems and semantic risks are real MN surfaces; the customer and events are not a real record.

SCENE 01 / 12

ACTIVE FEEDS Identity · Experiments + actions

09:00

Acquisition

“I need my work dashboard to function safely on hotel Wi-Fi.”

Current MN fit: attribution path is partial

IdentityProduct telemetryPayments + economicsSupportExperiments + actionsCustomer evidence
SOURCE FACTcampaign_click { click_id: c-19, campaign: travel-01 }

Kept at source grain. The raw fact is never overwritten by a later interpretation.

EVENT ENVELOPEevent_id e-001 · schema v1 · occurred 09:00 · received 09:00 · quality observed

Source, schema, timestamps, quality and privacy state travel with the event.

IDENTITY EDGEvisitor v-19 ↔ install i-77 · valid from 09:00 · deterministic

The relationship is versioned. Unknown or conflicting links remain visible.

TECHNICALUnknown
CUSTOMER JOBKnown intent; outcome unknown
ECONOMICSNo payment yet
BURDENNone observed
ROLE IN THE ROOM

Indrė G. · recorded Head of Digital Performance

“A click tells me the campaign created a visit. It does not tell me whether this person became a successful, retained or profitable customer.”

Fictional dialogue for teaching. This is not a recorded quote or real assignment.

DECISION BOUNDARY

Can decidePreserve the campaign and click identity for later attribution.

Cannot claim“This campaign acquires good customers.”

OWNER
Growth owner + Data identity owner
WHEN TRUTH MATURES
After signup, product outcome, D30/D90 retention and contribution
WHY THIS SCENE MATTERS

Identity is not a customer fact. It is the governed claim that facts from different systems belong to the same journey.

Use buttons, swipe the rail, or press ← →

OPERATING MODEL · 06

The journey is a data product—not one giant table.

Source systems keep their native grain. A governed identity layer connects them. Semantic models calculate customer, product, support and economic outcomes without destroying the raw record.

05
DECISION PRODUCTS

Cohorts · journey viewer · failure queues · experiment readouts · case economics

04
SEMANTIC MODELS

Technical success · job success · activation · retention · contribution · support burden

03
IDENTITY + TIME

Versioned edges · source grain · occurred/received time · effective dates · conflict states

02
QUALITY + GOVERNANCE

Contracts · tests · lineage · access classes · retention · late-event policy

01
SOURCE-OWNED FACTS

Auth · app/network · payments · support · surveys · campaign and experiment exposure

TOOL / SYSTEMROLESTATUSWHAT IT CONTRIBUTES
BigQuery · mysterium-bqWarehouseObserved MN surfaceRaw and transformed records. Object-specific permissions and meaning apply; the excluded purchases table is not a default source.
App_usage + Grafana + VictoriaMetricsProduct telemetryObserved / partialActivity and operational telemetry exist; attempt-level semantics still need a named contract.
Intercom + BigQuery mirrorsSupportObserved / partialConversation records exist; identity, resolution and labour need governed definitions.
Mr Universe → export → BigQuery → Looker/ClaudeCommercial pipelineObserved / partialExisting route with a manual export seam and Airbyte monitoring.
Governed identity graphCross-system spineProposedVersioned edges preserve direction, cardinality, provenance and conflicts.
Exposure + decision ledgerLearning loopProposedRecords eligibility, treatment, holdout, owner, metrics, maturity and the final decision.

IMPLEMENTATION · 07

Start with the facts that time can destroy.

First test what existing records can already reconstruct, while preserving facts that would otherwise expire. Add collection only where a necessary fact is genuinely missing. The timings below are illustrative planning ranges, not an audited MN delivery estimate.

01

Now · 1–2 weeks

Preserve

Keep irreversible raw facts: source IDs, result codes, timestamps, recorded handle time and source lineage.

02

Parallel · 2–4 weeks

Define

Simonas and source owners write the identity, payment, attempt, support, lifecycle and economics contracts.

03

4–8 weeks

Join

Reuse or repair existing event records and identity edges; add quality tests and one traceable customer case.

04

6–12 weeks

Close

Add minimal customer-job evidence, case-level contribution and support burden without retaining needless private text.

05

10–16 weeks

Learn

Commission exposure records, holdouts, outcome windows and keep/kill/revise decision receipts.

THE 90 / 10 MOVE

Instrument the irreversible seams first.

  1. Stable attempt IDsConnect client, network, customer check and support episode.
  2. Raw source result codesFuture semantic fixes can reinterpret history instead of losing it.
  3. Governed payment Day 0Choose the settlement state and retain processor/store timestamps.
  4. Support timestamps + recorded handle timeExpose the hidden labour burden around product failure.
  5. One minimal job-success checkSeparate a live tunnel from a customer whose problem was solved.

EVIDENCE DISCIPLINE · 08

Every claim carries its own limits.

Observed MN surface

A source or role confirmed in the existing reconstruction record.

Exists, not fully commissioned

A surface is present, but governed use or semantics remain incomplete.

Proposed

An implementation choice, not a statement of current MN capability.

Synthetic

A teaching example. Never evidence about a real customer.

THE RULE

Missing evidence stays missing. It never silently becomes zero, success, failure, retention, profit or causality.