# Mirror Physics Blueprint — internal presentation profile

## Scope and authority

Activate only for an explicitly internal Mirror Physics deck or an explicit request for the Mirror Physics Blueprint template/style. Mentioning Mirror Physics in slide content, using Fractal, or having Figma MCP installed does not select this profile. External or unspecified audiences do not inherit it. This profile is canonical brand evidence within the existing presentations domain, not a general presentation guide.

Select the output format separately through [Fractal routing](../../routing.md). For Figma Slides, pair this profile with [the Figma workflow](../figma-slides.md). For a requested PowerPoint file, pair it with the create/edit PPTX workflow. This profile governs visual choices over generic PPTX design suggestions, including Figtree, Medium titles, and blueprint rules; format tooling still governs file construction and validation. Do not silently replace Figtree or Medium with Arial/Bold; verify font availability and discuss a material substitution if necessary.

Promoted from the supplied presentation guidance on 2026-09-16. User requirements and the [evidence contract](../../evidence-contract.md) take precedence. Historical reference slides are examples, not instructions. Current written corrections override their heavier text, solid markers, or excessive junction markers. The rejected initial template, orbit motif, dark split layouts, edge glows, and candidate teal palette are not approved preferences.

## Explicit foundation

- The slide has a blueprint-like structure: lines define its gutters and sections.
- Decide content hierarchy before placing section rules and markers.
- The outer gutter boundaries follow the highest-level content region. If content is smaller, move those boundaries inward. Do not keep an outer box and add another nested gutter box.
- Deeply inset gutters are allowed for deliberate compositions such as a contact band.
- Hexes mark only the TOPMOST level of hierarchy division. Identify that level explicitly before placing markers. In a title-plus-grid slide, title and grid are the top-level regions; grid cells are subordinate. Keep all useful grid lines, but omit hexes at their internal crossing and at the four places their dividers meet the grid boundary. Retain the four outer corners and the two title/grid boundary endpoints (six hexes total). A divider touching a top-level boundary does not itself become top-level.
- Markers use a stroke and an opaque fill matching the slide background. Solid line-colored markers are incorrect, even where they appear in older examples. Transparent interiors are also incorrect because lines would show through.
- The structure is essential. Rule and marker colors may change to suit the slide's aesthetic.
- A home/cover slide normally features a captivating image. The supplied molecular image is an example and reusable asset, not a mandatory subject for every deck.
- Slide 11's Conduit background and branding remain application-specific; they must not become presentation-wide defaults.

## Measured source geometry

