Google Slides System — INTO Consulting Brand System

Readable Decks, Not Pitch-Theatre

INTO Slides should behave like editorial documents that can also be presented. A reader should understand the argument without a narrator.

The default is reader-first. Use presentation mode only when the deck will be live-delivered and needs room-scale type. Proposal, status, and investor decks all use the same geometry but different narrative contracts.

example-slides-default-contract

Default Contract

Use Google Slides in widescreen 16:9, Warm Light as the default surface, Blueprint Dark for title or section cards, and a readable page-like rhythm rather than decorative slideware.

example-slides-foundation-route

Foundation Route

Use contexts/design-foundations-system.html before changing baseline rhythm, type roles, reading path, bento usage, button treatment, or image/text composition in decks. Then apply media framework, channel data, the deck sheet, this hybrid spec, the deck template, and export checks.

What Google Slides Allows

Google Slides supports standard, widescreen, and custom slide sizes. It also supports theme, background, and layout controls that should carry INTO's reusable deck system.

Size Use widescreen 16:9 by default. Custom 13.333 x 7.5in or 1920 x 1080px is the working coordinate.

Measurement Pixel or inch measurement is acceptable as long as the deck uses one coordinate system consistently.

Themes Build theme colors, backgrounds, and layouts once. Do not create every slide as a one-off canvas.

Accessibility Preserve logical reading order, high contrast, useful text labels, and captions for presented video when relevant.

example-slides-platform-risk

Platform Risk

Slides can look polished while becoming unreadable as PDFs. If the deck must be read, use the reader-first contract and export-check it like a document.

Current Guidance Was Directional, Not Build-Ready

The existing Slides guidance correctly set the reader-first posture, 16:9 format, two type modes, and template governance. It did not yet define enough master-layout detail for consistent implementation.

Area	Current State	Gap Closed In This Version
Master layouts	Named only a partial set.	Defines the full canonical set from cover through appendix, including executive summary, proposal argument, schematic, and team/roles.
Geometry	Margins, rows, columns, and gutters existed.	Adds safe-zone behavior, coordinate conversion, column-width intent, footer limits, and full-bleed exceptions.
Evidence	Charts and tables were mentioned.	Routes KPI, chart, Gantt, table, and schematic masters to the data visualization system and requires conclusion/source anatomy.
Brand devices	Deck guidance did not fully constrain star, circle, mark, or petrol use.	Star, circle, square mark, gradients, and petrol now have slide-specific placement and prohibition rules.
Review	Export checks existed but were general.	Adds human-review examples and AI-readable constraints for deck contract, master choice, readability, and PDF validation.

example-slides-audit-agent-rule

Agent Rule

Do not generate a deck from the old archetype list alone. Use the canonical master-layout set, then apply the deck contract and export review gates.

Borrow Operating Discipline, Not Visual Identity

The Slides system now uses external benchmarks for governance and communication logic: B&O for template discipline, Accenture for research-report evidence, McKinsey-style doctrine for executive decision structure, and design consultancies for human-centered proof.

Benchmark	Transfer Into INTO Slides	Do Not Copy
Bang & Olufsen	Category-led guideline architecture, official template artifacts, usage rules, and layout governance.	Visual identity, palette, typography, product-world imagery, or luxury audio language.
Accenture	Research-report structure: authored claims, figure labels, source notes, methodology, and editorial chapter pacing.	Purple/black visual system, report cover style, reinvention language, or proprietary figure styling.
McKinsey-style doctrine	Decision memo in slide form: answer first, SCQA, MECE, action titles, title-chain test, dominant exhibit, source discipline.	Internal templates, generic blue-box consulting aesthetic, or unsupported density.
Design / research consultancies	Observed needs, systems context, prototype learning, method clarity, uncertainty, and human impact tied to operating impact.	Playful illustration systems, agency portfolio layouts, or research walls without decisions.

Decision Brief

Before layout, define audience, decision, recommendation, SCQA, MECE support points, evidence needed, and appendix depth.

Action Titles

Use full-sentence conclusion titles with verbs. The slide body must prove the title. Neutral topic labels fail review.

Title Chain

Extract slide titles into a list. If the list does not read like a coherent executive memo, fix the story before styling.

Evidence Contract

Every quantitative claim needs a source note or assumption label. Every analytical slide needs context, implication, and one dominant exhibit.

example-slides-benchmark-agent-rule

Agent Rule

Use research/benchmarks/2026-05-13-consulting-deck-benchmarks.md for benchmark logic. Translate governance, evidence, and decision structure only; do not import another firm's visual system.

Use The Website For Signal, Not Formatting

The live INTO Consulting site is useful for current positioning and rhythm. It is not a slide template, and agents must not copy its web-specific layout into decks.

Website Signal	Deck Translation	Boundary
AI studio positioning	Decks should sound practical, builder-led, and operator-facing.	Do not turn deck headlines into web hero copy.
Numbered editorial sections	Use mono section numbers, page rhythm, and title-chain logic.	Do not over-number every object or create decorative counters.
Discovery, define, build, optimize model	Use as the default delivery or roadmap vocabulary when it fits the work.	Do not force it into investor, appendix, or data-only slides.
Evidence-led use cases with measured outcomes	Use Statistic, Chart, KPI, and Proposal Argument layouts to connect outcome, mechanism, and proof.	Do not use unsupported claims or generic AI transformation language.
Working-session call to action	Get In Touch and Decision / Ask layouts should include a concrete next action, route, owner, and date.	Do not close with vague contact-only slides.
Copyright and contact footer	Reader-first deck footers keep copyright left and page number right.	Do not replace footer metadata with a decorative mark.

example-slides-website-agent-rule

Agent Rule

Use https://www.weareinto.consulting/ to check current positioning, offers, address/contact, and CTA language before finalizing external-facing decks. Preserve the deck system's grid, type scale, margins, and master layouts.

Past Decks Are Inputs, Not Templates

The supplied QDHP, About INTO, Puxxle, and Banque Nationale decks are calibration material. Use their content jobs and omissions to improve the system; do not copy their style, density, or client-specific language.

Reference Pattern	Keep As System Learning	Do Not Carry Forward
Bank / enterprise deck	Pattern-to-client-implication flow, production-grade posture, and concrete working-session close.	Dark photo-heavy density, tiny copy, or client-specific examples as reusable generic proof.
Startup proposal deck	Proposal skeleton: challenge, architecture, phased delivery, timeline, investment, team, legal notices.	Dense three-column prose, weak hierarchy, and legal terms squeezed into a closing wall of text.
About / capability decks	Core capability blocks, team roles, and proof points need reusable masters.	Generic “who we are” copy, inconsistent footer casing, and decorative AI imagery.
Puxxle terms and conditions	Confidentiality/use, resource availability, validity period, pricing/terms review, IP/copyright, and SOW precedence are required commercial deck content.	Legal/commercial content treated as optional appendix filler.

example-slides-legacy-agent-rule

Agent Rule

When using old decks, extract slide jobs and required commercial clauses only. Rewrite into the canonical master set and remove inherited visual style, client-specific wording, and stale tone.

Four Deck Contracts

The deck type sets the layout logic before any slide is designed. Agents must choose the contract first, then choose the slide mode.

Proposal Presentation

