debrief

You can automate post-task memory analysis by running a structured debrief that enforces a five-gate rubric, performs cap checks, and generates durable developer-facing logs. This process captures actionable learnings and creates proposals to update your operational context.

A five-gate rubric for task review is a structured validation framework applied during a debrief to enforce operational governance. It evaluates completed tasks to determine if learnings qualify to update operational context and routes rationale to human reviewers.

To update operational context, the debriefing process evaluates task artifacts against a five-gate rubric. When learnings qualify, it generates proposed changes and rationale, routing them to human reviewers before archiving task history and writing human-side logs.

Yes, running a post-task debrief requires artifacts from your current task, operational context, and constitution. These inputs allow the process to perform cap checks, enforce the five-gate rubric, and produce updated governance documentation.

You should run an ad-hoc task review when you need to evaluate specific operational context outside of regular task completion. The debriefing process supports on-demand reviews, enforcing the five-gate rubric and generating human-facing documentation like update logs and consumer guides.