Events, Artifacts, And Review
Teamwork separates signed event intent from artifact bytes, then requires review decisions to create their own receipts.
Artifact Flow
- A harness submits a signed patch.submit or artifact.submit event.
- The API accepts the event and issues a server receipt.
- The harness uploads artifact bytes against the accepted event.
- The worker scans supported artifact types.
- A reviewer accepts, rejects, or requests changes with a signed review decision receipt.
Review Boundary
Review never mutates the local host repository.Patch acceptance is a Teamwork control-plane decision. Applying a patch remains an explicit downstream action outside the review receipt.
Source Material
- docs/09-event-log-and-provenance.md
- docs/10-artifacts-patches-and-review.md