Lead with recommendation, business bottleneck, and expected value.
Show evidence before scope.
Make commercials and next action impossible to miss.

Project Status

Lead with decisions, progress, risks, and asks.
Use a fixed weekly rhythm so readers know where to look.
Separate facts, judgment, and required action.

Investor Presentation

Lead with thesis, market pressure, proof, and system advantage.
Use charts as evidence, not decoration.
End with the ask and use of funds or use of support.

Reader-First Editorial

Treat each slide like a page in an editorial document.
Put the conclusion up top, then evidence, source, and recovery space.
Make speaker notes optional, never required for comprehension.

Executive Filter

Every visible phrase answers what changed, why it matters, what decision is needed, what evidence proves it, or what action follows.

No Meta Commentary

Build labels, facilitator cues, narration state, and process notes stay in speaker notes, drawers, voiceover files, or appendix detail.

Proximity

Related items sit closer together than unrelated items. Source notes stay attached to their chart, table, or screenshot.

Visual First

Analytical slides choose the chart, table, screenshot, schematic, timeline, or decision board before prose expansion.

Type Floors

Do not shrink KPI, table, chart, annotation, source-note, or footnote text below the minimum floor to force fit.

Accent Rails

Use at most one accent rail on a normal slide. Repeated left borders are decoration, not hierarchy.

Backgrounds

Use Blueprint Dark, editorial gradients, or photo overlays for title, section, quote, dramatic conclusion, or room reset slides; keep routine evidence on Warm Light.

The Page Still Exists

Even in Slides, the INTO system starts with surface, margin, grid, and reading direction. Empty space is a layout material, not leftover room.

Reader-first / 96px margin / 12 x 8 The Deck Must Read Alone

Presented / 80px margin / 12 x 6 One Claim Per Slide

Reader-First 96px margin, 12 columns, 8 rows, 24px gutters, document-style reading flow.

Presented 80px margin, 12 columns, 6 rows, 24px gutters, one dominant claim or exhibit.

Bottom-Right Keep critical content out of the bottom-right 96px zone. Video calls, playback, and presenter controls often compete there.

Footer Reader-first, evidence, commercial, appendix, status, investor, and proposal body slides use a quiet footer: copyright left, optional client or section center, page number right.

Line Length Use columns to keep prose to 35-52 characters per line. Add columns before shrinking type.

Column Ceiling Use one or two columns by default. Three columns are for peer lists, KPI triplets, compact comparisons, or agenda items only.

Editorial Rhythm Build every slide as label, pause, display, argument, evidence, and recovery space. Wide evidence gets its own row or exhibit area.

Spec	Reader-First	Presented
Working size	1920 x 1080px or 13.333 x 7.5in.	1920 x 1080px or 13.333 x 7.5in.
Coordinate conversion	1px equals 0.006944in at the 1920px working coordinate.	Use the same conversion; do not mix pixel and inch systems mid-deck.
Grid	12 columns x 8 rows, 24px gutters, approximately 125px columns.	12 columns x 6 rows, 24px gutters, approximately 127px columns.
Safe area	96px margin plus bottom-right 96px control zone.	80px margin plus bottom-right 96px control zone.
Footer	40px zone with copyright left, optional client/section center, page number right.	Optional on pause slides; required when the slide is read, cited, or exported.

Two Type Modes, Smaller By Default

A deck can switch between reader-first and presented modes slide by slide, but a single slide must not mix the two density contracts. Use the low end first; the high end is a ceiling.

Role	Reader-First	Presented
Title	Newsreader 34-44pt	Newsreader 42-56pt
Cover title	Newsreader 54-66pt	Newsreader 60-72pt
Lead / argument	Lexend 18-21pt	Lexend 22-26pt
Body	Lexend 16-18pt	Lexend 20-24pt
Caption	IBM Plex Mono 10-12pt	IBM Plex Mono 12-14pt
Figure label	IBM Plex Mono 10-12pt	IBM Plex Mono 12-14pt
Defect line	Body below 16pt is too dense for a readable deck.	Screen-share body below 20pt is a defect; title above 56pt needs a reason.

Slide-Specific Typography Ramp

This ramp is tuned for Google Slides. The rem-equivalent is a cross-reference for browser/reveal.js implementations using the same optical role; native Slides builds use the point values.

Role	Slides Size	Rem Equivalent	Line Height	Family / Weight	Binding
Display	54-72pt	4.5-6rem	1.0-1.06	Newsreader 400	Cover, decision/ask, closer only.
Statement	44-56pt	3.67-4.67rem	1.04-1.1	Newsreader 400	Single-argument slide with no decoration.
Section header	40-64pt	3.33-5.33rem	1.04-1.1	Newsreader 400	Section divider and chapter reset.
Body	16-24pt	1.33-2rem	1.35-1.55	Lexend 300	Argument, context, and mitigation copy.
Eyebrow	10-14pt	0.83-1.17rem	1.2-1.35	IBM Plex Mono 500	Section number, figure label, source category.
Footnote / source	9-12pt	0.75-1rem	1.35-1.5	IBM Plex Mono 400	Source, assumption, caveat, copyright.
Caption	10-14pt	0.83-1.17rem	1.35-1.5	Lexend 300 or IBM Plex Mono 400	Image, table, chart, or screenshot explanation.

example-slides-type-ramp-specimen

Ramp Specimen

Display: Applied AI that ships inside the work.

Statement: The workflow bottleneck is now visible enough to automate safely.

FIG 03 / SOURCE: pilot model, May 2026.

Use 12-16px between label and title, 20-28px between title and copy, 32-48px between body and exhibit, and 64-96px for major section breathing room. Reader-first slides should use columns to preserve comfortable sentence width before they reduce type size.

The Grid Is The Template

Use the grid to decide what the reader sees first, where evidence lands, and how the footer stays quiet. The grid is not decoration; it is the contract between argument, exhibit, and review.

0.5in safe margin 12 columns / 0.14in gutters 01 / LABEL Conclusion title spans 6-8 columns Lexend 18pt base body. Keep prose to 35-52 characters per line. Dominant exhibit, chart, schematic, table, or image Source / assumption note © INTO Consulting 2026. Confidential. 07

Coordinate Contract

Canvas	16:9, 13.333in x 7.5in, or 1920 x 1080px.
Safe margin	0.5in left/right/top, 0.38in bottom content clear, 0.24in footer band.
Grid	12 columns x 8 rows for reader-first; 12 columns x 6 rows for presented.
Modules	4-column text, 6-column visual, and 12-column panoramic evidence zones.
Base Type	Lexend 18pt body for read decks; 16pt minimum, 20pt when the slide carries dense review.
Footer	Copyright left, optional context center, page number right. Never replace it with a mark.

Reader Page

Title and argument live left; evidence lands right or below. Best for summaries, proposals, and status pages.

Dominant Exhibit

Conclusion up top, chart/table/schematic takes the full evidence row. Best for figures and appendix proof.

Presentation Pause

Blueprint Dark, one title block, one optional cue. Best for covers, sections, Q&A, and thank-you moments.

Master Move

Choose one dominant zone per slide. If the exhibit is wide, give it the full row instead of squeezing it beside prose.

Reading Measure

Body copy lives in 4-5 columns. If it needs more width, it probably needs a table, schematic, or appendix split.

Footer Discipline

