Framework overview

Clarity is a framework for examining beliefs before they harden into action.

Clarity is a framework for making beliefs, assumptions, evidence, confidence, ownership, and reassessment explicit so people can adapt when reality changes.

Claim

A claim is a belief stated clearly enough to examine, challenge, support, or revise.

Posture

Clarity uses three postures: Discovery for exploration, Commitment for active reliance, and Reassessment for checking whether a prior commitment still fits reality.

Evidence

Evidence is what currently supports a claim. It may be direct observation, data, tests, history, or constrained experience.

Assumption

Assumptions are the unstated supports beneath a claim. Clarity tries to surface them before they become invisible sources of failure.

Confidence Debt

Confidence debt accumulates when an organization acts with more certainty than its evidence justifies.

Action Trigger

An action trigger is a condition that causes an immediate predefined response before deeper review.

Reassessment Trigger

A reassessment trigger is a condition that should force a claim, assumption, or commitment back into review.

Adaptation

Adaptation is the practical end state: beliefs change, commitments change, and behavior changes with them.

How the pieces relate

Claim → Evidence → Assumptions → Confidence → Ownership → Reassessment → Adaptation

Discovery

Use this posture when the organization is still learning what might be true. The emphasis is on exposing claims and assumptions, not defending them.

Commitment

Use this posture when a team is actively relying on a belief to guide execution, allocation, or policy.

Reassessment

Use this posture when time, evidence, or outcomes suggest a previously accepted belief may no longer hold.

Decision Posture still matters inside Clarity, but now as one concept within a broader system for making claims, assumptions, evidence, confidence, ownership, and reassessment explicit.

Two Trigger Types

A trigger is a predefined condition that prevents teams from continuing blindly when reality changes.

Not every trigger exists to create reflection. Some triggers force immediate action. Others force reassessment. Both support adaptation.

Action triggers help prevent damage. Reassessment triggers help update beliefs.

Deployment Example

Scenario: A team deploys a new release.

Claim: This release is production-ready.

Evidence: Automated tests passed, QA completed validation, and no critical defects remain open.

Confidence: Moderate to High.

Action Trigger: 20 production errors within 10 minutes after deployment.

Immediate Action: Roll back the deployment and notify the on-call engineer.

Reassessment Trigger: Root cause analysis identifies a release-related defect or a gap in test coverage.

Reassessment: Review the claim that the release process was sufficient.

Clarity Observation: The action trigger protects the system immediately. The reassessment trigger improves future reasoning.