/form
Build a form on MeshWeaver — a typed content record and NodeType, the GUI bound straight to the node stream, and secrets entered write-only and saved straight to Key Vault through the sealed instance-secret-write seam. Points at the files to read; the worked example is the setup intake.
- Instructions: You are asked to build a form, an intake, a settings page or anything a person fills in. **Read `Hosting.Instance/BuildingAForm` first** (`get Hosting.Instance/BuildingAForm`) and follow its three steps; do not reconstruct them from memory. 1. **Data model** — one typed content record, a property per answer, `[Description]` + `[Translation("de", …)]` on each, `[Browsable(false)]`/`[Editable(false)]` for what the viewer must not change; a NodeType with `WithContentType<T>()` and a `Tests` area. Example: `Hosting.Instance/SetupIntake/Source/SetupIntakeContent.cs`. 2. **Data binding** — `MeshNodeContentEditorControl` over the node's own path with `MeshNodeEditorField.FromType(typeof(T), locale)`, `CanEdit` from `hub.CheckPermission(path, Permission.Update)`. Read `Doc/GUI/DataBinding`, `Doc/GUI/LayoutAreas` and `/layout-area`. Never a `/data` copy, never a Save loop. 3. **Secrets** — `WriteOnlySecretSection` (core `MeshWeaver.Graph.Configuration`) with Save/Generate verbs wired to the `Hosting.Instance` seams: an administrator's write for the record's own `operator.selfServiceSecrets`, or a guest's write for a target record's `operator.intakeSecrets` from the installations in `operator.intakeFrom` (parked for an administrator's approval). The value is sealed in memory and goes to Key Vault through the governed `SetSecrets` run; it is never a property, never logged, never read back. If a control you need does not exist, say so and add it to the platform — never hand-roll HTML, CSS or a save loop.
- Auto mount: yes
- Launches sub thread: no