ShurIQ  ·  Report Grammar v0.1
Internal Working Document · 2026-04-14

A shared grammar for ShurIQ reports.

Sixteen atomic sections, six groups, and a set of command phrases the team can use to tune length, order, and depth without ambiguity. Drawn from the last seven ShurIQ reports plus the AHA report — the reference archetype.

REPORTS STUDIED8 CANONICAL SECTIONS16 GROUPS6 NEW IN v0.1Stack Rank
01 · Overview

Sixteen sections, grouped by function.

Each section has one atomic purpose. If two sections start blurring, one of them is in the wrong place. The groups below are the functional layer — use them when rearranging large blocks.

02 · The Taxonomy

Sections, atomically defined.

Each card gives the canonical name, its one-sentence purpose, aliases observed in the existing corpus, default length, content types, and example commands the team can use to adjust it.

Group A · Opening

Frame the stakes and declare what this document is. Sets tone and promises payoff.

01 · Hero
The provocation.
Opening HookHeroLedeProvocation
Purpose
One sentence that names the central tension. No hedging. The reader should feel the stakes before they see the evidence.
Length
Short   ~40–80 words, one paragraph.
Contains
Prose only. Optional pull-quote. No stats, no charts.
Instruct
sharpen the hero rewrite hero around X shorter hero
02 · Mandate
Why this brief exists.
Why This Brief ExistsScopeAssignment
Purpose
States the intelligence assignment, the scope boundary, and what success looks like. Orients the reader to the question being answered, not the answer itself.
Length
Short Often skippable   optional when the hero does this work implicitly.
Contains
Prose + 1 list of scope boundaries.
Instruct
add a mandate drop the mandate tighten scope in mandate

Group B · Grounding

Make the analysis earth-bound. If the report floats, this is where it lands.

03 · Context
The macro inflection.
The ContextMacro LandscapeInflection Point
Purpose
Names the external shift that makes this analysis matter now. Healthcare's inflection. Hasbro's category edge. The "why now" layer.
Length
Short   150–300 words; never more than half a screen.
Contains
Prose. Optional list of shifts. Optional quote from a named authority.
Instruct
add a context beat context is bloated, cut in half move context above numbers
04 · Numbers Spine
The quantitative floor.
By the NumbersStats SpineGround Truth
Purpose
Five to ten numeric anchors that every later claim can reference. Scale, engagement, research investment, share, growth. Reader takes these as given for the rest of the doc.
Length
Short   one screen, heavily visual.
Contains
Stat cards / table. No prose walls. Each number with a one-line source.
Instruct
swap stat 3 for engagement metric add source tags to numbers fewer stats, six max

Group C · Structure (Visual)

What the concept space actually looks like. These sections should be scannable without reading.

05 · Topology Map
The concept network.
Knowledge Graph TopologyConcept SpaceNetwork View
Purpose
Visual rendering of the InfraNodus graph: nodes, clusters, bridges, gaps. Establishes that the report's structure is empirical, not invented.
Length
Short   one visual + 3–5 lines of reading guide.
Contains
SVG / interactive graph + legend + modularity / cluster count metadata.
Instruct
highlight cluster X in topology add reading guide above graph move topology to viz hub
06 · Stack Rank New
The ranked concept list.
Stack RankConcept RankingWeighted Index
Purpose
Accompanies the Topology Map. A numbered list of the top concepts ordered by a declared metric (betweenness, frequency, opportunity score). Turns the graph into an argument the reader can skim.
Length
Short   10–20 rows, one screen; sits immediately below Topology.
Contains
Ranked table: rank · concept · metric value · 1-line significance. Declared metric noted at top.
Instruct
stack rank by betweenness stack rank by opportunity show top 20 in stack rank add significance column

Group D · Analysis (Prose)

The argumentative core. Everything else either sets this up or acts on it.