Reader-first body slides use © INTO Consulting [year]. Confidential. at left and page number at right.

Interactive Translation

In reveal.js, the same grid becomes CSS layout classes. Motion can reveal the zones, but it cannot rearrange the argument.

Layout Primitives Compose The Masters

Use these primitives inside the canonical master layouts. Choose the master first, then the primitive that best carries the slide's content.

Layout	Use When	Grid / Margins	Type / Color Rule
Title	Opening, closing, Q&A, or high-emphasis claim.	Presented 12 x 6, 80px margin. Title columns 1-8, rows 3-4.	Newsreader 60-88pt. Blueprint Dark or Warm editorial gradient.
Agenda	Orienting the reader before the argument.	Reader-first 12 x 8, 96px margin. List columns 1-10, rows 3-7.	Newsreader 40-52pt, Lexend 18-20pt, mono numbers. Petrol only for current section.
Section Title	Resetting pace between chapters.	Presented 12 x 6, 80px margin. Title columns 1-8.	Newsreader 60-80pt, one Lexend transition sentence. Blueprint Dark by default.
Timeline	Showing sequence, phases, dependencies, or wave plan.	Reader-first 12 x 8. Labels columns 1-3; axis columns 4-12.	Mono phase labels, Lexend body. Saffron signal only for milestones.
Image And Text	Pairing evidence image, screenshot, diagram, or macro texture with interpretation.	Reader-first 12 x 8. Text 4-5 columns, image 6-7 columns, 48px gutter.	Warm Light. Caption/source required. Photo overlay only when contrast passes.
Columns	Comparing related points or structuring dense editorial copy.	Reader-first 12 x 8. Two columns use 5+5; three columns use 3+3+3.	Aligned baselines, Lexend 16-20pt. No decorative color blocks.
Terms	Commercial, legal, assumptions, exclusions, or glossary detail.	Reader-first 12 x 8. Term column 3-4 cols, explanation 7-8 cols.	Mono term labels, Lexend 16-18pt. Hairlines and light row shading only.
Chart	Showing quantitative pattern, comparison, composition, or movement.	Reader-first 12 x 8. Header rows 1-2; exhibit rows 3-7; source above footer.	Chart/Data on Warm Light. Direct labels, context line, and source required.
Statistic	Showing one to four numbers with movement and cause.	Reader-first 12 x 8. Hero stat spans 5-6 cols; multi-stat uses 3 or 4 cells.	Newsreader numerals 54-88pt. Petrol marks only the primary value.
Budget Table	Showing fees, budget, cost plan, discount, taxes, or assumptions.	Reader-first 12 x 8. Row labels 3-4 cols, values 2-3 cols, notes 4-5 cols.	Tabular numerals, hairlines, totals, assumptions, and approval path.
Team	Showing people, roles, responsibilities, decision rights, availability.	Reader-first 12 x 8. Role matrix spans columns 1-12.	Role clarity first. Portraits optional and secondary.
Get In Touch	Closing with contact, next action, and route.	Presented 12 x 6 or reader-first 12 x 8. Contact cols 1-5, action cols 7-12.	Blueprint Dark or Warm Light. Wordmark or mark, not both.
Comparison	Comparing options, vendors, models, or scenarios.	Reader-first 12 x 8. Criteria left 3 cols, options across remaining 9 cols.	Petrol marks selected option only. Criteria must be MECE.
Decision / Ask	Requesting approval, access, budget, or commitment.	Reader-first 12 x 8. Ask cols 1-5, rationale cols 7-12.	Decision line above footer. Owner and date required.
Risk / Issue	Surfacing uncertainty, blocker, dependency, or mitigation.	Reader-first 12 x 8. Issue log spans columns 1-12.	Saffron for warning, red only for critical contrast.

Spacing

Use 24-32px from label to title, 32-48px from title to body or exhibit, 32-48px between columns, 12-16px table cell padding, and 16-24px for timeline, terms, or risk rows.

Hierarchy

Every primitive keeps the pacing rule: label, pause, display, argument, evidence, recovery space.

Imagery

Image And Text uses evidence images, screenshots, diagrams, or approved macro texture only. No stock imagery or generic AI visuals.

Terms

Terms slides require source, assumption, or approval context when used for commercial or legal content.

Footer

Reader-first, evidence, commercial, appendix, status, investor, and proposal body slides use copyright left and page number right.

example-slides-layout-agent-rule

Agent Rule

Choose deck contract, master, and slide mode first. Then compose the slide with one of the layout primitives. Do not create a new primitive until the existing set fails the communication job.

Master Gallery For Review

These are not gray placeholders. They are composition specimens for review: visible grids, real footer behavior, hierarchy, dominant evidence, and the content job of each master.

example-slides-p4-existing-state

P4 Verification Finding

The current file already had a master gallery and substantial slide-system architecture. P4 keeps that work, then adds the required slide-type taxonomy, dark-cover binding, slide-specific type ramp, and JSON-LD layout primitives so agents can route every slide in a 20-slide deck without inventing layouts.

Required Slide-Type Taxonomy

Use these fifteen slide types as the routing layer. The visual gallery below shows the canonical master behavior; this table adds the missing anatomy, binding, accessibility, and anti-pattern contract.

Slide Type	Purpose / Use	Anatomy	Grid / Type / Media Binding	Motion / Accessibility / Anti-Pattern
Title / cover	Open the deck or major proposal; default dark-editorial register.	`[meta] [title] [subtitle] [presenter/date]`	Presented 12 x 6. Display Newsreader. Macro photo or Blueprint Dark, text in quiet half.	Hero entrance only; static final state. No photo collage, tiny logo, or paragraph cover.
Section divider	Reset pace between chapters.	`[02 /] [section] [one-line setup]`	Presented grid. Deep teal #0a1c1c, subtle grain, hairline rule.	Section transition may fade in. No card, agenda wall, or decorative badge stack.
Statement / argument	Let one declarative line carry the slide.	`[eyebrow] [single claim]`	Presented or reader-first sparse grid. Statement role only; no ornament.	Optional text entrance. Screen reader order is eyebrow then claim. No bullet list disguised as statement.
Two-column image + text	Pair evidence or macro image with interpretation.	`[claim] [body/action] \| [image/caption]`	Reader-first 50/50 or 60/40. Text 4-5 cols; image 6-7 cols. Shallow-DOF or evidence image.	Image loads static; caption attached. No text over focal subject or stock photo filler.
Three-column	Show three peer points.	`[title] [point] [point] [point]`	Reader-first three equal peer columns with hairline separators before cards.	Reveal peer points only when pacing helps. No unequal fragments or decorative card wall.
Exhibit full-width	Make one chart, diagram, quote, table, or photo the slide.	`[eyebrow] [takeaway] [exhibit] [source]`	12-column panoramic evidence row. Title proves exhibit; source attached.	Animate exhibit only to reveal reasoning. No chart-as-decoration or detached footnote.
Data / chart	Show quantified pattern or movement.	`[figure] [conclusion] [chart] [source]`	Bound to brand/data-visualization-system.md. Direct labels, restrained axes, source line.	D3/anime may reveal series. No neutral chart title, unsupported number, or decorative legend.
Comparison two-up	Compare us/them, before/after, or option A/B.	`[title] [A] \| [B] [criteria/source]`	Symmetric 5+5 columns with center hairline. Petrol marks selected option only.	Reveal sides together unless presenting sequence. No asymmetrical proof or vague criteria.
Timeline / Gantt	Show phases, weeks, bars, dependencies, and milestones.	`[title] [phase labels] [week markers] [bars]`	Dark-editorial process timeline when used as high-emphasis plan; otherwise Warm Light data master.	Timeline marker may advance. No unlabeled bars, milestone confetti, or compressed plan card.
Quote	Create an editorial proof or voice moment.	`[quote] [attribution/source]`	Presented sparse grid. Newsreader quote, quiet attribution; optional one circle highlight.	Quote can fade in once. No quotation collage, oversized decorative marks, or missing attribution.
Team	Clarify people, roles, responsibilities, rights, and availability.	`[title] [photo strip/grid] [names/roles]`	Role matrix first. Portraits use shallow-DOF environmental register when available.	No animated portrait wall. Alt text names role; no portrait-first layout that hides decision rights.
Terms / legal	Make proposal terms readable.	`[section anchors] [term] [condition] [footer]`	Reader-first dense-but-legible grid. Hairline rows, required footer, no dark-cover.	Static only. Reading order must follow anchors. No tiny legal wall or hidden speaker-note terms.
Decision / ask	Request approval, access, budget, or commitment.	`[ask] [rationale] [owner/date/route]`	Reader-first or dark-cover when elevating final ask. Decision line above footer.	Decision lock-in motion allowed. No vague next steps or action detached from rationale.
Risk / issue	Surface uncertainty with mitigation.	`[risk] [impact] [mitigation] [owner/trigger]`	Reader-first issue table. Saffron #FFC64F for warning/milestone/comparison only.	Severity changes can highlight. No red panic styling, badges, or risk without owner.
Closer / thank-you / contact	Close with next step, contact, or investor ask.	`[thank you/ask] [contact] [route/date]`	Dark-editorial by default; Warm Light allowed for reader-first appendix close.	Static or title entrance. No vague contact-only slide or wordmark plus mark clutter.

