Skip to content

v2.3.0 — ForgeHub Discovery and Lifecycle

Purpose: Defines product intent, users, scope, non-goals, journeys, value, and measurable outcomes. Audience: product, architecture, engineering, security, operations, documentation, release, and AI coding agents Owner: ForgeHub Product Maintainers Roadmap authority: docs/strategy/FORGEVENA_VERSIONED_PRODUCT_ROADMAP.md#v230--forgehub-discovery-and-lifecycle Lifecycle: planned Review: before implementation and at every lifecycle promotion

Problem and Business Value

Deliver accessible, policy-controlled capability discovery, installation, updates, AgentSpace, collections, and lifecycle history.

This version reduces the operational and governance risk represented by its committed work while preserving local-first operation and human authority.

Personas and Journeys

  • Individual developer: previews, validates, and adopts the capability locally.
  • Platform engineer: configures policy, compatibility, and operational boundaries.
  • Security or compliance reviewer: verifies evidence without receiving secrets or source content.
  • Maintainer: publishes, supports, migrates, and retires the capability safely.

The primary journey is discover or configure, preview, validate, approve, apply, observe, update, and roll back.

Scope

  • ForgeHub Lifecycle Experience: Provide search, package details, docs, compatibility, versions, installation plans, updates, rollback, health, and history.
  • AgentSpace, Collections, and Community: Organize agents, teams, profiles, bundles, evaluations, reviews, collections, and publisher responses inside ForgeHub.

Candidates

  • None approved.

Non-Goals

  • No hidden sponsored ranking, behavioral advertising, or marketplace execution outside Core.
  • No popularity or verification signal may imply safety.

Success Metrics

  • Discovery and lifecycle journeys meet accessibility targets.
  • Installs are reproducible and ownership is precise.
  • Reviews and publisher evidence are version-scoped and moderated.