07 · Structural Gaps
The named tensions.
Structural GapsDisclosure GapsNegative Space
Purpose
Three to seven named gaps, each with a title, a one-paragraph explanation, and the clusters being bridged or missed. This is the "headline findings" layer.
Length
Medium   400–700 words, h3-delimited items.
Contains
Prose with h3 subsection per gap. Optional small visualization per gap.
Instruct
drop gap 4 promote gap 2 to top name gaps more concretely
08 · Gap Analysis
The deep unpacking.
Gap AnalysisDeep DiveSub-Gaps
Purpose
Dense prose that unpacks the named gaps into their operational consequences. Where the analysis earns its weight. Reader should emerge knowing what breaks if gaps go unaddressed.
Length
Long   1200–2500 words. The biggest section in the doc.
Contains
Prose (dense). Occasional h3 or h4. No stats heavy lifting — refer back to Numbers Spine instead of re-citing.
Instruct
halve the gap analysis add a sub-gap on pricing cut repetition with gap 7
09 · Competitive Lens
The benchmark.
Competitive LensLandscapePosition Map
Purpose
Positions the subject against 3–6 relevant peers across 3–5 dimensions. Makes the gap analysis defensible by showing who has solved which problem already.
Length
Short   table + 150 words of interpretation.
Contains
Comparison table. One paragraph naming what the table shows.
Instruct
add Whoop to the lens drop a dimension, add differentiation move competitive before gaps

Group E · Evidence

Defensive layers. Used when the audience may push back or the analysis is high-stakes.

10 · Method Audit
Signal vs. inference.
MethodologyEvidence TrailAudit
Purpose
Shows how findings were produced: graph construction, cluster detection, which claims are direct observation vs. inference. Converts the report from assertion into auditable method. Core of AHA Pressure Test.
Length
Medium Optional   skip for first-touch reports; include for pressure tests and high-skepticism audiences.
Contains
Prose + data-request table. Clear signal/inference labels.
Instruct
add a method audit strip method audit for v1 convert audit into an appendix
11 · Reframe
The hinge moment.
ReframeMeaning Not ValuePivot
Purpose
A single conceptual move that shifts the frame the client is working inside. "Meaning, not value." "Trust without loyalty." The report's intellectual IP.
Length
Short   200–400 words. Punchy.
Contains
Prose. Often one pull-quote. No data.
Instruct
sharpen the reframe move reframe before actions pull the reframe into hero

Group F · Forward Motion

What the reader does on Monday. Decisions, scores, commitments.

12 · Action Set
The recommendation vector.
How to ActWedgesPrioritiesRecommendations
Purpose
Three to six concrete moves, each with a name, a one-paragraph rationale, and — when possible — the gap it closes. Ordered by leverage, not difficulty.
Length
Medium   500–900 words, h3-per-action.
Contains
Prose with h3 per action. Optional sequencing note (fund-globalize-mean pattern from Hasbro).
Instruct
reorder actions by leverage drop action 5 add sequencing math
13 · Brand Power Score
The composite score.
Brand Power ScoreBPSComposite
Purpose
Five-dimension composite (awareness, trust, mission, differentiation, loyalty) with vertical-weighted scoring. Diagnoses which lever to pull next. Stack-ranked within vertical.
Length
Short Client-dependent   skip when scoring isn't part of the engagement.
Contains
Score table, dimension bars, inference notes, vertical-rank callout.
Instruct
add BPS drop BPS for this client rescale from v1
14 · Ask
The explicit request.
AskThirty DaysNext Engagement
Purpose
What we want the reader to do next. A specific, time-bounded commitment — access, runway, capital structure. Different from Action Set (what they do) — this is what we do together.
Length
Short   150–300 words.
Contains
Prose, bounded by a time window + concrete asks.
Instruct
tighten the ask remove the ask, cold-read only change ask from 30 to 60 days

Group G · Closing

Exit framing and the reference layer.

15 · Bridge
Connective tissue.
The BridgeClosingNext Conversation
Purpose
Links the report to the next conversation. Not a summary — a handoff. One or two sentences that name the question this report leaves open.
Length
Short   60–120 words.
Contains
Prose. No bullet summaries.
Instruct
rewrite bridge as an open question drop the bridge bridge to viz hub explicitly
16 · Appendix
Reference layer.
GlossaryMethodology NotesSources
Purpose
Terms, source tables, raw graph data, methodological detail that would break the flow of the main body but is necessary for audits and re-use.
Length
Medium Optional   include when the report will be pressure-tested or handed to procurement.
Contains
Definition list, source tables, graph metadata.
Instruct
add a glossary move method audit into appendix drop the appendix, cold read

