Piik/docs

Project Documentation

• 需求理解: current product scope, priorities, constraints, and acceptance criteria.
• 方案设计: accepted implementation design; unfinished release and validation work is tracked in the current TODO ledger.
• Project memory: durable current product and source snapshot to read at the start of future work.
• Current status: bounded current/index snapshot of production, active milestones, decisions, blockers, and links to detail.
• Verification status: exact integrated/deployed v10 gates, current production evidence, open physical proof boundaries, and expensive-test applicability.
• Session handoff: temporary bootstrap prompt that points a new session back to the canonical truth owners.
• Current TODO: unresolved work, active truth holds, and decisions that still require user confirmation.
• Deployment: exact current v10 production and rollback configuration, release operations, and transport evidence boundaries.
• Maintenance guide: Git workflow, context hygiene, document lifecycle, research policy, and automation.
• P2P WebRTC research: evidence, bandwidth model, browser constraints, reference implementations, and feasibility assessment.
• Peer-assisted media research: browser shared-encode limits, standard relay re-encoding, deterministic sticky topology, exact-route implementation evidence, and remaining physical gates.
• Low-server-cost media routes: Host-publication/SFU distribution, route diagnostics, direct-to-SFU conclusion, hop-level accounting, privacy-safe ICE evidence, and bounded transport gates.
• Built-in peer ICE TURN candidate: historical evidence for the rejected participant-wide and selected-edge TURN candidates.
• Advanced peer distribution: generic local-reconcile evidence plus multi-tree/SVC, encoded-object relay, native RTP forwarding, FEC/network-coding, and MoQ gates.
• Native shared-encode sender: consolidated Draft #16/#18/#22/#23/#25/#28 ladder, unclassified product-gate failure, staged revalidation, and stop line.
• Native H.264 hardware decision: bounded WebCodecs no-go, proved Media Foundation/NVIDIA hardware encode, the default-fmtp 42c01f stop, and the retained interop boundary.
• Native H.264 opt-in path: explicit H.264 sender mode, exact Pion profile registration, and one bounded Host/Viewer loopback with hardware caveats.
• Realtime quality adaptation: current v10 manual profile/codec boundaries, diagnostic-only capture/send/receive correlation, path-isolated dual representations, and bounded simulcast/Dynacast/SVC checks.
• Browser background capture diagnostics: browser lifecycle evidence, a privacy-bounded capture/send/receive experiment, interpretation gates, and non-goal keepalive mechanisms.
• Browser screen-audio quality: capture/source compatibility, v10 live sender-ceiling readback, Opus negotiation boundaries, and remaining audible/device evidence.
• Display name and presence boundaries: browser-local storage failure behavior, Unicode normalization, control-character policy, and the Web-only presence capability boundary.
• Agent context governance research: official Codex, Claude Code, Hermes Agent, and GitHub practices adopted by this repository.
• ADR-0001: historical P2P-first baseline; later access and automatic-routing decisions supersede its stale current-state details.
• ADR-0002: four-digit leased in-memory rooms, local Host defaults, scoped Viewer grants, and orthogonal code entry.
• ADR-0004: historical standard-WebRTC peer-assisted experiment and reusable evidence.
• ADR-0005: accepted and deployed P2P-first single-reconcile route model; remaining real-network validation is tracked in verification status.
• ADR-0006: proposed fixed-HIGH native canary, current no-go result, and staged revalidation boundary.
• ADR-0007: accepted path-isolated HIGH + at most one LOW policy, optional idle-layer stop, evidence contract, and SVC boundary.
• ADR-0008: browser window-audio hint and the Windows WASAPI process-loopback boundary.

Documentation and project memory are part of the product source of truth. Update them in the same change that alters the corresponding requirement or architecture.