Calculus

Derive the structure.

The Calculus is the derivation surface. It records how Reality Mechanics moves from relation, order, trace, and carrying toward explicit derivation — and preserves every gap it has not yet closed.

Nothing on this page is promoted. The Calculus has no accepted operation; the : operator is not accepted. Statuses below are exact — where derivation is incomplete, the gap is shown, not papered over.

The status vocabulary

Every claim on this surface carries one of four statuses. They are not interchangeable.

derivedForced by repository evidence through a named test or locked definition. Independently retraceable to source and report.
calibratedAligned to existing structure by a tested rule or configured threshold. Faithful — but chosen, not forced from first principles.
heuristicA working number or rendering choice made for legibility. Carries no structural claim and can change without a derivation event.
unresolvedInsufficient evidence in either direction. The gap is preserved deliberately.

The live derivation chain

This chain runs on the Observatory today. Each step names its exact rule and its status — mathematics already implied by the runtime, made explicit.

Declared relationcanonical source holds · traces · carries · pairs · nests Every edge is declared in Atlas frontmatter, in GitHub. Nothing downstream may invent an edge. Source: Common Term Structure.md.
Structural massderived mass(t) = |{ s ≠ t : t ∈ holds(s) ∪ traces(s) }| Carrier in-degree over holds and traces only. needs, carries, pairs, nests are excluded by locked definition. Source: D-010B-generalise-ratio-mechanics.md.
Ratio modecalibrated mode(x) = continuous if x ≥ 8 · transitional if x ≥ 3 · else discrete Threshold bands are configured operational values, not derived constants. They translate mass into a render register. Source: DERIVED_RATIO.md.
Render behaviourheuristic amplification coefficients × what the runtime already computes Rendering only — no new mechanics. Legibility floors and placement jitter are likewise heuristic (D-022, D-023). Source: D-020B-mechanics-amplification.md.
Retracederived GET /api/field/behaviour-trace?id=… recomputes the chain for any term The read back is mechanical. If a rendered behaviour cannot be retraced to a declared relation, it is marked, not bonded. Source: D-012-behaviour-retrace-instrument.md.

This scalar chain is a narrower Field read. It is not Atlas Ratio — falsification found it viable with constraints, and a richer structural signature remains a future unknown. (D-015B-derived-ratio-falsification.md, DERIVED_RATIO.md)

Maturity, derived at read timecalibrated

Each term's maturity band — placed → fresh → settling → established → mature — is computed from revision history, carrier count, and proposal record every time the field is read. It is never stored. Band thresholds (48 h, 7 d / 30 d / 90 d, carrier minimums) are configured values.

The candidate calculus

The working relation under investigation, recorded in Practice Calculus:

Order : Structure : Read

The : marks an operation, not punctuation — and that operator is precisely what is not yet accepted. The burden of proof rests on the operations, not on the names of the stages.

Candidate runtime — Ark Runcandidate

Pressure → Trace → Check → Determine → Step

Seven proposed practice stages compress into this runtime already present in the Atlas — none of its operations required invention (C-001). It remains a candidate, not the Practice Calculus.

Minimum support — a negative result, keptderived

Relation → Connection

The candidate Order/Ark calculus was tested for minimality and found not minimal (C-003). A single held Connection — which needs only Relation — already offers forward availability (the Carry direction) and backward availability (the Trace direction). The candidate's apparent size comes from Hold, which pulls in nearly the whole first order. The negative result is preserved; the candidate is not promoted.

Standing constraints before any promotion

The full inventory

Derived

Calibrated

Heuristic

Unresolved

How this surface relates to the others

The Observatory shows structure; Pulse shows behaviour through time; Theory states the claim; Proof retraces the evidence. The Calculus shows how far the claims have actually been derived — and exactly where derivation stops.

Calculus — the derivation surface. The Calculus remains an open investigation; this page records its state and promotes nothing.

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.