Zagnetism

Journey audit for TidePilot daily operating brief

We think this is TidePilot's critical journey.

Confirm the business meaning, then Zagnetism audits the full path before monitoring is enabled.

01Arrives at activation entryReplay only
02Signs up or redeems entryProduct truth
03Reaches TodayReplay only
04Generates first useful briefProduct truth
05Acts on or shares the briefProduct truth
06Recipient opens or value is confirmedProduct truth
First useful briefActivation reached
  1. Step 1Connect behavior
  2. Step 2Connect product truth
  3. Step 3Confirm journey
  4. Step 4Review findings
  5. Step 5Enable monitoring
Audit run2026-06-25 15:00-2026-06-25 16:00 UTC

We already ran the audit.

Before you change a single setting, Zagnetism reviewed 4 behavior signals against TidePilot’s product truth, opened 3 cases, and ranked 3 findings.

4
behavior signals reviewed
3
cases opened
3
findings ranked
2
high or critical
3 backed by product truth3 linked to replay sessions
What we found

Zagnetism found these before you opened a log

Ranked by severity, each carries the durable evidence behind it and the one question only you can answer. Nothing is sent anywhere until you review them.

Top finding this window

Brief flow reached, but durable plan creation failed

HighConfirmed

Repeated no-plan result blocked first-brief generation (2 in window).

Bucket
UX friction
Affected users
1
Journey steps
first_brief
Product truth: Plan generation returned no_planLogRocket: LogRocket session filterFounder: Redacted user-friction summary

Suggested fix. Inspect the no-plan/provider branch and fallback handling before trusting first-brief conversion.

Should this be treated as a product bug, expected no-plan branch, or first-value definition issue?

Route share send failed before recipient delivery

HighConfirmed

Route share send failed before recipient delivery.

Bucket
Bug
Affected users
1
Journey steps
acts_or_shares
Product truth: Route share send failedLogRocket: LogRocket session filter

Suggested fix. Inspect share delivery provider status capture and error handling before enabling share follow-through alerts.

Should a failed share send wake up the founder during the TidePilot pilot?

Share follow-through needs durable open confirmation

MediumConfirmed

Route share was created with no recipient open evidence.

Bucket
UX friction
Affected users
1
Journey steps
acts_or_shares, recipient_value
Product truth: Route share has no open evidenceLogRocket: LogRocket session filter

Suggested fix. Decide whether recipient open is required for activation or belongs in a separate collaboration journey.

Is recipient open required for first value, or should it become a separate monitored journey?

Proposed journey

Activation to first useful brief

A TidePilot user is activated when they receive a useful operating brief and can act on or share it.

Primary success: First useful operating brief is generated and reaches follow-through.

  1. 1

    Arrives at activation entry

    Find the route into the TidePilot setup flow.

    Not yet measurableReplay signal only

    Behavior evidence

    Activation entry sessionsReplay can show the entry path and visible friction.lr:entry

    Product-truth evidence

    No durable proof for this step yet.

    Is this the right start of the journey?

  2. 2

    Signs up or redeems entry

    Create an account and enter the product.

    ConfirmedProven by product data

    Behavior evidence

    Signup path reachedReplay can show sign-up and redeem screens.lr:signup

    Product-truth evidence

    Durable account/redeem factsRead-only views can prove whether account and redeem outcomes exist.truth:signup

    Does signup plus redeem represent a real committed user?

  3. 3

    Reaches Today

    Reach the operating cockpit where the brief should become useful.

    Not yet measurableReplay signal only

    Behavior evidence

    Today sessionsReplay can show arrival and interaction on Today.lr:today

    Product-truth evidence

    No durable proof for this step yet.

    Is Today the first-value surface, or only a setup waypoint?

  4. 4

    Generates first useful brief

    Receive the first operating brief with enough substance to act.

    UnconfirmedProven by product data

    Behavior evidence

    Brief generation sessionsReplay can show the user reached the brief flow.lr:first-brief

    Product-truth evidence

    Plan and provider outcomesRead-only views show no-plan and provider-failed branches for the same journey window.truth:first-brief

    What durable fact proves the brief was actually useful?

  5. 5

    Acts on or shares the brief

    Use the brief or share it with someone who can act.

    UnconfirmedProven by product data

    Behavior evidence

    Share flow sessionsReplay can show whether the user attempted share follow-through.lr:share

    Product-truth evidence

    Share/send/open factsRead-only views can prove created, send_failed, and opened states.truth:share

    Is sharing the right follow-through signal for this pilot?

  6. 6

    Recipient opens or value is confirmed

    Confirm the brief produced value beyond initial generation.

    Not yet measurableProven by product data

    Behavior evidence

    Follow-through sessionsReplay may explain visible follow-through, if linked.lr:recipient-value

    Product-truth evidence

    Open or downstream value statusThe durable value proof needs founder confirmation before it becomes a monitoring signal.truth:recipient-value

    What is the earliest durable downstream value signal?

