BSE 109: FIR Resilience Framework Tool Practicum
How to read this course. BSE 109 (FIR Resilience Framework Tool Practicum) is the hands-on complement to BSE 201 (FIR Resilience Framework): the methodology is taught there and operated here. The standard does not change when the work moves into software — an assessment is still a defensible claim, and now the claim ships as artifacts a client can open. Each lesson puts one surface of the tool under your hands: orientation and the canon display, site setup and archetype, the scenario planner, the stockpile calculator, the hardening posture displays, and the document generators. The capstone puts you back in the lead assessor’s chair for the same engagement you conducted in the methodology course — this time with the tool in the loop, a client watching the screen, and every output traceable to the pinned build.
Hands-on with the tool that executes the methodology (Assessor Methodology band; hard prerequisite: the 099 -> 100 -> 101 -> 102 foundation chain and the Common Paid Core of BSE 104 and GOV 106/107/108; BSE 201 (FIR Resilience Framework) is strongly recommended before or alongside this practicum — the methodology is taught there and only operated here). The student arrives knowing what an assessment must establish and leaves able to make the FIR Resilience Framework application produce it: verify the pinned tool version before a client session, set up a community site with the right archetype, run the Time-Phased Scenario Planner as a client conversation, read the Diamond-N Stockpile Calculator without warranting self-sufficiency, interpret the hardening posture displays as data, and generate the client-facing document package from the Doc Hub with the engagement protections in place before any scored output leaves the tool. Every named view, panel, and generator in this course is pinned to the ratified oracle build; the course re-verifies its own UI vocabulary against that build at generation time.
Before generating any client-facing document from the tool for a real engagement, before emailing or otherwise releasing any generated artifact, and before representing any computed result as a finding — consult your own counsel. A generated document is not a neutral printout: the moment it leaves the tool it can create reliance, its contents are discoverable, and the representations embedded in its templates attach to the assessor who releases it. This course teaches the generation workflow and the pre-release checks as curriculum — what the generators produce, what the assessor verifies, and why the engagement protections come before any scored output leaves the tool, every time. It does not provide legal advice, it does not establish an attorney-client relationship, and no passage in it substitutes for the judgment of qualified counsel retained by the parties to a real engagement.