# Requirements Extracted From docs.zip

Source archive: `/Users/ket/Desktop/docs.zip`  
Read scope: all markdown files in `docs/specs`, `docs/contracts`, `docs/governance`, `docs/index`.

## Product and Interface Requirements

1. Site is a user entrypoint/tube and must open as a regular web surface.
   - Sources: `DOCUMENT_02_server_site_coordination.md`, `SITE_INTERFACE_MAP.md`.
2. Server is a coordination layer and must not become a world/content truth store.
   - Sources: `DOCUMENT_02_server_site_coordination.md`, `DOCUMENT_08_message_and_file_transfer.md`, `DOCUMENT_11_chat_layer.md`.
3. Local runtime remains authority boundary for world and key custody.
   - Sources: `DOCUMENT_03_local_runtime_on_medium.md`, `DOCUMENT_21_transport_handshake_session_transcript_and_key_schedule.md`, `DOCUMENT_22_key_lifecycle_custody_rotation_revocation_and_compromise_recovery.md`.
4. Browser/site must not keep persistent truth state.
   - Sources: `SITE_ALLOWED_STATE_AND_FORBIDDEN_STATE.md`, `DOCUMENT_19_site_server_action_contract_binding.md`.

## Technical and Deployment Requirements

1. Bundle-based deployment/update path is required.
   - Sources: `DOCUMENT_09_update_bundle_runtime_device.md`, `DOCUMENT_25_endpoint_binding_deployment_rollout_and_update_execution.md`.
2. Bundle verification before activation is mandatory.
   - Sources: `DOCUMENT_25_endpoint_binding_deployment_rollout_and_update_execution.md`, `PACKAGE_S_ENDPOINT_BINDING_AND_DEPLOYMENT_ROLLOUT_CONTRACT.md`.
3. Portable-medium lifecycle and controlled rollout states are required.
   - Sources: `DOCUMENT_01_messenger_deploy_bootstrap_coordination.md`, `DOCUMENT_05_migration_backup_cutover_revoke.md`, `DOCUMENT_09_update_bundle_runtime_device.md`.
4. Public entry contour must remain bounded and governed.
   - Sources: contracts and governance package maps under `docs/contracts` and `docs/governance`.

## Implementation Direction Used For This App

- Deliver a local Rust host/server that serves a web site entrypoint.
- Keep runtime local-first with explicit health and requirement endpoints.
- Produce a one-click launch path and a portable, clean bundle artifact.