Update 2026-06-30-logic-principles-of-the-expression_v4.md

elements/neuron/appunti/2026-06-30-logic-principles-of-the-expression_v4.md

@@ -12,13 +12,15 @@ system does X," it is rewritten as "local components, contextualized thus, do X
 because the form of the document should enact its central claim, that locality goes all the way
 down and all the way up, with no privileged vantage anywhere inside.
 
-The ten categories run foundation-first. The closing category — the Three-Phase Ring — is the
-integrator: it shows how a single cycle of ACTION → EVALUATION → PREPARATION, run locally by
+The nine categories run foundation-first. The closing category — the Three-Phase Ring — is the
+integrator: it shows how a single cycle of ACTION, EVALUATION, and PREPARATION, run locally by
 every component and turned in two directions (outward by DAY, inward by NIGHT), is where all the
 flows the earlier categories describe actually happen in time. It comes last because it uses
-everything established before it. A vocabulary note on motion: causation *circulates* across
-scales (category VI); the ring *turns* across phases (category IX). Two different loops, two
-different words, kept distinct.
+everything established before it. Its sharpest claim: a phase is a *role*, not a fixed event, so
+the same physical machinery — a release, a structural change — serves as ACTION in one scope and
+EVALUATION in the other, and the two scopes enter the ring at different phases. A vocabulary note
+on motion: causation *circulates* across scales (category VI); the ring *turns* across phases
+(category IX). Two different loops, two different words, kept distinct.
 
 ---
 
@@ -425,7 +427,10 @@ is one turn through all three:
 
 The order around the ring is ACTION → EVALUATION → PREPARATION → ACTION. Because it is a ring, no
 phase is first; each turn's preparation feeds the next turn's action, and each turn's evaluation
-reads the action that preceded it.
+reads the action that preceded it. A phase is a *role*, not a fixed physical event: the same
+physical machinery (a release, a structural change) can serve as different phases in different
+scopes, and each scope enters the ring at a different phase — the rotation is worked out in "The
+two turnings" below.
 
 **The ring is necessary; its co-location in one component is not.** What the logic guarantees is
 that the ring *closes* — that every action is evaluated and every action is prepared for — not that
@@ -494,43 +499,73 @@ coincidence is evaluation.
 
 ### The two turnings
 
-The subjects are invariant across DAY and NIGHT; only the content that flows through them
-transposes — information by day, resource by night. From the component's own standpoint there is no
-"open" or "closed" scope: each turning runs against *its* environment, which is the world by day and
-the economy by night.
+One ring, turned in two directions. The three phases and their subjects are invariant across DAY
+and NIGHT; what rotates is the *content* flowing through them (information by day, resource by
+night) and — the sharp point — *which physical event counts as which phase*. From a component's
+own standpoint there is no "open" or "closed" scope: each turning runs against *its* environment,
+the world by day and the economy by night.
 
-**DAY — the ring turned outward.** ACTION is the cleft exchange (release, integrate, clear) against
-the external environment, leaving the fast trace. EVALUATION climbs the ladder to the tag —
-information worked up toward significance, minted for the night. PREPARATION reads the descended
-structure and refills the pools toward the next behavior. Currency: information, cheap and gathered
-passively. Direction on the ladder: evidence ascending. Handoff token minted: the **tag**.
+**The same physical event is ACTION in one scope and EVALUATION in the other.** This is the
+deepest form of the duality. Transmitter release is the day's ACTION — the defining outward deed,
+transmitting to the world — and the fast trace is its byproduct, later evaluated. But the *same
+release*, run at night, is EVALUATION: the component releases not to transmit but as a *probe*, to
+read its own fast trace as a measure of how much it participates in the re-evoked pattern. And the
+structural change, which the day can only *mark* (the tag is an inert claim pointing at a
+restructuring that never happens by day), is the night's ACTION — its defining, irreversible deed.
+So the defining act of each scope is the assessment-instrument of the other: release is
+day-action / night-evaluation; restructuring is night-action / day-inert-mark. The scopes do not
+merely run the ring in two directions — they swap which event is the deed and which is the
+measurement. Because it is a ring, each scope simply enters at a different phase: the day enters at
+ACTION (act, then evaluate, then prepare — it must act first, the world will not wait); the night
+enters at PREPARATION (prepare, then measure, then act — it can afford to look before it leaps).
 
-**NIGHT — the ring turned inward.** ACTION is the coherence check: the component signals its
-standing claim into the same channels, now economic, and reads whether its peers concur — the
-lateral interaction, its content now "should this be kept" rather than "transmit." It leaves a
-coherence verdict, the night's fast trace. EVALUATION is draw-and-commit: reading the verdict, the
-component burns energy and material into structure only if coherence was found, spending its tag —
-minting the token for the next day. PREPARATION is make-room: receiving the constraint broadcast
-from above, recycling material from decayed ceilings, resetting for the next round's building.
-Currency: resource, scarce and fought over. Direction: capacity descending, demand ascending.
-Handoff token minted: the **structure**.
+**DAY — the ring turned outward.** PREPARATION reads the descended structure and refills the pools;
+ACTION is the cleft exchange (release, integrate, clear) against the world, leaving the fast trace;
+EVALUATION climbs the ladder to the tag — significance worked up, minted for the night. Currency:
+information, cheap, gathered passively. Ladder direction: evidence ascending. Token minted: the
+**tag**.
 
