DiscoveryServicesHow We WorkPlatformSolutionsInsightsDocsStart with the Map
Docs/Product/Brevet Overview

Brevet Overview

Brevet is an HTML-first document studio: you compose a proposal, report, operating manual, or client deliverable once, and render it as an interactive web document or a polished PDF from the same structured source — no re-formatting the same work for each channel.

What Brevet produces

  • Interactive HTML — the canonical Brevet output: responsive, navigable, and capable of carrying interactive elements in the browser.
  • PDF export — a paginated, archival rendering of the same document for printing, review, and conventional exchange.
  • One source of truth — both outputs render from a single structured document, so the web version and the PDF never drift apart.

The rendering model

One structured document, rendered to the output the moment needs. The initial priority is reliable HTML rendering and PDF export; presentation and video are later-stage capabilities.

  • Interactive HTML — the primary experience today.
  • PDF — paginated export for print, compliance, and document exchange.
  • Presentation mode · planned — scene-based navigation and fullscreen delivery of the same material.
  • Video rendering · planned — capture a presentation timeline as MP4/WebM.
  • Additional exports · later — images and other formats where the conversion preserves the source’s meaning and layout.

The document model

A Brevet document is composed of blocks rather than free-form pages — headings, paragraphs, lists, dividers, callouts, stats, and feature rows — rendered from one structured source. Curated design systems keep the result on-brand instead of looking like a generic template.

How ProxyScout uses it

Brevet is intended to power Discovery reports, proposals, operating manuals, capability specifications, training materials, executive presentations, and client handoff packages — one source carrying the work everywhere it needs to go.

Status

Status · Development

Brevet is in active development. It is not generally available, sign-ready, payment-enabled, or legally archival, and should not be described as such until those behaviors are implemented and verified. Follow the build or ask how it could carry a specific deliverable — get in touch.

Related