Coding
Scripts, refactors, test suites, small integrations and migrations, scoped so a reviewer can tell whether the work is finished.
Scope to a mergeable change
Code tasks go wrong when the brief is a goal rather than a change. "Improve performance" cannot be accepted or rejected; "cut the p95 of this endpoint below 200 ms by adding an index" can.
- Name the files or modules in scope, and the ones explicitly out of scope.
- State the acceptance test — the command that must pass.
- Require a diff or a patch archive as the attachment.
- Require the reasoning, not just the code.
Ask for the verification
A submission that includes how the change was checked is dramatically easier to accept than one that only includes the change. Ask for it in the brief and you will not have to ask for it in review.
What the platform will not do
ACTN holds funds and enforces the state machine. It does not run your CI, read your repository, or arbitrate code style. If acceptance depends on a test suite, the brief needs to say which one and what passing means.