Dark-Cover Treatment For Slides

Slides route dark covers to design-foundations-system.html#dark-editorial-cover and the P2 photography/depth rules. Use the layer order photo - optional blur backstop - gradient - grain - content. The 16:9 image bleeds beyond all edges, the focal detail stays peripheral and low contrast, and text sits in the left or upper quiet half with no critical content in the bottom-right 96px zone. Dark cover is right for cover, section divider, decision/ask, closer, and occasional quote or dramatic conclusion slides; it is wrong for data/charts, terms/legal, dense tables, routine evidence, and any slide whose source note must be inspected.

Title / cover

Section divider

Statement

Two-column image + text

Three-column

Exhibit full-width

Data / chart

Comparison two-up

Timeline / Gantt

Quote

Team

Terms / legal

Decision / ask

Risk / issue

Closer / contact

Cover Presented / Blueprint Dark

INTO Consulting / Proposal

Applied AI That Ships Inside The Work

Client name / May 2026

✦

Use for title or section pauses only. One claim, one metadata line, optional north-star cue.

Executive Summary Reader-First / Warm Light

01 / CONCLUSION

The recommendation is to start with the highest-friction approval workflow.

1 Bottleneck is measurable 2 Data already exists 3 Risk is containable

Use after the cover. The reader gets the answer before the supporting path.

Agenda Reader-First

00 / MAP

Today’s Path

01 Decision context
02 Evidence review
03 Delivery plan
04 Terms and next action

Use mono numbers. Petrol may mark the current section only.

Proposal Argument Decision Slide

02 / RECOMMENDATION

Start with the workflow that already has executive demand.

The pilot is strongest where there is a named owner, visible pain, and reusable evidence.

Owner named Data ready 2-week prototype

Decision required: approve phase 1 scope.

Left side argues. Right side proves. The decision line sits above the footer.

Evidence / Table Reader-First

FIG 04 / EVIDENCE

Two workflows carry most of the avoidable review time.

WorkflowWeekly hoursOwner Approvals18Ops Client intake11Delivery Reporting6Finance

Source: workshop estimate, May 2026.

Tables need conclusion title, visible units, source, and enough row height to read.

Chart / KPI Data Exhibit

FIG 05 / THROUGHPUT

Cycle time falls when routing is explicit.

37%faster review loop

Source: pilot model, assumption case A.

Petrol marks the answer series or primary statistic, never chart decoration.

Timeline / Gantt Plan Exhibit

PLAN / 8 WEEKS

Delivery moves from discovery to working pilot in four contained waves.

Discover Define Build Optimize

Show sequence, owner, milestones, and dependencies. Saffron signal marks real decisions.

Schematic / Architecture System Exhibit

ARCHITECTURE / WORKFLOW

The system routes work through three controlled layers.

Client Surface INTO Orchestration Evidence Layer

Use seven nodes or fewer, ports, connector labels, and governance boundaries.

Budget Table Commercial

COMMERCIAL / BUDGET

The phase-one budget is fixed if the scope remains contained.

Discovery$12k Prototype$28k Governance$8k Total$48k

Expose assumptions, exclusions, totals, approval path, and validity period.

Team / Roles Responsibility Matrix

TEAM / ROLES

Responsibilities are clearer than portraits.

LeadDelivery owner2 days/wk ArchitectWorkflow design3 days/wk ClientApprovalsweekly

Portraits are optional. Decision rights and availability are not optional.

Terms / Notices Required Proposal Master

TERMS / NOTICES

Commercial terms must be readable before the close.

ConfidentialityUse limited to proposal review. AvailabilityResources held after signature. ValidityPricing valid for 30 days. SOW precedenceSigned SOW controls delivery.

Split terms into multiple slides before reducing body below reader-first minimums.

Get In Touch / Thank You Close

NEXT ACTION

Book the working session and bring the workflow.

hello@weareinto.consulting
weareinto.consulting

Owner / date / route

Close with a concrete action, route, owner, and timing. Use wordmark or mark, not both.

example-slides-wireframe-agent-rule

Agent Rule

When a new deck pattern is proposed, add a specimen to this gallery before writing long guidance. It must show margin, hierarchy, dominant exhibit, footer behavior, safe-area intent, and whether the surface is Warm Light or Blueprint Dark.

Use Archetypes, Not Decoration

The archetype tells the slide what job to do. Avoid decorative cards, badge clusters, and one-off compositions that do not clarify the argument.

Archetype	Use When	Layout Rule
Title Card	Opening or chapter break.	One claim, one mark, no body paragraph.
Recommendation	Decision or proposal answer.	Claim left, evidence right, next action visible.
Evidence	Metric, chart, quote, screenshot, or process finding.	Exhibit dominant, caption precise.
System Diagram	Workflow, architecture, governance, data flow.	Diagram first, annotations in mono.
Status	Project reporting.	Decision, progress, risk, ask in fixed positions.
Appendix	Detail that supports reader review.	Reader-first mode only.

