index.ts

// Copyright (c) 2025 ObjectStack. Licensed under the Apache-2.0 license.

/**
 * System Protocol Exports
 * 
 * Runtime Services & Infrastructure Configuration
 * - Infrastructure: Cache, Queue, Storage, Search, HTTP
 * - Observability: Audit, Logging, Metrics, Tracing
 * - Security: Compliance, Encryption, Masking, Auth Config
 * - Services: Job, Worker, Notification, Translation
 */

// Infrastructure Services
export * from './cache.zod';
export * from './disaster-recovery.zod';
// message-queue.zod (MessageQueueProviderSchema / TopicConfigSchema /
// ConsumerConfigSchema / DeadLetterQueueSchema / MessageQueueConfigSchema
// + every type alias) was REMOVED per ADR-0049 enforce-or-remove (#8075). The
// module declared broker-administration config for six providers — partitions,
// consumer groups, DLQs — including a required inline `sasl.password`
// credential, and no runtime ever parsed or read any of it: zero consumers
// outside this package repo-wide, no `message_queue` metadata type, and the
// connector 'message_queue' ConnectorType value never referenced these shapes.
// The consumed near-namesake is `kernel/events/integrations.zod.ts`'s
// `EventMessageQueueConfigSchema` (`EventBusConfigSchema.messageQueue`), which
// deliberately carries NO credential field — broker connection/credentials are
// deployment configuration for the runtime, not authorable metadata. Queue
// administration as authorable protocol metadata returns via the enforce route
// of ADR-0049 through a new ADR — the broker admin service first, the
// vocabulary second. See the D3 record
// `external-lookup-message-queue-families-retired`.
export * from './object-storage.zod';
export * from './search-engine.zod';
export * from './http-server.zod';
export * from './stack-server.zod';

// Observability & Operations
// audit.zod (AuditConfig/AuditStorageConfig/AuditRetentionPolicy/AuditEventFilter/
// SuspiciousActivityRule + the AuditEvent* shape schemas) was REMOVED per ADR-0056
// D8 "design+enforce or remove": the whole module had zero consumers — the LIVE
// audit path (plugin-audit) captures unconditionally via engine hooks and defines
// its own sys_audit_log row shape, and `AuditConfigSchema.enabled` contradicted
// the always-on compliance-ledger contract (object.zod `trackHistory`). The
// enforced authoring surface is object/field `trackHistory` + the object
// `lifecycle` `audit` category (retention), with per-org overrides in settings.
export * from './logging.zod';
export * from './metrics.zod';
export * from './tracing.zod';
// change-management.zod (ChangeTypeSchema / ChangePrioritySchema /
// ChangeStatusSchema / ChangeImpactSchema / RollbackPlanSchema /
// ChangeRequestSchema + every type alias) was REMOVED per ADR-0049
// enforce-or-remove (#15513, maintainer ruling 2026-09-05, ruled A). The module
// declared an ITIL change-request vocabulary — impact assessment, CAB approval,
// implementation steps, rollback plans, a `securityImpact.requiresSecurityApproval`
// gate — and no runtime ever parsed or read any of it: zero consumers outside
// this package repo-wide (examples, skills and objectui at the pinned sha
// included), no stack key, no metadata type, absent from the liveness ledgers.
// `approval.required` and `requiresSecurityApproval` read as gates the platform
// enforced, and neither ever did. The fourteen #14477 deadline-key tombstones
// the three compliance families carried leave with their defs' source; their
// `RETIRED_KEYS_BY_MAJOR[18]` entries stay as history. An approval that must
// actually gate something is a flow (ADR-0018) with an approval node; metadata
// change tracking is `sys_metadata` history and the package model (ADR-0126).
// See the D3 record `change-management-family-retired`.
export * from './migration.zod';

