gunnchOSArchitecture / UML
Service intent protocols
A service request has to say what should continue when the network changes, without pretending the protocol is already deployed.
Accepted source 088c5e88e155 · ACCEPTED_MAIN · protocol-research
Not a deployed network protocol and not standards-track by virtue of these diagrams.
Current is shown first. Future and legacy stay labeled. A rendered SVG is used when accepted main already committed one. Otherwise the Mermaid or Markdown source is shown and is not executed in the browser.
- current: Component — current
- current: Sequence — communication
- future: Future UML — emergent intent
- legacy: Legacy UML — emergent intent
Current
Component — current
current mermaid
What this diagram shows
LEARN[discrete / continuous learned tokens]
What this diagram does NOT prove
This diagram does not prove a standardized or deployed protocol.
Source path docs/uml/current/component.md @ 088c5e88e155
Sequence — communication
current mermaid
What this diagram shows
Messages enter the **observation inbox**. They never add a presence bonus to reward.
What this diagram does NOT prove
This diagram does not prove a standardized or deployed protocol.
Source path docs/uml/current/sequence_communication.md @ 088c5e88e155
Future
Future UML — emergent intent
future markdown
What this diagram shows
Current experiment/protocol views: [../current/index.md](../current/index.md).
What this diagram does NOT prove
This diagram does not prove a standardized or deployed protocol.
Source path docs/uml/future/index.md @ 088c5e88e155
Legacy
Legacy UML — emergent intent
legacy markdown
What this diagram shows
Older interpretability notes. Current authority: [../current/index.md](../current/index.md). Language-emergence claims stay gated off.
What this diagram does NOT prove
This diagram does not prove a standardized or deployed protocol.
Source path docs/uml/legacy/index.md @ 088c5e88e155