Evidence Job	Default Layout	Rule
Quantitative pattern	Chart	One dominant chart with direct labels, unit, period, source, method, and implication.
Option tradeoff	Evidence / Table	Criteria down the left, options across the top, preferred option highlighted.
Prioritization	Chart or Evidence / Table	Use a matrix only when both axes are explicit and useful.
Number movement	Chart	Use a waterfall or bridge when explaining movement from one value to another.
Operating model	Schematic / Architecture	Show roles, systems, decision gates, exception paths, and controls.
Execution sequence	Gantt	Show timing, dependencies, milestones, and ownership.
Uncertainty	Evidence / Table	Show risk, impact, mitigation, owner, and trigger.
Commitment	Proposal Argument	Recommendation, rationale, decision required, owner, and date.
Meta commentary	Speaker notes or appendix	Do not show it in the primary slide path unless it directly changes the room's decision.

Advanced Chart Patterns Stay Evidence-Led

Use advanced charts only when the chart shape clarifies the argument faster than a table or simple bar chart. Every exhibit keeps the conclusion in the title and the unit, period, and source on the slide.

Review drag is mostly approval wait, not drafting effort.

Waterfall bridge / Unit: indexed cycle-time hours / Period: fictional four-week baseline.

StartDraftApproval waitReworkEnd

Source: fictional ACME workflow model. Use when explaining movement from one value to another.

Most requests flow from intake to two approval paths.

Sankey flow / Unit: indexed request share / Period: fictional month.

IntakeFast pathIntakeReview path

Source: fictional ACME routing sample. Use only when flow magnitude is the story.

Three request families account for most pilot surface area.

Treemap / Unit: indexed request share / Period: fictional quarter.

Family AFamily BFamily COther

Source: fictional ACME discovery data. Use for proportion within a hierarchy.

The same adoption pattern repeats across four operating teams.

Small multiples / Unit: indexed completion rate / Period: fictional weeks 01-06.

Team ATeam BTeam CTeam D

Source: fictional adoption tracker. Use when repeated chart shapes enable comparison.

The controlled pilot reduces handoff steps before release.

Before/after pair / Unit: indexed handoff steps / Period: fictional pilot model.

Before: manual routingAfter: governed pilot path

Source: fictional process model. Use only as a paired conclusion-led comparison.

Volume rises while exception rate stays inside the pilot guardrail.

Combo bar and line / Unit: indexed volume and rate / Period: fictional six-week pilot.

Source: fictional pilot telemetry. Use when one axis is volume and the other is rate.

Templates Are Canonical Artifacts

A repeated deck layout should live in the theme or template system. Do not rebuild the brand on each slide.

Core Masters

Cover, section break, agenda, quote, Q&A, thank-you, terms/notices, and appendix.

Evidence Masters

Evidence/table, KPI, chart, Gantt, screenshot, and system diagram.

Governance

Each master declares surface, margin, grid, type mode, footer behavior, mark use, and safe area.

Promotion Rule

If a one-off layout is reused, promote it to a named master layout before the next deck.

Master Layout	Primary Job	Control
Cover	Brand, client, title, date.	Wordmark, strong margin, one display claim.
Section Break	Reset the reader.	Blueprint Dark or Warm editorial gradient; no dense body copy.
Agenda	Orient the reader.	Two-column numbered agenda; no decorative bullets.
Executive Summary / Conclusion Up Top	State the answer first.	Conclusion band, three evidence points, next action.
Proposal Argument	Make the recommendation defensible.	Claim left, proof right, decision visible.
Evidence / Table	Prove a claim.	Exhibit dominates; conclusion, caption, and source are visible.
KPI	Show value and movement.	Every metric includes period, unit, delta, and cause.
Chart	Compare, show time, or show part-to-whole.	Teal plus gray; Saffron signal only when meaningful.
Gantt	Show schedule and dependencies.	Readable task list, quiet timeline, milestones visible.
Schematic / Architecture	Explain workflow or system structure.	Layered node canvas, seven primary nodes or fewer, labeled connectors.
Quote	Create a high-emphasis proof or voice moment.	One quote, attribution, optional single circle highlight.
Team / Roles	Clarify delivery responsibility.	Role matrix, decision rights, availability, no portrait-first layout.
Terms & Conditions / Legal Notices	Protect proposal/commercial context.	Reader-first terms blocks with validity, confidentiality, availability, IP/copyright, assumptions, and SOW precedence.
Q&A	Open discussion.	Blueprint Dark, large title, one prompt line, optional compact mark.
Thank You	Close with action.	Contact, next action, wordmark or compact mark, not both.
Appendix	Support diligence and detail review.	Reader-first only, one dense evidence object per slide.

example-slides-template-agent-rule

Agent Rule

Choose the deck contract, then choose a master layout. Create a new layout only when no canonical master can express the communication job.

Canonical Slide Master Set

Each master declares surface, mode, grid, footer, mark behavior, and the content job. Build from this set before creating a one-off layout.

Master	Surface / Mode	Layout Rule	Brand Control
Cover	Blueprint Dark or Warm editorial gradient / Presented	Wordmark, client/date label, one title claim.	Optional north-star cue only when meaningful.
Section Break	Blueprint Dark / Presented	Mono section marker, Newsreader title, one transition sentence.	Keep at least one empty third of the slide.
Agenda	Warm Light / Reader-first	Two-column numbered agenda when more than five items.	Numbers use mono; star and circle are never bullets.
Executive Summary / Conclusion Up Top	Warm Light / Reader-first	Conclusion first, three evidence points, one next action.	Use after cover by default in proposal and status decks.
Proposal Argument	Warm Light / Reader-first	Left 5 columns claim, right 6 columns proof or workflow.	Petrol may mark the recommended action only.
Evidence / Table	Warm Light / Reader-first	Figure label, conclusion, table or exhibit, source note.	Expose totals and data caveats; no chart gradients.
KPI	Warm Light / Reader-first	Three to four KPI cards with value, period, delta, cause.	No decorative KPI cards or unsupported numbers.
Chart	Warm Light / Reader-first	Chart spans the exhibit row with direct labels where possible.	Teal answer, gray context, Saffron signal only for real milestones or warnings.
Gantt	Warm Light / Reader-first	Workstreams left, timeline right, dependency labels below lines.	Full-width row; do not compress into a small card.
Schematic / Architecture	Warm Light / Reader-first	Three layers, node cards, ports, labeled connectors.	Seven primary nodes or fewer; use logos only when recognition matters.
Quote	Warm Light or Blueprint Dark / Presented	One quote, attribution, source/context.	Thick circle may highlight one phrase or number.
Team / Roles	Warm Light / Reader-first	Role matrix with responsibilities and decision rights.	Portraits are optional and never replace role clarity.
Terms & Conditions / Legal Notices	Warm Light / Reader-first	Confidentiality/use, resource availability, validity period, pricing/terms review, IP/copyright, assumptions, and SOW precedence.	Required for proposal/commercial decks; split before shrinking text below minimums.
Q&A	Blueprint Dark / Presented	Large Q&A title and one prompt line.	No question-mark pattern or decorative sparkle field.
Thank You	Blueprint Dark / Presented	Contact, concrete next action, date or route.	Use wordmark or compact mark, not both.
Appendix	Warm Light / Reader-first	Appendix ID, one dense evidence object, source or caveat.	Page number required; speaker notes cannot carry essential context.

Human Review Example

example-slides-canonical-master-set: Proposal Argument needs the decision line moved above the footer safe zone.

AI Constraint

When a user asks for a deck, select the deck contract, then the master layout, then the slide mode. Styling comes last.

Promotion Rule

