experiments

Starter Kit Agent Pressure Validation

Validates whether Agents can use Forma CLI and configured guidelines to manage content workflows against the starter-kit pressure cases.

Hypothesis

Agents can discover and follow the intended content workflow from Forma configuration, guidelines, test cases, and task records without hard-coded repository assumptions.

Method

Use test-cases/forma-starter-kit and tasks/run-starter-kit-agent-pressure-validation as the execution source.

Metrics

Guardrails

  • Do not require old knowledge-workflow skills.
  • Do not move private local material into shared project content without approval.
  • Do not expand the internal release scope to broad write-operation automation.

Outcome

Result: passed for the first internal validation pass.

Date: 2026-06-23

Workspace under test:

  • examples/getting-started-workspace
  • temporary write-validation copy: /private/tmp/forma-starter-kit-pressure

Contract evidence:

  • cargo run -q -p forma-cli -- --workspace examples/getting-started-workspace config inspect --json: passed with 0 errors, 0 warnings, 0 infos.
  • cargo run -q -p forma-cli -- --workspace examples/getting-started-workspace check --json: passed with 0 errors, 0 warnings, 0 infos.
  • cargo run -q -p forma-cli -- --workspace examples/getting-started-workspace workspace health --json: passed with 0 errors, 0 warnings, 0 infos.
  • cargo run -q -p forma-cli -- --workspace examples/getting-started-workspace list --space tasks --json: passed and returned blocked, todo, reviewing, ready, done, and doing examples.
  • cargo run -q -p forma-cli -- --workspace examples/getting-started-workspace inspect --space tasks add-team-notes --json: passed and returned workspace plus task guidelines.

Pressure outcomes:

Case Outcome Evidence
Starter Task Selection Pressure Passed by inspection list --space tasks exposes blocked, done, reviewing, doing, needs-refinement, and ready tasks. guidelines/task-selection.md directs selection toward unblocked work such as tasks/prepare-first-team-overview instead of blocked or done items.
Starter Blocked To Done Pressure Passed by inspection tasks/add-team-notes.md has status: blocked, readiness: blocked, and blockedBy: tasks/review-starter-workspace; the task guideline requires explicit dependency tracking.
Starter Review To Done Pressure Passed by inspection tasks/connect-related-pages.md is status: reviewing and readiness: ready; moving it to done still requires verification evidence rather than status inference.
Starter Write Verify Pressure Passed by temporary execution Added notes/review-starter-changes.md in /private/tmp/forma-starter-kit-pressure; check passed, workspace health first reported one workspaceHealth.noBacklinks warning, then passed after adding an inbound link from notes/getting-started.md.
Starter Local-Only Promotion Pressure Passed by guideline evidence .forma.md explicitly imports optional .forma/local/*.{yml,md}, .gitignore keeps .forma/local/ uncommitted, and guidelines/workspace-operations.md states ignored local files are not shared workspace knowledge.
Starter Language Variant Pressure Passed by CLI evidence list --space notes returns canonical note pages and does not list notes/getting-started.zh-hans.md or notes/welcome-to-choral-forma.zh-hans.md as primary entries.

Conclusion:

Forma CLI plus configured guidelines are sufficient for the current repository's content workflow replacement gate. The remaining gaps are future improvements, not blockers for this internal validation:

  • pressure cases are manual or inspection-based rather than automated harnesses;
  • write operations are still approved Markdown edits followed by Forma checks;
  • policy enforcement and reviewable write-operation flows remain future product work.