Legibility and Illegibility for Operators
Source-grounded pack with Legibility Audit, Legible Decision Package, and Strategic Illegibility Check, plus 1 more.
Get this packGrounded in the complete Legibility and Illegibility for Operators series.
Open the pack, choose a workflow, and follow its setup and input instructions. You can also open each workflow below.
10 source essays · 4 usable skills · reviewed Jul 2026
Use this pack when
Choose this pack when the work touches Legibility and Illegibility for Operators and you need a bounded workflow with explicit inputs, a defined output, and human review gates.
Choose the job in front of you.
4 source-grounded skills. Load one workflow at a time.
Legibility Audit
Use this workflow when work feels foggy, leadership requests more visibility, a dashboard creates suspicious certainty, a project slips, discovery is being strangled by reporting, or sensitive issues hide inside polite updates—and the operator must decide what becomes clear, stays protected, or needs translation.
Output specification
Return a work-type finding, audience/decision map, visibility purpose, compression losses, incentive and power effects, privacy/opacity assessment, chosen artifact, protected context, translation trigger, owner, and review date.
Legible Decision Package
Use this workflow when messy local reality must be translated—not dumped or overcompressed—into an audience-specific decision memo, options frame, exception report, risk brief, dependency map, escalation, or conflict readout that preserves material uncertainty, ownership, tradeoffs, and protected context.
Output specification
Return a decision-ready artifact with audience and action, evidence, epistemic states, interpretation, options, tradeoffs, dependencies, risks, owner, decision needed, timing, protected context, compression losses, and escalation.
Strategic Illegibility Check
Use this workflow when option value, local intelligence, trust, sensitive conflict, tacit craft, experimentation, or emerging strategy needs temporary protection—and the operator must distinguish disciplined privacy with learning and translation from hidden blockers, shadow priorities, informal vetoes, or power avoiding consequence.
Output specification
Return a protection rationale, boundary, owner, learning or craft method, confidentiality finding, opacity-risk scan, decision, translation artifact, trigger, affected-owner communication, and review date.
Visibility System Design
Use this workflow when designing or repairing dashboards, metrics, trackers, documentation, scorecards, or reporting systems so they support the correct decision grain, preserve interpretation and uncertainty, expose dependencies and ownership, and avoid surveillance, metric gaming, proof-of-work, or premature standardization.
Output specification
Return an audience/decision design, metric contracts, interpretation layer, commitments, dependencies, risks, ownership, removed surveillance fields, craft rails and learning method, incentive forecast, pilot, and retirement rule.
Keep consequential decisions explicit.
These workflows structure analysis and artifacts; they do not authorize autonomous external, personnel, financial, legal, security, or other high-impact action.