metrics

Product Workflow Readiness

Measures whether Forma CLI plus configured guidelines can support this repository's product knowledge workflow without recreating the old knowledge-workflow system.

Definition

This metric answers whether Forma can serve as the normal Human and Agent workflow for this repository's product knowledge work without recreating the old knowledge-workflow skill system.

Why It Matters

The product goal is not to preserve old workflow mechanics. The goal is to prove that repository Markdown, configured Forma spaces, schemas, guidelines, CLI diagnostics, and the WebApp read surface are enough to manage product R&D knowledge in a reviewable way.

Calculation

Classify the metric as:

not-ready: Forma checks fail, starter-kit validation is missing, or Agents cannot discover the expected guidance from configuration.
partially-ready: Forma checks pass and core guidance is discoverable, but pressure validation has unresolved blocking gaps.
ready: Forma checks pass, workspace health passes, pressure validation evidence exists, and remaining productization gaps are explicitly deferred to future tasks or releases.

Source

cargo run -q -p forma-cli -- config inspect --json
cargo run -q -p forma-cli -- check --json
cargo run -q -p forma-cli -- workspace health --json
test-cases/forma-starter-kit
tasks/run-starter-kit-agent-pressure-validation
experiments/starter-kit-agent-pressure-validation
planning/forma-cli-knowledge-workflow-replacement-validation

Target Or Threshold

The next internal release can proceed when this metric is ready.

Interpretation

Passing diagnostics alone is not enough. The workflow must also be understandable to Agents and Humans through configured guidelines, test cases, task records, and release validation records.

Current Judgment

Status: ready

As of 2026-07-26, the metric meets its threshold for the current Public Preview workflow:

repository config inspect, check, and workspace health pass;
starter-kit config inspect, check, workspace health, list --space tasks, and inspect --space tasks pass;
experiments/starter-kit-agent-pressure-validation records outcomes for all four contract cases and all six pressure cases;
the remaining productization gaps are explicitly deferred to reviewable write-operation work, minimal policy gates, and future validation automation.
planning/forma-release-and-delivery-ledger records the current release chain and active delivery cutline so historical release records and in-flight work remain reachable from maintained project knowledge.

This ready status does not mean Forma has cloned the old knowledge-workflow skills. It means the current project can continue product R&D using Forma configuration, guidelines, diagnostics, and review evidence while intentionally leaving nonessential old workflow mechanics behind.

Review Cadence

Review before the next internal release and after any significant change to Forma configuration, guidelines, starter-kit structure, or Agent-facing CLI behavior.

Open Questions

Should this become an executable report generated by Forma CLI?
Which pressure cases should become CI or release-gate checks, and which should remain manual product R&D review evidence?