Concepts
Human review
Human review is the trust layer. Company Brain can draft and organize operational knowledge, but it does not approve policy or decide that an output is correct.
You should know what the reviewer must do before an issue pack can become usable.
Review states
- Draft: extracted item has not been reviewed yet.
- Needs Edit: reviewer sees value but requires changes before approval.
- Approved: reviewer accepts the item for inclusion in the final pack.
- Rejected: reviewer excludes the item from usable output.
Needs edit is not a dead end
Needs-edit items can be edited later. After editing, the item must be approved or rejected before finalization. Editing an approved output moves it back to Needs Edit so the reviewer re-checks it.
Finalization gate
Finalization is blocked while any item is still Draft or Needs Edit. At least one approved item is required to create the final output pack.
Reviewer responsibilities
- Verify that source-backed claims match the operational reality.
- Resolve contradictions between old docs, tickets, macros, and team memory.
- Reject unsupported or low-value drafts.
- Add review notes so future users know what changed or remains uncertain.