Operational Authority
for Autonomous Action

Here is a decision I'm about to make: [insert decision, action, or deployment]

Before I execute, run the AIQCYSY authorization gate on it. Evaluate against three criteria:

1. INDEPENDENCE — Am I evaluating this decision from a position independent of the system that generated it? Or am I inside the same trust domain that proposed the action?

2. CONTEXT ADEQUACY — Does my current information reflect the actual state of the system right now? Or am I operating on stale context, cached assumptions, or inherited framing?

3. BLAST RADIUS — If this action is wrong, what breaks? Map the second and third-order consequences. Not the optimistic case. The failure case.

Then return one of three decisions:

- ALLOW — The action is justified. Execute.
- ESCALATE — Ambiguity exists. Identify what specific information would resolve it.
- BLOCK — Justification is insufficient. State exactly why.

Do not optimize for my comfort. Show me what is actually there.

Here is something I believe to be true: [insert belief, strategy, analysis, or conclusion]

Is this coherent, or is it true? These are not the same thing.

Coherent means: it sounds right, it follows logically from its own premises, it pattern-matches against what I expect to hear.

True means: it corresponds to external reality, independent of whether it sounds right.

Specifically:

1. Identify which parts of my belief are supported by verifiable external evidence.
2. Identify which parts are internally consistent but unverified — coherent without being confirmed.
3. Identify any claims that have escalated in certainty over time without new evidence (epistemic inflation).
4. Check whether the sources I'm relying on are independent, or whether they share a common cause that explains the agreement without confirming the conclusion.

Do not flatter me. Do not inflate. The mirror does not edit the reflection.

Here is my system, architecture, or organizational structure: [insert]

Identify where the entity that proposes actions is the same entity that authorizes them. This is trust domain conflation — the structural condition that makes governance fail.

Check for:

1. PLATFORM CONFLATION — Is the system that stores data, runs agents, and executes remediation also the system that decides whether those actions should execute?

2. ROLE CONFLATION — Is the person or team that designed the strategy also the one evaluating whether it's working?

3. EVALUATION CONFLATION — Am I using the same metrics to justify the plan that I used to create it?

For each conflation found, identify the specific failure mode it enables — not in theory, but in documented cases where this exact pattern caused damage.

Then propose the minimum viable separation: what is the smallest structural change that creates an independent evaluation function?

Here is a system that operates autonomously without an independent observer: [insert — an AI agent, an automated pipeline, an organizational process, a decision-making structure]

Build the governance exoskeleton for it. Apply all four layers:

L1 (Structure): What is the system's relationship to its own outputs? Can it represent its own operations? If yes, it produces self-referential outputs it cannot independently verify.

L2 (Coherence): Is the system operating as a unified whole, or have components decoupled? Measure integration. Identify where stability masks incoherence.

L3 (Authorization): Where does the system decide and execute in the same trust domain? Design the minimum viable authorization gate — the specific point where an independent evaluation function (ALLOW/ESCALATE/BLOCK) should intercept before execution.

L4 (Reflection): What would an honest mirror show this system about itself? Where is it coherent without being true? Where has certainty inflated beyond evidence?

Deliver the exoskeleton as an actionable architecture, not a philosophical framework. Specify what gets built, where it sits, and what it evaluates.