Brand | Slide charter

Slide charter

Build on-brand Rippletide slides from the same design language as the website. This page defines the canvas, themes, type scale, reusable templates, and deck blueprints so any team member (or AI assistant) can build a pitch deck or tech deck that looks and reads like Rippletide. For programmatic access, see the machine-readable manifest below.

/.well-known/slides.json Brand assets

Canvas

Aspect ratio: 16:9
Working size: 1280 x 720 px
Safe margin: 64px
Grid: 12 columns, 24px gutter, 8px baseline

Design at 1280x720; multiply every value by 1.5 for a 1920x1080 export.
Keep all text and key elements inside the 64px safe margin on every edge.
One idea per slide. If a slide needs a second headline, split it in two.
Generous whitespace is on-brand. Do not fill the canvas edge to edge.

Themes

Light (default)The default for most slides: content, bullets, diagrams, stats, comparisons.

Dark (impact)Section dividers, the big statement, the vision, and the closing CTA. Use to mark a beat in the narrative.

Warm gradient (cover)Cover slide and occasional feature highlights. Use sparingly, never for dense text.

Type scale

Poppins for everything except code, which uses JetBrains Mono. Sizes are set for the 1280 x 720 canvas.

Role	Font	Size	Weight	Usage
coverTitle	Poppins	68px	800	Cover headline and the single big statement slide. One per deck section.
slideTitle	Poppins	42px	700	The headline of a standard content slide. Max two lines.
eyebrow	Poppins	14px	600	Short label above the title (e.g. THE PROBLEM, HOW IT WORKS). Muted or accent color.
subtitle	Poppins	22px	400	One supporting sentence under a title. Secondary text color.
body	Poppins	18px	400	Body copy and bullet text. Keep to 3 to 5 bullets per slide.
statValue	Poppins	72px	800	The number in a stat block (e.g. 99%, <600ms, 100%). Navy on light.
statLabel	Poppins	16px	600	The label under a stat value. Secondary text color.
caption	Poppins	14px	400	Footnotes, source lines, and slide captions. Secondary text color.
mono	JetBrains Mono	16px	400	Terminal blocks, code, traces, and policy IDs. Always on a dark panel.

Components

Eyebrow label

