Base annotation contract
Know what happened, when it happened, and whether it worked.
Every accepted episode carries the same coherent base record, while buyer-funded enrichment can add deeper labels when the program needs them.
- Program and task version
- Initial-state and terminal-state boundaries
- Major task phases and corrections
- Failure and rejection reasons
- Privacy and safety flags
- Reviewer decision and rework history
SuccessThe terminal condition and required phases are present.
PartialUseful work occurred, but the complete success state was not met.
FailureThe attempt ended without the required outcome.
UnsafeThe episode contains a safety-policy violation.
InvalidThe episode cannot be accepted under the program rubric.
AbortedThe contributor stopped after an interruption or declared issue.