Skip to content

v2.2.0 — ForgeRegistry Federation and Enterprise Registries

Purpose: Tracks decisions, assumptions, rejected alternatives, open questions, expiry, and risk ownership. 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

Required Decisions

  • Architecture and trust-boundary ADRs must be approved before implementation.
  • Every external protocol, schema, storage change, compatibility policy, and lifecycle authority requires an owner and review date.

Assumptions

  • Registries expose signed immutable metadata.
  • Regional and private deployments may impose residency constraints.

Open Questions

  • How are cross-registry namespaces reconciled?
  • What transparency guarantees apply to private registries?

Decision Expiry

Unresolved questions block affected implementation. Assumptions expire at the first release candidate unless converted into verified evidence or approved decisions.