The Working Postulate

Claim

The current participant-determined postulate is:

Relation holds.
Order carries.
Trace places.

Order is not merely arrangement. Order holds where meaningful distinction can resolve while the path of resolution remains retraceable. Resolution Rate names the live rate at which that resolving can occur without losing coupling, clearance, or trace.

The postulate is deliberately small. It does not say this is the only possible language. It says the Atlas tests what becomes readable when relation, order, and trace are treated as the minimum conditions for valid Atlas placement.

Status

Rooted working postulate, version 0.6. This version is currently load-bearing for the Atlas, but remains answerable to bearing passes, alternative postures, and failure tests.

This version replaces the posture-sequence framing of version 0.5. The posture sequence — Connection, Posture, Structure, Clear, Clean — is retained as a planted Posture Read and practice test. It is not the root postulate. Hold, Carry, and Place remain first-order terms with their own dependency placements.

Terms As Operations

An Atlas term is not free meaning. It is a placed operation.

Outside the Atlas, a word may remain ordinary language. Inside the Atlas, a term must answer to relation, order, trace, carry, and correction. The postulate tests whether a term can be placed by relation, carried by order, and returned through trace.

The terms do not gain force by definition alone. They gain force where the Atlas can show what they make possible, what depends on them, and where a claim fails without them.

Representation Condition

The working postulate tests validity by retrace: a read enters the Atlas where what it carries can be followed back to what holds it.

• **Relation holds**: the term must not float as a label; it must enter relation.
• **Order carries**: what holds must remain available enough to carry forward.
• **Trace places**: what carries must be followable back to what holds it.

Where trace cannot place what carry claims, the read has not yet entered Atlas order. The Atlas does not make order by naming it; it tests whether a read remains answerable when followed backward through what holds it.

Consequence 1: Relation Grounds

Relation grounds the system. It is not produced by the postulate as a later term. It is the primitive condition from which the Atlas begins tracing.

The working hierarchy is:

Relation grounds.
Root Order carries dependency.
Trace places what carries.

Relation is what the postulate must remain answerable to. Root Order names the governing dependency arrangement through which relation can carry. Trace makes that carrying placeable because a downstream claim can be followed back to what holds it.

Consequence 2: Connection

Connection is the first passage in which held relation becomes available to carry and trace. It comes before posture inside the sequence; it does not precede Relation.

Connection does not require a participant to read it. A participant may enter the forward availability as Carrying or follow the backward availability through Retracing, but neither act creates the connection.

Where there is no connection, no carry or trace is claimed between the conditions.

Consequence 3: Carry And Trace

Carry and Trace are directional reads of one held connection.

A --carry--> B
A <--trace-- B

Carry names forward availability. Trace names backward availability. They are not two relations. Carrying is carry being enacted. Retracing is a participant following trace.

Consequence 4: Hold, Carry, Place As First-Order Terms

Hold, Carry, and Place are first-order terms that become readable where the working postulate is checked at first order:

• **Hold**: resolution remaining supportable as the same condition — what becomes readable where structure must not collapse.
• **Carry**: the forward availability of held connection — what becomes readable where order must remain available across change.
• **Place**: locatable entry into relation — what becomes readable where an operation must become enterable and correctable.

These terms have their own dependency placements in the Atlas and do not trace the working postulate as if it produced them. The postulate gives a reading of how they work together: relation holds, order carries, trace places.

Consequence 5: Order, Resolution Rate, And Crossings

An order names a mode in which carrying operates. A crossing names a passage where carrying changes structural role.

Order is not static arrangement. In Reality Mechanics, order becomes readable where relation can keep resolving distinction without losing the path by which that resolution is held. Root Order names the governing dependency arrangement. Order Trace names the followable path through that arrangement. Resolution Rate tests the living pressure on that order: how quickly meaningful distinction can resolve while remaining coupled, clear, and retraceable.

A system can move quickly while resolving poorly. A slower system may carry more order where prior resolution is nested and available. The postulate therefore does not treat speed as proof of order. It asks whether relation can hold, order can carry, and trace can place resolution without source drift.

The current order read is:

First     relation connects, posture orients, carry and trace become available
Second    carried order is enacted through coupling and participation
Third     participating carrying becomes organised and nested
Higher    organised carrying enters its own carrying
Practice  a participant retraces, checks, corrects, and carries forward

The posture sequence remains useful as a planted read of how order becomes workable: Connection and Posture are first-order; Structure is second-order, where carrying produces organised relation that bears. Clear and Clean then test whether what crossed is followable and residue-free. This sequence is not the root postulate. It is a practice read for testing whether the postulate can become workable through connection, orientation, structure, clarity, and cleanliness.

An order is not a world separate from another world. The difference is participation and access, not two realities.

Rules Of Use

The Atlas is valid only where the practice remains repeatable.

