Shared Foundation Consumption
Tokens, base runtime helpers, translation-engine support, and approved shared assets remain canonical in the website docs asset layer.
This layer exists to build Neuroartan Brand architecture in a way that remains visually expressive, structurally governed, and fully aligned with the canonical website source foundation.
The Brand sovereign layer should inherit approved shared primitives from the canonical website asset layer, while preserving Brand-owned page structure, page styling, page behavior, and future public resource-center experience.
Tokens, base runtime helpers, translation-engine support, and approved shared assets remain canonical in the website docs asset layer.
Brand keeps ownership of its own page architecture, expressive menu exception, future public resource-center pages, and brand-specific implementation logic.
Shared primitives should not be recreated locally when governed shared consumption is the correct architectural choice.
Brand currently uses the more artistic website menu family as a controlled source exception rather than the institutional menu family.
Public-facing Brand docs should be built only after the development layer is structurally stable and the publication subset is explicitly approved.
The website docs asset layer is the canonical shared-source domain for approved cross-layer primitives. Brand consumes that shared foundation instead of forking it.
Shared foundation and sovereign implementation must remain visibly separate. The goal is to avoid both hidden dependency chaos and needless duplication.
The docs layer for Brand will come later. Development must first establish the full internal resource-center structure, controlled source bridges, and approved public-subset logic.