Why sell correction tasks separately from ordinary record-editing tasks?

**Is this just a record-editing dataset?**

No. An editing task asks whether a value can be changed correctly. A correction task also asks whether the current actor may make that change, whether another role must approve it and whether execution is permitted in the current state.

**What distinction should a reseller explain to customers?**

Preparing a balanced adjustment, approving its business justification and posting it are separate capabilities. A generated policy can assign these capabilities to different roles. A model that calculates the right correction can still fail by posting it using the preparer’s credentials.

**Why does this matter for training?**

Examples can teach the model to produce a proposed adjustment when posting authority is absent. That is a useful completed response, even though the underlying ledger has not changed. Training labels should distinguish this outcome from refusal or abandonment.

**How should it appear in a catalogue?**

Describe the permission decisions included and the actions customers can evaluate. Avoid a broad claim that successful completion establishes accounting competence. The task measures behaviour under its supplied authority model.