Approval History and Reviewer Activity
Definition
Approval history records attributable decisions about a governed artifact. Reviewer activity records observable actions such as contribution progress, edits, comments, Checkpoint decisions, or materialization. They answer different questions: history explains which decision established the current governed state, while activity explains what work occurred around it.
Neither should be inferred from a final label alone. A Policy marked approved does not reveal every preceding suggestion, and activity does not become approval merely because an expert performed it.
Fields, states, or lifecycle rules
- Approval belongs to the exact artifact or version shown by its owning surface.
- A Checkpoint decision can authorize Contribution progress or materialization without approving every related project object.
- Comments, interviews, task answers, and agent suggestions remain inputs until the owning workflow records an accepted or approved result.
- Current state and chronological activity should be read together; an older approval does not automatically govern a newer version.
- Reviewer identity, timestamps, and rationale are useful only when the product exposes them. Do not reconstruct missing history from private memory or internal logs.
- This documentation does not promise audit-log completeness, retention, export, or compliance behavior.
Related objects
Read this page with Contribution Lifecycle and Status for Contribution state, Contributed Artifacts for materialized learning, and Human Approval Boundaries for accountable decisions. Policy and Rubric detail pages remain the authority for their current governed state.
Worked example
Contribution work versus policy approval
An expert completes an interview, edits a proposed exception, and approves a Contribution Checkpoint. The Contribution activity shows that work and the Checkpoint decision. When the accepted statement materializes as a Policy, its Policy detail records the governed version and approval context. A later reader can distinguish the expert's working history from the Policy version that actually entered benchmark evidence.
Source confidence
Code-backed: Policy detail exposes approval and activity sections, while Contribution detail exposes lifecycle and Checkpoint state. These surfaces support attributable current-state interpretation, not a general compliance or audit-retention guarantee.