Skip to content

v2.1.0 — ForgeRegistry Protocol Foundation

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 Maintainers Roadmap authority: docs/strategy/FORGEVENA_VERSIONED_PRODUCT_ROADMAP.md#v210--forgeregistry-protocol-foundation 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

  • The canonical package is vendor-neutral.
  • OCI may transport artifacts but does not define package semantics.

Open Questions

  • Which trust roots are built in versus organization-managed?
  • How are namespace ownership disputes resolved?

Decision Expiry

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