@metamynd/mmt-graph 0.2.0 → 0.3.1

package/mmt-graph.anchor-live-demo.mjs

@@ -67,15 +67,18 @@ function parseOperatorKey(raw) {
   }
 }
 
+const operatorPrivateKey = parseOperatorKey(operatorKey);
 const client = Client.forName(network);
-client.setOperator(AccountId.fromString(operatorId), parseOperatorKey(operatorKey));
+client.setOperator(AccountId.fromString(operatorId), operatorPrivateKey);
 
 async function ensureTopicId() {
   const fromEnv = process.env.MMT_GRAPH_TOPIC_ID;
   if (fromEnv) return fromEnv;
 
   console.log('No MMT_GRAPH_TOPIC_ID set — creating a fresh topic (set this env var to reuse it next time).');
-  const resp = await new TopicCreateTransaction().execute(client);
+  // Admin key IS set (the operator key) so this topic stays upgradeable later (e.g. an
+  // HSuite multisig validator key) — omitting it makes a topic permanently immutable.
+  const resp = await new TopicCreateTransaction().setAdminKey(operatorPrivateKey).execute(client);
   const topicId = (await resp.getReceipt(client)).topicId?.toString();
   if (!topicId) throw new Error('topic creation succeeded but returned no topicId');
   return topicId;

package/mmt-graph.types.mjs

@@ -60,6 +60,25 @@
  */
 /** @typedef {{ op: 'mandate-revoked', policyId: string }} MandateRevoked */
 
+/**
+ * Owner-initiated agent containment (distinct from a rule-fired suspend/quarantine,
+ * neither of which anchor to this graph today). `reason` is the free-text
+ * `AgentIdentity.containedReason` at the moment of decommission, capped the same way
+ * the DB column is.
+ *
+ * NOT YET WIRED to a projector or an adapter/backend call site (unlike
+ * MandateGranted/MandateRevoked, both of which have engine.mjs `#project()` cases —
+ * MandateRevoked's is just never invoked from a backend call site today). Applying
+ * AgentReinstated correctly needs a projector that clears just the prior
+ * containmentStatus/containmentReason quads for the agent — `apply()`'s only removal
+ * primitive today is `{removeSubject}`, which deletes the WHOLE agent node (its type,
+ * memberOf, mandates, cohorts…), not a single predicate. Add an
+ * `mmt-graph.engine.mjs` case (+ project.mjs projector) with a predicate-scoped
+ * removal before wiring an adapter call — until then this is vocabulary-only.
+ */
+/** @typedef {{ op: 'agent-decommissioned', agentDid: string, reason?: string }} AgentDecommissioned */
+/** @typedef {{ op: 'agent-reinstated', agentDid: string }} AgentReinstated */
+
 /**
  * Domain H (runtime activity/evidence) — Phase 5's first slice, proving the engine can
  * answer evidence-path.ts's "independently verifiable" question, not a full replacement
@@ -161,6 +180,20 @@ export function mandateRevoked({ policyId }) {
   return ev;
 }
 
+/** @returns {AgentDecommissioned} */
+export function agentDecommissioned({ agentDid, reason }) {
+  const ev = { op: 'agent-decommissioned', agentDid, reason };
+  requireFields(ev, ['agentDid']);
+  return ev;
+}
+
+/** @returns {AgentReinstated} */
+export function agentReinstated({ agentDid }) {
+  const ev = { op: 'agent-reinstated', agentDid };
+  requireFields(ev, ['agentDid']);
+  return ev;
+}
+
 /** @returns {DecisionRecorded} */
 export function decisionRecorded({ decisionId, decisionDigest, agentDid }) {
   const ev = { op: 'decision-recorded', decisionId, decisionDigest, agentDid };

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@metamynd/mmt-graph",
-  "version": "0.2.0",
+  "version": "0.3.1",
   "type": "module",
   "description": "Reference trust-graph engine (Oxigraph/SPARQL + SHACL) + HCS-anchor contract: apply mutation events, validate the MMTO §3 authority-chain invariant, batch the changelog into a Merkle root ready to anchor, and verify a disclosed tenant graph with MetaMynd fully offline. Hosting-mode-agnostic — no MetaMynd backend, no Postgres, no MetaMynd credentials anywhere in the code path. See docs/design/metamynd-trust-ontology.md Appendix C.",
   "main": "mmt-graph.engine.mjs",