Feature Registry

The Feature Registry tracks what exists, who can use it, and how ready it is for broader adoption. It is the source of truth for feature maturity decisions.

Registry Purpose

Use the registry when deciding whether to enable, expand, freeze, or retire a feature. It helps avoid accidental exposure of incomplete or high-risk behavior.

Maturity Model

Prototype -- exploratory, unstable, developer-only.
Beta -- functional for limited cohort, may contain known gaps.
General Availability -- production-ready with support expectations.
Deprecated -- scheduled for removal; migration required.

Feature Registry Entry

id: local_web_remote_access
title: Remote Access Tunnel
maturity: beta
availability: allowlist
owner: network-platform
lastUpdated: 2026-03-04T09:20:00+11:00
knownRisks:
  - tunnel setup drift
nextAction: validate onboarding runbook before GA

Availability Signals

Maturity alone is not enough. Also read availability constraints:

Internal -- team-only use.
Allowlist -- controlled external cohort.
Default On -- enabled for all eligible users.
Hidden/Off -- disabled pending fixes or policy updates.

Operator Actions

Registry Signal	Immediate Action	Follow-up
Prototype + rising demand	Keep access restricted	Define beta entry criteria
Beta + stable metrics	Propose cohort expansion	Run GA readiness review
GA + recurring incidents	Pause expansion	Initiate reliability hardening
Deprecated + active usage	Publish migration deadline	Track team-by-team migration

Promotion Criteria

Promote a feature only when quality signals and operational readiness both pass: clear owner, reliable behavior, support runbook, and rollback path.

Promotion is reversible

If a promoted feature regresses, downgrade its maturity and availability in the registry immediately. Keep status truthful rather than optimistic.

Releases