Code and tests are the evidence of present behavior. Where documents appear to
disagree, security-model.md controls claims about enforced security,
architecture.md controls the browser foundation, and product-system.md
controls product intent.
- Architecture: implemented browser structure, domain ownership and native lifecycle.
- Security model: the guarantees the tree enforces and the gates for disabled capabilities.
- Product system: what Zephium is, the first-release scope and the target architecture.
- Frontend contract: stack, ownership, import boundaries and native presentation rules for
frame/.
- Interface design: why the browser chrome is shaped the way it is.
- Interface system: tokens, shared components and how to inspect them.
- Settings: settings structure, search and navigation.
- Launcher: the floating search window and what it hands off.
- History: the history module, omnibox queries and site icons.
- Tasks: the shared Tasks surface for people and agents.
- Charts: the chart kit used by Work results and Activity.
- File workflows: upload and download ownership, recovery, and Windows acceptance checks.
- Agentic browsing: the browser-execution layer behind Work and how it is qualified.
- Bounded browser session: the semantic locate/act controller session.
- Work runtime subsystems: execution, scoped runtime, composition, native lifetimes, persistence, retained resources, discovery, inspection, retained inspection evidence, native actions, retained actions, forms, results, artifacts, evidence, review.
- Evidence tooling: committed qualification manifests and the probes that produce them.
- Using extensions: installing from the Chrome Web Store and what to expect.
- Initial release scope: what extension support covers and its completion criteria.
- Windows extension QA: the isolated QA build, acceptance checklist and performance checks.
- Windows extension lab: native qualification harness.
- Ad and tracker protection: the native network blocker, cosmetic hiding and release gates.
- Cosmetic index delivery: keeping the generic cosmetic index out of every page.
- Blocker fuzz harness: running the fuzz targets.
- Contributing: prerequisites, workflow and quality bar.
- Security maintenance: recurring security and engine-floor checks.
- Release engineering: building, signing and publishing releases.
- Frame guide: layout of the Svelte frontend.