Complete assisted intake provenance UI

docs/FORMS_RUNTIME_DOMAIN_BOUNDARY.md

@@ -62,6 +62,10 @@ Runtime form submissions for validation, drafts, attachments, signatures, status
   channel, affected and represented party references, authority basis, purpose,
   notice, responsible function, language, accessibility needs, and field-level
   source/confidence provenance on the same exact Form revision used digitally
+- a responsive operator source editor that classifies each populated field
+  independently, including its confidence and optional governed declaring-party,
+  document, or source-system reference; it restores the current revision's
+  retained source map instead of flattening mixed provenance
 - append-only assisted read-back outcomes bound to the exact current Form
   revision, normalized values, attachments, and signatures; draft corrections
   invalidate earlier confirmation evidence and submission fails closed until a
@@ -157,6 +161,9 @@ The immutable outcome identifies the confirming party and operator. Corrections
 are saved as a new Form revision and require a new read-back. When confirmation
 cannot be obtained, the operator must choose that outcome and record the
 exception; policy or downstream review may still stop or escalate the case.
+Newly started assisted sessions may be saved as their first ordinary draft;
+this is required before read-back whenever the operator entered or corrected
+values, attachments, or acknowledgements.
 
 ## Approved Intake And Evidence Profiles
 

docs/INTERFACE_PATTERN_MIGRATION.md

@@ -30,4 +30,7 @@ instance revisions, validation, receipts, and handoff evidence.
 Native controls preserve keyboard order, shared dialogs manage focus, changed
 values use the global unsaved-draft guard, and bounded list/detail regions keep
 their existing responsive scrolling. English and German catalogues cover
-module-owned copy; definition content uses its own published localization.
+module-owned copy; definition content uses its own published localization. The
+assisted read-back dialog uses one responsive fieldset per populated value so
+mixed person, representative, document, system, and derived provenance remains
+legible and independently editable at desktop and mobile widths.