Browser
Give governed agents a browser surface and bring capture back into Primitive.
Primitive Browser exists as part of the wider estate, while the canonical Workspace release still lists end-to-end browser acceptance and typed bridge wiring as remaining work.
Primitive can have a set of eyes and hands on the web, but the final connection between that browser and the main OS still needs to be treated as a real integration, not assumed because both pieces exist.
The browser should serve two directions: outward execution for agents and inward capture for people. Both directions need identity, permissions, provenance and durable receipts so browsing does not become an ungoverned side channel.
Estate capability
Primitive Browser is a separate estate capability and is included in the canonical reuse preflight.
Remaining integration
Workspace's release notes explicitly retain Primitive Browser end-to-end acceptance and typed bridge wiring as a remaining environment/integration gate.
Target contract
Browser actions should enter the Harness/runtime as typed executions, while captured pages/observations should enter Capture/Knowledge with source provenance.
Where this description comes from
These pointers are the authority behind the status and technical description. If implementation and documentation disagree, the canonical implementation or Control contract wins and this page should be corrected.