// Security & Compliance
export * from './auth-config.zod';
export * from './doc.zod';
export * from './book.zod';
export * from './email-config.zod';
export * from './email-template.zod';
export * from './email-template.form';
export * from './metadata-form-registry';
// compliance.zod (GDPR/HIPAA/PCI configs) and masking.zod (role-based data
// masking) were REMOVED per ADR-0056 D8 "design+enforce or remove": both were
// declared-but-never-enforced (no runtime consumer), and compliance-grade
// configuration must never merely LOOK live. FLS (plugin-security) is the
// enforced field-visibility mechanism; a masking/deny layer arrives with
// ADR-0066 ⑦/⑧ if needed. encryption.zod stays (EXPERIMENTAL — roadmap).
export * from './encryption.zod';
export * from './security-context.zod';
// incident-response.zod (IncidentSeveritySchema / IncidentCategorySchema /
// IncidentStatusSchema / IncidentResponsePhaseSchema /
// IncidentNotificationRuleSchema / IncidentNotificationMatrixSchema /
// IncidentSchema / IncidentResponsePolicySchema + every type alias) was REMOVED
// per ADR-0049 enforce-or-remove (#15513, maintainer ruling 2026-09-05, ruled
// A; not roadmapped). The module declared an ISO 27001 A.5.24–A.5.28
// incident-management vocabulary — severity grading, response phases, a
// notification matrix with `notifyRegulators`, a policy with
// `requirePostIncidentReview` — and no runtime ever parsed or read any of it:
// zero consumers outside this package repo-wide (examples, skills and objectui
// at the pinned sha included), no stack key, no metadata type, absent from the
// liveness ledgers. An author writing `notifyRegulators: true` held a
// compliance promise the platform never kept, with no error and no feedback —
// the exact declared-≠-enforced shape ADR-0049 exists for, on a compliance
// surface where "believed it notified the regulator" and "knew it did not" are
// not the same risk. Incident response as authorable protocol metadata returns
// via the enforce route of ADR-0049 through a new ADR — the engine first, the
// vocabulary second. See the D3 record `incident-response-family-retired`.
export * from './supplier-security.zod';
// training.zod (TrainingCategorySchema / TrainingCompletionStatusSchema /
// TrainingCourseSchema / TrainingRecordSchema / TrainingPlanSchema + every type
// alias) was REMOVED per ADR-0049 enforce-or-remove (#15513, same ruling). The
// module declared an ISO 27001 A.6.3 training-management vocabulary — courses
// with `mandatory`, plans with `trackCompletion` / `sendReminders`, completion
// records — and no runtime ever parsed or read any of it (same census, same
// zero). Nothing assigned a course, tracked a completion, sent a reminder or
// expired a certification. See the D3 record `training-family-retired`.

// Settings (ADR-0007: Manifest + K/V Store + Resolver)
export * from './settings-manifest.zod';
export * from './settings-client.zod';

// Runtime Services
export * from './job.zod';
export * from './worker.zod';
export * from './notification.zod';
export * from './translation.zod';
export * from './i18n-resolver';
// Localized templates for the built-in field-validation messages (#3957).
export * from './validation-message';
// Localized templates for OPERATION-level data refusals (#7307) — a write the
// engine declines as a whole, which names no field the caller supplied and so
// cannot honestly live under `validation.field.*`.
export * from './operation-message';
export * from './translation-typegen';
export * from './translation-skeleton';
export * from './collaboration.zod';
export * from './metadata-persistence.zod';
export * from './core-services.zod';

// Multi-Tenant & Licensing
export * from './tenant.zod';
export * from './license.zod';
export * from './registry-config.zod';

// Provisioning & Deployment
// './provisioning.zod' removed (#4739, v17, dual-source #4535 C16): the
// system-side tenant-provisioning family (TenantPlan / TenantRegion /
// TenantProvisioningStatus / ProvisioningStep / TenantProvisioningRequest /
// TenantProvisioningResult) was declared-only — zero implementations and zero
// importers across objectstack / cloud / objectui — and its
// `TenantPlan(Schema)` collided with the live declaration in `./cloud`. The
// living provisioning surface is the `Provision*` family in
// `@objectstack/spec/cloud` (cloud/tenant.zod.ts, cloud/environment.zod.ts),
// which the cloud services actually consume.
export * from './deploy-bundle.zod';
export * from './app-install.zod';
export * from './environment-artifact.zod';

// Constants
export * from './constants';

// `./types` (the `ObjectStackPlugin` lifecycle interface and its
// `PluginContext` / `PluginLogger` / `ObjectQLClient` / `IKernel` /
// `ObjectOSKernel` companions) was retired in #4212: it described an
// `onInstall`/`onEnable`/`onDisable` contract the kernel never implemented —
// the real plugin contract is `init`/`start`/`destroy` in
// `packages/core/src/types.ts` — and nothing in any repo imported it. It was
// seeded by the aspirational spec in issue #2 and survived as fiction.