Run with Browser AI · Chapter 07
Run Chapter 07: Text Authority Laboratory
Compare Writer, Rewriter and Proofreader as operations with different permission to change text.
← Read Writing, Rewriting and Proofreading Are Different OperationsObserved 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
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
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
Writing, Rewriting and Proofreading Are Different Operations
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 07 and evaluates text operations by their permitted delta.
Authority levels
- Writer may create a new artifact from a request.
- Rewriter may transform an existing artifact along declared dimensions while preserving protected meaning.
- Proofreader may correct a narrow class of errors and should leave correct material unchanged.
Evaluation boundary
Fluency is not a shared success criterion. Writer is checked against artifact requirements, Rewriter against transformation plus invariants, and Proofreader against structured correction evidence and unnecessary edits.
User control
Generated or transformed text remains a proposal. A production interface should show the operation, preserve undo and make meaningful changes reviewable.
Evidence boundary
Operational completion does not establish that an authority boundary was respected. The trace records the requested API and options; the fixture records automatic checks and leaves semantic preservation or correction completeness for human review.
This laboratory runs the three canonical Observatory fixtures for Writer, Rewriter and Proofreader. Select an operation to see its authority level, options, source/request distinction and evaluation contract before creating a browser-managed instance.
The replay trace contains none of these task APIs. It remains available as earlier Prompt API evidence and is never presented as a Writer, Rewriter or Proofreader result.