feat(item-bank): enforce immutable lifecycle transitions

[seonghobae]

Closed unmerged — duplicate lifecycle authority

Fresh protected-main inspection after this Draft was opened found the canonical lifecycle implementation that this branch would duplicate:

• python/fast_mlsirm/rubric/item_bank.py already owns the factory-sealed ItemBankLifecycleRecord, exact predecessor replay, explicit post-pilot state graph, cumulative evidence, approved-use preservation, and fail-closed transition_item_bank_record(...) boundary;
• docs/doctoring/governed_item_bank_lifecycle.md already documents that transition authority;
• issue Implement governed dynamic rubric and calibrated item-bank lifecycle #609's protected-main maturity note records that PR feat(rubric): govern post-pilot item-bank lifecycle #761 merged this immutable lifecycle/evidence-gate slice and explicitly says the remaining Implement governed dynamic rubric and calibrated item-bank lifecycle #609 work is semantic screening, governed pilot/artificial-crowd observations, typed calibration-evidence adapters, CAT/ATA integration, linking/release comparison, exposure/drift/quarantine, provisional-vs-calibrated parameters, buyer reporting, and later governed rubric revision.

Therefore adding a second transition state machine to python/fast_mlsirm/scoring/item_bank.py would violate #609's requirement to reuse existing rubric/lifecycle contracts rather than create a parallel schema/authority. The commits on this branch are intentionally not merged.

The branch's RED/GREEN experiments are retained only as historical diagnostic evidence. No protected-main behavior depends on them, and no predecessor-head CI/review evidence should be reused.

Next #609 work must advance one of the still-open acceptance stages against the canonical fast_mlsirm.rubric lifecycle boundary rather than duplicate lifecycle transition ownership.

[coderabbitai]

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 7f04f8a0-9e3d-4a69-8023-f18462bba884

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}