To use a term as an Atlas term:

1. Place it by what it does in the order.
2. Trace what must already hold for it.
3. Show what it carries forward.
4. Check whether its wording can change while its placement remains recoverable.
5. Relieve or revise it where it drifts from what bears it.

This is why the Atlas is closer to a tended surface than a monument. A term is kept where it remains traceable. It is revised where its placement no longer answers to what it claims to carry.

Structural Care

The working postulate is tended as backbone, not defended as doctrine. It is load-bearing because it currently carries Atlas practice, not because it is immune to revision.

Alternative postures can be placed through Posture Read. A failed posture can be decommissioned as structural learning where it shows what could not hold, carry, place, clear, clean, or remain re-enterable. A failed postulate can also be tended this way: it is revised where it stops helping the Atlas place relation, carry order, or return by trace.

Failure Tests

The postulate should fail where it cannot do work.

**Relation test.** If no relation holds, the passage is asserted rather than entered.

**Order test.** If what holds cannot carry forward without losing dependency, order has been named but not carried.

**Trace test.** If a carry claim cannot be followed back to what holds it, trace cannot place the claim.

**Connection test.** If no relation holds between the conditions being connected, the passage is asserted rather than entered.

**Posture test.** If no orientation is present — if the connection is symmetrical in all directions — posture is a label rather than a held toward-ness.

**Structure test.** If posture does not carry as ordered relation that bears, structure has been named but not generated.

**Clarity test.** If the structure cannot be followed without obstruction, it is present but unreadable.

**Clean test.** If following the structure leaves residue that carries into the next operation, the carrying is contaminated.

**Resolution Rate test.** If a system resolves quickly but loses coupling, clearance, or trace, it has speed without Atlas order. If it resolves slowly but keeps more dependency available for continuation, its resolution rate may be higher in the Atlas sense.

Formal Sketch

The notation is a sketch, not the substance of the postulate.

Let `x` be an Atlas claim.

Rel(x)       relation holds
Ord(x)       order carries what holds
Tr(x)        trace places what carries

An Atlas operation is provisionally valid where:

AtlasValid(x) if Rel(x) and Ord(x) and Tr(x)

Directional reads of connection:

carry_c : a -> b
trace_c : b -> a

These are directional reads of the same held connection, not two relations.

The posture sequence can still be used as a practice read:

Conn(x)      relation holds between distinguishable conditions
Post(x)      connection is oriented — held with toward-ness
Str(x)       posture carries as ordered relation that bears
Cl(x)        structure is followable without obstruction
Cn(x)        following carries without residue

Worked Reads

**A note.** A note enters the Atlas where relation holds, order carries, and trace places: its term is related to what holds it, its position carries forward without losing dependency, and its claims can be followed back.

**A measurement.** A measured result carries value only where the measurement condition relates source to result, order carries the transformation through a scale or procedure, and trace can place the result back through the conditions that produced it.

**A conversation.** A reply carries relation only where enough context holds, the response carries the order of that context forward, and trace can place the reply back through what it is answering.

Relation To Existing Mathematics

The formal layer remains a comparison surface, not an authority.

• [Causality and the Semantics of Provenance](https://arxiv.org/abs/1006.1429) is relevant to followable dependency paths.
• [Categories of Optics](https://arxiv.org/abs/1809.00738) is relevant to lawful forward access with backward recovery.
• [Hypergraph Categories](https://arxiv.org/abs/1806.08304) and [Double Categories of Open Systems](https://arxiv.org/abs/2509.22584) are relevant to composition through exposed structure.
• [Abstracting Causal Models](https://arxiv.org/abs/1812.03789) is relevant to structure preserved across levels.
• [Traced Monoidal Categories](https://doi.org/10.1017/S0305004100074338) is relevant as a contrast for trace as feedback.

These comparisons do not ground the postulate. They help test whether a formalisation is already covered, wrongly stated, or useful enough to keep.

Places

The Working Postulate places the ordinary-language postulate of Reality Mechanics: relation holds, order carries, trace places.

Holds

The Working Postulate is held by Atlas, Relation, Root Order, and Trace.

Pairs

The Working Postulate pairs with Atlas. Atlas is the worked surface; the postulate bounds what counts as a valid Atlas operation.

Traces

• Atlas
• Relation
• Root Order
• Trace

Nests

The Working Postulate nests beside the Atlas as a versioned working postulate. Connection, Posture, Carry, Bearing, Memory, Order Trace, Resolution Rate, Atlas Practice, Posture Read, and Carry-Trace Test remain nearby as consequences, guides, practices, reads, or tests, but they do not replace the postulate as root.

Reads

The Working Postulate becomes recognisable where terms can be treated as placed operations: relation holds, order carries, trace places, and Resolution Rate tests whether meaningful distinction can resolve without losing order.

Carries

• Atlas Practice