Files
organism/winnertakeall/BEH-EXH.md
T

82 lines
1.7 KiB
Markdown
Raw Normal View History

2026-03-12 18:46:05 +01:00
# EXH-WTA.md
## EXH-WTA: Container
**Exhitory Behavior**: (directly observable, excluding TUN e DEV).
Qui devo fare la distinzione fra il behavior su exhitation e inhibition (SOMA)
L'associazione PRE<->POST fatta con SYN dall'interprete/enliver, e' possibile perche' in POST e PRE si fa riferimento a NT che vengono immessi in SYN. Ovviamente tutto concettuale, ma in enliving il concettuale viene attualizzato.
Quindi deve lavorare per ogni dichiarazione, casomai privilegiando alcune possibilita' che sono piu' impellenti di altre.
```Gen
container: BEH-WTA
contained_by: WTA
tub_local:
- ??? (fullness: 50x, active: 0x, emptiness: 0x)
tub_intricated:
- GoodTraces ( contained_by: BEH-?? )
- BadTraces ( contained_by: BEH-?? )
- pre
- post
- syn
# qui vanno tutte le pre e post che fanno capo ad una Ast nella dichiarazione di relazione fatta in WTA
context_intricated:
- TunPossible ( contained_by: WTA )
```
### CheckDirection: Context
Qui devo capire queste tracce chi le lascia e se sono esclusive?
```Gen
context: CheckDirection
contained_by: TUN-AST-SYN
in_context: TunPossible
rf: 60x
condition: ( GoodTraces Full ) AND NOT ( fullSyn full )
out_context: ActivateSyn
condition: ( BadTraces Full )
out_context: DeActivateSyn
```
### ActivateSyn: Episode
....
```Gen
episode: activateSyn
contained_by: TUN-AST-SYN
in_context: TunPossible
rf: ( active: 6x )
hypothesis: ( GoodTraces Full ) AND NOT ( fullSyn full )
action: [GoodTraces decrease, ]
trace: None
```
### DeActivateSyn: Episode
....
```Gen
episode: deActivateSyn
contained_by: TUN-AST-SYN
in_context: ???
rf: ( active: 6x )
hypothesis: NOT (?? empty)
action: [??? decrease]
trace: None
```