Domstamp

0.3.0 previewSchema 2Drivers Playwright + Puppeteer

Capture the browser state an automation agent can perceive—DOM, frames, interaction, geometry, and consistency—in one bounded, validated snapshot.

Start capturing →Inspect the schema

One capture, four accountable stages

Every stage is typed, bounded, and independently replaceable.

1. TargetPage or driver session
2. AdapterAccessible browser state
3. CoreValidate, retry, transform
4. SnapshotSchema 3 or TQ1

Make the first capture

• Install the core and Playwright adapter5 min
• Choose document, viewport, or focusGuide
• Capture frames and open Shadow DOMGuide

Build on the contract

• Author a driver adapterExtension
• Transform snapshots with pluginsExtension
• Validate against the browser gymOperate

Capture capability ledger

Boundaries are declared before capture, never hidden afterward.

SupportedDOM · open Shadow DOM · templates

SupportedSame- and cross-origin frames

SupportedARIA perception trees · masked pixel evidence

SupportedTrusted structural redaction

UnavailableClosed Shadow DOM · browser chrome · JavaScript heap

The contract in one sentence

Domstamp asks a typed adapter to capture accessible browser state, validates the resulting graph, applies bounded orchestration, and returns a driver-independent snapshot.

It is intentionally split into four packages:

Package	Owns	Runtime dependencies
domstamp	Schema, configuration, orchestration, evidence providers, validation, plugins	None
@domstamp/playwright	Playwright adapter, ARIA perception capture, and pixel evidence	playwright-core peer and YAML parser
@domstamp/puppeteer	Puppeteer adapter for DOM, frames, layout, and interaction	puppeteer-core peer and shared preview walker
@domstamp/tq1	Dictionary encoding and bounded gzip transport	Node standard library

Preview contract

Version 0.3.0 is suitable for evaluation. Schema 3 records evidence provenance and explicitly migrates stored schema-1 and schema-2 snapshots. During 0.x, readers retain at least the two preceding schemas; schemas accepted at 1.0 remain readable throughout 1.x. Read Release status before treating a preview API as stable.