@nomosprotocol/sdk 2.0.0 → 2.3.0

package/README.md

@@ -50,7 +50,11 @@ verifier locally and then, in one transaction, records the nonce, re-reads your
 `commit` exactly the verified action, and stores the receipt:
 
 ```ts
-import { accept } from '@nomosprotocol/sdk';
+import pg from 'pg';
+import { accept, postgresStore } from '@nomosprotocol/sdk';
+
+const store = postgresStore(new pg.Pool({ connectionString: process.env.DATABASE_URL }));
+await store.migrate();                                       // once: creates the nomos_acts table
 
 const rp = accept({
   relyingPartyId: 'orders.acme.example',
@@ -59,8 +63,8 @@ const rp = accept({
   authorities: [{ artifactId: 'acme-purchasing', issuer: 'https://policy.acme.example',
                   actions: ['purchase'], currencyPolicy: 'record', inForceSealHash: POLICY_SEAL_HASH }],
   localFacts: async (act) => ({ vendor_blocked: await isBlocked(act.action.params.vendor) }),
-  commit: async (action, { tx }) => createOrder(tx, action),  // your existing code
-  store: myPostgresStore,                                    // nonces and receipts; memoryStore() for development
+  commit: async (action, { tx }) => createOrder(tx, action),  // your existing code, on the same transaction
+  store,                                                     // nonces, receipts and the Acts themselves
 });
 
 app.use(rp.express());          // Express, Connect, node:http
@@ -70,6 +74,13 @@ app.use(rp.express());          // Express, Connect, node:http
 `accept()` serves your discovery document at `/.well-known/nomos-relying-party`, generated from this
 same configuration, and answers every Act with the status NOMOS-SPEC-009 assigns.
 
+`postgresStore()` records the nonce, your change and the receipt in one transaction: `commit`
+receives `tx`, the same client. Under any number of concurrent submissions of one Act exactly one
+commits and the rest get `409` with its receipt, and the exact Act is kept beside its receipt so
+an auditor can re-verify it later. It takes a node-postgres `Pool` or anything with the same
+`query`/`connect` methods (Neon's serverless driver on edge runtimes, for example) and depends on
+no driver itself. `memoryStore()`, the default, is for development only.
+
 | Verdict | Status |
 |---|---|
 | AUTHORIZED, committed | 201 |
@@ -79,12 +90,21 @@ same configuration, and answers every Act with the status NOMOS-SPEC-009 assigns
 | REPLAYED | 409, with the original receipt |
 | any other refusal | 400 |
 
+**Certificates and revocations.** `act()` presents exactly the certificates an Act relies on
+(NOMOS-SPEC-009 0.2.0), so an issuer can certify any number of approvers. Witnesses and approvers
+can return their own chains with what they sign (`keyCerts`). On the relying party,
+`revocations: revocationSource({ url, root, maxAgeSeconds })` reads the issuer's signed list
+(NOMOS-SPEC-007 rev. 1.10). Revocations are never forgotten, and without a current list
+`accept()` answers 503 instead of committing.
+
 **The other roles** are one call each:
 - `issuer()` publishes your sealed policies and certificates;
 - `witness()` turns an existing lookup into signed statements;
-- `approver()` shows a person the exact change and signs their consent.
+- `approver()` shows a person the exact change and signs their consent; `passkeyApprover()` has them
+  sign it with Face ID, Touch ID or a security key, enrolled through a single-use link
+  (`nomos enroll`), so no server can approve for them.
 
-Keys are `Signer`s, so they can live in your KMS or HSM.
+Keys are `Signer`s, so they can live in your KMS or HSM: [`@nomosprotocol/signers`](../packages/signers) has adapters for AWS KMS, Google Cloud KMS, Azure Key Vault and any other HSM.
 
 **Any MCP agent** can carry Acts with no code: the `nomos-mcp` server has an `act` tool.