pith. machine review for the scientific record. sign in
module module high

IndisputableMonolith.Foundation.Atomicity

show as:
view Lean formalization →

The Atomicity module introduces a precedence relation on events to enforce ordering in the Recognition Science foundation. Researchers modeling causal sequences or discrete scheduling in physics would cite it for its minimal-element and topological-sort primitives. The module supplies definitions and basic lemmas that let later results construct sequential schedules while preserving conservation. It consists entirely of definitions and supporting lemmas with no complex proofs.

claimLet $E$ be a set of events. A precedence relation $prec : E → E → Prop$ is defined so that $prec(e_1, e_2)$ asserts $e_1$ must occur before $e_2$. The module also supplies predicates $isMinimalIn$ for events with no predecessors and functions $topoSort$ that produce linear extensions respecting the relation.

background

Recognition Science models physical processes as sequences of atomic events whose order is governed by a precedence relation. The module defines this relation (Precedence) and equips it with standard order-theoretic tools: minimality checks, existence of minimal elements, and topological sorting that respects the given precedence. These constructions sit inside the broader Foundation layer that later builds atomic ticks and sequential schedules. The module imports only Mathlib, relying on its standard library for Prop, lists, and permutation lemmas.

proof idea

This is a definition module, no proofs.

why it matters in Recognition Science

Atomicity supplies the ordering primitives that later modules use to construct sequential schedules and prove conservation preservation. It directly supports the atomic_tick and sequential_preserves_conservation declarations listed among its siblings, which in turn feed the eight-tick octave structure of the unified forcing chain. The module therefore closes the gap between raw event sets and the discrete time steps required by T7.

scope and limits

declarations in this module (26)