Create 2026-07-08-the-unexpressed-objects.md

elements/neuron/appunti/2026-07-08-the-unexpressed-objects.md

@@ -0,0 +1,188 @@
+# The Unexpressed Objects — v1
+
+*The objects the mechanism implies but never expresses. The pseudocode has PRE, POST,
+ASTROSYNAPSE — three components, each running its own local loop. It has no `synapse`: no variable
+holds one, no line makes one act. Yet the synapse is real — the system builds it, sustains it,
+consolidates or forgets it. The synapse is an object that is **verified but never expressed**: it
+exists only as a behavior that three components continuously constitute together, along the axes of
+time, space, and quantity. This document is the catalogue of such objects — the synapse, the branch,
+the cell, the assembly, the rhythm — each real, each acted upon, none appearing in the mechanism,
+each existing only as a sustained mutual project its parts are always working at without any of them
+containing it.*
+
+*How this document differs from the other two. The pseudocode describes what is **directly
+expressed**: local components and their loops. logic_principles describes **why** the model is the
+kind of object it is, and the general operations (integrate, coincide, broadcast, inject) by which
+the unexpressed becomes verifiable. This document describes the **unexpressed objects themselves** —
+a distinct ontological layer: the things that exist by verification rather than by expression. It is
+not a higher-level summary of the pseudocode; the pseudocode does not contain these objects at all.
+It is the ontology the mechanism implies but never states.*
+
+*Why the framing matters. If read as "a convenient higher-level view," this document collapses into
+redundancy. Its actual claim is stronger: there is a whole layer of real objects that the mechanism
+acts upon but expresses nowhere, and describing that layer honestly is a genuine addition. Each
+object below is real in the only sense the model allows — it is continuously verified — and expressed
+in no component.*
+
+---
+
+## The frame: verified but not expressed
+
+The three axes along which any behavior is conceptualized are **time, space, and quantity**. An
+unexpressed object is *verified* when its behavior, read along these axes, is constituted by its
+parts and held as the level of some store — the object's present shadow (see logic_principles §7,
+Integrate). Behaviors read along the axes compose into the observables: a **frequency** (events per
+time), a **flow** (quantity per time), an **elapsed interval** (time between events), an **amount at
+a moment** (quantity at a time), a **spatial extent** (quantity over space), a **coincidence**
+(several things at one time and place). None is emitted by any component; each is constituted by many
+local acts and readable only where they accumulate. The verification is not a computation anyone
+performs — it is the automatic consequence of local acts accumulating in a store.
+
+But an unexpressed object is more than a passively-observed pattern. It is an **active project**: its
+parts are continuously *aligning* along the three axes — tuning toward each other so the behavior
+lands better and lasts longer. So each object is described through two lenses that are the same
+structure still and moving:
+
+- **Decomposed (still):** what behavior the object's parts constitute, and how it separates along the
+  three axes — which part owns which axis, and where the axes recombine.
+- **Aligned (moving):** how the parts actively tune toward each other along those axes — and, because
+  each part belongs to its own larger whole, how the object is really the *discovered compatibility
+  of several larger rhythms*, sustained under a stamina budget (align well **and** align long).
+
+To describe an unexpressed object, five questions:
+
+1. **What behavior** does it constitute, read along time, space, quantity, or their compounds?
+2. **Which part owns which axis**, and at what site do the axes recombine (the meeting-site that owns
+   none of them)?
+3. **Over what timescales at once** — the object is verified concurrently at several grains, each a
+   store the faster fills and the slower reads.
+4. **As what alignment project** — what are the parts tuning toward, within which larger wholes, and
+   under what stamina budget?
+5. **How does it turn day to night** — day constitutes the object from behavior; night re-evokes it
+   as a probe to decide what structure to keep.
+
+The objects below are the ones where these have interesting, non-obvious answers.
+
+
+---
+
+## Object 1 — The Synapse (constituted by PRE ⇄ POST ⇄ ASTROSYNAPSE)
+
+The synapse is the first unexpressed object: nowhere in the mechanism, everywhere in the behaviour.
+Three components constitute it, and it is real only as what they verify together.
+
+### Decomposed — the coincidence, separated into three owned axes
+
+A coincidence is several things at one time and place. In a two-party contact it would be an
+undifferentiated fact — release met response, or it did not. The third party decomposes it, because
+each party owns one axis:
+- **PRE owns quantity** — how much is released, set by its own occupancy × drive.
+- **The astrosynapse owns timing and space** — its clearance sets how long transmitter dwells (the
+  temporal window); its coverage sets whether release stays contained or spills (spatial isolation).
+- **POST owns the recombination** — its NMDA receptor is where quantity (glutamate), the postsynaptic
+  contribution (depolarisation), and the astrosynapse's gain (D-serine) meet; it reads the
+  coincidence *as scaled by* the timing and gain the others set.
+
+So the synapse verifies not "did they coincide" but "how much, how sharply timed, how contained" —
+three separable reads because three owners. This is why the synapse is tripartite and not bipartite
+(logic_principles §2, here made concrete as a division of who-holds-what). And the sites are plural:
+quantity is integrated in PRE's release, timing/space in the astrosynapse's clearance and coverage,
+the coincidence *event* at a fourth site — POST's NMDA — which holds none of the three axis-stores
+but is where their shadows overlap. The astrosynapse is what makes the coincidence witnessable under
+locality: it supplies the third input neither coinciding party owns, so the event registers without
+any party reading another's interior.
+
+### Aligned — the same three axes, in motion, as a sustained project
+
+The decomposition is the object at rest. In motion, the synapse is not detecting a coincidence but
+**working toward one, repeatedly, along all three axes** — the two sides tuning toward each other so
+the next attempt lands better:
+- **quantity alignment** — PRE and POST tune the match between how much is released and how strongly
+  POST responds (release capacity against receptor sensitivity);
+- **timing alignment** — the astrosynapse tunes the window (clearance → dwell) so release and
+  response fall within the same instant;
+- **space alignment** — the astrosynapse tunes coverage so the contact is contained, not bleeding
+  into neighbours.
+
+The synapse is the *project of aligning along three axes at once*. And it is never bilateral: each
+party belongs to its own larger whole — PRE to its neuron, POST to its neuron, the astrosynapse to
+the astrocyte's territory (with its alpha rhythm and territory-wide calcium spike). So the two
+synaptic partners are not free agents agreeing to meet; each is already committed to a larger rhythm.
+The synapse therefore verifies the **discovered compatibility of larger rhythms** — do PRE's neuron
+and POST's neuron (and the astrocyte's territory) turn out to match in *when*, in *how much*, and in
+*where*, often enough and sustainably enough to be worth cementing. Strengthening happens where three
+larger wholes prove temporally, quantitatively, and spatially compatible at one contact point. The
+astrosynapse's "indirect assistance" is precisely its folding of a *third* larger rhythm (the
+territory's) into the two-neuron alignment.
+
+### Concurrent — several alignments at once, at different grains, coupled through stores
+
+The alignment is not one process but a stack of them, running **at the same time** at different
+temporal grains, and this is the hard thing to say plainly: at any instant the synapse is
+simultaneously
+- attempting a **spike-to-spike** alignment (does this release meet this depolarisation? — ms),
+- tracking a **train-to-train** alignment (does the *burst* fall in the depolarised *window*? — tens
+  to hundreds of ms; synchronisation is over multiples of spikes, not single ones — short-term
+  plasticity lives here),
+- accumulating a **participation** alignment (is this synapse *consistently* in the co-active set? —
+  minutes; the running average),
+- and holding a **structural** alignment (is this worth permanent structure? — the overnight tag).
+
+They run concurrently but communicate only through stores, and the coupling has a direction: **the
+fast attempts deposit into stores the slower processes integrate, and the slow decisions set the
+configuration the fast attempts run within.** Last night's structural alignment is this morning's
+starting bias (the standing ceilings); the participation average reads the train-level's success; the
+train-level tunes the gain the next spike-attempt uses; each spike deposits the fast trace the
+train-level reads. So one does not describe them in sequence — one describes a stack of servos, each
+closing its loop at its own rate, nested so that slow sets the frame and fast fills the evidence. This
+is the timescale ladder (logic_principles §4) read as concurrent alignment rather than as static
+decay rates.
+
+### Under a budget — precision and stamina are the two success-conditions of one project
+
+Alignment is not free; it costs fuel, and the budget limits how long the synapse can keep trying. So
+the project has *two* success-conditions, not one: **align well** (land the coincidence hard enough
+to matter) **and align long** (hold the alignment as long as the task demands). These are exactly the
+two consolidation pathways the mechanism separates — strength and endurance — now revealed as the two
+dimensions of a single project: *be good at coincidence, for as long as it takes*. Strength is
+**precision** (did the alignment land?); endurance is **stamina** (could you sustain it?). A memory
+must be both — well-aligned and sustainable — which is why the model carries both a dopamine-gated
+strength tag (precision, at the significance-deciding sites) and a homeostatic endurance need
+(stamina, everywhere). The synapse is not just trying to align; it is trying to align *and hold*,
+within a budget that says how long the holding can last.
+
+### Day to night — constitute, then re-verify
+
+By day the synapse constitutes the coincidence from behaviour and deposits evidence (the tag at
+PRE/POST, the coverage-need at the astrosynapse). By night the same three parties re-run the
+coincidence as a probe — replay release, replay response, replay clearance — not to transmit but to
+verify whether the alignment still holds when the pattern is re-evoked without the world driving it.
+The participation this re-verification measures decides whether each party keeps its structure. So the
+synapse's day-role (constitute the alignment) and night-role (re-verify it to consolidate) are the
+identical three-party project read for two purposes — the rotation of logic_principles §3, at the
+level of the object.
+
+**The synapse in one line:** *three larger rhythms, meeting at one contact, trying to align along
+when / how-much / where — concurrently at four grains, under a stamina budget — so that a coincidence
+is decomposed into three owned axes by day and re-verified as a sustained alignment by night.*
+
+---
+
+## The queue — objects still to build
+
+- **The dendritic branch** (constituted by its spines → DEND). The clearest spatial integrator: how
+  spatially distributed spine alignments sum into one branch behaviour; how attention (ACh) reweights
+  the spatial sum; what "a branch" verifies that no spine does.
+- **The neuron's decision** (constituted by branches → SOMA). Convergence of dendritic integrals into
+  one fire/no-fire; where the neuron's own **frequency** (its firing rate) and **flow** (summed input)
+  become verifiable; the point at which continuous integration turns into a discrete event.
+- **The astrocytic territory** (constituted by processes → ASTROCYTE). Coincidence one scale up —
+  synapse-synapse-synapse co-activity, not pre-post — integrated into the regenerative calcium spike
+  and broadcast back; a higher-order unexpressed object detecting a higher-order coincidence.
+- **The pathway loop / assembly** (PRE→POST→DEND→SOMA→AXON→PRE). The largest unexpressed object: how
+  a recurrent loop verifies flow and timing around itself, and how the night's replay reads the whole
+  loop's coherence as mechanical all-or-nothing (every link primed or the pattern breaks). The
+  assembly is the object most purely unexpressed — it is nothing but the coincidence of many primed
+  thresholds.
+- **The rhythm** (cross-cutting). Frequency and phase as objects in their own right — what it means
+  for the system to verify and align to a rhythm (alpha, the day/night switch) that no component holds.