A mission, a maintenance schedule, and a limit. That's all a jet gets.
Nobody ever issued you the three.
Not weak. Unlogged.
No account. Nothing is ever uploaded. About 10 minutes.
Metals. Ceramics. Polymers. Elastomers. Composites. Foams. Naturals. Seven families, thirty-eight properties, one genuinely fun hour deciding which one is you. Do you bend and come back, or hold rigid right up until you don't? Carry the load alone, or only in layers? Does heat make you soft, or make you stronger?
Nobody's grading you. It's a thought experiment with real materials science under it — the same property tables I've used on actual structures, pointed somewhere they were never meant to go.
Then we fly it. Fighter, sailplane, transport, aerobatic — trainer, rescue, test bed, depot. Same properties, eight completely different missions. Some materials thrive in one and come apart in the others. That's not a flaw. That's the whole point.
There's a mission that fits the airframe you actually are — your flight path, more lift than drag, where cruise doesn't take full power.
For twenty years I kept other people's jets airworthy. Not one of them fell out of the sky.
Every jet I touched had a logbook. I didn't.
The job that kept them flying is what wore me down — too steep for too long, on a flight plan that was never mine. I stalled the way airplanes do. So I gave myself the same rigor and the same tools I'd been handing out for two decades. The three.
2,395 days of log later, I'm the engineer and the airplane both.
This isn't medicine and I'm not a clinician. It's a program that was never meant for people, pointed at one anyway — half engineering, half art. I published it because it's mine, not because it's a prescription.
I'm not here to fix you. The songs that got me through the worst nights never fixed anything either. They just put somebody on my wing. A wingman doesn't take your controls. He confirms you're not alone up there.
Human performance, built on military-grade engineering — the same standards that keep million-dollar, high-performance aircraft flying for decades, adapted one-for-one to a human life. You are not weak, and you are not broken. You’ve just been flying without your paperwork. We issue it.
𝑖Sight Laboratories maintains 𝑖SIP — the inner-𝑖 Soundness & Integrity Program — and builds the instruments that let a person execute it. MIL-STD-1530D, the USAF Aircraft Structural Integrity Program, translated one-for-one onto a human life. Not aviation used as decoration: the arithmetic is actually the same. Declared service life. Uncontrolled loads. Known flaws you mostly cannot see. A catastrophic failure mode. Only the units change.
You are not weak, and you are not broken. You are uncertificated — operating without placards, on a mission you were never shown the order for. We issue the paperwork. What 𝑖Sight Laboratories offers you is a tail number in a managed fleet: aero-proven instruments to reconstruct what you were built for, measure what actually loads you, and convert your boundaries from preferences into certified limits. The discipline that keeps an airframe airworthy, aimed instead at the turbulence and gusts of life. Your downtime gets planned for, not just survived.
You don't get a label. You enter a lifecycle.
Layer 1 — the wave: one service life, rising and falling. Add the terrain →
Thirty-eight properties, seven archetypes. You find out what you are actually made of before anyone puts load on it.
Not a label — a spec sheet. Where you are strong, where you crack, and the load path you were built to carry.
Your result rendered as a card you can keep or post. Then the instruments that turn it into a maintenance plan.
Not ready yet? Get the weekly lab note — one instrument, one finding, one idea.
I'm Nathan G. Phillips — an aerospace structural engineer with nearly 20 years in fatigue and fracture mechanics, ASIP documentation, and the federal SBIR ecosystem. My career has taken me through Hill AFB, Northrop Grumman, the USAF, and Lockheed Martin.
At some point I started noticing that the same physical laws governing how materials fail under stress — yielding, fracturing, fatigue, creep — map remarkably well onto how people behave under pressure. 𝑖Sight Laboratories is the result of following that thread.
I build tools that help people understand themselves with the same rigor engineers apply to materials. Not soft self-help — frameworks with actual structure, rooted in measurable properties.
𝑖Sight Laboratories maintains the inner-𝑖 Soundness & Integrity Program and builds the instruments that let a person execute it — for people who accept every load applied to them. That second clause is not a market segment appended to a mission; it is what makes the first one specific enough to act on. These structures are not failing for lack of capability. They are failing for lack of a document that says no on their behalf. Read the program →
What 𝑖Sight Laboratories offers you is a tail number in a managed fleet — the discipline that keeps an airframe airworthy, aimed instead at the turbulence and gusts of life.
Aero-proven instruments to reconstruct what you were built for and measure what actually loads you. The working instruments are free, on the web, and log 100% on your device.
Your boundaries convert from preferences into certified never-exceed limits. A boundary stated as a preference is negotiable; a certified placard is not.
Your downtime gets planned for, not just survived — inspection intervals computed from how fast damage is actually growing, not from how guilty you feel.
The loop does not return you to where you started — it returns you with a larger envelope. Expansion flown like a test pilot, not a redliner.
A standard is written against a threat, and this one's is specific. The people 𝑖SIP is for tend to share some mix of nine traits — reflexive yes-sayers, people-pleasers, the easily exploited, people carrying anxiety or made to feel expendable, talented status-quo challengers, innovators who overcommit and burn out, tradespeople who over-sacrifice, and people who want rigorous tools while loving to dream past reason. Those are not nine problems. They are one failure mode: the structure accepts every load applied to it. No placards, no never-exceed limits, a load spectrum filed by other people — so every mission gets assigned, and every load becomes an ultimate load. Exploitation is a documentation gap, not a character flaw. Read who this standard is written for →
𝑖SIP is ASIP pointed inward — MIL-STD-1530D, flown over a person instead of an airframe. Fifty-two tasks translated one-for-one, plus a Task 0 the standard never needed, because aircraft arrive with a drawing package and a chain of command and people do not. Above all of it sits Insider Threat — the policy layer, where AFPD 63-1 sits above the standard: you are the load and the crack. Here's the induction sequence.
Never Task I. In ASIP, MAJCOM sets your service life, your mission mix and your readiness requirement — and for most people arriving here, MAJCOM has been outsourced. An employer, a family system, an institution or an accumulated habit of deference is filing the flight plans. Ask a person in that state to declare their design service life and they will faithfully declare someone else's, and every task above it gets rigorously executed against the wrong requirement. The analysis comes out correct and the answer comes out worthless. So first: inventory what you actually are, trace each recurring load back to the authority that assigned it, and write down a dated baseline before the program tells you where you should be.
Task I is where you decide what counts as success before you have any data — which is why it is the task most people skip and the one that invalidates everything downstream when skipped. i5.1.2 is the single most consequential number in the whole program: how long you intend to remain in service, doing what, as a mix with percentages. Declare it on Hindsight Daily’s Mission tab — walkthrough, 3:15. Then i5.1.3: name your clamps, your braces, and your assumed initial crookedness. If you don't set your margin deliberately, you're operating at 1.0 — and every load is an ultimate load.
Fifteen tasks — the largest and most analytical block. Characterize the material before you load it, then enumerate everything that loads it: the discipline here is completeness, not severity ranking. Ground-handling loads are unglamorous and they crack airplanes — commutes, admin, logistics, small obligations are usually missing from people's mental inventory entirely and are frequently the governing case. Then i5.2.6, damage tolerance: assume the largest flaw your self-inspection could have missed, estimate its growth under your actual spectrum, and inspect at half the remaining life. Insider Threat rendered as arithmetic.
Task III exists because analysis is a hypothesis. The test is where reality gets a vote — and when test and analysis disagree, the test wins and the analysis is updated. Stand up Hindsight 80/20 and log your load history; rainflow the ups and downs so accumulated fatigue surfaces before it grounds you; fly the model in Flight Test to find where you crack first. And keep the boundary straight: a crisis is a static test — it tells you your strength and nothing at all about your life. Surviving ultimate load says nothing about how many cycles at 40% you can take, and it is the 40% cycles that kill airframes. And Task III has a second half most people never reach — i5.3.2.1, the modal survey: thump the finished structure and time how long it rings. Not the drawings, the real thing. Everywhere else in the program the structure's properties are assumed and the wear on them is tracked; this is the one task that measures the properties. That is what the ring-down test reads out of your own record.
The throat. Everything before it is characterization; everything after it is operation, and everything upstream compresses into four artifacts: a Master Plan, a placard set, a certification basis, and the 𝑖SMP. Certification is dated, evidenced, conditional and revocable — a completely different object from self-esteem, and exactly what a person operating under the Insider Threat premise needs, because the premise denies you the option of trusting yourself on feel. And the placards are the flagship: a boundary stated as a preference is negotiable; a never-exceed limit is not.
Fifteen tasks, most of them "update" — which is the point. Task V is not maintenance in the sense of holding still; it is a running loop that continuously invalidates and rebuilds the analysis above it. Log, recompute, revise every interval, recertify when the mission changes. ASIP without Task V is a binder on a shelf — and a placard set issued once to a person who cannot say no will erode without an interval that re-issues it. One safeguard is built in and non-negotiable: inspection happens at the interval and not otherwise. Continuous self-monitoring couples with the thing it monitors and drives the instability.
Read the whole program — all 55 tasks →
Task 0's three sub-tasks are added under the licence of i5.5.15 — Others as Required, which exists in the standard precisely so a program can add what its structure requires. One further addition sits inside the lattice rather than beside it — i5.3.2.1, the Modal Survey — numbered as a sub-task of Pre-Flight Verification so the count of fifty-five does not move. The 52 translated tasks remain 1:1 with MIL-STD-1530D; the numbering keeps every addition visible. See the full lattice →
In the ASIP policy stack, nothing starts with the technical standard. It starts with AFPD 63-1, a policy directive that does exactly one thing: it states that an integrity program shall exist. It does not say how — it says that the alternative, running the fleet without one, is not permitted. 𝑖SIP needs the same thing at the top, and Insider Threat is it.
You are the load and the crack. The structure and the flaw are the same object.
Therefore no program built on the assumption of your own soundness can be trusted, and every program must be built on measurement instead. Once you accept that the flaw is already present and already yours, "inspection" stops being self-improvement and becomes crack detection. "Damage tolerance" stops being resilience-talk and becomes an operating posture: I will fly with a known flaw, on a known growth curve, under a known inspection interval, and I will not pretend otherwise.
The compensating half, from Converge to Diverge: this is not a sentence. The pinch in a nozzle is not damage — it is the precondition for thrust. A flaw under a managed program is what generates the very data that lets the structure be trusted. Ease cannot make a diamond. Pressure can.
Soundness is condition — am I whole, rested, undamaged, fit to fly? It fails as fatigue, corrosion, accumulated wear, burnout.
Integrity is coherence — Latin integer, untouched and undivided. It fails as saying yes while meaning no; as the outward answer and the inward answer no longer being the same object.
English never split the engineering sense of integrity from the moral sense. That is not a coincidence of vocabulary — it is the strongest evidence that 𝑖SIP is a transfer rather than a metaphor.
In ASIP, MAJCOM sets service life, planned usage, readiness and budget. The SPO translates that into plans. They are deliberately separate — and for the people this program is written for, MAJCOM has been outsourced. Someone else is filing the flight plans.
The planning is often excellent. That is what makes it hard to see. A well-run SPO serving a captured MAJCOM produces a person who is extremely effective at a life they did not choose, and who cannot work out why competence has not produced relief.
Which is why the program cannot open at i5.1.2, and why it has a Task 0.
Reflexive yes. People-pleasing. Being easy to exploit. Anxiety and depression. Being made to feel expendable. Talent that challenges the status quo. Innovators who overcommit. Tradespeople who over-sacrifice. Wanting rigorous tools and loving to dream past reason.
Those are not nine problems. They are one failure mode: the structure accepts every load applied to it — and in this standard's vocabulary, that is a missing Strength Summary & Operating Restrictions. No placards. No never-exceed limits. A load spectrum filed by other people.
Exploitation is a documentation gap, not a character flaw. If there is no SSOR, there is nothing for a demanding operator to violate.
Scope. 𝑖SIP is a structural integrity framework and not a substitute for medical or psychological care. Some findings — persistent depression, crisis, anxiety that does not respond to load reduction, anything involving harm — are outside its certification basis and require a qualified authority. Referring a finding to the correct authority is a completed task, not a failed one. In the US, the 988 Suicide & Crisis Lifeline is reachable by call or text at 988.
Every product here is a numbered task inside 𝑖SIP — not a standalone app that happens to share a logo. If a product cannot be assigned to a numbered task, it is either mis-scoped or it is revealing a task the standard hasn't articulated yet. That test is the discipline the standard exists to impose. The three divisions — HINDsight, 𝑖NSight, FOREsight — are the three time-domains every integrity program has to work in at once: what has been loaded onto me, what I am made of, and where the crack is going. See the full product-to-task map →
The quiz identified your material type — but within every material there are distinct grades. The Level-2 Deep-Dive is here: a precision 14-question category refinement, then a material-specific assessment that pinpoints your one specific material among its seven siblings — with a personalized multi-page persona report. One unlock, $24.99 — every category open.
Six input streams, six output products, one instrument in the middle — every box is a link. Tap any station to open it, or keep the map handy at its own page →
This is the Daily's map. Its companion — one characterization, five consumers — charts the Mind My Material line: the MmM map → · Every page in the fleet: the Hangar →
Eight brand films — six short silent spots, a two-minute silent 𝑖SRM explainer, and one 2:14 cut with original score. They play right in your browser — no downloads, just press of a link.
From philosophical memoir to illustrated allegory — the same ideas explored through different lenses.
An upcoming podcast exploring the science of materials as a lens on human behavior — hosted by an aerospace engineer who spent two decades studying how things break. Expect humor, depth, and a healthy disrespect for conventional self-help. Inspired by the format of Completely Arbitrary.
Early YouTube episodes are live now. Subscribe to be notified when the full podcast launches.
Nathan and his brother Doug interview guests to help uncover their unique gifts — probing questions, 30-day challenges, and stories of triumph and defeat. A Health & Fitness podcast active since 2014.
𝑖Sight Laboratories is independently built. Membership funds the instruments, the episodes, and the time to keep the record running.
Two paid rungs, on purpose. Every Observer perk is content that gets made anyway; the only new monthly obligation is the Analyst Deep Dive. Looking for the full Mind My Material breakdown instead? That is a one-time purchase over in the instruments — no membership required.
One instrument, one finding, one idea — from a record that now runs past 2,395 logged days. No noise.
Prefer to write instead? isightlaboratories@gmail.com reaches us directly.