dec-0094

Vista generada de dec-0094: StyxCapsule 4-primitive taxonomy with qualified naming 'Styx Capsule' prefix to avoid collision with RFC 9297 HTTP Datagrams Capsule Protocol and Zig UEFI CapsuleHeader

ImplementadoSin versión del tren todavía· generada desde docs/decisions/dec-0094-styxcapsule-4-primitive-taxonomy-with-qualified.md
track/docsdec-0124track/docs:DC10

Vista generada desde docs/decisions/dec-0094-styxcapsule-4-primitive-taxonomy-with-qualified.md. No se edita a mano: bun run docs:gen la regenera y bun run docs:check falla si difiere. El estado aquí es el del model: si discrepa con otra página, manda el model.

CampoValor
EstadoLOCKED (migrado de un rNN por gate-3: el fichero no declara estado)
Referencia legadaD1
Ficherodocs/decisions/dec-0094-styxcapsule-4-primitive-taxonomy-with-qualified.md

Por qué importa (del frontmatter del ADR):

Referenced in styx.model.yml extends: [r04, r23, r26, r45, r46, r48, r49, r52, r58, r39, r40, r20, r08]; CLAUDE.md invariantes globales (r04 SeekableMediaSource, r23 CanonicalCodecPolicy, r20 §2.3 contract-first, r08 catalog federated, r26/r45 cache, r40 scheduler mechanics). D1 is foundational for F-WEB-PLAYER-ENGINE.W3+ and F-CLIENT-PLATFORM-FOUNDATION.C3-C4 SessionStash portable state.

Nodos del roadmap que lo citan en refs: ninguno.

Páginas de la documentación que lo citan: Dispositivos, mando y handoff (especificado), Transferencias (especificado)

Texto del ADR

Leído de docs/decisions/dec-0094-styxcapsule-4-primitive-taxonomy-with-qualified.md, el fichero canónico.

StyxCapsule 4-primitive taxonomy with qualified naming 'Styx Capsule' prefix to avoid collision with RFC 9297 HTTP Datagrams Capsule Protocol and Zig UEFI CapsuleHeader

StyxCapsule 4-primitive taxonomy with qualified naming 'Styx Capsule' prefix to avoid collision with RFC 9297 HTTP Datagrams Capsule Protocol and Zig UEFI CapsuleHeader

Por qué pasa gate-3

  • Hard-to-reverse: Naming convention embedded throughout codebase, contracts (Arktype schemas in @styx/api-contracts), and documentation. Changing would require global rename with ripple effects across all references.
  • Surprising sin contexto: Without ADR context, engineers would not understand why 'Styx' namespace prefix is required or why specific 4-primitive taxonomy (Session/Startup/Seek/OfflineBundle) exists. Naming resolved via AskUserQuestion (waxin pick session cont. 41) - historical context not inferable from code alone. Collision risk with RFC 9297 and Zig UEFI CapsuleHeader is non-obvious without documentation.
  • Trade-off real: Alternatives explicitly considered and rejected in ADR: (1) Maintain 'Capsule' without qualifier - REJECTED due to grep pollution with RFC 9297 + Zig UEFI CapsuleHeader over 5+ years; (2) F-OFFLINE-CONTINUITY as top-level phase - DEFERRED per r28 §3 anti-speculative; (3) Capsules as standalone ADR - REJECTED as skeleton without consumers. Cost of 'Styx' prefix = extra verbosity; benefit = unambiguous cross-stack grep. Waxin made explicit choice via AskUserQuestion with preview.

Procedencia

Split de docs/decisions/r61-isolation-lifecycle-2026-07-15.md (lock D1) durante PASO 7 (2026-07-16). Ver el fichero padre para el contexto completo del pack original.

dec-0093

Vista generada de dec-0093: Placement Planner

dec-0095

Vista generada de dec-0095: 0-RTT replay-safe policy as annex to F-IDENTITY

Texto del ADR
StyxCapsule 4-primitive taxonomy with qualified naming 'Styx Capsule' prefix to avoid collision with RFC 9297 HTTP Datagrams Capsule Protocol and Zig UEFI CapsuleHeader
Por qué pasa gate-3
Procedencia