@epistery/client-lib

The modules of epistery that run in a browser and in Node alike, with the environment injected rather than assumed: the group key tree over the relay's delivery service, the one sealing module, the one relay client, the key-delivery policy, the signed manifests, the record helpers, and the small UI atoms every kind's page shares. The console serves the package directory at /lib/*; a page imports by that URL, a server by the package name — the same file either way, so nothing is written twice.

| module | environment | purpose | |---|---|---| | ds-group.mjs | browser + Node | DsGroup — a session's group over the relay's delivery service: create, load, replay, add, remove, update, restore; commit diligence and the rotation rule on the chain's word (format 5); seatedMembers() | | sealed.mjs | browser + Node | the ONE sealing module: sealedKeys(group, cipher) → seal, sealBlob, open, openBlob; isEpoch, isSealed; an untagged record never opens | | pool.mjs | Node | ComponentPool — the host's cross-package component namespace | | adslot.mjs | browser | the ad slot a kind's page may carry when its declaration says so | | components/ | browser | the shared atoms (saveButton, …) resolved by the pool | | records.mjs | browser + Node | the record shapes every kind shares: listRecords (list, match, read, drop tombstones), tombstone, stamp, newId, nextNumbered, isSealed | | relay.mjs | browser + Node | the one relay client — storage, upload, courier, identity reads, seals; signer and fetch injected; a failed relay answer throws, 404 is "none" | | manifest.mjs | browser + Node | the signed statements: the domain manifest (/.well-known/ai) and a session's declaration and discovery document; hash, message, build, verify (signature recovery injected) | | session-keys.mjs | browser + Node | key delivery over the courier: the one key-request shape, the asker and the responder (a durable messenger request) | | owner-seats.mjs | browser + Node | every key the owner holds is seated in every session the owner creates; records, seating, removal, restore | | cipher.mjs | browser + Node | per-session content + key wraps, over epistery core's one construction (epistery/client/peer-cipher.mjs); the server's serverKeys uses this same module | | markup.mjs | browser only | MarkUp — wiki markdown renderer (marked + Mermaid from CDN), WikiWord auto-linking | | wikiwords.mjs | browser + Node | pure WikiWord/reference extraction — served to the browser and imported by the wiki plugin's server code | | componentry.mjs | browser | the atomic-component base class (cloned+trimmed from @metric-im/componentry) — event hub, own-css injection, notification init | | IdForge.mjs | browser + Node | random / dated id generation | | Toast.mjs | browser | the one canonical toast/prompt (window.toast) | | Popup.mjs | browser | the one canonical modal (window.popup) | | component-acl.mjs | Node | server-side //ACL delivery preprocessor + levelOf(role) | | treekem-kdf.mjs | browser + Node | secp256k1 DHKEM + HKDF-SHA256 key schedule (EpisteryDataFrontier); one universal WebCrypto stack | | treekem.mjs | browser + Node | the ratchet-tree CGKA core (Member: commit/apply/Welcome) — the group key that feeds cipher.mjs |

TreeKEM — the frontier's key layer

treekem-kdf.mjs + treekem.mjs are the production port of the proven P0(b)/P2 spikes (EpisteryDataFrontier). One dual-environment module: ethers is the page global (window.ethers) in the browser and globalThis.ethers in Node, and the crypto stack is globalThis.crypto (WebCrypto) both places — so a browser rivet and a server participant derive the SAME group key by construction. The tree's per-epoch exporter secret is K for cipher.mjs. Commits are ordered by the relay's blind Delivery Service (/ds/...); this module is the crypto only.

componentry — the shared framework

The value is atomicity: a concept (a save button, a modal, a toast) has ONE canonical implementation, so it is never quietly rebuilt a dozen subtly-different ways. Components extend componentry.mjs and OWN their css via static css (authored scoped to the component's class; the base injects it once). No live css scope/concat serve — a component is self-contained.

The //ACL delivery preprocessor (component-acl.mjs) is the one server piece: the shell strips /*ACL>N*/…/*ENDACL*/ blocks the caller's level doesn't meet before delivering a component's .mjs, so privileged logic never reaches a lower-privilege browser. Level derives from req.episteryClient (initial map: 0 anonymous, 1 authenticated).

How it's consumed

The shell serves the package directory at /lib/ (the same way @epistery/art is served at /art), so a plugin bundle does:

import * as cipher from '/lib/cipher.mjs';
import MarkUp from '/lib/markup.mjs';

markup.mjs's import './wikiwords.mjs' resolves to /lib/wikiwords.mjs in the browser and to the package file in Node — the same source either way.

Server-side (wiki plugin), wikiwords is a normal package import:

import { extractWikiWords } from '@epistery/client-lib/wikiwords';

One cipher, in core

cipher.mjs implements nothing: a wrap (ECDH secp256k1 → SHA-256 → AES-256-GCM, {ciphertext, iv, tag}) and sealed content (AES-256-GCM under K, {iv, ciphertext} = ciphertext‖tag) are defined once in epistery core (epistery/client/peer-cipher.mjs), with vectors frozen against what is already stored. The browser page and a Node participant (@epistery/sessions serverKeys) run this same module, so nothing can drift. In the browser the console's import map resolves epistery/client/ to /lib/.

Tests

npm test

Every *.test.mjs in the package: the tree (ctx contract, growth, keyring, leaf-decap replay), the group (chain diligence, signed commits, leaf reuse and growth, the wedge and the restore, the twin stacks), sealing, records, and the owner-seats policy. Node resolves ethers and epistery through node_modules (a link to the console's is enough).

Dependencies

• epistery (peer) — the wire (storage-message, chain-read) and the one cipher (peer-cipher); a chainReader is required to construct a DsGroup.
• ethers v5 on globalThis in Node (the tree crypto, ECDH and address checksums read it there); the page provides window.ethers.