Update presynapse.md

This commit is contained in:
2026-06-25 18:42:45 +02:00
parent 6bb183ffc7
commit 4d12a6b107
+20 -86
View File
@@ -208,126 +208,60 @@ RECOVER
type: container
within_scope: !DAY
// Rp Schuttle, NOT *AP
// snippet: NOT *AP
£: INCLUDE [ accumulator: RPShuttleLow, event: act 24x, cost: act 3x ]
£: INCLUDE [ accumulator: RPShuttleMedium, event: act 48x, cost: act 3x ]
// The "Hard Bottleneck" State. Recruitment is throttled by a lack of signal, a lack of supply, or a lack of space. If even one of these "Near-Stop" conditions is met, the rate cannot exceed "Slow," regardless of the other two conditions. Rate: 0.00 0.25
£: INCLUDE [ accumulator: RefillGlutamine, event: act 24x, cost: act 3x ]
```
#### NOT *AP
##### RPShuttleLow
This happens in the seconds loop, once per second.
The "Hard Bottleneck" State. Recruitment is throttled by a lack of signal, a lack of supply, or a lack of space. If even one of these "Near-Stop" conditions is met, the rate cannot exceed "Slow," regardless of the other two conditions.
Rate: 0.00 0.25
```Gen
RPShuttleLow
type: accumulator
in_context: NOT *AP
hypothesis: _CaTraceLow fullness OR
_RP emptiness OR
_Rrp fullness
void: INSTANTIATE [ accumulator: RPShuttleLow, event: 24x, cost: 3x, context: NOT *AP ] {
hypothesis: _CaTraceLow fullness OR _RP emptiness OR _Rrp fullness
action: [ _RP decrease, _Rrp increase ]
trace: None
```
}
##### RPShuttleMedium
The "Sub-Optimal" State. The machinery is working, but it's held back by partial limitations. This covers cases where the signal is steady but the "piston" isn't firing at full speed, or where a high vacancy in the RRP (emptiness) forces a low signal to work a bit harder.
Rate: 0.50 0.97
```Gen
RPShuttleMedium
type: accumulator
in_context: *AP
// The "Sub-Optimal" State. The machinery is working, but it's held back by partial limitations. This covers cases where the signal is steady but the "piston" isn't firing at full speed, or where a high vacancy in the RRP (emptiness) forces a low signal to work a bit harder. Rate: 0.50 0.97
void: INSTANTIATE [ accumulator: RPShuttleMedium, event: 48x, cost: 3x, context: NOT *AP ] {
hypothesis: ( _CaTraceMedium fullness AND _RP mediumness AND _Rrp mediumness ) OR
( _CaTraceHigh fullness AND _RP mediumness AND _Rrp mediumness ) OR # signal boost
( _CaTraceMedium fullness AND _RP fullness AND _Rrp mediumness ) OR # supply boost
( _CaTraceMedium fullness AND _RP mediumness AND _Rrp emptiness ) # vacancy boost
action: [ _RP decrease, _Rrp increase ]
trace: None
```
}
##### RPShuttleHigh
The "High Performance" State. Multiple systems are optimized, but one is still at a "mediumness" level. This represents an active synapse that hasn't reached its absolute peak because either the supply is only 50% or the \_Rrp isn't empty enough to create that "maximal vacuum" pull.
Rate: 1.25 1.94
```Gen
RPShuttleHigh
type: accumulator
in_context: *AP
// The "High Performance" State. Multiple systems are optimized, but one is still at a "mediumness" level. This represents an active synapse that hasn't reached its absolute peak because either the supply is only 50% or the \_Rrp isn't empty enough to create that "maximal vacuum" pull. Rate: 1.25 1.94
void: INSTANTIATE [ accumulator: RefillGlutamine, event: 24x, cost: 3x, context: NOT *AP ] {
hypothesis: ( _CaTraceHigh fullness AND _RP fullness AND _Rrp mediumness ) OR # signal + supply
( _CaTraceHigh fullness AND _RP mediumness AND _Rrp emptiness ) OR # signal + vacancy
( _CaTraceMedium fullness AND _RP fullness AND _Rrp emptiness ) # supply + vacancy
action: [ _RP decrease, _Rrp increase ]
trace: None
}
// Refill Glutamine
```
##### RefillRPGlutamine
This happens in the minutes loop, once per minute, via the glutamine shuttle from the astrocyte. It is a two-step process across two cells.
Step 1 — astrocyte side
The astrocyte has been accumulating cleared glutamate from the cleft since the last minutes-loop execution. Its glutamine synthetase enzyme converts that glutamate into glutamine, filling the Glutamine_pool. The fraction successfully converted per cycle is conversion_efficiency, which is set by glucose availability and boosted temporarily if the astrocyte calcium wave fired during the preceding seconds:
refill_RP = Glutamine_pool * conversion_efficiency
Glutamine_pool = max(0.0, Glutamine_pool - refill_RP)
Step 2 — presynapse side
The glutamine crosses into the presynapse, where glutaminase converts it back into glutamate. That glutamate is immediately repackaged into vesicles and added to N_RP:
**The asymmetry that makes depletion possible**:
The chain reveals why sustained high-frequency firing eventually depletes the synapse even with all replenishment mechanisms running.
The RRP holds at most `Max_RRP = 20` vesicles. At 20 Hz with strong Ca2, release can draw 2-4 vesicles per spike — potentially exhausting the RRP in under a second. The seconds loop can move vesicles from RP to RRP at a maximum rate of `k_rec_fast = 5 /s`, meaning at most 5 vesicles per second under ideal conditions. Release outpaces recruitment by roughly an order of magnitude during a burst.
The RP holds up to `Max_RP = 200` vesicles — ten times the RRP. At sustained 20 Hz the RP can sustain firing for tens of seconds even after the RRP is repeatedly emptied, as long as recruitment keeps pace. But the minutes loop only refills N_RP once per minute at a rate limited by `Glutamine_pool * conversion_efficiency`. If glucose is low or the astrocyte wave has not fired, this replenishment may add only a fraction of what was consumed.
The result is a three-tier buffer with mismatched timescales:
RRP — depletes in seconds, refilled in seconds (fast but shallow)
RP — depletes in minutes, refilled in minutes (deep but slow)
Gln — depletes over bursts, refilled by glucose (slowest, astrocyte-dependent)
Each tier buys time for the one below it to respond. When all three are depleted simultaneously — which only happens under prolonged high-frequency firing with insufficient glucose — the synapse has no remaining buffer and goes silent until the minutes loop restores the Glutamine_pool.
## ADJUST
```Gen
ADJUST
type: container
// qui stiamo attivando e disattivando PRE_VGCC. Fra un massimo full e minimo empty (empty puo' non essere 0)
type: container
activity_scope: !DAY
// VGCC_TUNE: *TunPossible
// snippet: *TunPossible
@: INCLUDE [ contextor: VgccCheck, event: act 60x ]
void: INSTANTIATE [ contextor: VgccCheck, event: 60x, cost: 3x, context: NOT *AP ]
// *VcggIncrease
@: INCLUDE [ accumulator: VcggIncrease, event:act 10x ]
void: INCLUDE [ accumulator: VcggIncrease, event: 10x, cost: 3x, context: NOT *AP ]
// *VcggDecrease
@: INCLUDE [ accumulator: VcggDecrease, event:act 10x ]
void: INCLUDE [ accumulator: VcggDecrease, event: 10x, cost: 3x, context: NOT *AP ]
```
#### *TunPossible