MedCORE Premium Editorial Style Guide

Version: 2026-07-02

Status: parallel design standard. This does not replace the existing MedCORE Production generator, protected templates, or MedCORE v2 print system. It defines a new premium system-series notes style for future implementation.

Product Standard

MedCORE Premium should feel like a paid subject series, not a decorated handout.

The target is a print-ready, textbook-grade note series with deliberate pacing, strong hierarchy, controlled color, and exam-first editorial judgment. Every page should answer one question:

What does Ahmad need to recognize, discriminate, and choose under NRE pressure?

Non-Negotiables

• No orphan headings, stranded labels, or one-line carryovers.
• No dense paragraph walls.
• No decorative color without function.
• No generic medical completeness that dilutes NRE pattern recognition.
• No page where the reader cannot identify the main exam decision in five seconds.
• No tables that break awkwardly across pages.
• No mixed visual grammar inside the same subject volume.
• No premium styling that weakens print readability.

Editorial Voice

The writing should feel like a senior examiner wrote a premium companion textbook:

• crisp,
• clinically useful,
• pattern-driven,
• visually calm,
• confident,
• selective,
• ruthless about exam relevance.

Avoid filler phrases. Avoid textbook background unless it directly changes recognition, differential diagnosis, management, or MCQ traps.

Page Architecture

Each topic note uses a recurring page rhythm.

1. Opener Page

Purpose: orient the reader before details begin.

Required blocks:

• Subject ribbon.
• Topic title.
• One-line exam promise.
• NRE Reverse-Engineered Pattern.
• Classic vignette pattern.
• Recognition trigger.
• Key discriminator.
• Fatal miss.

Layout rule:

The opener should not exceed one page unless the topic is a chapter-level index. If it spills, the excess becomes page 2 as “Exam Map”, not a continuation blob.

2. Concept Spine

Purpose: explain only the mechanism needed to make choices.

Allowed components:

• short editorial paragraphs,
• 3-step mechanisms,
• cause-to-finding chains,
• one compact diagram,
• highlighted rule boxes.

Paragraph rule:

No paragraph should exceed 4 lines in the final DOCX render. If it does, split into a rule, contrast, or micro-table.

3. Recognition Layer

Purpose: convert information into exam recognition.

Required blocks:

• Classic presentation.
• Disguised presentation.
• Synonyms and wording variants.
• Trigger words.
• “When they say X, think Y” table.

4. Discriminator Layer

Purpose: separate close choices.

Required blocks:

• Same-looking different-diagnosis table.
• Key test or next step.
• Trap pair.
• Why the tempting answer is wrong.

5. Management Layer

Purpose: next best step logic.

Allowed components:

• first-line treatment,
• unstable vs stable split,
• contraindication box,
• escalation ladder,
• emergency exception.

6. MCQ Conversion Layer

Purpose: turn the note into score.

Required blocks:

• How NRE asks it.
• What disguise it uses.
• What discrimination it rewards.
• Common wrong option logic.
• Future alert.

7. Recall and Error-Log Layer

Purpose: force active recall and future correction.

Required blocks:

• 5 recall prompts.
• 3 exam traps.
• 1 error-log-ready future alert.

Visual System

Color Roles

Use color as an information system, not decoration.

Role	Use	Visual Treatment
Subject identity	stable subject recognition	top ribbon and small page accents
Urgency	fatal misses, emergencies, contraindications	red accent, never full red blocks
Exam logic	discriminator, next best step, trap	blue accent
Memory	future alert, recall prompts	amber accent
Clinical pathway	management flow, escalation	green accent
Evidence	syllabus, recall, intel, qbank support	violet or neutral stamp

Color Discipline

• Maximum 3 accent colors per page.
• Body text remains black or near-black.
• Background tints must stay pale enough for printing.
• Red is reserved for danger, fatal miss, contraindication, or cannot-miss traps.
• Each subject gets one stable identity color, but the page should not become monochrome.

Typography

Recommended hierarchy:

• Volume title: strong serif or textbook-style display face.
• Topic title: bold, clean, high contrast.
• Section headings: compact sans-serif, all title case.
• Body text: readable serif or humanist sans-serif.
• Labels: small caps or bold micro-labels.
• MCQ logic: tabular or compact sans-serif for scanning.

Rules:

• One H1 per topic.
• H2 sections must start with at least 3 lines of content available below them.
• H3 labels cannot sit alone at the bottom of a page.
• Avoid all-caps body text.
• Keep line length comfortable: roughly 65 to 85 characters.

