SHUR IQ | V3 Grammar Prep | Pre-Meeting Reading — Apr 28, 2026 // Internal Only
V3 Grammar Lockdown · Pre-Meeting Brief

Three drafts for tomorrow's V3 meeting.

The three open Bridge items from the V2 walkthrough, drafted as decision-ready working documents. Each ends with open questions for the meeting.

594 lines total · ~25 min read end-to-end · authored 2026-04-28

Nuri's V2 Call Additions — Pre-V3 Markup Extract

Purpose. Capture the contributions Nuri voiced during the 2026-04-22 walkthrough call so they can land in V3 alongside his pending Doc markup. This document stands in for the Doc-level markup until Nuri completes that pass; it is not a replacement for it.

Source. Transcript line numbers reference 00 Inbox/fiserve_gtm_meeting.md (Speaker 1 = Nuri).

1. Brand Power Score → Structural Advantage Score

Origin: transcript L186, L259–262.

The rename. Nuri ratified the change from "Brand Power Score" to "Structural Advantage Score" across all V3 surfaces.

The substantive shift. The metric becomes two-component:

"What's interesting about it is it kind of looks at your opportunity. The wealth of opportunity a brand has or a company has. ... Maybe that's one of the measures within the overall structure advantage score. The structure advantage, partly where do you sit today. But partly what your opportunity is really for growth."

V3 directive (proposed for §15 Brand Power Score → renamed §15 Structural Advantage Score):

Structural Advantage Score is a composite of two integrated subcomponents:
  · Present Position — the five-dimension diagnosis (awareness, trust,
    mission, differentiation, loyalty), normalized 0–100 against the
    vertical's stack rank.
  · Opportunity Wealth — the magnitude of structurally available
    growth, derived from gap density, competitive whitespace, and
    cross-vertical pattern data.

The composite reads as: "where you sit today + what you can become."
Action Set entries name the subcomponent they move.

