Prism platform infrastructure

@zephytiju/[email protected] composes Component 2.1.1, Composition 1.1.0, Build 1.1.0 and resident Builder 1.1.1 through the public Platform package contract. It owns Prism workloads, configuration projections, workload identities, network policy, public routes and observability wiring. The default export is the package selected by the thin Core composition.

import prism, {
  PRISM_MERIDIAN_REQUIREMENTS,
  PRISM_RELEASES,
  prismFoundationConsumers,
  type PrismInputs,
} from "@zephytiju/prism-iac";

Install the exact package version in Core's reviewed release set. The package pins public Foundations 1.5.0, Meridian Constructs 1.6.1 and Platform Constructs 1.0.0. Core supplies PRISM_MERIDIAN_REQUIREMENTS to Foundations meridian.domains, prismFoundationConsumers(namespace) to serviceConsumers, and explicit typed PrismInputs to Prism. Foundations owns physical Engine selections, migrations, and fingerprint-verified Meridian configuration. Component and Composition require the same opaque metadata-store fingerprint. Build has its own business binding.

Every Prism service installs its declared Meridian Python dependencies from PyPI using its released hash lock. GHCR references identify the final service and worker application images. Meridian Python dependency resolution uses normal package metadata and lockfiles. The package fetches and hash-verifies released OpenAPI and provenance artifacts before registering resources.

PRISM_RELEASES and the exported ./releases, ./provider-sources and ./manifest JSON files record exact sources, owned artifact URLs, image digests and provider requirements. Logical requirements are regenerated from the verified public wheels; schema payloads remain owned by their providers. Provider-bundle, ResourceDefinition, Core SchemaDefinition and inner SchemaDocument fingerprints retain their separate meanings.

Run npm ci --ignore-scripts and npm run check for formatting, lint, types, contract and resource-graph tests, package boundary and isolated consumer checks. The CI artifact gate uses the existing JUNTAI_CI_APP_ID and JUNTAI_CI_APP_PRIVATE_KEY to read exact repository-owned release artifacts. See release gates for verification commands, configuration for inputs, and deployment and rollback for separately authorized operational work. Package publication does not apply infrastructure.