# Autonomous Frontend Architecture Intelligence

Webdev Agent OS v28 governs the architecture between user journeys and browser runtime behavior. It records route ownership, composition graphs, bundles, rendering and hydration strategies, state boundaries, data-fetching and cache policies, browser contracts, performance budgets, dependencies, duplicate implementations, architecture options, and approval-gated evolution.

## Evidence chain

`Journey → Route → Composition → Bundle → Rendering → State/Data policy → Browser and performance contract → Release evidence`

## Operating rules

1. Every production route has an owner, source location, journey connection, rendering strategy, and evidence.
2. Composition graphs must remain cycle-free.
3. Bundle and route budgets cannot pass above their measured thresholds.
4. Supported browser contracts require reproducible test evidence.
5. Cache keys cannot use persistent personal identifiers.
6. Architecture proposals require rollback references, verification, and independent approval.
7. Failed browser or performance contracts block approval for affected routes.
8. External systems are never represented as connected without verified integration evidence.