{"v":"<p dir=\"auto\"><strong>Background.<\/strong> Forms V2 is the new paperwork system for client visits. Each visit type is a &#34;release&#34; (forms, placements, interview questions). From 29 Sep 2026 most of it is <strong>built by AI from the command line<\/strong>, and people check it. Item <strong>P5<\/strong> in <code>docs\/ActionItems.md<\/code> (\u00a76, tooling).<\/p>\n<h2 id=\"user-content-the-principle\" dir=\"auto\">The principle<\/h2>\n<p dir=\"auto\"><strong>Everything the AI writes is a file in the repo<\/strong>, reviewed as a diff, and the database is built from those files. This is the same approach already used for permissions (<code>code\/perms.inc.php<\/code> \u2192 <code>sync-perms.php<\/code>). It gives a history of every change and a review before it lands.<\/p>\n<h2 id=\"user-content-the-problem\" dir=\"auto\">The problem<\/h2>\n<p dir=\"auto\">There are also on-screen editors (<code>\/admin\/form-v2-maps<\/code> for placements, <code>\/admin\/form-v2-workflows<\/code> for question order). An edit made there changes the database but not the files, and the next import from the files would undo it, or the two quietly drift apart.<\/p>\n<h2 id=\"user-content-decision-needed\" dir=\"auto\">Decision needed<\/h2>\n<ul dir=\"auto\">\n<li><strong>Remove the edit screens<\/strong> (keep them read-only, or point to the Explorer), or<\/li>\n<li><strong>keep them, but export every edit back to the files<\/strong> so the files stay the truth.<\/li>\n<\/ul>\n<p dir=\"auto\">Our suggestion: make them read-only. Corrections go through a file change, which is what the AI and the review already work on.<\/p>\n"}