Data Presentation

| Location | Public package | Responsibility | | --- | --- | --- | | repository root | @zixcel/projection-runtime | Execute bounded producers and publish snapshots | | packages/projection-contracts | @zixcel/projection-contracts | Validate snapshots for independent consumers | | packages/projection-client | @zixcel/projection-client | Adopt snapshots and reject stale actions | | packages/dom-renderer | @zixcel/dom-renderer | Render trusted plans with native DOM | | packages/view-server | @zixcel/view-delivery | Deliver documents/assets and report owner outcomes | | packages/view-contracts | @zixcel/view-delivery-contracts | Validate delivery and submission boundaries | | playground / examples | development only | Public API data-to-screen and refusal examples |

Existing package names and wire/schema identifiers remain unchanged. The repository is the maintenance unit; each package owns its exports, validation and release. Product SQL, identity, business policy and hosting belong to their consumers. Imported Git history, LICENSE and NOTICE are preserved.

The repository-metadata patch versions in this branch are release candidates until official registry verification. The Node packages use public registry dependencies; Rust document-output remains publish=false. CI and publication are independent of a private central checkout. OIDC publishes only the immutable reviewed archives built by the separate verification job.

Run the examples and checks

pnpm install --frozen-lockfile --ignore-scripts
pnpm -r --include-workspace-root test
pnpm test:consumer
pnpm playground:build
pnpm playground:test

Package-specific interface

@zixcel/projection-runtime

日本語

Execute explicitly registered projection producers in bounded Node.js workers and publish disposable read-only snapshots with durable fencing and exact owner leases. The runtime never chooses a latest source, loads request-supplied code or owns application authorization. Owner adapters decide visibility and retention.

Package responsibilities

| Package | Owns | Does not own | | --- | --- | --- | | projection-contracts | Validated Data/Scene snapshots, exact identities and publication fences | Product authorization, durable storage or arbitrary producer code | | projection-runtime | Registered bounded workers and private durable snapshot publication | Product meaning or source visibility decisions | | projection-client | Exact snapshot adoption and presentation state | Canonical product state or permission grants | | dom-renderer | Bounded DOM rendering and declared interactions | Remote scripts, product commands or account credentials |

The current physical names remain unchanged while their migration candidates are reviewed. Data to screen playground uses public exports and shows the stages in one runnable example. Architecture and operations explains source, distribution and rollback ownership.

Install and use

npm install @zixcel/projection-runtime

import { ProducerRegistry, ProjectionRuntime, ExactSourceReader } from '@zixcel/projection-runtime'
import { FileProjectionStore } from '@zixcel/projection-runtime/store'

const registry = new ProducerRegistry()
const producer = registry.register({ id: 'review', kind: 'data' })
// Provision this existing parent as mode 0700 before creating the store once.
const store = FileProjectionStore.create('/private/application/projections')
// adapters is a Map of owner IDs to bounded acquire/read/release/releaseHolder APIs.
const reader = new ExactSourceReader(adapters)
const runtime = new ProjectionRuntime({ store, registry, reader })
try {
  const { snapshot } = await runtime.submit({
    key: 'review', producer, sources: exactOwnerReferences,
    focus: 'selected-resources', purpose: 'review', visibilityRef: acceptedVisibility,
    limits: {}
  }, { accessRef: acceptedOwnerAccess })
  console.log(snapshot.revision)
} finally {
  await runtime.close()
}

The application supplies adapters, exactOwnerReferences, acceptedVisibility and acceptedOwnerAccess; these are explicit authorization bindings, not defaults. A producer must be registered before requests can reference its returned identity.

Boundaries and operating environment

The file store requires Linux/WSL, Node.js 22 or newer, /usr/bin/flock and /usr/bin/setpriv. It rejects non-private directories, foreign ownership, symbolic links and hard-linked state files. It runs local transaction helpers and built-in producer workers; it does not execute arbitrary owner commands. It does not provide an OS sandbox against another process running as the same user.

Store hints are wakeups, not revision authorities. Read/inspect never initializes state. Repair leases preserve exact source identity, and cancelled or timed-out work must drain before protection is released. Owner IO must honor its deadline and AbortSignal, including independently bounded lost-response cleanup.

@zixcel/projection-contracts owns wire validation and deterministic sealing; projection-client owns disposable browser adoption; dom-renderer owns presentation. This package owns execution/publication and no product-specific meaning.

Development

pnpm install --frozen-lockfile --ignore-scripts
pnpm -r --include-workspace-root typecheck
pnpm -r --include-workspace-root test
pnpm audit --audit-level=low

Production manifests use registry versions. Numeric workspace linking is only a local development convenience. See LICENSE and NOTICE.

Package ownership and scope migration

保守正本と移行条件。The maintained source and npm scope are owned by Zixcel. Current @zixcel dependencies resolve through the official npm registry. Historical @hathq releases remain provenance history; new versions are adopted only after their official artifacts are verified.

Release provenance

Current releases use GitHub Actions OIDC trusted publishing from zixcel/data-presentation (publish-npm.yml), without a stored npm publishing token. The workflow verifies reviewed archive hashes and requires npm provenance metadata. Check the published version on npm and verify registry signatures and provenance with npm audit signatures in an installed consumer project. Package runtime behavior and API contracts are unchanged by this release.

OSS responsibility and source completion defines the supported package boundary and required acceptance. It does not declare unexecuted source, distribution or production checks complete.

Dependency updates: repository policy. Registry releases: version tags and GitHub OIDC.