Understand Organon

Start with three distinct objects

Philosophy states adopted commitments, their meanings and conditions of application. Skills apply methods to tasks and remain revisable. Tools check and transform files; they do not decide philosophical correctness or reasons for adoption.

How an assessment starts

Identify the actual input and adopted philosophy, then state the question to assess. Examine reasons, conditions and scope; distinguish contradiction from insufficient support. When considering a revision, keep the preceding baseline identifiable. Compatibility does not warrant adoption, and conflict does not by itself defeat reasons for revision.

When change is needed

An ordinary assessment can end with a report. Absorption examines reasons for philosophical revision and implements it after explicit authorization. Wording review concerns expression; file management checks structure and identity. These methods have different responsibilities and do not replace one another’s judgments.

A map of the reading material

• Philosophy: commitments, meanings and limits.
• Rationale: arguments, alternatives and objections; no additional philosophical obligations.
• Lean reader: begin with claims, premises and boundaries, then inspect declarations and line explanations.
• Maintenance protocols: review, validation and release procedures for maintainers, in the repository’s maintenance/ directory.

What Lean can establish

Lean checks formal conclusions under given definitions and assumptions. Target accepted, kernel passed and source fidelity are different judgments; limited, incomplete and not_applicable retain their recorded meanings. Defining a duty does not show its fulfillment; a finite model does not establish universal real-world correctness. Readers unfamiliar with Lean can start with the claim overview and consult the paired code and explanation pages one line at a time.

Installation and adoption are separate

Project installation supplies method entrypoints for that project; global installation supplies user-level entrypoints. Neither adopts a philosophy automatically. A project selects its baseline through explicit initialization; updating, rolling back or uninstalling methods does not automatically change that decision. A domain collection requires an explicit domain choice.

Choose a method

Method	Purpose
organon-core-assess	Assess an input under the selected philosophy.
organon-core-absorb	Examine reasons for philosophical revision and carry out authorized adoption.
organon-core-principled-review	Analyze an object under the shared method’s stated standards.
organon-core-wording-review	Review wording without deciding philosophical adoption.