Skip to content

v2.2.0 — ForgeRegistry Federation and Enterprise Registries

Purpose: Defines version-level CLI, API, SDK, dashboard, schema, and compatibility obligations. Audience: product, architecture, engineering, security, operations, documentation, release, and AI coding agents Owner: ForgeRegistry Federation Maintainers Roadmap authority: docs/strategy/FORGEVENA_VERSIONED_PRODUCT_ROADMAP.md#v220--forgeregistry-federation-and-enterprise-registries Lifecycle: planned Review: before implementation and at every lifecycle promotion

Contract Rules

  • Preserve forgevena, ai-workspace, .ai-workspace/, structured envelopes, preview-first mutation, and explicit external consent.
  • Add interfaces only through versioned schemas and shared domain services.
  • Document authentication references, permissions, rate limits, pagination, errors, idempotency, cancellation, and compatibility.
  • Never place credentials or sensitive content in arguments, URLs, logs, state, diagnostics, or evidence.

Surface Impact

  • Version remote source, mirror, federation, replication, revocation, transparency, and air-gap bundle schemas.
  • Add registry add, remove, sync, mirror, verify, doctor, quarantine, and continuity operations.

Compatibility

Backward compatibility is required throughout 1.x. Later breaking changes require deprecation, migration preview, compatibility reports, rollback, and support for the final prior-major release.