Implemented and validated

Milestone 002 — Metadata Core

This milestone introduced the first real metadata catalog for Metoriq and expanded the command language used to manage environments as governed platform objects.

Goal

Create the initial metadata core: tenants, protected TenantAdmin, environments, workspace profiles, models, model versions, connection metadata, and the first useful commands of the internal command language.

Delivered

  • Metadata schema for tenants, users, roles, environments, workspace profiles, models, model versions, and connections.
  • Protected TenantAdmin created with tenant provisioning.
  • External CLI commands for tenants and TenantAdmin administration.
  • Environment administration through Metoriq Command Language (MCL), using stable object keys instead of internal IDs.
  • Support for environment properties from inline JSON or JSON files.
  • Commands to create, alter, detail, generate, enable, disable, delete, and inspect dependents for environments.
  • Interactive and script-based MCL execution through connect and run.

Accessible command examples

MCL now treats an environment as a governed Metoriq object. Users refer to it by KEY, while Metoriq owns the internal identifiers, status, timestamps, and audit fields.

Properties describe the functional parts of the object and can be provided inline or through a JSON file. Technical fields stay controlled by the platform.

SHOW ENVIRONMENTS;
CREATE ENVIRONMENT KEY dev PROPERTIES JSON `{ "name": "Development" }`;
ALTER ENVIRONMENT KEY dev PROPERTIES FILE "environment.dev.json";
DETAIL ENVIRONMENT KEY dev;
GENERATE ALTER ENVIRONMENT KEY dev;
DEPENDENTS ENVIRONMENT KEY dev;
DISABLE ENVIRONMENT KEY dev;
ENABLE ENVIRONMENT KEY dev;

Important boundary

This milestone does not execute real data integrations. It creates the metadata foundation that future milestones will use for connector contracts, data movement, transformations, and flow runtime.