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

docs: documenter ce qui separe les identites sur une lecture

Browse Source
This commit is contained in:
Sylvain Duchesne
2026-10-01 13:53:02 +02:00
parent 4c1801f6ee
commit f5478643be
2 changed files with 64 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.project/concepts/app-contract/_overview.md
+3 -1
View File
@@ -2,12 +2,13 @@
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, inbox, deposit, IRI, urn, namespace, vocabulary, ontology, predicate, orm, useShape, getObjects, insertObject, OrmSubscription, ngSession]
keywords: [polyfill, sdk, surface, contract, publish, published, entry, export, migration, unlearn, consumer, app-facing, inbox, deposit, IRI, urn, namespace, vocabulary, ontology, predicate, orm, useShape, getObjects, insertObject, OrmSubscription, ngSession, read filter]
paths:
- "packages/polyfill/src/index.ts"
- "packages/polyfill/src/surface/**"
- "packages/polyfill/src/emulated-verifier/machinery.ts"
- "packages/polyfill/src/emulated-verifier/index-deposit.ts"
- "packages/polyfill/src/emulated-verifier/read-filter.ts"
- "packages/polyfill/README.md"
- "examples/notebook/**"
- "docs/api-contract.md"
@@ -51,3 +52,4 @@ This repo is the **provider** of `polyfill-surface`; consuming applications live
- `knowledge_what-the-orm-writes-and-deletes-upstream` — the writing half: removal is a set mutation wired end to end, and an ORM write never passes through `sparql_update`.
- `knowledge_what-an-inbox-is-upstream` — what the target actually offers around inboxes, and where a choice of ours begins.
- `knowledge_who-processes-an-inbox` — the division of labour along a deposit's path: what this package applies, what it merely delivers, and what a layer above owes itself.
- `knowledge_what-stands-between-identities` - the one module that isolates identities sharing a wallet: two views repaired together, a decided-or-refused default, and the hole host introspection leaves open.