Strategic Intent
What is the system trying to produce, and which priority governs when aims conflict?
Organizations do not usually fail because nobody noticed the symptom. They fail because different parts of the system assign it different meanings, protect different constraints and act from different versions of reality. The method makes that structure visible enough to examine, challenge and act from.

Intelligence is not the amount of information an organization possesses. It is its ability to sense what is happening, interpret it accurately and act without losing the meaning between those stages. Failure may occur in any transition.
The diagnostic follows the same sequence: evidence is sensed, interpretation is made explicit and intervention is tested against whether the system actually changed.
Systemic dissonance is the structural gap between what a system intends, what its participants perceive and what its behavior repeatedly produces.
Dissonance may appear as noise, friction, misalignment, drift or tension. These are system signals—not automatic loop classifications. A form of dissonance becomes a named pattern only when evidence supports assignment to the ClarityOS taxonomy.
Four diagnostic domains. A visible process problem may originate upstream in intent, authority, incentives, perception or interpretation. The Compass is a diagnostic frame, not a scoring device—and not every domain is equally responsible in every case.
What is the system trying to produce, and which priority governs when aims conflict?
Through what mechanisms, workflows and technologies does the system attempt to act?
What do people actually do, perceive, avoid, protect or compensate for?
How does the system sense, interpret, learn, decide and update?
Strategies, governance structures and processes describe how the organization intends to work. Decisions, incentives, exceptions and recurring behavior show how it actually works. The diagnostic begins where those versions diverge. Divergence is not automatically dishonesty—it may reflect missing information, incompatible constraints, informal authority, local adaptation, unresolved trade-offs, incentive design or the absence of an enforceable decision mechanism.
“We are prioritizing enterprise growth.”
Sales hears larger contracts. Product hears governance features. Engineering hears reliability. Finance hears higher margin.
Customer escalations and founder intervention determine priority.
The organization shares an aspiration, but not one operational ranking.
Every intake represents a vantage point. No stakeholder observes the whole organization. Different roles see different constraints. Disagreement may reveal missing data rather than resistance. An initial diagnosis may improve through challenge—model revision is part of the method, not evidence that the method failed.
A blind spot is not repaired by pretending the first account contained the whole organization.
Relevant evidence or stakeholder perspectives were not yet available.
The diagnosis contradicts evidence that was already available and sufficiently represented.
The interpretation is plausible, but the output states it more strongly than the evidence supports.
New evidence changes the strongest supported explanation.
Aurion does not only ask what caused a condition. It also asks what sequence allows the condition to reproduce itself. A diagnostic may describe a case-specific sequence without assigning a formal loop name. Recurring friction is not always random dysfunction—it may absorb an unresolved trade-off, protect an informal authority, preserve local autonomy or allow incompatible priorities to remain active.
Case mechanism · not a canonical patternDecision declared
Valid downside surfaces
The downside reopens the decision
Execution moves into unresolved dependencies
The deadline slips
Executive intervention declares the decision again
Where evidence supports a recurring mechanism that does not fit an active taxonomy category, the diagnosis uses Unclassified rather than forcing a name.
Formal ClarityOS pattern names and definitions are controlled terminology. Aurion publishes a term here only when its definition is ready for external use. Case-specific sequences can still describe a mechanism without assigning it an official category.
Evidence supports a recurring mechanism that does not yet fit an active taxonomy category.
Leverage is the change most likely to interrupt the regenerating mechanism—not the most visible symptom, the loudest complaint or the next available tool. Intervention is sequenced against that mechanism. Removing a symptom without understanding its function can move the problem rather than resolve it.
Validation signals are defined so leadership can determine whether the intervention changed the diagnosed mechanism—or whether the read must be revised.
Evidence is labeled by provenance. Observation and interpretation are kept separate. Single-perspective intake is recorded as such. Missing stakeholders are noted as blind spots rather than filled by inference. Uncertainty is stated when the evidence does not support a stronger claim.
A structural read is useful only when its evidence, assumptions and limits are visible. Stakeholders must be able to show where it is incomplete, which perspective is missing and what evidence would change the conclusion. The goal is not to make leadership agree with Aurion. It is to give leadership a model precise enough to examine, challenge and act from.
The first account could not see a relevant constraint.
The evidence did not support the initial causal jump.
Confidence was too high for the evidence scope.
The diagnosis changes and the earlier read remains traceable.
Disagreement is not automatically resistance. It may be missing evidence.