Sources

Connect what users did, and what actually happened

Behavior shows where sessions explain fallout. Product truth proves whether the journey actually succeeded. That pairing is the measurement upgrade over replay alone.

Behavior source

LogRocket

Session replay evidence for activation, Today, brief, and share follow-through.

replay sessions around drop-offroute and interaction contextvisible user friction signals

Review the preloaded replay evidence shape for the TidePilot design-partner demo.

Ready

PostHog

Optional analytics source for founders who already track funnels and product events there.

event funnel contextpath exploration contextcohort and conversion context

Skip for TidePilot's first pass, or connect later for analytics enrichment.

Available

Product truth

TidePilot product truth

Read-only Zagnetism views prove whether brief generation and share follow-through really happened.

durable plan and brief outcomesredacted user-friction factsshare/send/open status facts

Demo product-truth evidence is preloaded from safe fixture output; live read-only access is configured later through an approved path.

Ready

Alerting

Founder Slack alerts

Live outputs stay disabled until the founder reviews sample watch, recap, and destination behavior.

reviewed notification previewmanual enablement gate

Review the sample watch and recap experience here; live delivery is disabled for the hosted demo.

Review required

Connect your product truth

Behavior tools show what users did. Your database proves what actually happened. Connect a read-only source, describe the outcome that matters, and Zagnetism verifies it can trust your journey numbers.

1. Connect a read-only source

Used for this check only and then discarded. Never stored, never logged. Admin and service-role credentials are rejected.

2. Describe the outcome that proves success

3. Validate the view

Confirms the view is visible, correctly shaped, and read-only for the connected credential.

4. Enable scheduled monitoring

Monitoring re-checks your journey outcomes on a schedule, which requires storing this credential. It is encrypted before it is written, shown to you only as a fingerprint, and you can delete it here at any time. Deleting it stops monitoring.

Your call

Correct the business meaning

We drafted the journey from evidence. You decide what counts as first value, where the journey really ends, and which failure should wake you up tomorrow.

What proves a TidePilot user got first value?

Starting answer: First useful operating brief generated and available for action.

On step · acts_or_shares

Should sharing be part of activation, retention, or a separate collaboration journey?

Starting answer: Include it as follow-through for the first design-partner audit.

Which failure should wake up the founder tomorrow morning?

Starting answer: Durable no-plan/provider-failed outcomes after a user reaches the brief flow.

After the demo

The demo starts a pilot review, not the live operating loop.

A founder can use this page to decide whether the journey-audit loop is worth a real pilot. After safe setup is reviewed, Zagnetism should watch for high-confidence friction as it happens and send daily plus weekly recaps by default.

Confirm the critical journey

We compare Zagnetism's proposed journey with the founder's definition of first value, the durable outcome that proves it, and the known fallout points.

Send the first audit brief

The first useful output is a ranked review of what failed, how confident the evidence is, which sessions explain it, and what fix to try first.

Agree on verification

Before ongoing monitoring, we agree what number should move after the fix and which evidence proves the journey is healthier.

Real-time watch

Once active, high-confidence friction should surface as it occurs so the founder can remove it while the learning is still fresh.

Daily recap

A daily brief should summarize new friction, affected users, confidence, likely cause, and the next fix to try.

Weekly recap

A weekly recap should show patterns, verification movement, muted noise, and the biggest instrumentation gaps to close.

Draft email instead

This stores product context for review only. Do not include credentials, private tokens, raw user data, or admin database access.

Going through this demo does not connect Zagnetism to a product, enable live monitoring, or send alerts. The active defaults are real-time watch, daily recap, and weekly recap, each muteable after review.

Enable monitoring

Fast feedback, still reviewed

Once active, Zagnetism should watch the journey in near real time and recap what changed. Monitoring stays off until you have seen the sample output and chosen which default channels stay on.

Real-time watch plus daily and weekly recaps

Outputs off

Default outputs after approval

Destination

slackFounder review channel

Founder-visible preview

Demo preview only: no watch or recap will send

This hosted demo shows the founder-visible watch and recap shape. Live persistence, relay, and Slack delivery stay off until a separate reviewed gate is approved.

First live watch or recap still requires explicit approval