The authoritative blank is [training node 4006:21](https://www.figma.com/slides/bPfzacKuw33w73E5CeJ5rQ/Presentation-template---training?node-id=4006-21).

| Property | Observed value | Interpretation |
| --- | --- | --- |
| Canvas | 1920 × 1080 | 16:9 source dimensions |
| Background | #FAFAFA | Neutral source foundation |
| Horizontal rules | y=48 and y=1032 | Extend across the canvas |
| Vertical rules | x=48 and approximately x=1872 | Extend to the top and bottom canvas edges |
| Rules | 2 px, approximately #E7E7E7 | Quiet structural lines, not a saturated blueprint-paper effect |
| Markers | 14 × 14, 2 px stroke | Custom six-sided diagonal form with subtly rounded corners |
| Marker fill | #FAFAFA | Opaque ground that masks the line crossing |

The source right line was measured at x=1871 with small marker alignment offsets; the new template regularizes it to x=1872 and centers its markers at the line intersections. All other core proportions follow the source. The original marker vector path is retained in [source-geometry.json](source-geometry.json); do not substitute a regular hexagon, diamond, circle, or filled dot.

## Construction sequence

1. Identify the main content hierarchy: one region, left/right split, two-by-two grid, title with content, or a dominant region plus supporting list.
2. Position the content at a useful scale and establish its primary bounds.
3. Move the single outer gutter system to those bounds. Its horizontal and vertical lines continue outward to the slide edges.
4. Draw divisions within that system. Add outlined markers only for the topmost hierarchy level; subordinate divisions retain lines without hexes, including where they touch higher-level boundaries.
5. Add secondary separators only where needed. A list row, chart gridline, metadata row, or table row does not automatically become a primary section break and normally receives no hex.
6. Place markers above the gutter lines so their opaque fill masks the crossing. Artwork may intentionally overlap or crop the gutter treatment on an image-led cover.
7. Check hierarchy and typography at presentation scale, then adjust the gutter positions together with the content.

Allowed choices include changing gutter inset, split ratio, content alignment, number of primary sections, and line color. Consistency comes from this construction logic, not identical margins on every slide. A two-by-two grid can move inward as a whole. A contact band can sit deep inside the canvas. A metric can occupy a broad left region beside a narrow list.

## Minimal text and communication — explicit user preference

Err toward minimal text content specifically. Keep each slide focused on the smallest amount of text needed to communicate its point. This is not a directive to remove useful imagery, diagrams, data marks, or blueprint lines. Omit repetitive explanation, tangential detail, and material the presenter can explain verbally. Empty space is useful; do not fill it simply because it is available.

When useful source material is left out, tell the user in the agent chat which material was omitted or condensed and why. Summarize meaningful omissions by topic; do not burden the user with a word-by-word deletion log. Proceed with a clean draft instead of requesting permission for every routine editorial cut. Speaker notes or an appendix may help when requested or clearly useful, but they are not an automatic dumping ground and do not replace informing the user in chat.

Never remove a caveat, uncertainty, source qualifier, or contradictory result when doing so would make the remaining claim misleading. In that case, qualify the claim concisely, simplify it, or move the whole claim out and explain the choice. Honor explicitly required content.

Example chat handoff: “I left the detailed implementation chronology and repeated examples out of the slides to keep the main argument clear. The key result and its limitation remain on the evidence slide.” Only make that statement when those omissions actually occurred.

## Typography and imagery

Figtree is observed in the training deck and used in the new template. **Hard rule: slide titles use Medium (500); never exceed Medium anywhere.** Use Regular and Medium; SemiBold, Bold, and heavier weights are forbidden in authored presentation typography, including shared styles and text ranges. Use grayscale shades for additional hierarchy, keeping essential text readable. Historical heavier text in reference images is superseded by this explicit rule and must not be copied. The current cover uses 98 px Medium; many explanatory source headings use 48–50 px Regular. The new template uses 50–64 px content headings, 32–40 px body copy, and 24–30 px supporting labels as working values, not newly approved brand tokens. Use fewer words or another slide before making essential content tiny.

Keep typography quiet and subordinate decorative choices to the content. Do not automatically add a wordmark, page number, or footer to every slide. Preserve actual logos as assets; do not reconstruct a logo from plain text.

Use genuine product captures for product claims. Use readable front-facing crops for walkthroughs; perspective and dramatic cropping belong in showcases. The cover may feature large imagery bleeding off the canvas, with title and subtitle in a clear region. Adapt rule colors to the artwork while retaining the structural logic. Do not invent scientific imagery that purports to show verified evidence.

## Template versus finished presentation

Blank foundation slides contain only blueprint geometry. Template slides may include explicit replacement copy and image slots. Finished decks must replace those fields with real material, verify claims and sources, and remove instructional text. The example chart's values are illustrative and must never be treated as facts.

New slide types are allowed when they preserve this structural system. Diagrams, timelines, comparison layouts, charts, and appendices should express their own information hierarchy rather than acquire decorative nested frames.

## Figma implementation

Use native editable text and vectors; images remain replaceable fills. Keep gutter rules and markers named clearly. Read the current Figma skills for API details. Inspect reference files read-only. Build new files only when requested. Verify rendered output and report any remaining limitations honestly.

## Mandatory secondary visual pass: alignment and title weight

After the first content and overflow review, perform a separate visual pass focused on both axes. A new section boundary does not reset the alignment system. Related title and body content should share the same vertical left-edge guide unless a deliberate, content-driven indentation is evident. Peer columns should share top edges or baselines, and matching rows should align across columns.

Check rendered text, not just the text-box coordinates. For nested content, compare absolute slide coordinates rather than local frame coordinates. Verify slide titles actually render in Medium, including local overrides and mixed text ranges; a shared style name is insufficient. Use grayscale, not heavier weight, for additional hierarchy.

The concrete second-pass procedure in [review.md](review.md) is required evidence for this check. A title at absolute x=116 and related body content at x=180 is an unintended 64 px indent even when neither text box overlaps anything. Do not confuse absence of overlap with good alignment.

## Tables and spacing balance — explicit user correction

Show the blueprint; retain useful structural lines wherever they clarify organization. Minimalism reduces extraneous text content, not useful imagery, diagrams, data marks, or the visible structure of the slide. In tables, show both horizontal row rules and vertical column rules so each cell is defined. “Secondary rows stay plain” means no hex at every cell intersection, not missing gridlines. Hexes mark the major sections, such as the title, table, and notes bands.

Keep spacing consistent across equivalent cells and regions. For single-line table cells, balance visible space above and below the text; do not leave noticeably more padding on top than below. Start by centering the rendered text block within the row: `textY = rowTop + (rowHeight - textHeight) / 2`, then check optical balance in the render. Text-box height and font metrics can make mathematically centered text appear off.

Use consistent horizontal cell insets. Align column headers with their body values, and align peer cells vertically within each row. Header and body rows may have different heights when hierarchy warrants it, but each should feel balanced. With multiline content, use consistent row padding and a deliberate shared alignment; increase the row height or simplify copy rather than creating cramped or uneven cells.

The user's adjusted table (template node `6:121`) is the positive reference for these rules. Preserve user edits in the live file; inspect its current state before any future modification.

Notes, source labels, and captions inherit the slide's alignment system. In the corrected table reference, the title, first-column text, and methods/limitations line share one left edge across their section boundaries. Keep spacing balanced within each region while preserving that common anchor.

## Match divisions to the actual ideas

The user accepted the construction-guide critique: four peer principles should be expressed as four regions, rather than two columns of stacked paragraphs with a border added afterward. Use a 2×2 structure for this case, including the horizontal divider, with hexes only for the top-level title/grid division. This is not a requirement that every four-item slide use a grid; choose divisions from the actual hierarchy. Balance content within its regions instead of clustering it at the top above an accidental empty lower half. Preserve shared title/content left anchors and equivalent insets. Condense explanations to short statements when the details already belong in the agent guide. Secondary separators remain visible when useful; only their hex markers are omitted.

## Shared Figma template reference

Use [Mirror Physics — Blueprint Templates](https://www.figma.com/slides/n8T67Y2MXlA0JOMOJdB8v4) as the shared editable visual reference. Inspect relevant slides alongside these guides. Current written corrections take precedence over remaining defects in template slides, especially topmost-only hex placement, Medium titles, alignment, and spacing. Treat the template as read-only unless explicitly asked to edit it. Create a new destination file when adapting another presentation; preserve the source.