Next MissionRobot Kitchen · Owner IJen

Future feedback, not collection

A later pilot might ask adults whether a reply was useful. That design is shown here so the two consents stay separate. Both are off. This page does not submit anything.

Feedback consent

Would allow an optional comment about the product. It would not allow the text to be used to train a model.

Training consent

Would be a second, separate choice about using text to improve a model. It is not implied by feedback consent.

Do not send records

Do not enter a Social Security number, DD214, medical record, or disability rating. The field below cannot be typed in.

What a real pilot would need first

A secure backend, data minimization, a retention limit, and deletion plus revocation that actually exist. Independent review by veterans and qualified professionals. Separate opt-in for feedback and for training. This prototype has none of that.

There is no deletion button for stored user text, because user text is not stored and there is no submission to delete.

Two schemas, kept apart

Synthetic fixtures and a future human-feedback shape are different documents. The human shape has no records.

{
  "schema": "rk-next-mission.synthetic-persona.v1",
  "synthetic": true,
  "note": "Clearly fictional adults for scripted testing. Not real service histories and not a claim that any occupation implies a diagnosis."
}
{
  "schema": "rk-next-mission.future-human-feedback.v1",
  "collectionEnabled": false,
  "feedbackConsentEnabled": false,
  "trainingConsentEnabled": false,
  "consentsAreSeparate": true,
  "records": [],
  "deletionControlBuilt": false,
  "note": "Reserved shape only. This prototype does not collect, store, submit, or delete human feedback because no feedback is accepted."
}