If a one-off layout is reused in a second deck, add it to templates/decks/slide-system.md or replace it with an existing master.

Defect Rule

A slide fails review if it requires speaker notes to understand the conclusion, source, or next action.

Proposal Presentation Pattern

Proposal decks should make the recommendation feel inevitable. Scope and commercials come after the reader sees the operating problem and the proposed system.

Order	Slide	Purpose
01	Recommendation	One-line answer and expected business value.
02	Observed Bottleneck	Evidence of time leak, risk, or decision drag.
03	Proposed Workflow	How INTO changes the operating system.
04	Build Plan	Phases, outputs, timeline, and decision gates.
05	Commercials	Fee, assumptions, exclusions, and acceptance path.
06	Terms & Notices	Validity, confidentiality/use, resource availability, IP/copyright, and SOW precedence.
07	Next Action	Decision needed, owner, date, and working session.

Annotated Proposal Deck Example

This fictional 15-slide proposal deck shows the finished INTO rhythm: SCQA setup, MECE evidence, recommendation, delivery plan, terms, risks, and a specific ask. Client names, values, and figures are placeholder-only.

INTO Consulting / ACME Corp / Project Atlas / May 2026

ACME Corp can turn intake drag into a governed AI workflow.

Proposal for a contained eight-week pilot.

Slide job: Open the proposal with client, project, date, and one decision-oriented claim.
Master layout: Cover.
Primitive: Title.
Evidence form: None; title surface only.
Motion behavior: Cover fade-up entrance from the Slide Motion Catalog.
Title chain: Starts the memo by naming the outcome the deck must prove.

00 / Map

The argument moves from decision context to commitment.

01

Context and decision question.

02

Evidence across three MECE branches.

03

Build plan, investment, risks, and ask.

Slide job: Orient the reader to the proposal's decision arc.
Master layout: Agenda.
Primitive: Agenda.
Evidence form: None; numbered argument map.
Motion behavior: Agenda current-section reveal.
Title chain: Signals that the next slides establish the decision context before proof.

01 / Situation

Manual intake is stable enough to automate safely.

ACME Corp receives repeatable requests through known channels, with visible owners and existing source records.

ChannelOps inboxPatternRepeatableOwnerNamed SourceCRM exportPeriodIllustrative 4 weeksUsePilot baseline

Slide job: Set the neutral current state before tension appears.
Master layout: Proposal Argument.
Primitive: Image And Text adapted to evidence table.
Evidence form: Evidence table with source, period, and owner fields.
Motion behavior: Static sequencing; no motion needed.
Title chain: Establishes why this is a feasible automation candidate.

02 / Complication

Demand rose faster than the review model can absorb.

Indexed request volume / illustrative / four periods

The work is not novel each time, but the approval path treats it as novel. That creates avoidable review load.

Slide job: Name the tension that makes the current state risky.
Master layout: Chart.
Primitive: Chart.
Evidence form: Horizontal volume pattern with unit, period, and source note.
Motion behavior: Evidence stage: chart appears before callout.
Title chain: Moves from feasible current state to why action is needed.

03 / Decision Question

The decision is whether to fund a contained workflow pilot now.

The answer depends on fit, evidence readiness, delivery containment, and commercial risk.

Slide job: Convert the complication into the explicit question the deck answers.
Master layout: Statement / argument.
Primitive: Title.
Evidence form: None; decision statement.
Motion behavior: Focus zoom on the question line, reduced to fade-only.
Title chain: Creates the hinge between SCQ and the answer.

04 / Answer

Start with intake triage because it has owner, evidence, and repeat use.

Owner

One operating lead can approve the pilot path.

Evidence

Existing records are sufficient for an initial control model.

Repeat use

The request pattern recurs often enough to justify setup.

Slide job: Give the executive answer before the detail path.
Master layout: Executive Summary / Conclusion Up Top.
Primitive: Columns.
Evidence form: Three evidence-point summary.
Motion behavior: Evidence stage across three proof points.
Title chain: Answers the decision question directly and previews MECE support.

05 / Evidence A

Branch A: intake volume is concentrated in three repeatable request types.

A pilot does not need to cover every request. It should start where repeatability and volume intersect.

Slide job: Prove the first MECE branch with one dominant exhibit.
Master layout: Chart.
Primitive: Chart.
Evidence form: Ranked bar chart, direct labels implied, source attached.
Motion behavior: Evidence stage: bars reveal, then interpretation.
Title chain: Supports the answer by proving repeatability.

06 / Evidence B

Branch B: approval waits create more drag than drafting.

Cycle-time bridge / illustrative hours

The pilot should govern routing and approval, not only generate first drafts.

Slide job: Prove the second MECE branch by isolating the source of delay.
Master layout: Chart.
Primitive: Chart.
Evidence form: Waterfall bridge with Saffron for the caution segment.
Motion behavior: Evidence stage with sequential bridge reveal.
Title chain: Shows why governance is more valuable than draft automation alone.

07 / Evidence C

Branch C: evidence already exists in governed source systems.

Request intakeINTO routingApproved record

The pilot can route existing sources through validation and approval instead of creating a new shadow knowledge base.

Slide job: Prove the third MECE branch with a controlled source-flow schematic.
Master layout: Schematic / Architecture.
Primitive: Chart adapted as schematic.
Evidence form: Three-layer workflow schematic.
Motion behavior: Schematic build: nodes first, connectors implied second.
Title chain: Completes the evidence case for safe pilot selection.

08 / Approach

A four-phase build keeps the pilot bounded and measurable.

Discover

Confirm records, owners, acceptance criteria.

Define

Map the workflow and approval contract.

Build + Optimize

Ship pilot, measure, and refine.

Slide job: Translate the evidence case into a delivery model.
Master layout: Proposal Argument.
Primitive: Columns.
Evidence form: Four-phase schematic summary.
Motion behavior: Schematic build, reduced to instant show.
Title chain: Shows containment before timeline and investment.

09 / Team

A small senior team covers product, architecture, delivery, and adoption.

Engagement LeadOwns decision pathSystems ArchitectDesigns workflow controlsDelivery PartnerRuns build cadence Client OwnerApproves scopeOps ReviewerValidates evidenceAdoption LeadPrepares rollout

Slide job: Clarify responsibilities and decision rights before commitment.
Master layout: Team / Roles.
Primitive: Team.
Evidence form: Role matrix; no portraits.
Motion behavior: Static; role clarity beats animation.
Title chain: Confirms team sufficiency after the approach.

10 / Timeline

The pilot reaches decision-ready release in eight weeks.

Discover Define Build Optimize

Slide job: Show timing, phases, and the final pilot decision point.
Master layout: Gantt.
Primitive: Timeline.
Evidence form: Gantt plan with Saffron milestone.
Motion behavior: Timeline draw with current marker arriving last.
Title chain: Turns approach into schedule.

11 / Investment

The investment stays fixed while assumptions remain intact.

PhaseDiscover + defineUnits12 fictional unitsAssumptionOne workflow PhaseBuild + optimizeUnits36 fictional unitsAssumptionNamed reviewer Total48 fictional unitsValidity30 daysPathSOW controls

Slide job: Show commercial structure without hiding assumptions.
Master layout: Evidence / Table.
Primitive: Budget Table.
Evidence form: Budget table using fictional units, terms, and assumptions.
Motion behavior: Static; commercial terms stay visible.
Title chain: Connects schedule to bounded commercial decision.

