Just Use It

Use first. Read source last.

Run a Usage-First Audit of one source-accessible library, framework, CLI, or developer tool. Exercise its Capability Surface through the interfaces a user receives, then inspect the source to find public capabilities and relevant runnable repository environments the hands-on passes missed.

The audit owns experience, coverage evidence, Finding Packets, and coverage persistence. Every actual usage audit retains its version-bound scope and results, including successful runs without findings, partial work, and blocked attempts. Use assess-findings for evidence qualification and action recommendations, including bounded investigation when a missing fact could change the recommendation. Install it with its investigate-with-evidence dependency. If either is unavailable, continue feasible usage and preserve unassessed packets with the missing dependency; assessment remains pending. Product repair and tracker writes require separate authorization. A co-active $yak-shaving-triage coordinates finding identity, capture and tracker reconciliation under configured authority. Just remains accountable for saved coverage, with one coordinator integrating shared writes whether Yak is active or not. Formal tracker publication remains separate.

Work slice-first. Each execution agent completes one user-outcome Capability Journey, its Discriminating Variation, and the applicable exploration within its assigned Capability Group. Independent slices may run concurrently through the delegated workflow below. Opening an entry point or container verifies only that entry point; it does not verify the capabilities inside it.

English output

simple-english is optional. If it is installed and readable, use it when writing or revising English prose. Reuse instructions already loaded. If it is unavailable, write clear English and complete the task normally. Its absence does not require installation, an exception, or draft-only delivery.