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

docs: ce que NextGraph offre vraiment autour des inbox, et ce qui n'est qu'un nom réservé

Browse Source
This commit is contained in:
Sylvain Duchesne
2026-08-20 10:30:31 +02:00
parent fafac38907
commit c507e79f8a
3 changed files with 54 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.project/concepts/app-contract/_overview.md
+2 -1
View File
@@ -2,7 +2,7 @@
type: overview
summary: What an application may rely on from @ng-eventually/polyfill, and what it will have to delete
triggers:
keywords: [polyfill, sdk, surface, contract, publish, published, entry, export, migration, unlearn, consumer, app-facing]
keywords: [polyfill, sdk, surface, contract, publish, published, entry, export, migration, unlearn, consumer, app-facing, inbox, deposit]
paths:
- "packages/polyfill/src/index.ts"
- "packages/polyfill/src/surface/**"
@@ -36,3 +36,4 @@ This repo is the **provider** of `polyfill-surface`; consuming applications live
- `polyfill-surface/contract_polyfill-surface` — the engagement itself, written from the caller's point of view.
- `rule_no-divergence-from-nextgraph` — the test that decides what may be built at all.
- `knowledge_what-an-app-deletes-at-migration` — the two fates a published symbol can have.
- `knowledge_what-an-inbox-is-upstream` — what the target actually offers around inboxes, and where a choice of ours begins.