Reconnexion/ng-eventually
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

chore: la règle fondamentale devient toujours chargée, et la chaîne cesse d'être morte au sommet

Browse Source
This commit is contained in:
Sylvain Duchesne
2026-08-27 14:29:42 +02:00
parent f6a48a4507
commit 817f9074c4
8 changed files with 23 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.project/concepts/app-contract/knowledge_what-an-inbox-is-upstream.md
+1 -1
View File
@@ -26,7 +26,7 @@ Anything built here therefore aligns on the **engine's model**, because levels 2
`InboxMsgContent` declares eight variants. `ContactDetails` and `SocialQuery` carry data and have processors. **`Link`, `Patch`, `ServiceRequest`, `ExtRequest`, `RemoteQuery` and `DialogRequest` carry nothing at all** — they are bare unit variants, so they cannot hold a reference, name a servicer, or describe an operation.
That distinction decides how much they bind us, and it is why the provenance taxonomy in [[rule_no-divergence-from-nextgraph]] separates a reserved name from a declared shape.
That distinction decides how much they bind us, and it is why the provenance taxonomy in the no-divergence rule (`.project/rules/nextgraph/no-divergence-from-nextgraph.md`) separates a reserved name from a declared shape.
## Processing is closed, and so is posting