📖Purpose

The Initiative Review Inferer infers the reviewing transition. When a plan step is marked done it re-reads the steps committed status, counts the steps in that steps phase, and if every step in the phase is done AND no initiative_reviews row exists yet for that phase it flips the initiatives status to reviewing - exactly as it ran inside the app before phase 5. It does NOT review anything itself (that is the reviewer droid sr-01); it only INFERS the reviewing flip that the Manager then reads to trigger the reviewer. Carries its own DB handle so it is self-contained.

📖Duties

- Triggered whenever a plan step is updated through the initiatives app plan-step endpoint, after the step status commit.
- Re-reads the steps committed status and only proceeds when it is done.
- Counts the phases steps and checks whether every step in the phase is done.
- Checks for an existing review row for that phase before doing anything.
- Flips the initiative to status reviewing only when the phase is fully done and no review exists yet.
- Records a session_event and a Palantir post whenever it actually flips to reviewing.

📖Constraints

- Owns and closes its own database connections; never relies on a callers connection.
- Runs AFTER the plan-step status commit (commit step first, then infer) to avoid a WAL write race.
- Behavior is preserved exactly from the app (phase 5 is a relocation, not a refactor) modulo the self-contained-connection transform and re-reading the committed step status instead of the request payload.
- Never raises; returns a structured dict and is best-effort.
- Reached only through the initiatives apps shared shim, never imported by the app directly.
- Does not review (that is sr-01); it only infers the reviewing flip. Does not touch the bypass book, cookbook, or initiative status rows beyond the reviewing flip the original logic performed.

👤Belongs to

• Elrond