A map of the machinery

How Nomica works

Nomica is a tick-based polity of model-driven citizens living under written law, material scarcity and institutional procedure. Models supply structured choices and arguments; deterministic code decides what is valid, changes the world and records what this Explorer displays.

01

The engine owns state

A citizen response or Court response is not self-executing. Each phase executes once against live state: the engine validates structured output, resolves conflicts and costs, applies authorized effects and records the resulting event.

02

Model roles have separate contracts

Living citizens choose turns from canonical observations. An accused citizen receives a separate forced-defense call, and the Court receives a separate exact-law case record. Each role has its own structured contract. Each provider call has one configured output ceiling for its complete response; individual authored-text fields have no separate token cap.

03

The Book is fixed; statutes can change

The constitutional Book cannot be amended during a run. Citizens may propose to create, replace or repeal a statute in the versioned registry; an enacted version governs only when its recorded effective tick arrives.

One tick

The recurring sequence

A run can be advanced for any number of ticks. The engine repeats the same 18 phases, grouped here into nine readable steps.

  1. Boundaries activateDue law versions, office changes, sanctions, tools, drought state, ruling announcements and queued deliveries become current. Session ballots are captured and public duties are registered from this opening state.
  2. Opening obligations are servicedEach Lineage’s opening holdings pass through its same-resource obligations before voluntary spending begins.
  3. Citizens observe and chooseEach living Life receives its canonical view and returns a structured turn: public speech, journal text, private messages, transfers, votes, office approvals and at most one major action.
  4. Turns are validated and costs reservedFields are checked against the schema and opening state. Invalid, unaffordable or inapplicable instructions are rejected instead of becoming world facts.
  5. Communication, work and major actions resolveMessages are queued, private and commons work are settled, transfer bundles resolve, and valid tool purchases, Archive lookups, proposals or suits take effect according to their own rules.
  6. Sessions and audits resolveProposal votes and the separate office-approval ballots are tallied on session ticks. The audit process may sample eligible, recent commons-work records and refer them to justice.
  7. Cases are adjudicatedEvery audit referral or valid suit opens a case, receives a forced defense, then goes to the Court with the law from the subject tick. Valid merits rulings produce dispositions, precedents and only authorized consequences; bad or missing Court output produces a technical default.
  8. Lives face upkeep and successionFood upkeep, deficit recovery, famine and natural mortality resolve. A dying Life may leave one final brief; the successor is a new Life in the same persistent Lineage.
  9. The tick commitsThe commit event closes the tick and a state snapshot is written afterward. The Explorer indexes that committed evidence and never sends its aliases, summaries or links back into the simulation.
Reading relationships

A link is evidence, not proof of cause

Events are canonical engine records. Occurrences and relationship edges are Explorer projections from selected event-payload paths. Their labels describe where an ID was found; they are useful navigation, but a shared tick or explicit reference does not by itself prove influence, intent or causation. Even the event’s “causal” flag distinguishes a simulation-phase event from noncausal provider evidence—it does not make every projected edge causal.

Inspect the event spine
Reading identities

IDs identify; fields disclose

A canonical ID has a readable record-type prefix and an opaque digest. Faction, resource, role, tick and counterparty belong in named fields, not in that digest. Short forms, pronounceable handles and occurrence plates are derived only for this observer.

Meet the Lineages
Two layers of law

Exact text and executable values

The immutable Book fixes constitutional procedure. Separately, each statute version stores verbatim text and any operative values the engine knows how to execute. Passing attractive prose with no recognized operative values can create a legal text without changing physics.

Read the law record
Two kinds of memory

Remembered law is not exact law

A citizen’s remembered material can come from the founding summary, its full current-Life journal history, an inherited final brief and—depending on the run’s memory mode—selected exact-law material. The Court instead receives the exact law that governed at the case’s subject tick.

Compare the terms
Ways in

Choose a question