Cropwright — Edit, Test and Activate a Config Revision

Cropwright — Edit, Test and Activate a Config Revision A workflow diagram generated by Archify. 01 / Operator 02 / Config editor 03 / OpenProcessor API Edit Try Activate Edit draft · schema-driven form · Operator › Edit Edit draft schema-driven form Pick VLM · optional, per test · Operator › Try Pick VLM optional, per test Acknowledge · external VLM only · Operator › Activate Acknowledge external VLM only Reload to apply · region profile only · Operator › Activate Reload to apply region profile only Test on a crop · draft or saved · Config editor › Try Test on a crop draft or saved Validate · issues per field · OpenProcessor API › Edit Validate issues per field Save revision · expected_revision · OpenProcessor API › Try Save revision expected_revision Activate · pin revision, report · OpenProcessor API › Activate Activate pin revision, report Workers applied · lagging flagged · OpenProcessor API › Activate Workers applied lagging flagged debounced confirm Legend User UI Agent logic Policy Context / trace

Nothing is validated in the browser

  • • Every issue shown under a field is the backend's own report
  • • Activation can be refused with a report; force is offered only when the backend says it is allowed

A conflict is not an overwrite

  • • Saves and activations carry the revision the page last read
  • • A conflict offers reload or keep-my-edits

External VLMs need a deliberate yes

  • • The acknowledgement is sent only when ticked, never as false
  • • API keys are host secrets referenced by name; the app never reads one