Liveness Temporal Coupling Collective (LM-Dawn class)

Class card for the LM-Dawn collective operational form encoding `liveness_temporal_coupling` — the Wave-0 LM signature variable (Rao, *Engineering Liveness*, 2026). Where MM-Dusk coordination operates through slow ritual time and stored artifacts, and DM-Day operates through stored- artifact asynchrony (database reads, versioned documents, email threads), LM-Dawn's liveness signature is that participants are CO-PRESENT in the system's TEMPORAL FLOW — events happen NOW, with low latency between perception and response. The canonical Wave-0 definition: "A process condition in which time tells memory how to grow, and memory tells time which way to point." LM-speculated value: 0.70–0.90 (HIGH). THIS card encodes the COLLECTIVE FORM: multiple participants co-coupling in a shared real-time substrate simultaneously. This is structurally distinct from individual real-time forms (solo streamer, single player) and from asynchronous collective forms (Wikipedia edit history, git commit log). The defining invariant: ≥2 participants share temporal state in a system that requires their co-presence to function. Absence of any participant is a live event; their presence changes system behavior in real time. emergence_subtype: federated-live-collective [EXTRAP] — absorption into description per v0.2 constraint (field MISSING from schema; flagged as schema-extension proposal). The machine is not crowdsourced (DM-Wikipedia form) and not algorithmic (DM-platform form) — it is a LIVE GOVERNANCE- COORDINATION FORM: distributed human participants co-managing shared state in real time without a central telos of Progress. Named instances [EXTRAP]: (1) Wikipedia recent-changes stream (~5 edits/sec cumulative; Huggle, Vandal-patrol bots + human patrollers live-watching the same stream; ~1,000+ active patrollers globally at any moment). Liveness: participants must be present NOW to catch vandalism before it propagates; the stream IS the machine — without live-watchers it degrades to asynchronous cleanup. (2) Twitch live-streaming (~7M+ streamers; live attention-economy with chat-driven flow). Liveness: streamer and audience co-present; chat IS the signal that shapes stream content in real time; recorded VOD has no chat feedback loop and is a degraded artifact, not the machine. (3) OpenStreetMap crisis-response editing (Hurricane Maria 2017, Haiti 2010, Türkiye earthquake 2023: ~10K mappers in hours; HOT — Humanitarian OpenStreetMap Team). Liveness: map edits must land BEFORE emergency responders need them; temporal coupling is the operational constraint; asynchronous editing in non-crisis periods does not exhibit the collective liveness form. (4) Prediction-market price-discovery (Polymarket, Manifold Markets; real-time Bayesian aggregation of distributed beliefs). Liveness: market price IS the live collective belief state; delayed participation is degraded information; co-presence in the price-discovery moment IS the mechanism. (5) CodeWithMe / Replit Multiplayer / VS Code Live Share (collaborative coding with real-time cursor presence, shared execution state). Liveness: participants see each other's edits in real time; the session IS a live collective object; asynchronous code review is a different machine. (6) AlphaGo/Leela Chess Zero community live game analysis (Kibitzer culture; humans + AI analyzing live competitive games collectively with chat-driven hypothesis generation). Liveness: analysis is time-indexed to the live game; post-game analysis is an archive, not the machine. (7) Ham-radio emergency-net traditions [CAUTIONARY — MM-style]: NTS net structures exhibit live temporal coupling but with hierarchical scheduling (net control station, check-in protocol) — this is an MM-hosted form of liveness, not the LM-Dawn self-organized collective form. Included as cautionary exemplar to mark the boundary of the class. (8) LiveJournal/Mastodon "live posting" cultures (threads that unfold in real time and derive meaning from sequencing; readers co-present during posting). Borderline case: the thread IS the live performance; archival reading is a different experience. Cross-era position: the LM liveness-collective depends on DM-era ICT infrastructure (internet protocols, cloud compute, streaming CDN layers) that are themselves asynchronous-tolerant systems being pushed into live mode by LM collective demands. The DM substrate_provision relationship is the load-bearing cross-era coupling. MM-era broadcast infrastructure (radio, telephony) provides adapted_inheritance — early-form live coupling that the LM form supersedes by removing the one-to-many asymmetry and introducing genuine co-presence. Cautionary: DM-era algorithmic engagement machines (Twitch's recommendation algorithm, TikTok's live-stream OPP) attempt parasitic_extraction of liveness-collective temporal flow by inserting a programmer-machine-id that routes the live event through behavioral-surplus extraction. The LM collective form distinguishes itself by preserving programmer_machine_id=null (Castells) or making the algorithmic layer community-governed. All LM quantitative state-variable values are [EXTRAP]. Named instances and their factual records (Wikipedia patroller counts, Twitch streamer counts, HOT crisis-response mapper counts) are [CANON] where publicly documented.