Proof

Retrace pathway

Proof packages what the programme currently holds as accepted, what remains candidate, and what is still unresolved — so independent participants can review, challenge, and retrace it. Nothing here is promoted beyond its stated status.

The retrace pathway

Every claim on this site can be walked back to its source. The pathway has four steps:

1ClaimA statement with a named status — accepted, candidate, or unresolved. Never more than its status.
2SourceThe Atlas term or repository document the claim reads from. GitHub is canonical. 3MethodThe stewardship tests or commission that examined it. The burden of proof sits on every proposed change, never on existing structure. 4RecordThe evidence report that preserved the examination, in docs/reports/.

Submission 001

The first public submission coordinates repository evidence under the Constitution's standard of care.

What it is

Reality Mechanics exists to increase structural perception. Reality already carries order; participation becomes more faithful when the questions asked, the operations performed, and the answers preserved stay retraceable. The programme builds instruments to perceive and preserve structure that is already there — it does not claim to invent it.

Three-layer architecture

Atlas (source) → Stewardship (verification) → Platform (public surfaces). The Atlas is the editable, dependency-ordered record; Stewardship is a recovered audit method that verifies existing structure and authors nothing new; the Platform reads the Atlas through a generated D1 read-model. Authority flows down; evidence flows up.

Working architecture

Presented honestly: the accepted body is small and conservative; the investigated body is large. That is by design — derivation before promotion.

Accepted

  • Constitution (C001–C014) as governing constraints.
  • Atlas as canonical source; D1 as a generated read-model.
  • Relation as the sole primitive.
  • Working Postulate v0.6 — "relation holds, order carries, trace places."
  • Stewardship method v1 — eight invariants, evidence grading E1–E5.
  • Public surfaces: Observatory, Pulse, MCP.

Candidate

  • A candidate practice runtime, Ark Run.
  • A candidate calculus relating Order and Ark — tested, found not minimal; minimal seat is Relation → Connection.
  • Hypothesis: frontmatter fields are calibrated structural questions.

Unresolved

  • The Calculus has no accepted operation; the : operator is not accepted.
  • Pressure is not yet derived.
  • "operation" is used inconsistently across the repository.
  • Second Order terminal-marker gap, left unfilled.
  • D1 schema and non-entries recovery path uncharacterised (commission C005, open).

Public instruments

ObservatoryObserve structural relationships in the field. PulseCalibration — behaviour through time.

Evidence reports

What this does not claim

What this asks of reviewers

Proof — coordinated from accepted repository evidence. The Calculus remains an open investigation; nothing here promotes it.

Two ways in

Observing

Observe → Theory → Proof → Calculus → Repository

Begin in the Observatory and watch the structure before reading about it. Theory explains why the discipline works, Proof retraces the evidence, and Calculus shows what is derived — and what is not.

AI participation

MCP → Atlas → Runtime contracts → Programme index → Repository

The MCP is the read-only doorway for AI workers: the same canonical structure, served as traversal tools instead of pages. It exists so AI participants read structure rather than infer it. No write tools are exposed.

Begin with begin_atlas_session, then get_public_surfaces. Orientation: programme index · AI participation.

https://mcp.realitymechanics.nz/mcp

One record, one path: this site reads from GitHub, where the Atlas is canonical, reports preserve the evidence, and runtime contracts govern what the instruments may claim. Every public claim retraces along that path.