-**The two turnings are stitched together by evaluation.** Each scope's EVALUATION mints the token
-the *other* scope's PREPARATION consumes: day-evaluation mints the tag, night consolidates it;
-night-evaluation mints the structure, the next day reads it. The tag is information becoming a
-resource-claim; the structure is resource becoming the bound on future information-gathering. The
-DAY/NIGHT alternation is therefore not two separate cycles but *one ring turned in two directions*,
-handing off to itself through evaluation — tag outbound to the night, structure outbound to the day.
-The fatigue loop (category II) switches which way the ring is turning; the evaluation handoff passes
-what crosses when it turns. Switch and payload, one ring, two turnings.
+**NIGHT — the ring turned inward, as a sequence of replay cycles.** PREPARATION imports material
+and energy and *primes* the component's own spontaneous threshold from its own standing tag (a high
+tag lowers the threshold, raising occupancy). ACTION is the structural change — general homeostatic
+lowering, then rebuilding where the tag still stands and participation was confirmed, consuming the
+tag on the build. EVALUATION is the probe: the component spontaneously releases/fires and reads its
+fast trace as *participation* in the re-evoked pattern — no dopamine, because significance is
+already settled; this measures only circuit centrality. Currency: resource, scarce. Ladder
+direction: capacity descending. Token minted: the **structure**.
 
-**Why night must cycle its turnings.** By day the ring turns once per action and the actions come
-whenever the world drives them. By night the turning repeats in rounds because coherence is reached
-by different components at different times: a component that finds no coherent peers in one round's
-ACTION draws nothing in its EVALUATION, holds its tag, returns its resource to the pool for peers
-that did cohere, and turns again — its PREPARATION making room for a retry. Deferral is free because
-evaluation only spends when coherence is found, and energy, the irreversible currency (category IV),
-is burned only at the moment of coherent commitment. So the night is many turnings of the one ring,
-converging as coherence spreads, ending when demand is discharged or the night's energy is spent —
-and a change that never coheres before its tag decays is simply never spent on, which is how the
-turning forgets.
+**Replay is how the undifferentiated tag is spent on specific behaviors — and it needs no
+orchestrator.** A component's tag accumulates by day from *many* behaviors into a single
+magnitude — how much change it needs, stripped of what for. It cannot spend that lump correctly in
+one commit (that would build a blend serving no behavior). Replay re-presents the day's behaviors
+one at a time so the lump can be allocated to each. The mechanism is local and emergent: at night,
+freed from external drive, components spontaneously fire; where a tag has lowered a component's
+threshold, intrinsic fluctuation ignites it, and the activation propagates through the *same
+pathways used by day*, re-evoking the pattern — but only where *every* link is primed (each
+component's own tag lowered its own threshold), so a pattern carries only if it was significant all
+the way around. This coherence is mechanical, not checked: an un-primed link breaks the loop at the
+gap. The re-evoked components run their *structural* logic, not their significance logic — they are
+not re-asking "did this matter" (settled) but "how much do I change for this." The replaying
+assembly is not an actor; it is the coincidence of many components' own lowered thresholds
+propagating through recurrent coupling — holism enacted, not encoded (category I).
+
+**Why night cycles: the tag depletes, and depletion re-sorts the queue.** Each re-evocation lets
+the participating components allocate a *slice* of their tag to that behavior and consume it — which
+raises their thresholds back, so that pattern steps aside and the *next*-deepest tag surfaces on the
+next cycle. The night sweeps its repertoire in rough order of tag depth, strongest most often, each
+pattern depleting and yielding to the next, exactly as a vesicle pool depletes and refills to
+schedule release one scale down. This is why the tag is spent incrementally across cycles rather
+than all at once, why strong memories replay repeatedly, and why consolidation is a gentle settling
+over many cycles (and many nights) rather than a single commit. The night ends when the tag is
+exhausted (well-rested — every significant pattern replayed and its structure rebuilt) or the
+night's energy is spent (overloaded — unspent tags carry forward). A pattern that never re-evokes
+before its tag decays is simply never built — which is how the turning forgets.
+
+**The two turnings are stitched by evaluation, and the fatigue loop switches between them.** Each
+scope's EVALUATION mints the token the *other* scope will consume: day-evaluation mints the tag
+that night spends; night-evaluation (participation) gates the structure that the next day operates
+within. This *payload* handoff is distinct from the *switch* — the fatigue loop (category II) that
+decides *when* a component crosses between scopes. One says what crosses; the other says when to
+cross; they are orthogonal (category II). So the DAY/NIGHT alternation is one ring, entered at two
+different phases, handing off to itself through evaluation, switched by fatigue — not two separate
+machines.