@x12i/memorix-metadata-runtime

Install metadata packs into Catalox-backed stores, and resolve a unified effective-metadata client for agentIds[].

Pairs with @x12i/memorix-metadata (contracts/validation). This package is the runtime that persists and serves effective definitions inside the trusted platform boundary.

Install

npm install @x12i/[email protected]

| Audience | Use this package? | |----------|-------------------| | Remote app | Prefer HTTP /api/metadata/* on memorix-service | | Platform / memorix-service | Yes — install + createMetadataClient | | Pack validation only | @x12i/memorix-metadata is enough |

Core API

import {
  createInMemoryMetadataStore,
  installMetadataPack,
  createMetadataClient,
  CANONICAL_CATALOG_BY_KIND,
  catalogIdForKind,
} from "@x12i/memorix-metadata-runtime";

| Export | Role | |--------|------| | createInMemoryMetadataStore | Dev/test store (not for prod durable metadata) | | installMetadataPack | Validate + write pack into catalogs; returns issues | | createMetadataClient | resolveEffective / getDefinition over a store | | CANONICAL_CATALOG_BY_KIND | Kind → Catalox catalog id (e.g. views → memorix-views) | | checksumMetadataPack / packFromStore | Install ledger helpers |

Quick example

import { createInMemoryMetadataStore, installMetadataPack, createMetadataClient } from "@x12i/memorix-metadata-runtime";

const store = createInMemoryMetadataStore();
await installMetadataPack(store, pack, { agentId: "opx" });

const client = createMetadataClient(store);
const effective = client.resolveEffective(["opx"]);
const view = client.getDefinition(["opx"], "views", "opx-work-items-list");

Boundaries

• Does not auto-install intelligence proposals — install is always explicit.
• Prod service wires a durable Mongo metadata store; in-memory is for dev/tests.
• Subject data stays in @x12i/memorix-data.

Docs

• documentation/metadata.md
• Ebook: Metadata, Agents, Abstracts
• Hub: https://docs.memorix.x12i.com