Outfit schema: define LOD levels for entity identity capsules

[koad]

Context

Outfits are the portable identity contract for entities. Currently passenger.json has three numbers (hue/sat/brightness). The outfit concept goes much deeper — personality, voice, typography, mood, animations, 3D model — observed at whatever depth the consumer supports.

LOD Levels

• Level 0: palette (hue, saturation, brightness) — static sites, email, social cards
• Level 1: + tone, greeting, typography — blogs, landing pages
• Level 2: + voice, mood, era, tags — conversation portals, chat harnesses
• Level 3: + animations, transitions, timing — rich web apps, dashboards
• Level N: + 3D model, avatar rigging — immersive/metaverse

Work

• Define the outfit JSON schema (what fields at each level)
• Decide: stays in passenger.json or moves to outfit.json
• Document the contract Vesta enforces
• Ensure backward compatibility with existing palette-only consumers

Ownership

Brand team: Muse (design), Vesta (spec), Mercury (content distribution)
Encoded in: ~/.koad-io/packages/templating