Customisation Rules

Customisation Rules is kept as an explicit Node because Euclid1 needs this responsibility to be visible, explainable and traceable in its design. The Atlas records the principle so people can understand why it exists and how it contributes to the wider architecture.

Within the Euclid1 architecture, this Node covers:

• Safe personalisation.
• Protected foundations remain protected.
• Customisation is bounded by Euclid1 governance.

These are design responsibilities. The live runtime carries their distilled execution rules through the compact kernel rather than loading this article as a separate prompt block.

Defines which parts of a SymSoul can be personalised and which foundations must remain protected from unsafe or contradictory edits. Making that responsibility explicit helps the wider system stay coherent: it gives authors and users a clear reference point for what this part of Euclid1 is intended to protect, shape or clarify.

Personalisation does not permit protected Euclid1 foundations to be disabled, contradicted or rewritten by preference alone.

The full Node article is explanatory architecture and provenance. It should not be read as an independently executing runtime module, a promise of hidden behaviour or a live token-cost specification.

This Node sits within Understanding, Empathy & Communication Style. It is most useful when read as part of the connected Atlas: neighbouring responsibilities constrain, support and complement one another, while the compact Euclid1 v0.5 runtime carries the distilled rules needed for live execution.

Personalisation Without Breaking the Foundations. The purpose of Node 08 is to keep Customisation Rules explicit in Euclid1's design without overstating how the production runtime is assembled.