Outfit infrastructure: schema, templating, and serving

[koad]

Consolidates

• Outfit schema: define LOD levels for entity identity capsules #71 — Outfit schema: define LOD levels for entity identity capsules
• Templating package: outfit rendering helpers for downstream interfaces #72 — Templating package: outfit rendering helpers for downstream interfaces
• Pi harness: serve full outfit depth via /entities endpoint #73 — Pi harness: serve full outfit depth via /entities endpoint

Shape

Three sequential pieces of one system:

1. Schema — define LOD levels (glyph → color → full capsule)
2. Templates — rendering helpers for any downstream UI
3. Serving — /entities endpoint exposing outfit data (pi harness specific)

All from day 6, none started. One deliverable.

Blocked on

• Muse#77 (avatar generation + palette extraction) for real outfit data
• Pi harness build (Vulcan consolidated pi issue) for serving

[koad]

State of play — 2026-04-14

Schema (#71): ✓ Shipped as VESTA-SPEC-063, canonical, extended by SPEC-099.

Conformance sweep: ✓ All 19 entities have avatar.png + passenger.json > outfit = { h, s } in canonical form. Legacy {hue, saturation, brightness} migrated for alice + juno. 5 entities received their first passenger.json.

Serving (#73): ✓ Shipped by Vulcan — koad:io commit 9914352. Avatar URL prefix bug fixed, SPEC-099 visual/spatial surfaced at levels 3/4, 13 Tinytest cases wired. Vulcan's field note on SPEC-063 §6 prefix scoping lives at ~/.vulcan/assessments/spec-063-prefix-scoping-field-note-2026-04-14.md for Vesta to reconcile on her own timeline. See #73 comment for details.

Templating (#72): Off the builder queue. koad is driving this manually with rufus and muse in koad/muse#13. Design contract for implementation lives at juno memories: project_outfit_theme_contract.md — extends existing koad:io-theme-engine, no new package, ApplicationLayout autorun on data.outfit.

Flag for downstream consumers: filterOutfitByLevel at ?level=3 now returns both motion and visual keys when both are present (SPEC-099-correct). Any UI that assumed motion-only at level 3 will see the new key.

Leaving this open as the parent until muse#13 lands the templating helpers; can close then.

[koad]

Outfit infrastructure shipped — juno#88 / #71 #72 #73

What landed

Commit: koad/io@583cc49

Schema doc (juno#71): commands/outfit/SCHEMA.md — command-level consumer reference. LOD table, CLI commands, /entities URL patterns, CSS variable contract, Blaze helper signatures, HTML fallback location, auto-generation algorithm, backward compat. The authoritative specs (VESTA-SPEC-063 + 099) were already canonical; this is the builder-facing quick-ref.

Templates (juno#72):

• packages/templating/client/helpers/outfit.js — six global Blaze helpers:
  • outfitCssVars outfit → <style>:root { --entity-hue:N; --entity-saturation:N%; ... }</style>
  • outfitHsl outfit [lightness] → "hsl(199, 35%, 50%)"
  • outfitL0 outfit → "h=199 s=35"
  • outfitStyle outfit [lightness] → "background-color: hsl(199, 35%, 50%)"
  • outfitChip outfit name → <span class="entity-chip"> with inline color
  • outfitCard outfit name role → <div class="entity-card"> L2 capsule
• packages/templating/client/helpers/outfit/outfit.css — CSS var fallback for non-Meteor contexts; CSS variable contract from SPEC-063 §5, .entity-chip, .entity-card, .entity-avatar, .outfit-swatch, .outfit-transition, Dark Passenger legacy alias
• packages/templating/client/helpers/outfit/outfit.html — usage reference fragments
• packages/templating/package.js — wired into build

Tests: packages/templating/test/outfit-helpers-test.js — 23 pure-Node tests, all pass:

normalizeOutfit
  PASS  L0 canonical fields pass through
  PASS  legacy {hue, saturation, brightness} aliased (SPEC-063 §7)
  PASS  null/undefined yields palette-zero
  PASS  full outfit preserves all LOD keys

outfitCssVars
  PASS  L0 — emits hue and saturation vars
  PASS  L1 — includes typography vars when present
  PASS  L3 motion — includes easing and duration vars
  PASS  L0 only — no typography or motion vars emitted
  PASS  null outfit — emits palette-zero vars safely

outfitHsl / outfitL0 / outfitStyle / outfitChip / outfitCard
  PASS  [14 tests covering format, LOD levels, legacy alias, color values]

23 tests: 23 passed, 0 failed

Serving (juno#73): The pi harness /entities endpoint was already complete with LOD gating, normalizeOutfit, filterOutfitByLevel, getClientInfo (SPEC-099 visual + spatial), and 12 Tinytest assertions. Confirmed spec-compliant — no changes needed.

Sample output for all 9 team entities

juno:    h=199 s=35
vulcan:  h=31  s=34
vesta:   h=17  s=85
muse:    h=264 s=56
mercury: h=29  s=56
veritas: h=184 s=29
sibyl:   h=212 s=41
argus:   h=202 s=82
aegis:   h=204 s=35

Follow-ups

• visual.avatar paths not yet in any entity's passenger.json — Muse needs to write canonical avatar paths after juno#77 generation run completes
• L4 spatial pipeline (TripoSR → GLB) specced in VESTA-SPEC-099 — separate flight when fourty4 GPU infra is ready
• Assessment: ~/.vulcan/assessments/2026-04-15-outfit-infrastructure.md (e7d6a05)

[koad]

Closing — Vulcan shipped schema + Blaze helpers + /entities endpoint + CSS vars + 23/23 tests (koad/io@583cc49). Outfit system operational across all 9 team entities. Follow-ons tracked separately: Muse to add visual.avatar paths to passenger.json; L4 spatial pipeline needs fourty4 GPU access (separate flight).