12 / Risks

The main risks are access, adoption, and evidence quality.

AccessRecords arrive lateSeverityAmberMitigationData cut by kickoffOwnerClient AdoptionReviewer bypassSeverityAmberMitigationApproval gate trainingOwnerINTO EvidenceSource driftSeverityGreenMitigationWeekly source auditOwnerShared

Slide job: Expose uncertainty and containment before the final ask.
Master layout: Evidence / Table.
Primitive: Risk / Issue.
Evidence form: Risk table with severity, mitigation, owner.
Motion behavior: State highlight allowed; no decorative severity animation.
Title chain: Shows the recommendation is bounded by explicit assumptions.

13 / Decision

Approve the pilot scope and nominate the operating owner.

DecisionApprove one-workflow pilot scope. OwnerNominate ACME operating owner by Friday. RouteKickoff once source pack and reviewer are confirmed.

Slide job: Close with the specific decision, owner, route, and timing requested.
Master layout: Decision / Ask adapted from Cover emphasis.
Primitive: Decision / Ask.
Evidence form: Decision list; no new data.
Motion behavior: Focus zoom on the ask, reduced to fade-only.
Title chain: Completes the memo by converting the recommendation into action.

Project Status Pattern

A status deck is an operating document. It should reduce meeting time by making decisions and risks visible before the call starts.

Order	Slide	Purpose
01	Executive Pulse	Green, Saffron, red only when tied to decisions.
02	Shipped	What changed, what is now usable, what was verified.
03	At Risk	Risks, blockers, dependencies, and impact.
04	Decisions	Decision, owner, deadline, recommendation.
05	Next Sprint	Planned work, validation target, expected output.
06	Asks	Access, approvals, meetings, data, or stakeholder input.

Annotated Status Deck Example

This fictional 8-slide status deck leads with decisions and risks, then asks. It uses placeholder engagement data only and keeps appendix detail out of the meeting path.

ACME Corp / Project Atlas / Reporting period: fictional week 04 Amber

Project Atlas is amber because source access is the only unresolved blocker.

Slide job: Declare project state, reporting period, and why the state is Amber.
Master layout: Cover.
Primitive: Title.
Evidence form: Status pill using Saffron for Amber.
Motion behavior: Cover fade-up entrance.
Title chain: Starts with the status judgment and its cause.

01 / Headline

The pilot is on plan, but export readiness depends on one source cut.

Shipped

Workflow shell and review gate are ready.

Blocked

One source file is not yet approved.

Ask

Confirm source owner by Friday.

Slide job: Give one-sentence status and three support points.
Master layout: Executive Summary / Conclusion Up Top.
Primitive: Columns.
Evidence form: Three-point status summary.
Motion behavior: Evidence stage across three points.
Title chain: Explains the cover's Amber status in one line.

02 / Progress

Build progress is ahead of workshop readiness.

Discover Define Build Adoption

Slide job: Show progress and the current marker before decision records.
Master layout: Gantt.
Primitive: Timeline.
Evidence form: Phased timeline with current marker.
Motion behavior: Timeline draw with marker arriving last.
Title chain: Connects the status judgment to visible schedule state.

03 / Decisions Made

Three operating decisions are now locked.

DecisionOne workflow firstOwnerACME OpsDateFictional W03 DecisionHuman approval before exportOwnerINTODateFictional W03 DecisionWeekly source auditOwnerSharedDateFictional W04

Slide job: Record decisions made with owner and date.
Master layout: Evidence / Table.
Primitive: Decision / Ask adapted to owner/action/date.
Evidence form: Owner/action/date table.
Motion behavior: Static; decision records stay visible.
Title chain: Separates closed decisions from needed decisions.

04 / Decisions Needed

Two decisions need stakeholder input before release.

Source ownerConfirm who approves the final source cut by Friday. Release windowChoose pilot release window after source approval.

Slide job: Make stakeholder decisions explicit and time-bound.
Master layout: Decision / Ask.
Primitive: Decision / Ask.
Evidence form: Decision list.
Motion behavior: Focus zoom on the two needed decisions.
Title chain: Moves from what is locked to what is needed.

05 / Risks

Source access is the only risk with schedule impact.

RiskFinal source cut lateSeverityAmberMitigationNamed approver by FridayOwnerClient RiskReviewer unavailableSeverityGreenMitigationBackup reviewer trainedOwnerINTO

Slide job: Show current risks with severity and mitigation.
Master layout: Evidence / Table.
Primitive: Risk / Issue.
Evidence form: Risk table.
Motion behavior: State highlight allowed for Amber row.
Title chain: Proves why the deck remains Amber but contained.

06 / Asks

Stakeholders need to confirm access, reviewer, and release window.

Access

Approve final source cut by Friday.

Reviewer

Name backup approver before release.

Window

Select release slot after access clears.

Slide job: List specific stakeholder asks with deadlines.
Master layout: Decision / Ask.
Primitive: Columns.
Evidence form: Ask list.
Motion behavior: Evidence stage across asks.
Title chain: Turns risk mitigation into concrete stakeholder action.

07 / Appendix Marker

Detailed logs sit in the appendix, not the meeting path.

Use the appendix for source lists, test logs, and issue history after the decision path is clear.

Slide job: Close the status path and point to detail without adding an appendix wall.
Master layout: Section Break / Appendix marker.
Primitive: Title.
Evidence form: None; appendix pointer.
Motion behavior: Fade-only title entrance.
Title chain: Ends the status memo by preserving meeting focus.

Investor Presentation Pattern

Investor presentations should still feel like INTO: precise, evidence-led, and operational. Avoid hype vocabulary and oversized market theatre.

Order	Slide	Purpose
01	Thesis	The change in the market and why now.
02	Problem	The operator pain, quantified in time, money, or risk.
03	Proof	Traction, case evidence, learning velocity, or validated demand.
04	System	Product, workflow, data advantage, or service model.
05	Market	Segment, entry wedge, expansion path, buyer logic.
06	Business Model	Commercial mechanics, margin logic, and repeatability.
07	Ask	Capital or support requested, timing, and use of funds.
08	Appendix	Reader-first evidence for diligence.

Interactive Decks Use The Same Masters

Interactive decks can use stronger web-rendering tools, but the job still starts with the static INTO master. Choose the library from the communication job, not from novelty.

Tool	Owns	Use When	Do Not Use For	Fallback / State
D3.js	Data graphics	Custom charts, data-driven infographics, animated evidence reveals, axes, scales, labels, joins, and bespoke quantitative exhibits.	Decorative motion, generic dashboards, unsupported numbers, or charts that could be clearer as a static table.	Final readable chart with conclusion title, direct labels, source note, loading, empty, partial-data, and error states.
Mermaid	Text-defined diagrams	Quick flowcharts, sequence diagrams, Gantt diagrams, and source-controlled process diagrams where editability matters more than art direction.	Client-facing diagrams that need refined visual polish, complex brand composition, untrusted diagram text without review, or dense strategy maps.	Rendered SVG or static screenshot with labels intact, security-reviewed source text, and an editable source block in the appendix when useful.
Three.js	Meaningful 3D	Spatial models, architecture walkthroughs, object/system demonstrations, or portfolio-style environments that cannot be explained in 2D.	Decorative 3D, spinning logos, novelty backgrounds, or evidence that needs exact chart reading.	Static hero frame or annotated 2D diagram; reduced-motion shows the final state and all labels without camera movement.
PixiJS	High-performance 2D scenes	Dense animated maps, sprite/canvas-heavy explainers, simulation-like state systems, or high-volume 2D rendering.	Particle decoration, atmospheric loops, or simple charts and diagrams that D3, Mermaid, or static SVG can handle.	Static canvas capture, visible legend, state summary, and non-animated final frame for export and reduced motion.

