pcb
This commit is contained in:
@@ -472,6 +472,40 @@ So, on the map, these now look like:
|
||||
- separate from the later selector/page layer
|
||||
- still not sufficient to produce full wake/session activation
|
||||
|
||||
## HE33 Maintained Startup-Class Follow-Up
|
||||
|
||||
HE33 tested the next obvious question:
|
||||
once a startup-beacon family opens, can the host maintain that same class as a
|
||||
live background stream?
|
||||
|
||||
What happened:
|
||||
|
||||
- `90 -> 64 40 30` stayed real, but did not become maintainable
|
||||
- `A0 -> 90 -> 64 40 30` behaved the same way
|
||||
- `90 -> E4 40 30` did not pivot into a stable `E4`-maintained state
|
||||
- `A0 -> AF -> 0D 04 AB` could briefly drain more `AB` responses, then fell
|
||||
back to heartbeat
|
||||
- repeated `AF` plus host `0D 04 EB` was slippery and often still returned the
|
||||
`AB` family instead
|
||||
- adding heartbeat beside these startup classes did not help
|
||||
|
||||
What this means on the map:
|
||||
|
||||
- the startup-beacon layer is probably **real but shallow**
|
||||
- it can bias or open a startup family
|
||||
- but those families still do not behave like the maintained session stream the
|
||||
panel needs in order to wake fully
|
||||
|
||||
Refined startup-layer view:
|
||||
|
||||
| Startup opener | Family observed | Maintainable as a live class? |
|
||||
| --- | --- | --- |
|
||||
| repeated `90` | `07 80 64 40 30 C9` | no |
|
||||
| `A0 -> 90` | `07 80 64 40 30 C9` | no |
|
||||
| repeated `90` alternate branch | `07 80 E4 40 30 49` | not confirmed as maintainable |
|
||||
| repeated `AF` | `07 80 0D 04 AB 7F` or `07 80 0D 04 EB 3F` | no |
|
||||
| `A0 -> AF` | `07 80 0D 04 AB 7F` | no |
|
||||
|
||||
## Best Next Uses Of This Map
|
||||
|
||||
This map is meant to help us ask sharper questions, for example:
|
||||
|
||||
Reference in New Issue
Block a user