Productify

Appearance

Launch Criteria ​

The exit criteria that must all be met before the Productify Framework drops its "Early Development" warnings and the website "early access" badge and declares itself launched.

These criteria are checked by a reviewer before the flip, not by CI. There is no automated launch gate: the ProductifyFW organisation is on the GitHub Free plan with private repositories, where branch protection and required status checks are unavailable, so no workflow result can block a merge. Making the flip mechanically gated is an open owner decision; it needs either a paid plan or a copy of the check in each repository that owns a badge file. Until then the criteria below are a convention the reviewer upholds.

The criteria ​

1. Security review passed (incl. tenant-isolation regression) ​

The tenant-isolation regression tests in the Manager must be present and passing on main. This proves the cross-tenant access vulnerabilities are fixed and guarded against silent regression.

How to check: run the Manager's test suite and confirm the tenant-isolation tests are present and passing. There is no dedicated security-regression workflow in any repository.

2. Zero open P0/P1 bugs ​

There must be no open P0 or P1 items in the bug-fixes backlog. Launch-blocking severities are tracked by issue label so the count is queryable, not a matter of opinion.

How to check:

console
$ gh issue list --label P0 --label P1 --state open

An empty result is the green state.

3. Coverage baselines met ​

Test coverage must be at or above the baselines set for each core repository. This prevents launching on a codebase whose coverage silently eroded.

How to check: run each repository's suite with coverage enabled and compare against the baseline recorded for it. No pipeline currently publishes a coverage report, so this is a manual measurement; wiring one up is an open task.

What flipping the gate unlocks ​

By project convention, only once all three criteria are met should a single pull request:

  • remove the Early Development warning from the deployment overview and the project profile README, and
  • replace the website "early access" badge with the launched state.

That flip is the final launch step, and the reviewer of that pull request is the enforcement.

See Also ​