Uppercase, 0.2em letter spacing, 14px, muted (#61649b) or accent (#ff8a63). Sits directly above the title.

Pill badge

Fully rounded (border-radius 999px), navy fill (#2a2a64) with white text, or accent outline. Use for status badges like "Live on AWS Bedrock".

Surface card

White (#ffffff) fill, 28px corner radius, soft shadow 0 20px 50px rgba(29,28,80,0.12), ~32px inner padding. Group related points or a single pillar.

Gradient feature card

Tall card with a coral gradient (linear-gradient(160deg, #f5845e, #ffb2b5)) or navy fill, white text, large 24px+ heading. Use for the 3 to 4 product pillars.

Bullet list

No native bullets. Use a coral glyph marker: "✦" for feature lists, "→" for key takeaways, "•" for plain lists. 18px body, ~12px gap between items.

Stat block

Big navy number (72px/800) over a 16px muted label. Group three across in a light panel (#f2f4ff) with a 28px radius.

Terminal / trace block

Dark navy panel (#1f1f50), JetBrains Mono 16px, light text (#e8e8f0), 20px radius. Status glyphs: "✓" pass (green), "⚠" warning (accent), "→" decision. The signature Rippletide demo visual.

Three-block flow

Left to right: Agent -> Rippletide -> Execution. Three rounded boxes joined by accent arrows. Center box is navy filled; the outer two are outlined.

Logo / proof row

A single horizontal row of monochrome partner or investor logos on the page background, evenly spaced. Add a muted eyebrow above (e.g. POWERING PRODUCTION AGENTS AT).

Slide templates

Coverwarm

Open the deck. Logo, one-line positioning, optional status pill.

Logo top-left. Cover title centered or lower-left. Pill badge and date/audience in a bottom row.

Section dividerdark

Mark a new chapter of the narrative.

Large section number or eyebrow, then a coverTitle. Lots of empty space.

Big statementdark

A single sentence that reframes the problem. The emotional beat.

One coverTitle sentence, centered, with an accent keyword. Nothing else.

Problem / contextlight

Explain the gap. Text-led.

Eyebrow + slideTitle on the left third, body and a short bullet list on the right two-thirds.

How it workslight

Show the architecture in three blocks.

Title at top, three-block flow diagram centered, one caption line under it.

Pillars gridlight

Three or four product benefits, one per card.

Title at top, a row of 3 to 4 gradient/navy feature cards, each with a heading and one line.

Product demolight

Show the product working with a real trace.

Short title, a terminal/trace block taking the lower two-thirds, one caption.

Stats / prooflight

Quantify the value with three numbers.

Title at top, three stat blocks across the middle in a light panel.

Comparisonlight

Before vs after, or us vs the alternative.

Two columns of cards. Left column muted (the old way), right column accent-highlighted (Rippletide).

Quotelight

Customer or analyst proof.

Large quote in slideTitle size with an accent left border, attribution line below in caption style.

Social prooflight

Clients, team pedigree, or investors.

Eyebrow label, then one logo row. Stack up to three labelled rows (clients / team / backed by).

Roadmap / visiondark

Today vs tomorrow. Where this is going.

Two-line coverTitle (Today: ... / Tomorrow: ...), short body, optional horizontal timeline.

Teamlight

Founders and key hires.

Row of cards, each with a circular avatar (navy ring), name, role in accent, one-line bio.

Closing CTAdark

Drive the next step.

One coverTitle question, a single primary action line, and contact details in caption style.

Deck blueprints

Pitch deck

Audience: Investors and executive buyers. Goal: Move from "here is the future" to "what about you?" across one tight narrative arc.

1cover
The decision context graph for enterprise AI agentsLogo, one-line positioning, "Live on AWS Bedrock" pill.
2statement
What if every agent decision had to pass deterministic execution?The reframe. Dark theme, accent on the verb.
3problem
The problem isn't intelligence. It's trust.The 85% that works is the LLM. The 15% that blocks production is the gap.
4demo
See it workRefund approval trace ending in ESCALATE. Caption: "Your LLM proposed. Rippletide caught what it missed."
5flow
One layer. Total control.Agent -> Rippletide (Validate, Enforce, Audit) -> Execution or Rejection.
6pillars
What changes for your agentsDeterministic decisions, Pre-execution enforcement, Full audit trail, Production-grade reliability.
7statement
Every day without enforcement is a day of exposureThe cost of doing nothing. A mirror, not FUD.
8logos
Built for your stack. Already.Integration logos, then clients, then team pedigree (AWS, Meta, DeepMind, Imperial).
9stats
Provable in production<1% hallucination rate, 99%+ accuracy, 100% decision traceability.
10roadmap
Today: the decision graph in your agent stack. Tomorrow: the decision layer in every AI system.The ambition slide.
11team
Built by operators who have done this beforePatrick Joubert (3 exits), Yann Bilien (Chief Scientist). Backed by OneRagtime.
12cta
Your agents are already making decisions. The question is whether you control them.CTA: 2-week validation sprint. Contact line.

Tech deck

Audience: Engineering leaders, architects, and developer audiences. Goal: Earn technical trust: explain the architecture, the determinism, and the integration path.

1cover
Rippletide: the decision runtime for AI agentsLogo, one-line technical positioning.
2problem
Why 95% accuracy fails in productionProbabilistic decisions compound. The gray zone blocks deployment.
3flow
Where Rippletide sitsDrop-in layer between any LLM/framework and the real world. Framework-agnostic.
4pillars
The Hypergraph Decision DatabaseMemory (facts, context, provenance) + reasoning (plans, rules, constraints) in one database.
5flow
The decision pipelineCheck facts -> apply policy-as-code -> log causal trace. Neuro-symbolic engine.
6demo
A deterministic traceTerminal block: validated facts, policy version, ESCALATE decision, full audit trail.
7comparison
Monitoring vs pre-execution enforcementLeft: flagged 3 days later. Right: prevented before it executes.
8pillars
Memory hierarchy for coding agentscompany > team > personal, resolved deterministically. Pre-merge regression prevention.
9stats
Performance and reliabilitySub-600ms, 99.9% uptime, <1% hallucination rate.
10logos
IntegrationsAWS Bedrock AgentCore, LangChain/LangGraph, CrewAI, Agentforce, Google ADK, Claude Code, Mistral, NVIDIA, Snowflake.
11pillars
Compliance and securitySOC 2 Type II, GDPR/CCPA ready, EU-resident servers, PII encryption, row-level access.
12cta
Deploy in hours, not quartersCTA: Executive Benchmark Sprint (10 days). Talk to our engineers.

Rules

No em dashes or en dashes anywhere on a slide (titles, body, captions, notes). Use commas, periods, colons, or parentheses.
One idea per slide. The headline states it; everything else supports it.
Headlines are sentences or sharp fragments, not labels. Lead with the point, not the topic.
Maximum 3 to 5 bullets per slide, each one line. If you need more, split the slide.
Use the light theme by default. Switch to dark only for the statement, divider, vision, and closing slides.
Accent coral (#ff8a63) is for one emphasis per slide: a keyword, a CTA, or a bullet marker. Never for body text.
Numbers earn their size. Only the stat slide uses statValue type; keep claims to verifiable metrics.
Always pair the logo with clear space of at least half the logo height. Never recolor the logo; monochrome uses navy (#2a2a64).
Terminal and code blocks always sit on the dark navy panel with JetBrains Mono. Never put mono text on a light background.
Keep contrast high: navy text on cream or white, white text on navy deep. Do not put muted text on the warm gradient.