One blueprint: a page, an email, a PDF, in any language

Email from a blueprint

renderEmail validates a blueprint at the untrusted tier, then writes a complete email: tables and inline styles mail clients understand, every value escaped, links and images through the untrusted URL policy, and a plain-text part. Content with no email form falls back to its text with a warning; a draft with anything executable is refused whole.

Anything else (charts, diagrams, maps, interactive blocks) falls back to its text. Planned: a dark-mode rule set in the head of the email (today it declares color-scheme: light) and an email envelope profile in a later spec minor.

Print and PDF

Two ways to print the same blueprint. In the browser the player has a print mode, a static paint with page-break rules for its frames, tables and code; the print dialog prints this whole page with the digest on it. Headless, @texuli/tools/print maps the blueprint to a validated document and the owned PDF writer draws it, with no JavaScript, forms or embedded files in the file.

import { renderBlueprintPdf } from '@texuli/tools/print';

const pdf = await renderBlueprintPdf(agentDraft, {
  page: { size: 'a4', orientation: 'portrait' },
});
if (pdf.ok) downloadBlob(new Blob([pdf.bytes], { type: pdf.mime }), 'digest.pdf');

<Player blueprint={agentDraft} print />

Every label from one message catalog

Component labels resolve through @texuli/core/i18n: an instance prop first, then the catalog in context, then the English default next to the component. Locales load lazily, plurals and selects follow Intl, and catalogs from outside are validated. English is the default, and opt-in Spanish catalogs ship from 0.14.3; other translations are planned, and hosts can load their own catalogs today.

import { createI18n } from '@texuli/core/i18n';
import { setI18nContext } from 'texuli';

const i18n = createI18n({
  locale: 'en',
  loaders: { 'pt-BR': () => import('./locales/pt-BR.ts') }, // loads only when active
});
setI18nContext(i18n); // in the root component's script
await i18n.setLocale('pt-BR');

What keeps it safe

Static outputs are built, not templated. These hold by construction.

• Validation first

  Email and print run validateDraft at the untrusted tier with the deep block schemas and the sink scan before mapping anything; only the sink-free render tree is ever read.

• Escaped by construction

  Email HTML is built with the markup builders of @texuli/core: element and attribute names are allowlisted, every value is escaped, and there is no raw-markup API. No scripts, style elements, forms, frames or event handlers.

• Links and images through the URL policy

  Links must end up absolute https or mailto, images absolute https, at the untrusted tier. A refused link keeps its text; a refused image keeps its alt text.

• Messages are text

  formatMessage makes one pass with no recursion: a value is never scanned again, so a value holding {name} stays literal. Translation files are checked by parseCatalog: bad ids, prototype keys and oversized messages are dropped with an issue.

import { renderEmail } from '@texuli/tools/email';

const { ok, html, text, diagnostics } = renderEmail(agentDraft, {
  preheader: 'Orders up 12%',
  baseUrl: 'https://example.com/',
});
if (ok) await mailer.send({ html, text }); // your mail service

Package docs

The site does not render the package docs yet. Read them in the repository:

• Email: packages/tools/docs/email.md
• Print and PDF: packages/tools/docs/print.md
• Player print mode: packages/player/docs/embedding.md
• Message catalog: packages/core/docs/core-i18n.md
• Primitive labels: packages/primitives/docs/i18n.md