{"v":"

Background.<\/strong> Forms V2 is the new paperwork system for client visits. Each visit type (e.g. Start of Care) is a "release" built from several pieces: form definitions, placements (where each answer prints on the PDF), the shared data pool, prefills, and the interview (questions, order, branching). From 29 Sep 2026 most of that is built by AI from the command line<\/strong>, and people check it. Item P3<\/strong> in docs\/ActionItems.md<\/code> (\u00a76, tooling).<\/p>\n

The problem<\/h2>\n

Today's tools assumed office staff would build and publish on screen:<\/p>\n

    \n
  • seed-form-v2-workflow.php<\/code> never publishes.<\/li>\n
  • form-publish.php<\/code> publishes definitions and maps but deliberately not interviews or releases<\/strong> ("the office's decision").<\/li>\n
  • The steps are separate scripts (import-forms.php<\/code>, form-overlay-propose.php<\/code>, form-attest-propose.php<\/code>, seed-form-v2-workflow.php<\/code>, form-publish.php<\/code>) with no single chain.<\/li>\n<\/ul>\n

    What to do<\/h2>\n

    One pipeline over the files in the repo: interviews (docs\/form-v2-interviews\/<\/code>), definitions (docs\/forms\/<\/code>), shared pool, placements (docs\/form-placements\/<\/code>), prefills.<\/p>\n

    import \u2192 validate \u2192 publish a new version \u2192 assemble a release \u2192 (optionally) activate<\/strong><\/p>\n

      \n
    • Dry run by default, --apply<\/code> to write.<\/li>\n
    • Idempotent: an unchanged file creates no new version.<\/li>\n
    • Same checks as the screens, and a refusal is printed, never forced.<\/li>\n
    • Missing today: publishing an interview, assembling and publishing a release, the one command that runs the chain.<\/li>\n<\/ul>\n

      Related<\/h2>\n

      P4 (#128, where a person must sign off), P5 (#129, files are the source of truth), P6 (#130, pre-publish check).<\/p>\n"}