Put it on your home screen.

Hindsight Daily is a web app — nothing to download from an app store, nothing that phones home. Installing it just gives it an icon and a full screen.

After the first visit it works offline — in a canyon, on a flight, anywhere. Entries wait on the device; nothing needs a connection except the one-time unlock.

In a minute.

Wings don't fail from one terrible moment — they wear out from thousands of ordinary flexes. Engineers add those flexes up with an eighty-year-old method and read one number: how much of the structure's life has been spent.

This app points that method at a person. You give it one number a day — how are you, 0 to 10. Every swing between a good stretch and a hard one is one flex. The math (rainflow counting → Walker correction → S-N life curve → Miner's sum) does the rest, and the surprise it tends to find is the 80/20: the everyday swing, not the catastrophe, spends most of the life.

And since v2.0, the app carries the other half of the sentence: damage units measure what a life costs — missions name what it buys.

---

---

Thirty seconds, honestly spent.

1. 1Set the number. Drag the needle, tap a chip, or use half-steps — 0 is the floor, 10 is bullet-proof. Tap What the numbers mean for the full scale in plain words. Don't overthink it; the method reads the pattern, not the precision of one day.
2. 2Missed a day? Change the date field and backfill. Gaps are fine — the math never counts a swing across a long gap.
3. 3Note what mattered — optional, never analyzed, never uploaded. It's for the future reader of your record: you.
4. 4Save. The record block below shows days logged, streak, and median W — and, once your record is long enough, a one-line read of your acute pace against your baseline.

Log more than once in a day — each save adds an entry; the day stores the average and keeps every distinct note. Replace starts the day over for corrections.

---

Rate first. Level second.

dD/dt · 30-day	The sprint — damage deposited in the last month. Sensitive, a little noisy.
dD/dt · 365-day	The marathon pace, and the honest gauge. It appears once your record spans a year.
Damage index D	The running total. Uncalibrated until you set your own anchor (Data tab) — the app says so under the number.
Wellness trace	Your W over any window — 30d / 90d / 180d / 1y / All or any custom N. Remembered.
Year view	January–December of any year — daily dots plus a trailing moving average you pick.
D(t) curve	The accumulation over the full record, live from every entry.
Damage bands	Which size of swing is spending your life — amplitude is the lever.
Structure	New in v2.3 — a second life-model at the bottom of the tab; see below.

The pace alert. Every time you open Trends, the app compares your acute rate (last 30 days) against your baseline pace. Running hot (≥2× your chronic pace): the last month is spending life faster than your baseline — open the Report, protect the recovery days, and if it stays hot a few more weeks, say it out loud to someone you trust. Easing (≤0.5×): whatever changed is working. In between, the app stays quiet — steady flight needs no callout.

The flight profile. At the top of Trends the app reads your last 90 days like a usage spectrum and names the profile — Fighter, Sailplane, Transport, Aerobatic (or "ferry flight" when it's too quiet to call) — then checks the pairing against your Mind My Material family: Thrives · Serviceable · Mismatched. An opt-in toggle can even feed your material's own fatigue constants into the damage model.

---

What the spending buys.

D measures spending; the Mission tab names what the spending is for — the ASIP Task I move — 𝑖 SIP i5.1.2, deciding what the airframe is built to do.

1. 1Start a mission in three taps. Pick a spectrum — Fighter, Sailplane, Transport, Aerobatic, Trainer, Rescue, Test bed, Depot (✦ marks the ones your MmM material typically flies well) — name it in your own words, Start.
2. 2Dates live under an Advanced fold. Start defaults to today; an end date is only for logging past missions — so a whole life's record can be mapped from journals, retroactively.
3. 3Then, each day: one chip. "Did you build the mission today?" — −1 ran against it · 0 didn't engage · +1 built it. One tap saves it. The chips have their own date field, so backfilling engagement works like backfilling W.

One mission at a time; gaps between missions are allowed and never counted against you — ground time is preparation for engagement.

---

The service log, and the alignment map.

The service log lays your declared missions under the D(t) curve as amber bands — Mission 3 — 0.31 life-units over 2.1 years — a service log, not a diary. Every mission flown stays reviewable; sometimes the hangar was exactly the right call, and the log should say so without apology.

The alignment map is a 2×2, measured only against yourself. Across: 28-day mission engagement (the chips). Up: 30-day damage rate against your own chronic pace. You are the bright dot; the faint trail is your last twelve weeks.

Each week earns its trail point once it has three daily chips in its trailing 28 days — so a young record shows one dot, and the caption counts "Trail: n of 12 weeks" until the trail is full. Backfill chips from a journal and it fills in immediately.

No quadrant is red and none is green, because no quadrant is a verdict — and the tab stays silent when your last two weeks have been heavy.

---

The pacer, and return on damage.

The mission pacer. Edit a mission and mark a reference stretch — a spell when you were flying it well — and a pace strip appears on the current mission: your last month's damage rate against your own reference rate, behind / on pace / ahead.

Mismatch is the signal in both directions: above-pace on a Depot or Sailplane refit is the alarm ("the refit is running hot"); below-pace on a build mission means it isn't being flown. Pace is never a score to maximize, and the target only ever comes from your own record — never a lookup table.

Return on damage (experimental) folds at the bottom of the tab and starts reading within days of your first chips: engagement bought per life-unit spent over a trailing 28-day window, shown only against your own trailing median. There is no good number — only your own history.

---

Resonance — the natural-frequency check.

The instrument's third leg. D measures what the flying costs; the −1 / 0 / +1 chips measure whether the mission moved; resonance asks the question neither can: does flying this mission feed the airframe? On the days you tapped +1, did W run above or below your own baseline?

The headline is a mean ΔW — always shown with an approximate ± band, never a bare number — and beneath it the resonance response: your average W distance from baseline at each day around a built-it day, three days either side. The bars before day 0 are the honest direction check: if W is already up before you engage, the record reads "you fly when well" at least as much as "flying makes you well," and the caption says which side your record favors.

Three reads, and the band must clear zero before the copy commits to any of them: Resonating — the mission and your material appear to be answering each other. Reading level — no clear response either way yet. Holding on too tight? — engagement running against your own wellness. That last one is a question by design: some missions are worth what they cost, and only the pilot prices that. It follows the mission selector, so past missions replay their resonance too — sometimes the review says the expensive mission was feeding you all along.

---

A second opinion from fracture mechanics.

A fold at the bottom of Trends — folded to its title like every section since v2.6.1; tap to expand — runs a second life-model on the same days: a crack index a(t), grown cycle-by-cycle in time order (Paris' law with Wheeler retardation). Where the damage sum is sequence-blind, this track is sequence-dependent by construction — the same days in a different order give a different answer.

Hard stretches — your own worst 5% of swings, marked ▲ — temporarily slow the growth that follows. Retardation, not repair: nothing heals. A hard event changes how the ordinary cycles after it bite, for a finite while.

Set your anchor and the curve calibrates; everything after that date reads "Operating with known history" — the damage-tolerance frame: not undamaged, damage-tolerant.

"Next self-inspection by [date]" is the app's only forward-looking line, and it is maintenance language — when to look inside, the way airframes get scheduled inspections. Never a countdown: spent is knowable; remaining is not, and neither track ever shows remaining life.

---

How fast do you get back up?

Every other panel on Trends measures wear — damage piling up on a structure whose properties are taken as given. This one measures the structure. The damage and crack tracks are 𝑖SIP Task V, force management; the Modal Survey is i5.3.2.1, Task III — the ground vibration test, where engineers thump a finished airframe and time how long it rings.

Think of a marble in a bowl. Something knocks it up the side; the bowl pulls it back. Three separate things govern that, and the panel keeps them as three separate readings, never averaged into one:

Ring-down	The days it takes to shed about two-thirds of a knock — how steep the bowl is. Your recovery speed.
Set point	Where the bottom of the bowl sits: the level you return to, whatever today happened to be.
Daily jolt	How hard the table is being shaken — the size of a typical one-day swing.

Each prints with a range, because a bare number would claim a precision the record hasn't got. The ranges come from resampling your own day-pairs, and they are seeded from the record itself, so the same record always prints the same range.

The second analogy is the design choice, and it is the one that explains why a slow ring-down isn't simply "worse". A trainer is built stable — let go of the stick and it finds level on its own, predictably, slowly. A modern fighter is built with relaxed stability on purpose: the centre of gravity is moved aft until the airframe barely holds its own attitude, which is exactly what makes it quick, and it needs a flight control system correcting it many times a second to stay flyable. Neither is the better aircraft — they are different answers to different missions. A short ring-down is the trainer's virtue; a ring-down held short by effort is the fighter's, and it is worth knowing which one you are reading.

Below the gauges, the rolling survey shows how the ring-down and the set point have moved. Each point reads the 180 days centred on it, so the line lags real change by about three months — read the shape, not the day. The survey by mission fold runs the same fit inside each declared mission's own dates; short missions give wide ranges, and two numbers only differ meaningfully when their ranges don't overlap.

---

What actually works on you?

Every other tab keeps the flight log — where you went, what it cost. The Repair Bay keeps the maintenance record: which recovery procedures actually hold on you, and which well-meant ones read as maintenance-induced damage (mechanics call it hangar rash — the dents the maintenance itself puts in). The added burden is one tag on repairs you already log: what it was, its dose, and whether you did it to recover.

The Brief	First thing on the tab: your top three that read good, your top three reading as MID, and the effect ladder — signed bars in W with 95% whiskers. A whisker crossing zero means the record isn't sure yet.
Certified · 3 slots	Dose stated, interval stated, a positive read, and a survived coupon test. Your working repair manual.
Grounded · 3 slots	Done to recover, reads negative. Both halves required — a vice reading badly is not news; a remedy reading badly is.
In Test · 5 slots	Candidates, ranked, waiting on evidence. A full list always asks who gets displaced; everything ever tried keeps its verdict in the Service History archive.

The engine scores surprise, not mood: it subtracts what yesterday alone would predict (the Modal Survey's ring-down model) and compares only against days from the same era of your record — so neither momentum nor a hard year can masquerade as the procedure. Verdicts wait for five occurrences and print in plain words: reads good or reads bad, on the days you did it, the day after, or across the week after.

Two disciplines are program rules, not preferences. Coupon tests (i5.2.13) are declared before the run — dose, direction, schedule, and your falsifier in your own words — and the close reports only the declared comparison. Adherence is exception-based: every ON day is a dot on the coupon card; tap any you didn't actually run, and missed days are excluded at close with adherence printed beside the verdict (under 70% brands the run LOW ADHERENCE). And results recompute only when your inspection interval comes due (i5.2.10): watching a gauge continuously couples you to the gauge. Early reads are allowed, warned plainly, and logged.

Reading the history. Every behavior can be renamed and given a one-line description of what it measured — a rename carries its evidence with it, and renaming onto an existing name asks whether to merge (one all-time study) or keep separate as "#2", never silently. Same-named studies pool, and Detail keeps a by-period breakdown — practice stretches split on 90-day gaps, each judged against its own era — with a periods disagree flag when seasons contradict. The Brief toggles between the lists (curated) and the whole record (unvetted association, confound caveat attached; [Rx] entries print set-aside, never ranked). The archive sorts by certainty, best, worst, most recent, or most days, with a text filter.

The month, read like a service log.

Every calendar month builds its own report: coverage, damage deposited, the acute rate at month end, cycles closed, largest swing, hardest and strongest days, and a plain-language read.

1. 1Pick the month from the selector.
2. 2Save as PDF opens your phone's print sheet — choose "Save as PDF" and keep or share the file.
3. 3Month CSV exports just that month's rows.

The read to carry forward: does next month's acute rate rise or ease against this one?

---

It lives here. Nowhere else.

The monthly ritual — one tap. Your record exists only on this device — clearing the browser or losing the phone takes it. Once a month, Export backup file (or Share backup to email or cloud). A banner nags when a backup is missing or stale.

Restore — on a new phone, install the app and feed it the backup file. Everything returns: entries, notes, settings — and since v2.0, missions, daily engagement, the structure parameters — and, since v2.4, the repair log — ride along in the same file. Old backups restore into new versions and vice-versa; unknown keys are simply ignored.

Coverage & Gaps — answers "what am I missing?": span, days logged vs. missing, each gap listed by date range. Fill any day by hand from the Today tab — or auto-fill short gaps with straight-line estimates, each tagged and removable in one tap.

Add past data — import a CSV (date,W,note) or paste rows; days already logged are skipped unless you tick Overwrite.

Advanced — the model parameters, plus one honest button: set your own anchor date and Calibrate pins D = 1.0 to it. Until then, watch the rates.

---

Fourteen days, on the house.

The first fourteen days are free — the pill in the top corner counts them down. When the trial ends, the instrument locks; your record does not. The lock screen itself carries an export button, because your data is never the hostage.

1. 1Unlock Hindsight Daily takes you to secure checkout (Stripe).
2. 2After payment you land back in the app and it unlocks itself.
3. 3On a second device, or if anything hiccups: enter the email you paid with (or your code) under Purchased before? — it verifies online once, then never needs the network again.

One purchase, yours. No subscription, no account, no tracking.

---

What this instrument is not.

It is not a diagnosis. D is a gauge of accumulated load, read the way engineers read a wing — it is not a screening score, a clinical judgment, or a prediction. It cannot see a crisis. That includes the pace alert, the alignment map, and the structure view: they compare rates, nothing more.

Privacy	Every entry stays in this browser's storage on this device. Nothing is uploaded, synced, or seen by anyone — including the lab. The unlock check sends only a code or payment ID, never your record.
The catch	That privacy is also the risk: the device is the only copy. Hence the monthly backup ritual — the app will nag, and it means well.
Decimals	Half-steps are honored everywhere. A 6.5 kind of day is a 6.5.
Missed days	Expected. Log what you can; the method was built for irregular records.
Missions	Not goals, not scores. A mission is a name for what the spending is for — and "in the hangar" is a legitimate place for an airframe to be.
Go deeper	The Application Workbook runs the same pipeline with every formula exposed, and the full story is in Insider Threat, Volume II — "The Spar That Failed."

---

Prefer a document?

The same guide, laid out as a 14-page illustrated PDF — it downloads to your device rather than opening here, so you can keep it, print it, or read it anywhere.

↓ Download the PDF guide ▶ Or watch the walkthrough — 3:42