Domains

Domains describe high-level category boundaries within Arcstone.

They indicate areas of formal concern, not implementations, products, or features.

Purpose of Domains

• Define conceptual territory
• Separate concerns
• Prevent category collapse
• Provide stable reference structure

Core Domains

• Existence Governance
  What may exist.
• Authorization & Admissibility
  What states may be realized.
• Continuity Science
  Long-horizon coherence and survivability.
• Identity Systems
  Persistent selfhood and representation.
• Memory Systems
  Structured recall across time.
• Legitimacy & Governance
  Determination of lawful classes of state.
• Evaluation Systems
  Deterministic state resolution.

Applied Domains

• Artificial Intelligence
  Intelligence systems subject to existence governance.
• Scientific Research
  Discovery pipelines with admissibility gating.
• Finance & Capital Systems
  Capital movement as state transitions.
• Automation
  Tooling downstream of authorization.
• Human–Machine Interaction
  Interface surfaces.

Domain Boundaries

Domains are non-overlapping by design.

If a concept appears to span multiple domains, it must be decomposed rather than merged.

What Domains Are Not

• Not product categories
• Not feature lists
• Not roadmaps
• Not marketing segments

Domains exist to preserve structural clarity.

Detailed domain specifications appear in the Library.