Building a form: data model → data binding → write-only secrets

A form is three things, and the platform already has each of them. You wire them together; you build none of them. The worked example is the setup intake (Hosting.Instance/SetupIntake): a client's IT administrator, a guest with Editor on one node, answers questions and saves three secrets to the client's own Key Vault.

1. The data model — a typed content record and a NodeType

2. Data binding — the GUI on the node stream, nothing in between

3. Secrets — from the write-only section straight to Key Vault

"keyVault": "<vault>",
"keyVaultSecretPrefix": "acme-",
"operator": {
  "intakeSecrets": [ "acme-Authentication-Microsoft-ClientSecret", "acme-GitHub-App-PrivateKey", "acme-GitHub-Webhook-Secret" ],
  "intakeFrom": [ "<speaking installation's record id>" ]
}

Forbidden — each has already cost someone a day