varie
This commit is contained in:
@@ -1,11 +1,3 @@
|
||||
## Da aggiungere
|
||||
- intricazione
|
||||
- top-down
|
||||
- eterarchia
|
||||
- questo tipo logica non ha un corrispettivo nella programmazione tradizionale.Perche' questa si ispira al nostro ragionando che e' unico. Ragionare su una logica unificante nella programmazione tradizionale non ha senso, perche' non c'e' una logica unica, ma una per ciascun programma
|
||||
- in G esprimiamo la possibilità di eventi con RF che da la possibilità relativa. in enliving le possibilità diventano attualità. a quel punto possiamo interpretare temporaneamente le relative attializzazioni, perche abbiamo imposto la matrice spazio temporale.
|
||||
- il fatto che possiamo far girare lenliving su un hardware piu o meno veloce, se manteniamo la relatività fra possibilità di eventi, non cambia nulla alle attualità. quello xhe cambia è la velocita di scorrimento del tempo, non le seqyenze di eventi.
|
||||
|
||||
# Logic Principles of the Tripartite Synapse Model
|
||||
|
||||
These are the principles that govern the system's logic — not the syntax in which it is
|
||||
@@ -157,6 +149,23 @@ downward, TRACE accumulates evidence upward, and NIGHT commits the top of the up
|
||||
the source of the downward flow. To understand the system is to see that it is a four-rung ladder
|
||||
with capacity descending and evidence ascending, turning once per DAY/NIGHT cycle.
|
||||
|
||||
**The ladder governs pools as well as traces — and a pool's recovery timescale is what its
|
||||
exhaustion means.** Each tier has a depletion process, a recovery process, and a failure meaning,
|
||||
and the three are bound together by the tier's timescale. *Fast* pools (the readily-releasable
|
||||
vesicle pool) deplete and recover fast, so their shortfall is transient — short-term depression,
|
||||
self-correcting within a second once activity slows. *Medium* pools (the operational budget)
|
||||
deplete and recover at the medium scale, so their shortfall is a standing constraint, not
|
||||
instantly self-correcting — which is exactly why it is worth recording as endurance evidence.
|
||||
*Persistent* capacity (structure) changes only at NIGHT, so its "shortfall" is a structural limit
|
||||
that cannot be fixed in DAY at all. The recovery timescale of a pool therefore determines what
|
||||
kind of thing its exhaustion *is*: a passing inconvenience, a standing problem worth consolidating
|
||||
against, or a hard ceiling. This is the same "timescale = meaning" principle that governs traces,
|
||||
now applied to pools — and it is why the model can read a behavior's failure mode off which pool
|
||||
ran dry: fast-pool exhaustion is STD, medium-pool exhaustion is endurance evidence, persistent-pool
|
||||
limit is structural. Depletion and recovery are the pool-side mirror of creation and decay: a pool
|
||||
is drawn down by behaving and refilled toward its ceiling, just as a trace is deposited by behaving
|
||||
and relaxes toward zero, and in both cases the timescale is the meaning.
|
||||
|
||||
---
|
||||
|
||||
## V. Locality
|
||||
|
||||
Reference in New Issue
Block a user