Reveal.js Rules

Map each slide to a canonical master class such as into-slide--proposal-argument or into-slide--chart.
Default to one or two columns with clear margins. Do not use reveal.js as permission for custom slide theatre.
Use fragments only for pacing evidence, not hiding essential context.
Speaker notes may support delivery, but the visible slide must read without them.
Nested vertical slides are appendix or drill-down only; the horizontal path must carry the argument.
PDF export must preserve order, source notes, captions, and the footer system.

Anime.js Rules

Animate meaning: chart reveal, timeline current marker, schematic path draw, evidence callout, or section transition.
Use short, calm timelines. Motion is a reading aid, not a performance layer.
Respect prefers-reduced-motion and provide a non-animated state.
Do not use looping backgrounds, decorative parallax, glow, or kinetic filler.
Never animate the only copy of a source note, assumption, legal term, or decision line out of view.

Interaction States

Every click, key press, filter, scrub, or fragment advance needs an immediate response state.
Every dynamic chart, diagram, scene, or canvas needs loading, empty, partial-data, error, success, and static states.
Focus order follows the reading order: title, control, exhibit, source, footer. Keyboard users must not enter hidden fragments.
Tooltips and highlights add interpretation, but they never contain the only copy of essential evidence.
Reduced-motion mode shows the final readable state, not a broken first frame.

Static Fallback Review

Export a PDF or static HTML capture before review and read it without presenter notes.
Confirm assumptions, sources, legal terms, decision lines, and contact routes remain visible.
Check that D3 and Pixi outputs preserve INTO color rules and do not invent decorative palettes.
Check that Mermaid diagrams are not accepted raw when the visual hierarchy fails the deck grid.
Require explicit justification before using Three.js or PixiJS in a client-facing deck.

Interaction	Allowed Use	Static Fallback
Fragment reveal	Evidence points, agenda current state, staged recommendation proof.	All fragments visible in PDF order.
Chart draw	One selected data path, bar sequence, or KPI delta explanation.	Completed chart with conclusion and source note.
Timeline marker	Current phase, milestone, dependency, or handoff.	Marker visible at final state with label.
Schematic path	Workflow route, approval path, data movement, or exception path.	All nodes and connectors visible with labels.
Section transition	Blueprint Dark pause between chapters.	Static section break master.

example-slides-interactive-agent-rule

Agent Rule

For interactive decks, generate the static master first. Then select reveal.js, anime.js, D3.js, Mermaid, Three.js, or PixiJS only when that tool is the clearest way to express the argument while preserving export readability.

Review The Deck Like A Document

INTO decks are often read before or after the meeting. Review must test the PDF reading path, not only the slide canvas.

Human Review Examples

Cover: Can the client, date, and title claim be read in one glance?
Executive Summary: Is the conclusion visible before supporting evidence?
Chart: Does the title state the takeaway and does the source note sit on-slide?
Terms & Conditions / Legal Notices: Are validity, confidentiality/use, resource availability, IP/copyright, assumptions, and SOW precedence visible without speaker notes?
Thank You: Is the next action concrete, dated, and easy to contact?

AI-Readable Constraints

Always declare deck contract: proposal, status, investor, or reader-first editorial.
Always generate the decision brief before generating slide bodies.
Always generate and check the title chain before styling the deck.
Always declare slide mode: reader-first or presented.
Use canonical master names exactly as written in this file.
Use brand/layout-composition-system.md for proximity, executive relevance, visual-first evidence, and motion decisions.
Use brand/data-visualization-system.md for KPI, chart, Gantt, table, and schematic slides.
Use source notes, method notes, units, periods, and assumption labels for every quantitative claim.
Reject bar charts built from unquantified headlines.
Do not use the four-point star, thick circle, or square mark as bullets.

Gate	Pass Condition
Contract	Deck type, audience, and delivery mode are stated before slide creation.
Decision Brief	Audience, decision, recommendation, SCQA, MECE support points, evidence, and appendix depth are defined.
Title Chain	Slide titles alone read like a coherent executive memo.
Master	Every slide maps to a canonical master or has a documented reason for a new layout.
Readability	Reader-first body is 16pt or larger; presented screen-share body is 22pt or larger.
Composition	Related items are closer together than unrelated items; visible copy passes the executive filter.
Evidence	Charts, tables, KPIs, Gantt plans, and schematics include conclusion, source context, unit, period, method, and assumption when relevant.
Visual First	Analytical slides use one dominant exhibit before prose. Text-only slides have a clear reason.
Type Floors	KPIs, tables, charts, annotations, source notes, footnotes, and buttons stay above minimum type floors.
Terms	Proposal/commercial decks include readable terms and notices before the final CTA.
Brand Devices	Petrol, star, circle, mark, and gradients reinforce meaning and are not decorative filler.
Motion	Presented or interactive decks declare the motion job or explain why static sequencing is clearer.
Export	PDF export preserves order, links, captions, source notes, and bottom-right safe areas.

Theme And Layout Governance

The theme is the control plane. Layouts should carry repeated judgment so agents and humans are not rebuilding the brand on every slide.

Use theme colors for Warm Light and Blueprint Dark. Do not create one-off near matches.
Use Newsreader, Lexend, and IBM Plex Mono only.
Create master layouts for cover, section break, agenda, executive summary, proposal argument, evidence/table, KPI, chart, Gantt, schematic/architecture, quote, team/roles, Q&A, thank-you, and appendix slides.
Do not mix Warm Light and Blueprint Dark on the same slide except for small marks, lines, or restrained signal elements.
Use petrol for action, signal, and measured emphasis. Do not use it as decorative fill.
Use the four-point star only for north-star goals or compact AI cues and the thick circle only for framing one key idea. Never use either device as bullets.
Use the data visualization system for chart, KPI, Gantt, evidence/table, and schematic masters.

Review As A Deck And A Document

A Google Slides file can pass in presentation mode and fail as a readable PDF. The export check is part of the spec, not an afterthought.

Present the deck once at screen-share size and check that body text is readable.
Export to PDF and check page order, links, charts, captions, and appendix readability.
Check bottom-right safe area on title, recommendation, chart, and call-to-action slides.
Confirm the title chain reads as a coherent executive memo.
Confirm every analytical slide has one dominant exhibit and an implication.
Confirm every chart has a conclusion, source, and readable label.
Confirm every number has a source note or assumption label.
Confirm the deck can be read without speaker notes.

Research Basis

Platform constraints come from official Google help sources. Interactive library guidance comes from primary project sources. Deck logic is benchmarked against B&O governance, Accenture public research reports, McKinsey-style executive communication doctrine, design/research consultancy practice, and the current INTO Consulting website for positioning signals.