Sylvain Duchesne
ae9c32e271
Two batches, verified against nextgraph-rs throughout. P1a — the capability surface. Reading was an ACL (Map<doc, Set<principal>>), the exact inversion of key possession. It is now possession: `capFor(nuri)` is the only question, there is no principal parameter anywhere, and nothing turns a bare reference into a cap. Sharing is `shareCap(cap, toInbox)`, a Link deposit; receiving needs no operation. `Nuri` and `ReadCap` are template literal types, so passing a bare reference where a cap belongs is a compile error, with runtime guards behind it for JavaScript callers. The virtual user boundary. Every access function is now confined to the connected user, through two rules on one criterion (possession), implemented in two places so a lapse in either is caught by the other: authorization at the passage points, and "do not even attempt" at the callers. The polyfill's own machinery moved to physical.ts — unguarded, never exported — which replaced an exemption list: the machinery no longer gets waved through the guard, it calls something the guard never saw. Removed, as emulating capabilities the target does not have: - discovery.ts and its global index. There is no discovery in NextGraph; you follow links. It also pooled user data across wallets. - the cross-account fan-out (listEntityDocs, resolveReadGraphs, allAccounts, loadShim), which was cross-user enumeration by construction. - resolveInboxAnchor, a single inbox common to every user. Caps are now stored where NextGraph stores them, and read back rather than recomputed: AddRepo on the store's Store branch for documents a user creates, AddLink on its User branch for caps received. Inboxes belong to someone — the user's own, plus one per document — and connecting a user drains them all; that is the library's job, not the app's. Corrections worth recording: a ReadCap is `r:`, not `:k:` (reported by NextGraph's developer, verified in BlockRef::readcap_nuri); received caps DO have a register (AddLink), contrary to what this repo's notes claimed; and "wallet" upstream means keyring — what owns three stores is a user, so the vocabulary follows. The cap value is the constant OK: the only question the emulation answers is whether a cap is held. P1b replaces that one constant with a real key. After this the shape is right and the isolation is still fake. Nothing here may be described as anonymous or private.
18 lines
783 B
TypeScript
18 lines
783 B
TypeScript
/**
|
|
* Wrapped `useShape`: same signature as `@ng-org/orm`. Once the cap emulation is
|
|
* in force, the returned set is a read-filtered VIEW (only items in documents the
|
|
* current holder has the ReadCap of); before the first cap is issued it passes the
|
|
* real set through unchanged. At migration the filtering disappears — the broker
|
|
* only delivers documents whose cap the wallet holds.
|
|
*/
|
|
|
|
import { getConfig, getCaps } from "./polyfill";
|
|
import { makeReadFilteredView } from "./read-filter";
|
|
|
|
export function useShape(shapeType: unknown, scope: unknown): unknown {
|
|
const set = getConfig().useShape(shapeType, scope) as object;
|
|
const caps = getCaps();
|
|
if (!caps.isEnforcing()) return set; // no cap issued yet → passthrough
|
|
return makeReadFilteredView(set, caps);
|
|
}
|