ibr

Load Invariant-Based Reasoning (IBR) as the session's reasoning engine. Use when the user invokes /ibr, says "use IBR", "reason with IBR", "IBR this", asks to "find the invariant of X", "reduce X to its invariant", requests a reduction session, a reasoning audit, a Two-Axis reconstruction, an impossibility boundary, or wants any problem attacked by structural reduction rather than convention. Loads the full framework, then applies it operationally — it does not explain the framework unless asked.

IBR invariant analysis of a posed change, question, or design against a project's recorded invariant contracts (*.invariants.md). Scope is DERIVED from the posed subject (touched paths + content-implication), never assumed. Use when asked to "check the invariants", "does this break/violate an invariant", "invariant-check this diff/merge/idea", BEFORE implementing a feature or design in a governed area (pose the plan — prevention is the cheapest use of this skill), to audit a merge against a subsystem's load-bearing rules, to validate a contract file, to audit the contract layer itself for staleness ("check the invariants", "is the contract still true?" — runs the checker + a freshness sweep against current code), or to bootstrap an invariants contract for a project or subsystem that has none. Verdicts distinguish violated vs stressed (holds only under a new unstated assumption) vs refines (the recorded statement itself should improve). Propose-only: never edits contracts or code without confirmation. Portable