Behavioral Specs

INV-format invariant contracts for jackin' subsystems targeted for structural refactor. Each spec names the invariants that must be preserved when a file or module is split or extracted into a crate.

Available specs

• auth source-folder sync — the goal, evidence, and invariants for alternate agent credential/config folders.
• runtime/launch.rs — the jackin load critical-path pipeline (INV-1 through INV-6).
• op_picker — the 4-stage 1Password picker state machine (INV-1 through INV-4).

Purpose

A behavioral spec is the verification oracle for a refactor. Without it, there is no contract against which to verify that a split preserved all invariants. Specs must exist before the corresponding file is split; writing them first forces explicit articulation of what the code promises.