Worked example (TruData, from call): present-position composite 56/100 → ranks 11 of 12 in vertical → Opportunity Wealth high (multiple structural gaps in migration narrative competitors haven't claimed) → Structural Advantage Score = composite (Present 56, Opportunity high) → Action Set targets the migration quadrant.

2. Stack Rank Should Be Dynamic, Not Frozen

Origin: transcript L232, L186.

Direct quote:

"What's currently called the brand power score in the stack rank, I agree should be dynamic. This is something we should be optimizing over time and adding... Improving the measure."

V3 directive (proposed addition to §03 Stack Rank — the concept-to-argument layer):

The stack-ranking metric is not frozen. It is reviewed at biweekly
delivery cycles and adjusted when:
  · A vertical's data accumulates beyond 4 weeks (longitudinal validity)
  · A new dimension surfaces from cross-vertical pattern recognition
  · An archetype demonstrates that an existing dimension is
    under-resolving differentiation between competitors

Document each metric change in the engagement cycle's session history.

3. Add a Peer to the Competitive Lens

Origin: transcript L235.

Direct quote:

"Add a peer to competitive lens. That's actually another interesting thing that we haven't done. Like let's basically comparing each brand to the field of peers. But we haven't done much like compare this brand to these two brands. Only these two."

V3 directive (proposed addition to §13 Competitive Lens):

The Competitive Lens supports two comparison modes:
  · Field comparison (default) — subject vs. 3–6 peers across 3–5
    dimensions. Defensible breadth.
  · Pair comparison (on demand) — subject vs. 1–2 named competitors
    only. Higher resolution. Used when:
      - Client has named the competitive set explicitly
      - Cold-read archetype is hooking into a specific rivalry
      - Pressure-test archetype is interrogating a specific claim

Pair comparison sets the dimension count at 5–8 (more granular)
and replaces the comparison table with a side-by-side card view.

4. Competitor-Set Recalibration (Future Module)

Origin: transcript L236–263. Brooks/Nike/Figs/Cherokee narrative.

The wedge. Companies fixate on the wrong competitive set. Careismatic targets Figs; Cherokee — a tenth Figs's size and structurally a closer comp — gets ignored. Brooks went up-market into super-premium runners while Nike abandoned the segment (post-Run-Club). The engine should call this when its data supports it.

Direct quote:

"There might be that ability for the tool to say okay you've identified B3 but you might want to think about these three because of, you know, whatever criterion."

V3 directive (NOT in V3 — flagged as roadmap, scope as new §13b Competitor-Set Recalibration sub-module):

[ROADMAP — six-week horizon, ~10th–11th client report data threshold]

Competitor-Set Recalibration surfaces when the engine's cross-vertical
pattern data shows the client's identified competitive set is
structurally mismatched to their position. Output:

  "You identified [A, B, C] as competitors. Given your structural
   position and dimensional gaps, [X, Y, Z] are the more relevant
   set because [criterion: size proximity / category-edge overlap /
   gap-pattern similarity]."

Do not surface in the first 9 client reports. Engine needs the
cross-vertical reference data first. After that data threshold,
make available as an opt-in module in the archetype selector.

5. Cold Read as Prospect Hook (Diana's Reframe, Nuri Ratified)

Origin: transcript L196–199. Diana introduced the amuse-bouche framing; Nuri ratified.

V3 directive (proposed refinement to §05 Report Archetypes → Archetype 03 · Cold Read):

Cold Read is the prospecting amuse-bouche. Tune for:
  · Length: shorter than Editorial Brief — target 60% of section count
  · Voice: more provocative, less hedged
  · Function: open dialogue, not deliver verdict
  · Reframe placement: latent (stated, not built around)
  · Editor's Letter: optional; if included, reduce diagnostic-to-dialogue
    move to a neutral close

Cold reads are prospecting moves. They are designed to make the
reader want a follow-up conversation, not to settle the question.

6. Score Before Prescription — Repetition Tension Acknowledged

Origin: transcript L209–211.

The tension. V2 directive 06.4 says "Score before prescription" — every action names the diagnostic dimension it addresses. Nuri agreed in principle but flagged a side effect: the rule generates restatements of the same insight across diagnostic + action set + ask sections.

Direct quote:

"There's a tension here with repetition of ideas and insights. So we have to figure out how to ride that wave. We don't want it to restate the same thing many times."

V3 directive (proposed refinement to §06.4):

Score before prescription. Diagnostic layer (BPS / Capability Index /
Maturity Map) precedes the Action Set. Each Action names the score
dimension it closes.

CAVEAT — anti-restatement rule: an insight stated in the Reframe or
Structural Gaps section is referenced by name in the Action Set, not
restated. The Action Set entry assumes the reader has the diagnostic
context. Restating dilutes both layers.

Test: read the Action Set in isolation. If an entry only makes sense
with the diagnostic preamble re-stated inline, the diagnostic was
under-named upstream — fix the upstream section, do not pad the
Action Set.

7. Ask Section as Sales-Stage CTA / Upsell

Origin: transcript L186–192. Nuri characterized Ask as "the upsell section."

Context: Jonny clarified that Action Set is "client does," Ask is "we do together." Nuri's contribution was on the commercial function of the Ask section.

V3 directive (proposed refinement to §17 Ask):

The Ask is the recurring revenue surface. Each Ask entry names:
  · Time-bound commitment (specific window)
  · Access required (data / personnel / runway)
  · Capital structure implication (retainer / project / equity)

Ask section function by archetype:
  · Editorial Brief — open the next conversation
  · Pressure Test — close the engagement decision
  · Cold Read — earn the next meeting

If a report ships without an Ask, it is delivery-stage work, not
sales-stage work. Mark the report archetype accordingly.

8. Intake Should Capture Assumed Competitors

Origin: transcript L237.

Direct quote:

"I was about to say that I think that's important to get from an intake. So if our process and it might be one of those, you know, additional modules that we add in or you know, what does the company [think]."

V3 process change (not a grammar directive; flag for intake template):

[INTAKE TEMPLATE ADDITION]

During intake, ask the client:
  · Who do you consider your top 3 competitors?
  · What is your target competitive position relative to them?
  · Have these competitors changed in the last 12 months?

Capture as engagement_cycle frontmatter:
  client_assumed_competitors: [Brand A, Brand B, Brand C]
  client_target_position: ""
  competitive_set_volatility: stable | shifting | unknown

This data feeds the Competitor-Set Recalibration module (§13b
roadmap) once the data threshold is hit.

9. Editorial Voice — Inside-Baseball Naming Hard Rule

Origin: transcript L201–203, L208–209. Nuri fully aligned with Jonny + Diana.

V3 directive (already in §06.2; reinforce):

AHA naming convention inherits to client surface unless explicitly
overridden. "Why this brief exists," "headline findings layer,"
"named tensions," and other inside-baseball labels demote to the
dashboard. They never appear on the report surface.

Override syntax: pass --label-style=internal to render with the
internal labels. Default render uses AHA-inherited labels.

10. Nuri's Pending Doc Markup

Status: Nuri committed during the call to mark up the V2 Doc directly. Pending as of 2026-04-28.

Recovery procedure when his markup arrives:

  1. Pull the Doc body via gws docs documents get --suggestionsViewMode SUGGESTIONS_INLINE (gdoc_id 1Z9DIcn-MnSv2koj6ToQcuDQoYtbblDkmkL2B2VbHz_s).
  2. Diff against grammar-v03.md.
  3. Cross-reference with the items in this document — anything Nuri added in the Doc that is NOT captured here is net-new and goes straight into V3.
  4. Update 2026-04-16-nuri-contributions-internalization.md Part A catalog with new comments / suggestions.
  5. Resolve conflicts with this document by Nuri's Doc edit taking precedence (his markup is the authoritative version).

Open Questions for the V3 Meeting

  1. Structural Advantage Score weights. Present Position vs. Opportunity Wealth — equal weighting, or Present-weighted? Nuri's framing implies Opportunity is the differentiator; weighting may want to favor it.
  2. Pair comparison threshold. When does the Competitive Lens default switch from field → pair? Client request only, or also auto-trigger when intake names 2–3 competitors explicitly?
  3. Ask archetype function. Confirm the three archetype × Ask functions (open / close / earn) — each may need a worked example.
  4. Anti-restatement test. Concrete: if an Action Set entry repeats the diagnostic, is the fix in the diagnostic section or the Action entry? The directive says upstream — confirm with a real edge case.

Archetype × Section Coverage Matrix — Prescriptive

Purpose. The V3 grammar treats the 19 sections as a superset that archetypes draw from. This document specifies, per archetype, which sections are MANDATORY, OPTIONAL, EXCLUDED, or CONDITIONAL. The engine reads the archetype, the archetype reads this matrix, and the matrix dictates the section set.

Distinction from grammar-v03 §04. That section is a retrospective coverage matrix — which sections were present in past reports (AHA, Hasbro, DRN). This document is prescriptive — which sections SHOULD be present in future reports of each archetype.

Legend

Symbol Meaning Engine behavior
● Mandatory Section ships in every report of this archetype. Engine errors if absent.
◐ Optional default-on Section ships unless explicitly excluded by command.
○ Optional default-off Section ships only when explicitly requested by command.
✦ Conditional Ships when a trigger condition is met (specified in §Triggers).
— Excluded Section does not ship in this archetype. Engine warns if explicitly requested.

Matrix

# Section Group Editorial Brief Pressure Test Cold Read
01 Hero A ● ● ●
02 Letter from the Editor A ● ● ○
03 How to Read This Report A ✦ ✦ —
04 Decision Snapshot A ✦ ● ○
05 Mandate A ● ● ◐
06 Context B ● ◐ ●
07 Numbers Spine B ● ◐ ●
08 Topology Map C ● ◐ ◐
09 Stack Rank C ◐ ● ◐
10 Reframe D ● ◐ ✦ (latent)
11 Structural Gaps D ● ● ●
12 Gap Analysis D ● ● ◐
13 Competitive Lens D ● ● ◐
13b Competitor-Set Recalibration D — — —
14 Method Audit E — ● ●
15 Structural Advantage Score F ● ◐ —
16 Action Set F ● ● ◐
17 Ask F ◐ ● ●
18 Bridge G ● ● ●
19 Appendix G ◐ ● ●

Counts (mandatory + default-on): - Editorial Brief: 14 sections (target depth) - Pressure Test: 13 sections (target — defensibility-weighted) - Cold Read: 9 sections (target — prospecting-tuned)

Triggers (✦ Conditional)

§03 How to Read This Report

  • Editorial Brief / Pressure Test: ships only when audience includes mixed reader modes (board + analyst together) AND length exceeds 4,000 words. Default for solo board or solo analyst audiences: omit.
  • Rationale: the Hero + Letter from the Editor handle reader routing in most cases. Adding §03 is redundant unless the document is genuinely bifurcated.

§04 Decision Snapshot

  • Editorial Brief: ships when audience includes a C-suite or board.
  • Pressure Test: mandatory always (defensibility-weighted; the snapshot is the audit-ready output).
  • Cold Read: ships only on explicit request — typically counterproductive for the prospecting function.

§10 Reframe (Cold Read mode)

  • The Reframe is latent in Cold Read — stated in the Editor's Letter (if present) or Hero, but the body does not build around it. Evidence does.
  • Trigger: archetype: cold-read automatically sets reframe-mode: latent.

§13b Competitor-Set Recalibration

  • Currently — (excluded) for all archetypes.
  • Becomes ○ (optional default-off) for Editorial Brief and Pressure Test once the engine has accumulated data on ≥10 client reports across ≥3 verticals (cross-vertical pattern threshold).
  • Tracked in engagement_cycle.md frontmatter: client_reports_completed: N and verticals_covered: [...].

Reader-Mode Tagging (closes Gap 01 from post-call analysis)

Every section in the matrix is also tagged with its primary reader mode. This is the bridge between the grammar (§02 Taxonomy) and the navigation system (§06.8 Navigation respects time).

# Section Primary Reader Skim Affordance
01 Hero Board + Operator + Analyst Headline reads in 8 seconds
02 Letter from the Editor Board Key Insights bullets carry the report for skimmers
03 How to Read This Report All (router) Sidebar layout
04 Decision Snapshot Board Three-column table
05 Mandate Board + Operator One-paragraph framing
06 Context Operator Pull-quote from inflection statement
07 Numbers Spine Operator Stat cards
08 Topology Map Analyst (with caption for Operator skim) Sidebar caption (see topology-caption-template)
09 Stack Rank Operator + Analyst Numbered list, scannable
10 Reframe Board + Operator Pull-quote callout (one per report)
11 Structural Gaps Operator + Analyst Named gap headers (3–7)
12 Gap Analysis Analyst Dense prose; no skim affordance by design
13 Competitive Lens Operator Comparison table
14 Method Audit Analyst Signal/inference labels in body
15 Structural Advantage Score Board + Operator Composite score + dimensional sparkline
16 Action Set Operator (executor) "Client does" prefix, H3 per action
17 Ask Board (decision) "We do together" prefix, time-bound list
18 Bridge Board + Operator Question-form one-liner
19 Appendix Analyst Reference layer, no body

Skimmer's path (Board reader, 10 minutes): Hero → Editor's Letter Key Insights → Decision Snapshot → Reframe pull-quote → Structural Advantage Score → Action Set / Ask → Bridge.

Operator's path (1 hour): full Hero → Letter → Mandate → Context → Numbers Spine → Reframe → all of Group D body → Structural Advantage Score → Action Set/Ask → Bridge.

Analyst's path (2+ hours): everything plus §14 Method Audit, §08 Topology Map deep read, §12 Gap Analysis full prose, §19 Appendix.

Engine Implementation Notes

Archetype declaration

The archetype is declared in the report frontmatter:

archetype: editorial-brief | pressure-test | cold-read
archetype_overrides:
  include: [03]    # force §03 even if not in archetype default
  exclude: [09]    # force omit even if mandatory

Conflict resolution

  • archetype_overrides.exclude cannot remove a mandatory (●) section without explicit --force flag (engine warning required).
  • archetype_overrides.include can promote any optional section regardless of archetype.
  • Conflicts between archetype defaults and triggers (✦): trigger wins.

Engine error states

  • Mandatory section absent → hard error, do not ship.
  • Excluded section present without archetype_overrides.include → warn, ship anyway with annotation.
  • Two sections with the same atomic purpose → hard error per §07 governing principle ("If two sections start to blur, one of them is misnamed").

Open Questions for the V3 Meeting

  1. §02 Letter from the Editor in Cold Read. Currently ○ (default-off). Diana's amuse-bouche framing implies the Letter IS the hook — argues for ◐ (default-on) instead. Decide.
  2. §13 Competitive Lens in Cold Read. Currently ◐. Cold reads often surface competitive context as the wedge — does this strengthen to ●?
  3. §17 Ask in Editorial Brief. Currently ◐. Per Nuri's "If a report ships without an Ask, it is delivery-stage work" — should this be ● mandatory for sales-stage Editorial Briefs and — for delivery-stage? If so, we need a sub-archetype split (Editorial Brief — Sales / Editorial Brief — Delivery).
  4. §13b Competitor-Set Recalibration threshold. ≥10 reports across ≥3 verticals — confirm the threshold or adjust. Could also be triggered by client request even before threshold.
  5. Reader-mode tagging accuracy. §10 Reframe is tagged Board+Operator — is the analyst expected to skip it? Or is it Board+Operator+Analyst at differing depths?

Topology Map Caption Template

Purpose. Every topology map ships with a magazine-style sidebar caption that explains what the reader is looking at in plain language. This closes Gap 03 from the 2026-04-22 post-call analysis: the topology map is internally cherished but externally quizzical without explanation.

Diana's framing (transcript L315):

"When you're in a magazine, there's something complicated, there's an infographic, but there's a little explanation. ... Our brains are so trained to ingest information this way."

Function. Three jobs, in this order: 1. Tell the reader what they are looking at (cluster topology, not flow chart). 2. Tell them how to read it (color = cluster, size = betweenness, edges = co-occurrence). 3. Surface the one strategic insight that makes the map worth reading for THIS report.

Template

<aside class="topo-aside">
  <h5>Reading the map</h5>

  <p><!-- WHAT --></p>
  <p>Each circle is a {{NODE_DEFINITION}}; size scales with
     {{SIZE_METRIC}} — {{SIZE_METRIC_PLAIN_LANGUAGE}}. Color groups
     indicate clusters: {{CLUSTER_LEGEND}}.</p>

  <p><!-- HOW --></p>
  <p>The heaviest gateway{{S}} — {{TOP_NODES}} — {{GATEWAY_DESCRIPTION}}.
     {{SECONDARY_NODE_COMMENTARY}}</p>

  <p><!-- WHY (this report) --></p>
  <p>{{ONE_INSIGHT}}</p>
</aside>

Variable definitions

Variable Source Example
NODE_DEFINITION Always: "concept that surfaced in {{CORPUS_TYPE}}" "concept that surfaced in the conversation"
SIZE_METRIC "betweenness centrality" or "frequency" depending on graph mode "betweenness centrality"
SIZE_METRIC_PLAIN_LANGUAGE One-line gloss of the metric "how often a concept bridges two otherwise-separate topics"
CLUSTER_LEGEND Auto-derived from cluster colors. List 3–5 most influential clusters with their semantic labels and color "cobalt for brand dimensions, warm for design archetypes, red for grammar insights"
TOP_NODES Top 1–3 nodes by betweenness centrality, with their BC scores "brand (BC 0.32) and design (BC 0.30)"
GATEWAY_DESCRIPTION What it means that these nodes are gateways — connect this to the report's reframe "are co-dominant. The call was structurally about how brand intelligence flows through the design system"
SECONDARY_NODE_COMMENTARY Optional. Highlight 1–2 lower-influence nodes that nonetheless matter for the strategic argument "Lens (BC 0.18) emerges third, connecting competitive analysis, gap analysis, and dimensional scoring"
ONE_INSIGHT One sentence. The strategic insight the topology surfaces for this specific report. Should connect to the Reframe. "The Brooks/Nike/Figs cluster (lower right) is the Pivot Thesis future module Nuri surfaced — small in volume but conceptually consequential"

Worked Examples

Example 1 — From the deployed Fiserv GTM brief

Reading the map

Each circle is a concept that surfaced in the conversation; size scales with betweenness centrality — how often a concept bridges two otherwise-separate topics. Color groups indicate clusters: cobalt for brand dimensions, warm for design archetypes, red for grammar insights, violet for topology & tools, green for navigation & reader-mode.

The two heaviest gateways — brand (BC 0.32) and design (BC 0.30) — are co-dominant. The call was structurally about how brand intelligence flows through the design system. Lens (BC 0.18) emerges third, connecting competitive analysis, gap analysis, and dimensional scoring.

The Brooks/Nike/Figs cluster (lower right) is the Pivot Thesis future module Nuri surfaced — small in volume but conceptually consequential.

Example 2 — Generic Editorial Brief skeleton

Reading the map

Each circle is a concept that surfaced in [the SERP analysis / the source corpus / the client's content]; size scales with betweenness centrality — how often a concept bridges two otherwise-separate topics. Color groups indicate clusters: [list 3–5].

The heaviest gateway — [TOP_NODE] (BC X.XX) — anchors the discourse. [WHAT_THIS_MEANS_FOR_REPORT].

[STRATEGIC_INSIGHT_ONE_SENTENCE].

Example 3 — Pressure Test variant (defensibility-weighted)

Reading the map

Each circle is a concept; size scales with betweenness centrality. Color = cluster.

The map is the audit trail for [SECTION_BEING_DEFENDED]. [TOP_NODES] are the gateway concepts the analysis rests on; if the data underneath these nodes is challenged, the gap analysis above [paragraph X] needs to be re-stated. [SECONDARY_NODES] are corroborative — they confirm the pattern without being load-bearing.

Inference vs. observation: nodes labeled with [convention TBD] are direct observations; unlabeled nodes are inferred from co-occurrence frequency.

Example 4 — Cold Read variant (hook-tuned)

Reading the map

Each circle is a concept that came up when we looked at [your category / your competitive set]. Size = how connected; color = cluster.

[TOP_NODE] is the gateway. The pattern around it is [ONE_LINE_OBSERVATION_THAT_CREATES_CURIOSITY].

Worth a longer conversation: [SPECIFIC_NODE_OR_CLUSTER] looks structurally [thinner / denser / mismatched] than we'd expect for a [VERTICAL_TYPE] of your size.

Style Rules

Rule Reason
Three paragraphs maximum Magazine sidebar discipline. Reader scans, doesn't study.
First paragraph defines, second describes, third points Diana's "what / how / why" structure.
Use the cluster's semantic label, not its color name only "brand dimensions" not just "cobalt cluster"
Bold the top 1–3 nodes with their BC scores Reader's eye finds the gateway concepts.
Italicize the strategic insight if it embeds the Reframe Visual signal that this is the pivot, not just a description.
One topology map = one caption Multiple maps each get their own caption.
Caption is part of the map Engine treats them as a single visual unit. Section §08 ships both or neither.

Engine Integration

Frontmatter on the topology figure

topology_figure:
  graph_id: shur-fiserv-gtm-call-2026-04-22
  modularity: 0.654
  node_count: 150
  edge_count: 376
  cluster_count: 14
  top_nodes:
    - { node: brand, bc: 0.32, color: cobalt }
    - { node: design, bc: 0.30, color: warm }
    - { node: lens, bc: 0.18, color: cobalt }
  cluster_legend:
    - { color: cobalt, label: "brand dimensions" }
    - { color: warm, label: "design archetypes" }
    - { color: red, label: "grammar insights" }
    - { color: violet, label: "topology & tools" }
    - { color: green, label: "navigation & reader-mode" }
  strategic_insight: "The Brooks/Nike/Figs cluster (lower right) is the Pivot Thesis future module Nuri surfaced — small in volume but conceptually consequential"
  reader_mode_primary: analyst
  reader_mode_skim: operator  # via caption

The engine populates the template variables from this frontmatter.

Default vs. override

The strategic insight is the only field that REQUIRES human authoring. Everything else can be auto-derived from the InfraNodus graph metadata. If the strategic insight is missing, the engine ships the caption with a TODO marker — never with a placeholder.

Cold Read special case

In Cold Read archetype, the strategic_insight field becomes the hook. It must end in a question or an observation that invites a follow-up — not a closed claim.

Open Questions for the V3 Meeting

  1. Caption length cap. Three paragraphs is the rule — should we cap word count too? Suggest 80–120 words.
  2. Caption position. Sidebar (right of map, current Fiserv GTM brief layout) vs. below-map (more magazine-traditional)? Sidebar is better for desktop, below-map better for mobile. Accept both as responsive.
  3. Multiple maps in one report. Coverage matrix rule: each map gets its own caption. But the AHA Pressure Test sometimes shows three overlapping maps — should there be a meta-caption that links them?
  4. Cluster label sourcing. The semantic labels ("brand dimensions," "grammar insights") are currently human-authored. Can the engine auto-derive them from cluster top-concepts? If so, with what confidence threshold?
  5. Cold Read hook discipline. Should the strategic-insight-as-hook be enforced via a linter (no period at end, must contain question mark or curiosity verb) or left to editorial judgment?