Piik/docs/status.md

# Current Status

Last updated: 2026-10-04

This is the compact execution/deployment index. Product modules own behavior,
[verification status](./verification-status.md) owns unresolved physical limits,
and Git/PRs own completed history.

## Accepted Release Contract

- Browser/server v23, Native control v9 and capture v7 form the current contract.
  [Versioning](./standards/versioning.md#public-compatibility-promise) owns
  compatibility between published Web/App/Server versions.
- Hosted Server defaults to SQLite schema 2. Room authority has no inactivity
  expiry; explicit replacement/deletion or grant rotation/revocation ends the
  corresponding authority. Explicit memory mode and App Local end rooms at
  process exit. Site access retains its separate 24-hour idle lifetime within
  one service run; service restart requires site-password entry again.
- Browser/App entry lifecycle and current-edge reconnect ownership repairs
  are implemented. Browser node-local pooling and detailed local Debug export
  remain part of the accepted media surface. Product modules own their behavior;
  [configuration](./standards/configuration.md#diagnostics) owns Debug activation,
  report contents and disclosure.
- Shared feedback composition is implemented: generic loading uses the wink
  mascot, concrete media waits use their owning comic, and waiting captions are
  secondary to literal status. Website reduced-motion preference and player
  tooltip placement follow the same presentation owners.
- Camera sharing and Host microphone commentary are accepted product features.
  Both Browser and native App audio use the existing media routes; device
  selection and sharing settings keep their current resource owners. The
  [capture assessment](./research/camera-and-microphone.md) owns platform behavior
  and the remaining physical evidence limits.

Website delivery includes a bilingual reader documentation center generated
from the repository's guides alongside the homepage, with search and detailed
troubleshooting separate from the homepage FAQ.

## Accepted Interaction Phase

The accepted [room-interaction design](./research/room-interactions.md) includes
the verified media repairs. It adds authenticated text and reactions
over existing signaling, with optional local chat overlay and a shared floating
panel. Its opted-in room session can outlive a publication; capture, quality and
route owners remain unchanged. Optional Windows screen-audio exclusion uses the
existing source/mixer boundary. Hosted Server
also accepts an optional SFU-only policy through the same route controller.
Windows native capture and thumbnails now share automatic HDR-to-SDR conversion;
synthetic GPU and Browser reception checks pass, with physical HDR display
acceptance still pending in [verification status](./verification-status.md).
Room voice is outside the product plan; Host microphone commentary remains.
These features are published; physical device limits remain open.
Release artifacts and operator deployment records own delivery completion;
[TODO](./todo.md#now) owns remaining work.

## Current Candidate

The owner authorized v1.8.0 publication on 2026-10-04. This phase retains the
published protocols and 1440p ceiling; immutable release artifacts own delivery
completion. Follow-up work reviews extension boundaries, implements 4K and more
resolutions with capability negotiation, then develops Native Magicsock NAT
traversal. The isolated transport experiment is not part of v1.8.0; its product
integration and connectivity benefit still require verification.
[TODO](./todo.md#now) owns remaining work and later release authorization.

## Deployment

Source, package identity, GitHub repository and local worktree paths use Piik.
Runtime code keeps only the Piik wire labels and stored keys.
The immutable release descriptor, runtime `REVISION` and operator deployment
record own exact identity and postflight results.

The existing deployment uses one Go process for Web, room authority/signaling,
Binding-only STUN on UDP 3478/3479/3480 and optional SFU on UDP 7882. nginx owns
HTTPS; external LiveKit/coturn services remain disabled. Participants, routes and
media remain process-only. This private service is not a public demonstration.

The separate US [public demo](https://demo.piik.tv) is deployed with open site
entry, persistent room authority and P2P-only media. Cloudflare fronts HTTP/WSS
and caches static bundles; STUN uses a separate DNS-only hostname. Caddy owns
origin HTTPS, and the standard systemd service runs the published Server package.
Public DNS,
HTTPS, runtime assets, all three STUN listeners and a bounded browser P2P
sharing/stop check passed; the browser check used synthetic video on one network.
The operator record owns exact identity and postflight evidence.

[TODO](./todo.md) owns remaining verification and follow-up work. The owner declared the first
public release on 2026-09-12. Source is public, main protection is active, and
`piik.tv` runs on GitHub Pages behind Cloudflare with HTTPS. The private service
remains a separate deployment. Release descriptors and GitHub deployment records
identify published artifacts and website revisions.

The matching Server and three App packages are published on GitHub and Gitee;
anonymous mirror downloads match the original checksums. Public-repository CI
and native packaging passed. App entry, update links
and bounded two-build interoperability have acceptance evidence. Accepted
product changes publish automatically; standalone website and documentation
changes validate and deploy the website without creating App/Server versions.
GitHub/Gitee release comparison, mirror publishing and PR-sourced notes follow
[versioning](./standards/versioning.md). [Verification status](./verification-status.md#device-evidence-boundary)
owns the remaining physical limits; shared lessons live in
[engineering](./standards/engineering.md).

## Media Evidence And Limits

- Compatible Native consumers share one complete stock WebRTC encoding and
  adaptation pipeline per local output. Different weak demands stay independent;
  suitable received media can be forwarded without decoding/re-encoding.
  Pion/LiveKit retain transport, estimation, pacing and forwarding ownership.
- Windows H264/VP8 have bounded encoding/adaptation evidence. Actual Native
  relay checks cover compatible sharing, weak-budget separation and rejoining,
  source retirement and large encoded-frame delivery. These results do not
  establish a universal encoder count, CPU saving or Browser-equivalent quality.
- Windows Host acceptance covers live and paused settings, quiet-source
  preparation/restore, source changes and subsequent sharing. The owner
  confirmed Windows 10 whole-display capture resolved. Specific new game/device
  failures should be reopened from new evidence.
- Native Host publication through embedded SFU retains video/audio; Browser to
  App fanout and App-exit fallback have bounded physical checks. Two
  independent Native sessions have simultaneous media/retirement evidence.
- The Linux runtime container has non-root/read-only, memory/SQLite, diagnostic
  export, STUN and listener-lifecycle evidence. This does not establish every
  operator's proxy/firewall or public-media configuration.
- The independent Browser producer in ADR-0014 is integrated.
  Bounded H264/VP8 checks cover direct and received-track sharing, weak-child
  isolation/recovery, live/quiet settings, pause, source change and ordinary
  fallback. Its native allocation and complete-frame output replace the earlier
  payload-only Worker path. Fewer full encodes are established; total CPU gains
  depend on codec/hardware. [Browser research](./research/browser-local-encoding-pool.md)
  owns these measurements and failed controls. The owner accepted this scoped
  Browser composition for release; actual deployment identity stays in the
  runtime descriptor.
- Slow adaptation recovery, the extreme CPU-overload sampling limit and missing
  broad device/network/endurance results remain explicit in
  [encoder research](./research/webrtc-encoder-pool.md) and verification status.
  macOS/Linux physical capture is deferred by the owner; Windows App and
  Browser are this phase's primary targets.