IU72 panels

A 12-panel cognitive snapshot.

After a digest job succeeds you can open a second view: a single self-contained HTML page that lays out up to 72 indivisible units (IUs) across 12 panels, four rows of three. It is meant for visual review — a one-glance map of what the document actually says — alongside the linear Markdown digest you paste into your model.

How to open it

On any succeeded job in the dashboard, click View IU72 panels. The viewer loads the panel HTML in a sandboxed iframe and is signed for five minutes per session. IU72 generation is on by default for Pro and Business; Free plans see it for the first digest of each month.

The 12 panels

The pipeline derives each panel directly from the source — no model hallucination, no inferred filler. If the document does not provide content for a panel, that panel is sparse. The panel labels below describe the conventional reading order; the underlying archetype (analytical, narrative, instructive, persuasive) tunes the wording on the page.

1. P1Opening frame — the headline claim or thesis the document leads with.
2. P2Context block — actors, scope, time horizon, jurisdiction or market.
3. P3Driver — what changed or is changing that motivates the document.
4. P4Mechanism — the causal chain or process that explains how it works.
5. P5Evidence — the strongest supporting facts, figures, or citations.
6. P6Counter-evidence — caveats, dissenting findings, or limitations called out.
7. P7Quantification — numbers, ranges, KPIs, and material thresholds.
8. P8Stakeholders — who bears the cost, who captures the benefit, who decides.
9. P9Risks — the named downside scenarios and their triggers.
10. P10Decisions or commitments — actions taken, recommended, or required.
11. P11Open questions — what is unresolved, deferred, or flagged for follow-up.
12. P12Closing frame — the conclusion, ask, or call-to-action.

How it is rendered

The HTML is shipped as a static, script-free document with a Swiss high-load layout — heavy rules, monospace numerals, no interactive code. That keeps the artifact safe to embed anywhere and trivial to print. If you need machine-readable output, the same job also emits a CSV with one row per IU (id, panel_ref, archetype, proposition) and a JSON plan file.

Want the linear pipeline first? Read quick start.