P07 · Experience knowledge node
Token and theme harmonizer Preserve the quality of each imported capability while translating its visual assumptions into one semantic Actionist/client token system.
What we learned Current synthesis from the research packet. Exact records and complete source artifacts remain visible below.
Research conclusions Map donor variables into an Actionist semantic token contract rather than sharing raw CSS variables. Re-render previews under the selected pack so the client only chooses reproducible designs. Visual compatibility and scoped token bridges need tests across genuinely different donors. What it owns Token extraction Primitive-to-semantic mapping Scoped CSS/theme bridges State coverage across light/dark/hover/focus/error Visual coherence checks What research already tells us Blocks should consume semantic tokens rather than hard-coded brand values Existing Teable work shows format conversion and scoped bridges are safer than blind aliasing Taste profile and component selection are inputs, not the same artifact Open first-principles questions How much donor visual identity should remain? Can token mapping be inferred reliably? How are unmapped bespoke CSS and canvas surfaces handled? What score means two blocks look coherent? Inputs TasteProfile Donor styles Component tokens Brand assets Outputs ThemeContract TokenMap ScopedThemeBridge VisualReceipts Agent-sized workstream Define the semantic token contract and prove harmonization across three visually different imported surfaces.
Linked research Universal Block Framework visual contract research/actionmodel-builder-research-2026-08-26/phase-8/lanes/01-universal-block-framework/outputs/universal-block-framework.mdToken-pack science research/token-pack-science-2026-08-27.mdSISOCRM Teable absorption brief [private local source withheld]Connected knowledge nodes Where this beats a generator Lovable scans each generation for raw colour literals and auto-retries, so enforcement itself is table stakes. The unoccupied ground is making an off-token value a build error rather than a retry prompt, which is only possible when the token system is closed and the pieces are known in advance.
← P06 · Design taste and preference learner P08 · Archetypes, shells and layouts → Source: site/system-map/data/parts.json#P07 · preserved research datasets remain inline below their source-backed synthesis.