ee-postmortem

To capture project lessons learned from DRBFM logs and gate failures, drain the project's ee-memory and related records into a proposed-lessons queue for human review. Run this post-mortem process after a board spin, prototype completion, or project shipment.

The best way to extract BOM substitutions and fab constraints is to drain them from the project's ee-memory into a proposed-lessons queue. This process formats the candidates for review before they are entered into the ee-lessons library.

You should run a project post-mortem when a project ships, a prototype arrives, or a board spin completes. Running the extraction at these milestones captures learnings before they fade and surfaces actionable improvements.

No, the post-mortem extraction process does not automatically enter lessons into the library. It formats extracted project facts into a proposed-lessons queue and requires human review before entry into the ee-lessons library.

Yes, you can use ee-memory to surface actionable improvements from component substitutions. The process collects BOM substitutions and fab constraints from ee-memory to inform future designs and processes via a review queue.

To extract DRBFM entries and gate-fail patterns, you need the project's ee-memory, DRBFM logs, gate-fail records, and BOM substitution data. These records are drained into a review queue to surface actionable improvements.