# Architecture and Domain Lanes

> Separate lanes, interoperable packets.

A packet may move across lanes only when scope, source, authority state, and allowed use are explicitly carried forward.

## Boundary principles

- No silent authority inheritance.
- No merged claims without provenance.
- No execution packet without constraints.
- No educational page that pretends to be runtime policy.

## Public lanes

1. Short-term handoff.
2. Structural governance.
3. Machine-readable exchange.
4. Human-facing education.

## Architecture concerns

- Packet contract.
- Authority seal.
- Handoff envelope.
- Lineage trace.
- Reader map.
- Use boundary.

## No-op default

When a packet lacks source, scope, authority, constraints, or lineage, the safe public result is no-op by default and human review.