@x12i/memorix-ops-pack
v3.0.3
Published
Permanent ops/fieldstone acceptance pack: agent metadata, fixtures, ops-source, harness.
Readme
@x12i/memorix-ops-pack
Permanent ops acceptance pack for Memorix: agent metadata, fixtures, a localhost ops-source, and a harness.
This is tier-4 product vocabulary (object types, pipelines, views) on top of the platform — not an engine.
Platform gate acceptance uses fresh g12ops* (or similar) orgs with agentIds: ["ops"]. Never point acceptance at live customer orgs.
Install
npm install @x12i/[email protected]Usually you run it from the monorepo rather than depending on it from a product app.
Contents
| Path | Purpose |
|------|---------|
| metadata/ | Agent ops, child agents, abstracts, object types, relationships, views, pipelines, sources |
| fixtures/ops-source-data.json | Deterministic source payloads |
| ops-source/server.mjs | Local REST fixture (no internet) |
| scripts/harness.mjs | up / down / reset / accept |
| examples/v2/ | Golden memorix-record/2 records |
Exports: . · ./metadata/* · ./fixtures/*
Quick start
Prefer the monorepo stack (ops-source :5102, service :5100, Studio :5101, stack-status :5103):
# from repo root
node scripts/dev-stack.mjs
# opens /_live for service + ops-sourceops-source complies via @x12i/core-service (zone port, /health, /_live).
Pack-only:
npm install && npm test
node scripts/harness.mjs up # OPS_SOURCE_PORT default 5102
node scripts/harness.mjs accept # run acceptance against isolated org
node scripts/harness.mjs downHow it connects
ops-source (:5102)
→ Memory pull (credentialRef / fixture connector)
→ pipelines in metadata/
→ data + relationships
→ Studio Explore / OperateViews in this pack are also the descriptor source for data-journey coverage expected slots when metadata is installed.
