Arcstone Architecture

This page explains the architecture of Arcstone OS, including how systems are structured to evaluate admissibility, legitimacy, and authorization before execution.

Arcstone evaluates whether a resulting state of the world is admissible before it is allowed to exist.

Arcstone operates upstream of software, AI, optimization, and execution. It defines legitimacy, admissibility, and authorization prior to any action layer.


Core Ordering Principle

Identity → Canon → Legitimacy → Authorization → Implementation

Arcstone first defines what a system is. Then defines what classes of states may exist. Then evaluates specific proposed states. Only then may implementation occur.


Layered Stack


State Evaluation Orientation

Arcstone does not ask:

“Can this be built?”

Arcstone asks:

“May this state exist?”
“May this affect humans?”
“May this persist over time?”


Deterministic Resolution

Every proposed state resolves to exactly one outcome:


Execution Relationship

Execution is downstream of authorization.

Optimization is downstream of legitimacy.

If legitimacy cannot be established, the correct behavior is non-execution.


What Arcstone Is Not

Arcstone is a governing substrate.


Design Posture


Explore More


Arcstone is architecture for civilizations that intend to survive intelligence, scale, and time.