Run with Browser AI · Chapter 05
Run Chapter 05: Browser AI Switchboard
Inspect seven browser-managed AI interfaces side by side without flattening their distinct contracts.
← Read One Runtime, Several Interfaces
Execution
Not inspected
Observed state machine
What “built-in” means in this browser
No capability call has been made in this page yet.
- 01Not inspected
- 02Unsupported
- 03Unavailable
- 04Downloadable
- 05Downloading
- 06Available
- 07Session ready
- 08Running
- 09Completed
- 10Failed
Derived from events
Observatory measurements
Missing evidence stays missing. The dashboard never estimates an absent measurement.
Application instrumentation
Cross the boundary without erasing it
The page can validate what it sends. Extension receipt is confirmed only in the attached DevTools panel.
- 01Application SDKBuild a sanitized envelope
- 02Same-origin bridgeValidate schema and size
- 03Extension transportRoute by inspected tab
- 04DevTools panelConfirm receipt and correlate
To test end to end, load the Observatory extension, attach DevTools to this tab and enable instrumentation for this origin.
Shared lifecycle · distinct contracts
Browser AI capability switchboard
No interface has been inspected. Each check will use that interface's declared creation options.
| Interface | Global | Exposed | Availability | Options |
|---|
Canonical fixture · live task API
Summarization contract
Exposed Not inspected
Availability —
Session None
Load the canonical fixture, then inspect the current browser.
Generated artifact
No summary yet.
Contract evaluation
- No evaluation yet.
Ranked evidence · explicit routing policy
Language routing laboratory
Choose a fixture, then inspect Language Detector.
Ranked detector evidence
| Rank | Language | Confidence | Use |
|---|---|---|---|
| No ranked candidates yet. | |||
Translated artifact
No translation yet.
Translation evaluation
- No translation evaluation yet.
Resource state · measured lineage
Session lineage laboratory
Prompt API Not inspected
Availability —
Inspect the current browser before creating a session.
Original session
Not created- ID
- —
- Parent
- None
- Usage
- —
- Quota
- —
- Remaining
- —
- Clone / destroy
- —
No output yet.
Cloned session
Not created- ID
- —
- Parent
- —
- Usage
- —
- Quota
- —
- Remaining
- —
- Clone / destroy
- —
No output yet.
Shared-history acknowledgement
No shared-history run yet.
Lifecycle invariants
- No invariants evaluated yet.
Chapter experiment
One Runtime, Several Interfaces
Loading the chapter experiment…
No model output yet.
Inspect the context supplied by this chapter
What this experience knows
This experience is grounded in Chapter 05 and the distinction between a shared lifecycle and distinct task contracts.
Common lifecycle
Each interface can expose an availability check, an asynchronous creation step, optional acquisition progress, an operation and a terminal result. That common shape supports one observable adapter.
Distinct contracts
- Prompt leaves the task definition in instructions and context.
- Summarizer exposes summary type, format and length.
- Writer creates new material under tone, format and length constraints.
- Rewriter transforms supplied material while preserving an explicit relationship to the input.
- Proofreader returns correction-oriented structured output.
- Translator has declared source and target languages.
- Language Detector returns ranked language hypotheses rather than generated prose.
Evidence boundary
The capability matrix reports what each global and availability(options) call returns in this page. It does not attest the physical model, download sharing, implementation vendor or behavioral quality behind an interface.
Reuse rule
The adapter may normalize lifecycle events and transport. It must preserve API identity, creation options, operation name and output shape so later chapters can evaluate the feature actually exposed to users.
This experience inspects the Prompt, Summarizer, Writer, Rewriter, Proofreader, Translator and Language Detector interfaces in the current browser. Each availability call receives the options declared for that particular API.
The matrix reports exposure and operational availability separately. It does not infer that the interfaces share one downloaded model or that one available API implies the others are available.