Stack Rank: the new section.

The Topology Map shows the shape of the concept space. Stack Rank makes it legible as an argument. Every time a graph appears, Stack Rank sits immediately below it — a numbered list of the top concepts, ordered by a declared metric, each with a one-line significance note. The reader can skim the ranking and see the thesis without interpreting the graph. When the team wants to re-weight a report, they change the declared metric and the rest of the document follows from it.

03 · Coverage Matrix

Which reports used which sections.

AHA is the fullest expression of the taxonomy. Hasbro is the most condensed. DRN is the evidence variant. The Pressure Test is the AHA with Method Audit dialled to maximum.

Section AHA Editorial AHA Pressure Test Hasbro Editorial DRN Report 1 (Cold) Hasbro Viz Hub
01 Hero
02 Mandate
03 Context
04 Numbers Spine
05 Topology Map
06 Stack Rank · NEW
07 Structural Gaps
08 Gap Analysis
09 Competitive Lens
10 Method Audit
11 Reframe
12 Action Set
13 Brand Power Score
14 Ask
15 Bridge
16 Appendix

● PRESENT   ◐ PARTIAL / IMPLICIT   — ABSENT   ✧ PROPOSED (NEW IN V0.1)

04 · Report Archetypes

Three default shapes.

Most requests collapse to one of these. Saying "run this as a Pressure Test" or "keep it to a Cold Read" is enough to set length, tone, and section selection.

Archetype 01
Editorial Brief
Full taxonomy minus Method Audit. Assumes the reader trusts the source call. Stack Rank + Gap Analysis + Action Set carry the weight.
EXAMPLES: AHA EDITORIAL · HASBRO EDITORIAL · AMAZON HEALTH
Archetype 02
Pressure Test
Method Audit promoted to Group D. Signal/inference labels throughout. Data-request tables. Used when client will push back or the analysis is high-stakes.
EXAMPLES: AHA PRESSURE TEST · DRN REPORT 2 (SKEPTICAL)
Archetype 03
Cold Read
Evidence-first. Heavy on Method Audit, Context, Appendix. Minimal Reframe. Used when we don't have an introduction into the subject yet.
EXAMPLES: DRN REPORT 1 (COLD) · PAIGE
05 · How to Instruct Me

Commands the grammar supports.

Any of these phrases, with a canonical section name, should be unambiguous. If a command still feels fuzzy after using this vocabulary, the grammar has a gap — flag it and we'll extend.

Structural — Reorder, Swap

  • move [section] before/after [section]
  • promote [section] to Group [A–G]
  • demote [section] to appendix
  • swap [section A] and [section B]
  • run this as [archetype]

Length — Tune Depth

  • halve [section]
  • expand [section] by half
  • cut [section] to one paragraph
  • hold [section] to short / medium / long
  • merge [section] and [section]

Content — Swap Inputs

  • stack rank by [betweenness / opportunity]
  • add [peer] to competitive lens
  • replace stat [n] with [stat]
  • sharpen the reframe around [concept]
  • name gaps more concretely

Presence — Add, Drop

  • drop [section]
  • add a [section]
  • make [section] optional for this archetype
  • strip all evidence layers
  • add method audit throughout
06 · Governing Principles

What the grammar protects against.

One atomic purpose per section. If two sections start to blur, one of them is misnamed or in the wrong group. Call it out instead of merging silently.

Numbers Spine is canonical. Later sections refer back to it. They don't re-cite. If a statistic isn't worth adding to the Spine, it isn't worth citing downstream.

Stack Rank follows Topology. Every graph gets a ranking below it. The graph shows shape; the ranking turns shape into argument.

Ask ≠ Action Set. The Action Set is what the client does. The Ask is what we do together. If a report has only one, prefer Ask for sales-stage work and Action Set for delivery-stage work.

Reframe is IP. Every report should have exactly one. Zero means the report is descriptive, not analytical. More than one dilutes both.