𝑖SIP

ASIP works because authority flows in one direction and data flows back in the other. 𝑖SIP inherits that shape exactly.

Integrity comes from the Latin integer — in- plus tangere, untouched. Whole because nothing has been taken away, and undivided because it was never cut. English never split the engineering sense from the moral sense — structural integrity and personal integrity are the same word describing the same property of two different structures. That is the single strongest piece of evidence that 𝑖SIP is a transfer rather than a metaphor.

Undividedness, though, is not purity. 0 and 1 are both required. A structure that can only output 1 — only yes, only expansion, only light — is not whole. It is stuck. Wholeness is the capacity to hold both halves across the 𝑖-axis, and the loss of integrity is the amputation of one of them.

You can be entirely undamaged and entirely divided. You can also be perfectly coherent and badly worn. Most people arriving at this program are both at once — and a program with only one word for it can only see half of what is wrong. A person who says yes while meaning no is not integer. The yes and the no are two pieces. That makes people-pleasing a structural condition with a structural remedy, rather than a personality defect to be scolded out of.

A standard is written against a threat. This one's is specific, and naming it changes which tasks carry the most weight. The people this program is for tend to share some combination of nine traits:

In ASIP, the Major Command sets service life, planned usage, required readiness and budget. The System Program Office translates that into plans. They are deliberately separate functions, and the separation is what prevents a program from quietly redefining its mission to match whatever it happens to be achieving.

For this population, that separation has collapsed in a specific direction: MAJCOM has been outsourced. An employer, a family system, an institution, or an accumulated habit of deference is setting the usage — and the SPO, the person's own executive function, is loyally and competently translating someone else's requirements into plans. The planning is often excellent. That is precisely 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.

This has a hard programmatic consequence, and it is why the program has a Task 0: you cannot open at i5.1.2. Ask a person with a captured MAJCOM to declare their design service life and intended usage and they will faithfully declare someone else's — and every task built on that declaration will be rigorously executed against the wrong requirement. The analysis will be correct and the answer will be worthless.

Mapping the products onto the lattice makes the gaps visible. Ranking those gaps against the population makes the roadmap. The pattern: the existing line is strong at measurement and weak at commitment. Every product that tells a person about themselves is built. Every product that requires the person to declare something and be held to it is not. For a population whose defining failure is the inability to declare a limit, that is not a minor gap — it is the gap where the entire clinical value of the program sits.

One architectural decision unifies all of it, and it is build item zero: every 𝑖SIP instrument emits a structured output — a "form block" — into one personal record. The record is the Life Management Database (i5.4.6). Hindsight Daily is its daily accumulator and voice. The 𝑖SMP is its rendered display. A form block is small: which task produced it, when, and a handful of typed fields. Every existing page becomes an emitter by adding an export; every future page is designed as one. That is what turns a collection of interesting pages into a program that customizes itself from the person's own inputs.

The ordering is deliberate: authority before analysis, restriction before optimization.

Test pilots exceed limits professionally, and they are the most disciplined people on the airfield. The discipline is not in spite of the exceedance; it is what the exceedance requires. The method is the build-up approach: approach the boundary incrementally, never in one jump; stop at each increment and review the data before the next; brief the abort criteria before takeoff, when judgment is uncompromised; instrument everything, because an unmeasured excursion teaches nothing and costs the same; and fly it with a chase plane — someone whose only job is to see what you cannot see from inside the cockpit.

Run that way, exceedance stops being damage and becomes envelope expansion — and expansion has a reward prohibition never offers: the placards move. A limit set by analysis and then validated by instrumented flight test at higher load is a limit that gets formally raised. Feed the data to i5.5.3 and the certified envelope grows. You are not asked to stop. You are asked to qualify.

A-0 without A-1 produces concealment. A-1 without A-2 produces a person who only ever spends margin and never grows the envelope. The three are one instrument, and issuing only the prohibition is the failure mode this appendix exists to prevent.