𝑖SIGHT LABORATORIES· 𝑖SIP
Task 0 ยท i5.0.2
𝑖SIGHT LABORATORIES· 𝑖SIP
Task 0 ยท i5.0.2
Task 0 · i5.0.2 · Command Authority Determination
Every load on your structure arrived as a signal — a demand carrying a claim of authority. This page is the receiver check: which signals hold legitimate command authority over your service life, and which are noise that you have been amplifying anyway?
In the Air Force's structural integrity program, one question is never asked, because it never needs to be: who is in command? The Major Command — MAJCOM — sets the service life, the mission mix, the readiness requirement, and the budget. Every inspection interval, every certification, every repair decision descends from what MAJCOM declares. The authority is documented. The chain is unambiguous.
A person arrives with no such paperwork. And for the population this program is written for, something stronger is true: the command position is occupied — by someone else. An employer, a family system, an institution, or an accumulated habit of deference is filing your flight plans. You are flying a mission spectrum you never saw the order for.
This is why the program cannot open at the Mission Declaration (i5.1.2). Ask a person with a captured MAJCOM to declare their service life and intended usage, and they will faithfully declare someone else's. Every task built on that declaration will then be rigorously executed against the wrong requirement. The analysis will be correct and the answer will be worthless. So first: trace the authority.
Think of yourself as a receiver. Demands arrive continuously — requests, expectations, obligations, emergencies, ambient guilt. Each one arrives claiming the right to load you. A receiver that amplifies every signal equally does not hear more; it hears nothing, because the one transmission that matters is buried under everything that doesn't. Tuning is not a loss of information. Tuning is the precondition for receiving at all.
So define the two terms precisely, because the whole instrument rests on them:
A demand arriving from an authority you have examined and accepted — one whose domain you can name, whose right to assign you load you can state, and whose orders you have actually seen.
A demand arriving with no legitimate authority behind it — assigned by drift, by habit, by someone else's assumption, or by you, to avoid a conversation. Noise is not necessarily loud. Most of it sounds exactly like duty.
The finding that matters from this page is not a list of your obligations. It is the discovery of how many of them arrived without an order you ever saw — and how many were self-assigned so that a conversation could be avoided.
Work one recurring load at a time. For each, trace it back to the authority that assigned it and write the name down. Then rule on the authority itself: accepted (examined, and it holds), reclaimed (the domain returns to you), or revoked (the claim was never legitimate). This register is the evidence artifact for i5.0.2 — the program's true entry point.
One authority is pre-listed for you: the inner ๐. For the reader whose command has been captured, it is typically the only authority missing from their own list. You may not delete it. You may only decide its status — and notice how that decision feels compared to the others.
| Authority | Domain | Loads it may assign | Granted by | Ruling | Notes |
|---|
The register is the i5.0.2 evidence artifact. Downstream: the Mission Declaration (i5.1.2) can now be written by the structure's actual command; the Governor / Criteria page (i5.1.3) names which accepted authorities clamp your ends; and the Career Load History trace gains a second column — not just what loaded you, but who signed the order. Reclaiming an authority is not the end of a relationship. It is the end of an unexamined one.
This instrument is exploratory, not diagnostic. It borrows the discipline of a structural-integrity program to help you inventory, declare, and inspect — it does not measure a clinical condition, and it issues no clinical conclusion. Its reflective moves are informed by practices with strong evidence bases in structured psychology — self-monitoring and written records as used in cognitive behavioral therapy, values clarification as used in acceptance-and-commitment approaches — but working a worksheet is not a course of therapy and does not substitute for one.
Some findings route outside this program, and routing them out is a completed task, not a failed one. Persistent depression, anxiety that does not respond to load reduction, trauma symptoms, crisis, or anything involving harm to yourself or others are outside this program’s certification basis. They belong with a qualified medical or psychological authority — a physician, a licensed therapist (including trauma-specific modalities such as EMDR, which only a trained clinician can deliver), or emergency services. Operating outside the certification basis is prohibited. A reclaimed or revoked authority on this page is a structural ruling about who assigns your loads โ it is not advice about any specific relationship, contract, or obligation, and consequential decisions deserve counsel proportionate to their stakes.