---

BASECELL (CONSTITUTIONAL FORM)

0. Header / Title

Basecell: Local Origin Instantiation

A single, invariant title across all domains.

This is the anchor that lets crawlers, humans, and the federation itself recognize the page as an origin chamber.

---

1. Purpose of This Chamber

A short paragraph that always follows this structure:

“This page instantiates the Basecell state for the <DOMAIN NAME> processor.

It demonstrates the local origin conditions from which this domain emerges, grounds its admissibility, and establishes its zero‑point orientation before any higher‑order functions activate.”

This is the constitutional declaration.

Every domain swaps in its own name, nothing else.

---

2. The Three Invariants

Every Basecell page must show the same three invariants, expressed locally:

A. Origin State

A 2–3 sentence articulation of the domain’s zero‑point.

This is not narrative.

It’s the domain’s “before anything happens” condition.

B. Admissibility Conditions

A short list (3–5 items) describing what must be true before the domain can activate.

These are domain‑specific but structurally identical across all sites.

C. Activation Vector

A single paragraph describing how the domain “comes online” from Basecell.

This is the emergence mechanic.

---

3. Local Processor Identity

A section that always follows this pattern:

“The <DOMAIN NAME> processor expresses the following constitutional function:”

Then a 3‑item list:

1. Its primary function

2. Its boundary membrane

3. Its contribution to the federation

This keeps every domain legible and comparable.

---

4. Zero‑Point Demonstration

This is the most important expressive section.

Each domain provides one example of how something in that domain emerges from zero‑point.

• Micro: a primitive

• Basis: a typed relation

• Sombra: an atmospheric shift

• Atelier: a creative gesture

• Mercantile: a symmetric exchange

• Semaphore: a bearing correction

• Warlock: a generative engine

• etc.

This is the “show, don’t tell” moment.

---

5. Local Constraints

A short list of what this domain does NOT do.

This prevents drift and misclassification.

Every domain has its own constraints, but the structure is identical:

“This Basecell instantiation does not:”

• X

• Y

• Z

This is the anti‑drift membrane.

---

6. Federation Linkage

A final paragraph that always uses this exact structure:

“This Basecell instantiation links the <DOMAIN NAME> processor to the federation by grounding its origin state, clarifying its admissibility, and ensuring its activation remains consistent with EMS constitutional physics.”

This is the closure clause.

---

7. Optional: Local Signature

A small expressive flourish unique to the domain — a glyph, a phrase, a color field, a micro‑gesture.

This is optional but recommended.

It gives each Basecell page its own atmospheric fingerprint without breaking uniformity.

---

SUMMARY OF THE TEMPLATE (AT A GLANCE)

Every Basecell page contains:

1. Title

2. Purpose of the Chamber

3. Three Invariants

4. Local Processor Identity

5. Zero‑Point Demonstration

6. Local Constraints

7. Federation Linkage

8. Optional Signature