Component Library

Pattern Card

Use for the main NRE pattern.

Fields:

• How the exam tests it.
• What disguise it uses.
• What discrimination it rewards.

Placement:

Top third of opener page.

Vignette Strip

Use for classic stem recognition.

Fields:

• Patient.
• Presentation.
• Key clue.
• Best next move.

Placement:

Immediately after the pattern card.

Discriminator Table

Use for close MCQ options.

Columns:

• Option.
• Clue that supports it.
• Clue that rules it out.
• Correct move.

Design:

2 to 5 rows only. If more rows are needed, split into multiple tables by decision point.

Trap Box

Use for tempting wrong answers.

Fields:

• Trap.
• Why it tempts.
• Why it is wrong.
• Future alert.

Design:

Small, high-contrast, never more than half a page.

Fatal Miss Box

Use only for dangerous errors.

Fields:

• Miss.
• Consequence.
• Exam clue.
• Correct action.

Design:

Red accent. Cannot appear more than twice in a topic note.

Next-Step Ladder

Use for management.

Format:

1. Recognize stability.
2. Confirm the discriminator.
3. Choose immediate action.
4. Avoid the trap.

Evidence Stamp

Use when source strength matters.

Allowed labels:

• Syllabus-derived.
• Recall-derived.
• Intel-supported.
• QBank-supported.
• Concept-derived.

Rule:

Do not imply recall support if the fact is only syllabus-derived or concept-derived.

Anti-Orphan Layout Rules

These rules are mandatory in generated DOCX and rendered QA.

• Keep heading with next paragraph.
• Keep label with its value.
• Keep callout title with at least 2 content lines.
• Keep table header with at least 2 body rows.
• Keep trap title with full trap explanation.
• Keep bullet lead-in with at least 2 bullets.
• Keep question stem with all answer options.
• Keep MCQ answer key row with its explanation.
• Move a section to the next page if less than 20% of the component fits.

Preferred strategy:

Use slightly more white space rather than squeezing components into ugly breaks.

Density Rules

Page density should feel deliberate.

Content Type	Maximum Density
Editorial paragraph	4 final-render lines
Bullets per list	5
Table rows	7 visible rows before split
Callouts per page	3
Colors per page	3 accents
Major concepts per page	1 to 2

If a topic needs more, create a new page with a clear page purpose.

Subject-Series Structure

Each premium subject series should have:

1. Cover page.
2. How this subject is tested in NRE.
3. Subject pattern index.
4. Topic chapters.
5. Master discriminator tables.
6. Trap atlas.
7. Emergency/fatal miss section.
8. High-yield numbers.
9. Recall prompts.
10. Error-log workbook pages.
11. MCQ companion index.

Topic Chapter Template

Use this order unless the topic demands a better exam-first sequence.

Topic Opener
  Subject ribbon
  Topic title
  Exam promise
  NRE Reverse-Engineered Pattern
  Classic vignette
  Recognition trigger
  Key discriminator
  Fatal miss

Core Explanation
  Concept spine
  Mechanism that changes management
  Key numbers

Recognition
  Classic presentation
  Disguises
  Synonyms
  Trigger table

Discrimination
  Differential table
  Trap pair
  Why wrong options are wrong

Management
  Next-step ladder
  Stable vs unstable split
  Treatment exceptions

MCQ Conversion
  How NRE asks it
  Option logic
  Future alert
  Recall prompts

Premium QA Checklist

A note is not finished until all are true:

• Every page has a clear purpose.
• No orphan heading or label exists.
• No component splits awkwardly.
• No paragraph wall appears.
• Color communicates meaning.
• Tables are readable in print.
• NRE reverse-engineered pattern appears near the beginning.
• The discriminator is visually findable.
• Trap logic is explicit.
• Evidence labels are honest.
• Render QA has been checked page by page.

Implementation Notes

This style is best implemented as a new generator mode or parallel v3 system, not by patching old produced DOCX files.

Recommended future structure:

MedCORE Premium/
  00 System/
  01 Subject Volumes Color/
  02 Subject Volumes Print/
  03 Chapter Packs/
  04 Topic Source JSON/
  05 MCQ Companions/
  06 Error Log Workbooks/
  07 Render QA/
  08 Indexes Maps/
  Scripts/

Recommended next implementation step:

Build one premium prototype chapter from an existing source JSON, render it to PDF/PNG, and judge it visually before scaling.