Carbon Reduction Scenario

Versions

• v57 # Changelog ## 0.19.0 - The reports agent is the only way the Carbon Reduction Plan is laid out; the agent's own drawn design, its proof and the saved design are gone. - Turning the plans down asks what to change -- the wording or the cover photo -- and lays all three out again. - Each plan has a cover photo from Unsplash, shared by the three versions. - Headings in the plan stay on the page of the text and tables they introduce. ## 0.18.0 - A second quick action, "Generate carbon reduction plan report": no sign-off question, every sign-off accepted, the existing scenario used when there is one. - Automatic sign-off is the default. - Three Carbon Reduction Plans, one for each version of the Scope 3 deep dive -- fixed categories, focused (95% of Scope 3) and broad (99%) -- with how they differ spelt out. - The scenario analysis is no longer pasted into the thread at the checkpoint; the plan carries it as its scenario analysis section, and it is shown in full as the run's last message. ## 0.17.0 - One question at the start: accept every sign-off in the run automatically. - The Carbon Reduction Plan is produced at the end of every run, laid out by the reports agent first; the agent's own drawn design follows only when the user turns that plan down. ## 0.16.0 - The plan is drawn as a board document, with the faults seen in real plans named. - A design the user turns down can be rendered by the reports agent instead. ## 0.15.1 - Design proofs show in the reply, the publisher's mark sits small in the footer, and a plan whose brand guidelines never name the organisation asks which name it carries. ## 0.15.0 - The Carbon Reduction Plan is designed by the agent, with charts from the chart agents. - Projections are reconciled with their own percentages, so none is shown marked for checking. - Skills are referenced by name again. ## 0.14.0 - The Carbon Reduction Plan's design is reviewed in a run of its own and revised against what the review faults, so a design that needs a second pass gets one. ## 0.13.2 - The Carbon Reduction Plan's design is drawn rather than timing out, and a design that could not be made says so plainly. ## 0.13.1 - The blueprint installs and upgrades again: CRP Plan Report no longer ships a binary file. ## 0.13.0 - The Carbon Reduction Plan's standard design, and every design drawn for it, starts from the colours in the organisation's logo. ## 0.12.0 - The Carbon Reduction Plan is made in three steps that each end with the user: approve or change the design proof, approve or edit the narrative, then receive the plan. Every figure prints to the decimal places the reporting standard sets. ## 0.11.0 - The scenario, its delivery pathways and the Carbon Reduction Plan measure the commitment from the baseline: initiatives cover the whole committed reduction from the baseline's own sources, and today's emissions are shown for reference. Scenarios already signed off are unchanged. ## 0.10.0 - The Carbon Reduction Plan is designed from the organisation's brand guidelines and saved for future plans, with a contents page, a sign-off page and richer baseline, scenario and action plan content. The user can ask for a new look. ## 0.9.0 - The organisation can now ask for its Carbon Reduction Plan once both delivery pathways are signed off: a document covering an executive summary, the baseline, the SBTi criteria and targets, the least ambitious scenario, and the action plan and initiatives, produced only on request through CRP Plan Report. ## 0.8.0 - The entry gate reads the least ambitious targets from `organization/me/targets/sbti/least-ambitious.json`; emissions reports and scenarios live under `organization/me/` in memory. ## 0.7.0 - The entry gate reads the organisation's least ambitious targets from `targets/sbti/least-ambitious.json`, and the scenario is kept in memory as one file per commitment tier under `carbon-reduction-scenarios/`. ## 0.6.0 - Each signed-off delivery pathway's steps are added to the organisation's action plan as tasks for its team, and an optional yearly agent task reports progress against the pathways. - A scope whose proposed initiatives could not be used now says so on the checkpoint, instead of reading as if none was proposed. ## 0.5.0 - After the initiatives are agreed, the blueprint builds a delivery pathway for each commitment: the organisation answers at most three questions about itself, and signs off each commitment's pathway on its own. ## 0.4.1 - The agent tells the user what their data shows, never the files, paths or fields it is kept in. The scenario approval card names the scenario analysis document rather than its file. ## 0.4.0 - The blueprint now stops once a decarbonisation scenario is agreed. CRP Select Initiatives, CRP Contextualise Initiatives and CRP Compose Report are gone; `scenario.json` and its checkpoint document are the deliverable. Turning the agreed scenario into a Carbon Reduction Plan against the organisation's own template is a separate request naming `scenario.json` as its input. ## 0.3.0 - The initiative list is now contextualised against the organisation's registry assessments before report composition. Registry assessments are optional and enrich the plan without blocking it. ## 0.2.0 - Report appearance is configurable: colour, type and page in the stylesheet, chart geometry and titles in their own settings file. ## 0.1.0 - initial release Initial release of the Carbon Reduction Plan blueprint, binding CRP Assemble Figures, CRP Select Initiatives and CRP Compose Report into one installable service. 10/8/2026
• v56 # Changelog ## 0.18.0 - A second quick action, "Generate carbon reduction plan report": no sign-off question, every sign-off accepted, the existing scenario used when there is one. - Automatic sign-off is the default. - Three Carbon Reduction Plans, one for each version of the Scope 3 deep dive -- fixed categories, focused (95% of Scope 3) and broad (99%) -- with how they differ spelt out. - The scenario analysis is no longer pasted into the thread at the checkpoint; the plan carries it as its scenario analysis section, and it is shown in full as the run's last message. ## 0.17.0 - One question at the start: accept every sign-off in the run automatically. - The Carbon Reduction Plan is produced at the end of every run, laid out by the reports agent first; the agent's own drawn design follows only when the user turns that plan down. ## 0.16.0 - The plan is drawn as a board document, with the faults seen in real plans named. - A design the user turns down can be rendered by the reports agent instead. ## 0.15.1 - Design proofs show in the reply, the publisher's mark sits small in the footer, and a plan whose brand guidelines never name the organisation asks which name it carries. ## 0.15.0 - The Carbon Reduction Plan is designed by the agent, with charts from the chart agents. - Projections are reconciled with their own percentages, so none is shown marked for checking. - Skills are referenced by name again. ## 0.14.0 - The Carbon Reduction Plan's design is reviewed in a run of its own and revised against what the review faults, so a design that needs a second pass gets one. ## 0.13.2 - The Carbon Reduction Plan's design is drawn rather than timing out, and a design that could not be made says so plainly. ## 0.13.1 - The blueprint installs and upgrades again: CRP Plan Report no longer ships a binary file. ## 0.13.0 - The Carbon Reduction Plan's standard design, and every design drawn for it, starts from the colours in the organisation's logo. ## 0.12.0 - The Carbon Reduction Plan is made in three steps that each end with the user: approve or change the design proof, approve or edit the narrative, then receive the plan. Every figure prints to the decimal places the reporting standard sets. ## 0.11.0 - The scenario, its delivery pathways and the Carbon Reduction Plan measure the commitment from the baseline: initiatives cover the whole committed reduction from the baseline's own sources, and today's emissions are shown for reference. Scenarios already signed off are unchanged. ## 0.10.0 - The Carbon Reduction Plan is designed from the organisation's brand guidelines and saved for future plans, with a contents page, a sign-off page and richer baseline, scenario and action plan content. The user can ask for a new look. ## 0.9.0 - The organisation can now ask for its Carbon Reduction Plan once both delivery pathways are signed off: a document covering an executive summary, the baseline, the SBTi criteria and targets, the least ambitious scenario, and the action plan and initiatives, produced only on request through CRP Plan Report. ## 0.8.0 - The entry gate reads the least ambitious targets from `organization/me/targets/sbti/least-ambitious.json`; emissions reports and scenarios live under `organization/me/` in memory. ## 0.7.0 - The entry gate reads the organisation's least ambitious targets from `targets/sbti/least-ambitious.json`, and the scenario is kept in memory as one file per commitment tier under `carbon-reduction-scenarios/`. ## 0.6.0 - Each signed-off delivery pathway's steps are added to the organisation's action plan as tasks for its team, and an optional yearly agent task reports progress against the pathways. - A scope whose proposed initiatives could not be used now says so on the checkpoint, instead of reading as if none was proposed. ## 0.5.0 - After the initiatives are agreed, the blueprint builds a delivery pathway for each commitment: the organisation answers at most three questions about itself, and signs off each commitment's pathway on its own. ## 0.4.1 - The agent tells the user what their data shows, never the files, paths or fields it is kept in. The scenario approval card names the scenario analysis document rather than its file. ## 0.4.0 - The blueprint now stops once a decarbonisation scenario is agreed. CRP Select Initiatives, CRP Contextualise Initiatives and CRP Compose Report are gone; `scenario.json` and its checkpoint document are the deliverable. Turning the agreed scenario into a Carbon Reduction Plan against the organisation's own template is a separate request naming `scenario.json` as its input. ## 0.3.0 - The initiative list is now contextualised against the organisation's registry assessments before report composition. Registry assessments are optional and enrich the plan without blocking it. ## 0.2.0 - Report appearance is configurable: colour, type and page in the stylesheet, chart geometry and titles in their own settings file. ## 0.1.0 - initial release Initial release of the Carbon Reduction Plan blueprint, binding CRP Assemble Figures, CRP Select Initiatives and CRP Compose Report into one installable service. 10/5/2026
• v55 # Changelog ## 0.18.0 - A second quick action, "Generate carbon reduction plan report": no sign-off question, every sign-off accepted, the existing scenario used when there is one. - Automatic sign-off is the default. - Three Carbon Reduction Plans, one for each version of the Scope 3 deep dive -- fixed categories, focused (95% of Scope 3) and broad (99%) -- with how they differ spelt out. - The scenario analysis is no longer pasted into the thread at the checkpoint; the plan carries it as its scenario analysis section, and it is shown in full as the run's last message. ## 0.17.0 - One question at the start: accept every sign-off in the run automatically. - The Carbon Reduction Plan is produced at the end of every run, laid out by the reports agent first; the agent's own drawn design follows only when the user turns that plan down. ## 0.16.0 - The plan is drawn as a board document, with the faults seen in real plans named. - A design the user turns down can be rendered by the reports agent instead. ## 0.15.1 - Design proofs show in the reply, the publisher's mark sits small in the footer, and a plan whose brand guidelines never name the organisation asks which name it carries. ## 0.15.0 - The Carbon Reduction Plan is designed by the agent, with charts from the chart agents. - Projections are reconciled with their own percentages, so none is shown marked for checking. - Skills are referenced by name again. ## 0.14.0 - The Carbon Reduction Plan's design is reviewed in a run of its own and revised against what the review faults, so a design that needs a second pass gets one. ## 0.13.2 - The Carbon Reduction Plan's design is drawn rather than timing out, and a design that could not be made says so plainly. ## 0.13.1 - The blueprint installs and upgrades again: CRP Plan Report no longer ships a binary file. ## 0.13.0 - The Carbon Reduction Plan's standard design, and every design drawn for it, starts from the colours in the organisation's logo. ## 0.12.0 - The Carbon Reduction Plan is made in three steps that each end with the user: approve or change the design proof, approve or edit the narrative, then receive the plan. Every figure prints to the decimal places the reporting standard sets. ## 0.11.0 - The scenario, its delivery pathways and the Carbon Reduction Plan measure the commitment from the baseline: initiatives cover the whole committed reduction from the baseline's own sources, and today's emissions are shown for reference. Scenarios already signed off are unchanged. ## 0.10.0 - The Carbon Reduction Plan is designed from the organisation's brand guidelines and saved for future plans, with a contents page, a sign-off page and richer baseline, scenario and action plan content. The user can ask for a new look. ## 0.9.0 - The organisation can now ask for its Carbon Reduction Plan once both delivery pathways are signed off: a document covering an executive summary, the baseline, the SBTi criteria and targets, the least ambitious scenario, and the action plan and initiatives, produced only on request through CRP Plan Report. ## 0.8.0 - The entry gate reads the least ambitious targets from `organization/me/targets/sbti/least-ambitious.json`; emissions reports and scenarios live under `organization/me/` in memory. ## 0.7.0 - The entry gate reads the organisation's least ambitious targets from `targets/sbti/least-ambitious.json`, and the scenario is kept in memory as one file per commitment tier under `carbon-reduction-scenarios/`. ## 0.6.0 - Each signed-off delivery pathway's steps are added to the organisation's action plan as tasks for its team, and an optional yearly agent task reports progress against the pathways. - A scope whose proposed initiatives could not be used now says so on the checkpoint, instead of reading as if none was proposed. ## 0.5.0 - After the initiatives are agreed, the blueprint builds a delivery pathway for each commitment: the organisation answers at most three questions about itself, and signs off each commitment's pathway on its own. ## 0.4.1 - The agent tells the user what their data shows, never the files, paths or fields it is kept in. The scenario approval card names the scenario analysis document rather than its file. ## 0.4.0 - The blueprint now stops once a decarbonisation scenario is agreed. CRP Select Initiatives, CRP Contextualise Initiatives and CRP Compose Report are gone; `scenario.json` and its checkpoint document are the deliverable. Turning the agreed scenario into a Carbon Reduction Plan against the organisation's own template is a separate request naming `scenario.json` as its input. ## 0.3.0 - The initiative list is now contextualised against the organisation's registry assessments before report composition. Registry assessments are optional and enrich the plan without blocking it. ## 0.2.0 - Report appearance is configurable: colour, type and page in the stylesheet, chart geometry and titles in their own settings file. ## 0.1.0 - initial release Initial release of the Carbon Reduction Plan blueprint, binding CRP Assemble Figures, CRP Select Initiatives and CRP Compose Report into one installable service. 10/5/2026
• v54 # Changelog ## 0.18.0 - A second quick action, "Generate carbon reduction plan report": no sign-off question, every sign-off accepted, the existing scenario used when there is one. - Automatic sign-off is the default. - Three Carbon Reduction Plans, one for each version of the Scope 3 deep dive -- fixed categories, focused (95% of Scope 3) and broad (99%) -- with how they differ spelt out. - The scenario analysis is no longer pasted into the thread at the checkpoint; the plan carries it as its scenario analysis section, and it is shown in full as the run's last message. ## 0.17.0 - One question at the start: accept every sign-off in the run automatically. - The Carbon Reduction Plan is produced at the end of every run, laid out by the reports agent first; the agent's own drawn design follows only when the user turns that plan down. ## 0.16.0 - The plan is drawn as a board document, with the faults seen in real plans named. - A design the user turns down can be rendered by the reports agent instead. ## 0.15.1 - Design proofs show in the reply, the publisher's mark sits small in the footer, and a plan whose brand guidelines never name the organisation asks which name it carries. ## 0.15.0 - The Carbon Reduction Plan is designed by the agent, with charts from the chart agents. - Projections are reconciled with their own percentages, so none is shown marked for checking. - Skills are referenced by name again. ## 0.14.0 - The Carbon Reduction Plan's design is reviewed in a run of its own and revised against what the review faults, so a design that needs a second pass gets one. ## 0.13.2 - The Carbon Reduction Plan's design is drawn rather than timing out, and a design that could not be made says so plainly. ## 0.13.1 - The blueprint installs and upgrades again: CRP Plan Report no longer ships a binary file. ## 0.13.0 - The Carbon Reduction Plan's standard design, and every design drawn for it, starts from the colours in the organisation's logo. ## 0.12.0 - The Carbon Reduction Plan is made in three steps that each end with the user: approve or change the design proof, approve or edit the narrative, then receive the plan. Every figure prints to the decimal places the reporting standard sets. ## 0.11.0 - The scenario, its delivery pathways and the Carbon Reduction Plan measure the commitment from the baseline: initiatives cover the whole committed reduction from the baseline's own sources, and today's emissions are shown for reference. Scenarios already signed off are unchanged. ## 0.10.0 - The Carbon Reduction Plan is designed from the organisation's brand guidelines and saved for future plans, with a contents page, a sign-off page and richer baseline, scenario and action plan content. The user can ask for a new look. ## 0.9.0 - The organisation can now ask for its Carbon Reduction Plan once both delivery pathways are signed off: a document covering an executive summary, the baseline, the SBTi criteria and targets, the least ambitious scenario, and the action plan and initiatives, produced only on request through CRP Plan Report. ## 0.8.0 - The entry gate reads the least ambitious targets from `organization/me/targets/sbti/least-ambitious.json`; emissions reports and scenarios live under `organization/me/` in memory. ## 0.7.0 - The entry gate reads the organisation's least ambitious targets from `targets/sbti/least-ambitious.json`, and the scenario is kept in memory as one file per commitment tier under `carbon-reduction-scenarios/`. ## 0.6.0 - Each signed-off delivery pathway's steps are added to the organisation's action plan as tasks for its team, and an optional yearly agent task reports progress against the pathways. - A scope whose proposed initiatives could not be used now says so on the checkpoint, instead of reading as if none was proposed. ## 0.5.0 - After the initiatives are agreed, the blueprint builds a delivery pathway for each commitment: the organisation answers at most three questions about itself, and signs off each commitment's pathway on its own. ## 0.4.1 - The agent tells the user what their data shows, never the files, paths or fields it is kept in. The scenario approval card names the scenario analysis document rather than its file. ## 0.4.0 - The blueprint now stops once a decarbonisation scenario is agreed. CRP Select Initiatives, CRP Contextualise Initiatives and CRP Compose Report are gone; `scenario.json` and its checkpoint document are the deliverable. Turning the agreed scenario into a Carbon Reduction Plan against the organisation's own template is a separate request naming `scenario.json` as its input. ## 0.3.0 - The initiative list is now contextualised against the organisation's registry assessments before report composition. Registry assessments are optional and enrich the plan without blocking it. ## 0.2.0 - Report appearance is configurable: colour, type and page in the stylesheet, chart geometry and titles in their own settings file. ## 0.1.0 - initial release Initial release of the Carbon Reduction Plan blueprint, binding CRP Assemble Figures, CRP Select Initiatives and CRP Compose Report into one installable service. 10/5/2026
• v53 # Changelog ## 0.18.0 - A second quick action, "Generate carbon reduction plan report": no sign-off question, every sign-off accepted, the existing scenario used when there is one. - Automatic sign-off is the default. - Three Carbon Reduction Plans, one for each version of the Scope 3 deep dive -- fixed categories, focused (95% of Scope 3) and broad (99%) -- with how they differ spelt out. - The scenario analysis is no longer pasted into the thread at the checkpoint; the plan carries it as its scenario analysis section, and it is shown in full as the run's last message. ## 0.17.0 - One question at the start: accept every sign-off in the run automatically. - The Carbon Reduction Plan is produced at the end of every run, laid out by the reports agent first; the agent's own drawn design follows only when the user turns that plan down. ## 0.16.0 - The plan is drawn as a board document, with the faults seen in real plans named. - A design the user turns down can be rendered by the reports agent instead. ## 0.15.1 - Design proofs show in the reply, the publisher's mark sits small in the footer, and a plan whose brand guidelines never name the organisation asks which name it carries. ## 0.15.0 - The Carbon Reduction Plan is designed by the agent, with charts from the chart agents. - Projections are reconciled with their own percentages, so none is shown marked for checking. - Skills are referenced by name again. ## 0.14.0 - The Carbon Reduction Plan's design is reviewed in a run of its own and revised against what the review faults, so a design that needs a second pass gets one. ## 0.13.2 - The Carbon Reduction Plan's design is drawn rather than timing out, and a design that could not be made says so plainly. ## 0.13.1 - The blueprint installs and upgrades again: CRP Plan Report no longer ships a binary file. ## 0.13.0 - The Carbon Reduction Plan's standard design, and every design drawn for it, starts from the colours in the organisation's logo. ## 0.12.0 - The Carbon Reduction Plan is made in three steps that each end with the user: approve or change the design proof, approve or edit the narrative, then receive the plan. Every figure prints to the decimal places the reporting standard sets. ## 0.11.0 - The scenario, its delivery pathways and the Carbon Reduction Plan measure the commitment from the baseline: initiatives cover the whole committed reduction from the baseline's own sources, and today's emissions are shown for reference. Scenarios already signed off are unchanged. ## 0.10.0 - The Carbon Reduction Plan is designed from the organisation's brand guidelines and saved for future plans, with a contents page, a sign-off page and richer baseline, scenario and action plan content. The user can ask for a new look. ## 0.9.0 - The organisation can now ask for its Carbon Reduction Plan once both delivery pathways are signed off: a document covering an executive summary, the baseline, the SBTi criteria and targets, the least ambitious scenario, and the action plan and initiatives, produced only on request through CRP Plan Report. ## 0.8.0 - The entry gate reads the least ambitious targets from `organization/me/targets/sbti/least-ambitious.json`; emissions reports and scenarios live under `organization/me/` in memory. ## 0.7.0 - The entry gate reads the organisation's least ambitious targets from `targets/sbti/least-ambitious.json`, and the scenario is kept in memory as one file per commitment tier under `carbon-reduction-scenarios/`. ## 0.6.0 - Each signed-off delivery pathway's steps are added to the organisation's action plan as tasks for its team, and an optional yearly agent task reports progress against the pathways. - A scope whose proposed initiatives could not be used now says so on the checkpoint, instead of reading as if none was proposed. ## 0.5.0 - After the initiatives are agreed, the blueprint builds a delivery pathway for each commitment: the organisation answers at most three questions about itself, and signs off each commitment's pathway on its own. ## 0.4.1 - The agent tells the user what their data shows, never the files, paths or fields it is kept in. The scenario approval card names the scenario analysis document rather than its file. ## 0.4.0 - The blueprint now stops once a decarbonisation scenario is agreed. CRP Select Initiatives, CRP Contextualise Initiatives and CRP Compose Report are gone; `scenario.json` and its checkpoint document are the deliverable. Turning the agreed scenario into a Carbon Reduction Plan against the organisation's own template is a separate request naming `scenario.json` as its input. ## 0.3.0 - The initiative list is now contextualised against the organisation's registry assessments before report composition. Registry assessments are optional and enrich the plan without blocking it. ## 0.2.0 - Report appearance is configurable: colour, type and page in the stylesheet, chart geometry and titles in their own settings file. ## 0.1.0 - initial release Initial release of the Carbon Reduction Plan blueprint, binding CRP Assemble Figures, CRP Select Initiatives and CRP Compose Report into one installable service. 10/4/2026
• v52 # Changelog ## 0.18.0 - A second quick action, "Generate carbon reduction plan report": no sign-off question, every sign-off accepted, the existing scenario used when there is one. - Automatic sign-off is the default. - Three Carbon Reduction Plans, one for each version of the Scope 3 deep dive -- fixed categories, focused (95% of Scope 3) and broad (99%) -- with how they differ spelt out. - The scenario analysis is no longer pasted into the thread at the checkpoint; the plan carries it as its scenario analysis section, and it is shown in full as the run's last message. ## 0.17.0 - One question at the start: accept every sign-off in the run automatically. - The Carbon Reduction Plan is produced at the end of every run, laid out by the reports agent first; the agent's own drawn design follows only when the user turns that plan down. ## 0.16.0 - The plan is drawn as a board document, with the faults seen in real plans named. - A design the user turns down can be rendered by the reports agent instead. ## 0.15.1 - Design proofs show in the reply, the publisher's mark sits small in the footer, and a plan whose brand guidelines never name the organisation asks which name it carries. ## 0.15.0 - The Carbon Reduction Plan is designed by the agent, with charts from the chart agents. - Projections are reconciled with their own percentages, so none is shown marked for checking. - Skills are referenced by name again. ## 0.14.0 - The Carbon Reduction Plan's design is reviewed in a run of its own and revised against what the review faults, so a design that needs a second pass gets one. ## 0.13.2 - The Carbon Reduction Plan's design is drawn rather than timing out, and a design that could not be made says so plainly. ## 0.13.1 - The blueprint installs and upgrades again: CRP Plan Report no longer ships a binary file. ## 0.13.0 - The Carbon Reduction Plan's standard design, and every design drawn for it, starts from the colours in the organisation's logo. ## 0.12.0 - The Carbon Reduction Plan is made in three steps that each end with the user: approve or change the design proof, approve or edit the narrative, then receive the plan. Every figure prints to the decimal places the reporting standard sets. ## 0.11.0 - The scenario, its delivery pathways and the Carbon Reduction Plan measure the commitment from the baseline: initiatives cover the whole committed reduction from the baseline's own sources, and today's emissions are shown for reference. Scenarios already signed off are unchanged. ## 0.10.0 - The Carbon Reduction Plan is designed from the organisation's brand guidelines and saved for future plans, with a contents page, a sign-off page and richer baseline, scenario and action plan content. The user can ask for a new look. ## 0.9.0 - The organisation can now ask for its Carbon Reduction Plan once both delivery pathways are signed off: a document covering an executive summary, the baseline, the SBTi criteria and targets, the least ambitious scenario, and the action plan and initiatives, produced only on request through CRP Plan Report. ## 0.8.0 - The entry gate reads the least ambitious targets from `organization/me/targets/sbti/least-ambitious.json`; emissions reports and scenarios live under `organization/me/` in memory. ## 0.7.0 - The entry gate reads the organisation's least ambitious targets from `targets/sbti/least-ambitious.json`, and the scenario is kept in memory as one file per commitment tier under `carbon-reduction-scenarios/`. ## 0.6.0 - Each signed-off delivery pathway's steps are added to the organisation's action plan as tasks for its team, and an optional yearly agent task reports progress against the pathways. - A scope whose proposed initiatives could not be used now says so on the checkpoint, instead of reading as if none was proposed. ## 0.5.0 - After the initiatives are agreed, the blueprint builds a delivery pathway for each commitment: the organisation answers at most three questions about itself, and signs off each commitment's pathway on its own. ## 0.4.1 - The agent tells the user what their data shows, never the files, paths or fields it is kept in. The scenario approval card names the scenario analysis document rather than its file. ## 0.4.0 - The blueprint now stops once a decarbonisation scenario is agreed. CRP Select Initiatives, CRP Contextualise Initiatives and CRP Compose Report are gone; `scenario.json` and its checkpoint document are the deliverable. Turning the agreed scenario into a Carbon Reduction Plan against the organisation's own template is a separate request naming `scenario.json` as its input. ## 0.3.0 - The initiative list is now contextualised against the organisation's registry assessments before report composition. Registry assessments are optional and enrich the plan without blocking it. ## 0.2.0 - Report appearance is configurable: colour, type and page in the stylesheet, chart geometry and titles in their own settings file. ## 0.1.0 - initial release Initial release of the Carbon Reduction Plan blueprint, binding CRP Assemble Figures, CRP Select Initiatives and CRP Compose Report into one installable service. 10/2/2026
• v51 # Changelog ## 0.18.0 - A second quick action, "Generate carbon reduction plan report": no sign-off question, every sign-off accepted, the existing scenario used when there is one. - Automatic sign-off is the default. - Three Carbon Reduction Plans, one for each version of the Scope 3 deep dive -- fixed categories, focused (95% of Scope 3) and broad (99%) -- with how they differ spelt out. - The scenario analysis is no longer pasted into the thread at the checkpoint; the plan carries it as its scenario analysis section, and it is shown in full as the run's last message. ## 0.17.0 - One question at the start: accept every sign-off in the run automatically. - The Carbon Reduction Plan is produced at the end of every run, laid out by the reports agent first; the agent's own drawn design follows only when the user turns that plan down. ## 0.16.0 - The plan is drawn as a board document, with the faults seen in real plans named. - A design the user turns down can be rendered by the reports agent instead. ## 0.15.1 - Design proofs show in the reply, the publisher's mark sits small in the footer, and a plan whose brand guidelines never name the organisation asks which name it carries. ## 0.15.0 - The Carbon Reduction Plan is designed by the agent, with charts from the chart agents. - Projections are reconciled with their own percentages, so none is shown marked for checking. - Skills are referenced by name again. ## 0.14.0 - The Carbon Reduction Plan's design is reviewed in a run of its own and revised against what the review faults, so a design that needs a second pass gets one. ## 0.13.2 - The Carbon Reduction Plan's design is drawn rather than timing out, and a design that could not be made says so plainly. ## 0.13.1 - The blueprint installs and upgrades again: CRP Plan Report no longer ships a binary file. ## 0.13.0 - The Carbon Reduction Plan's standard design, and every design drawn for it, starts from the colours in the organisation's logo. ## 0.12.0 - The Carbon Reduction Plan is made in three steps that each end with the user: approve or change the design proof, approve or edit the narrative, then receive the plan. Every figure prints to the decimal places the reporting standard sets. ## 0.11.0 - The scenario, its delivery pathways and the Carbon Reduction Plan measure the commitment from the baseline: initiatives cover the whole committed reduction from the baseline's own sources, and today's emissions are shown for reference. Scenarios already signed off are unchanged. ## 0.10.0 - The Carbon Reduction Plan is designed from the organisation's brand guidelines and saved for future plans, with a contents page, a sign-off page and richer baseline, scenario and action plan content. The user can ask for a new look. ## 0.9.0 - The organisation can now ask for its Carbon Reduction Plan once both delivery pathways are signed off: a document covering an executive summary, the baseline, the SBTi criteria and targets, the least ambitious scenario, and the action plan and initiatives, produced only on request through CRP Plan Report. ## 0.8.0 - The entry gate reads the least ambitious targets from `organization/me/targets/sbti/least-ambitious.json`; emissions reports and scenarios live under `organization/me/` in memory. ## 0.7.0 - The entry gate reads the organisation's least ambitious targets from `targets/sbti/least-ambitious.json`, and the scenario is kept in memory as one file per commitment tier under `carbon-reduction-scenarios/`. ## 0.6.0 - Each signed-off delivery pathway's steps are added to the organisation's action plan as tasks for its team, and an optional yearly agent task reports progress against the pathways. - A scope whose proposed initiatives could not be used now says so on the checkpoint, instead of reading as if none was proposed. ## 0.5.0 - After the initiatives are agreed, the blueprint builds a delivery pathway for each commitment: the organisation answers at most three questions about itself, and signs off each commitment's pathway on its own. ## 0.4.1 - The agent tells the user what their data shows, never the files, paths or fields it is kept in. The scenario approval card names the scenario analysis document rather than its file. ## 0.4.0 - The blueprint now stops once a decarbonisation scenario is agreed. CRP Select Initiatives, CRP Contextualise Initiatives and CRP Compose Report are gone; `scenario.json` and its checkpoint document are the deliverable. Turning the agreed scenario into a Carbon Reduction Plan against the organisation's own template is a separate request naming `scenario.json` as its input. ## 0.3.0 - The initiative list is now contextualised against the organisation's registry assessments before report composition. Registry assessments are optional and enrich the plan without blocking it. ## 0.2.0 - Report appearance is configurable: colour, type and page in the stylesheet, chart geometry and titles in their own settings file. ## 0.1.0 - initial release Initial release of the Carbon Reduction Plan blueprint, binding CRP Assemble Figures, CRP Select Initiatives and CRP Compose Report into one installable service. 10/2/2026
• v50 # Changelog ## 0.18.0 - A second quick action, "Generate carbon reduction plan report": no sign-off question, every sign-off accepted, the existing scenario used when there is one. - Automatic sign-off is the default. - Three Carbon Reduction Plans, one for each version of the Scope 3 deep dive -- fixed categories, focused (95% of Scope 3) and broad (99%) -- with how they differ spelt out. - The scenario analysis is no longer pasted into the thread at the checkpoint; the plan carries it as its scenario analysis section, and it is shown in full as the run's last message. ## 0.17.0 - One question at the start: accept every sign-off in the run automatically. - The Carbon Reduction Plan is produced at the end of every run, laid out by the reports agent first; the agent's own drawn design follows only when the user turns that plan down. ## 0.16.0 - The plan is drawn as a board document, with the faults seen in real plans named. - A design the user turns down can be rendered by the reports agent instead. ## 0.15.1 - Design proofs show in the reply, the publisher's mark sits small in the footer, and a plan whose brand guidelines never name the organisation asks which name it carries. ## 0.15.0 - The Carbon Reduction Plan is designed by the agent, with charts from the chart agents. - Projections are reconciled with their own percentages, so none is shown marked for checking. - Skills are referenced by name again. ## 0.14.0 - The Carbon Reduction Plan's design is reviewed in a run of its own and revised against what the review faults, so a design that needs a second pass gets one. ## 0.13.2 - The Carbon Reduction Plan's design is drawn rather than timing out, and a design that could not be made says so plainly. ## 0.13.1 - The blueprint installs and upgrades again: CRP Plan Report no longer ships a binary file. ## 0.13.0 - The Carbon Reduction Plan's standard design, and every design drawn for it, starts from the colours in the organisation's logo. ## 0.12.0 - The Carbon Reduction Plan is made in three steps that each end with the user: approve or change the design proof, approve or edit the narrative, then receive the plan. Every figure prints to the decimal places the reporting standard sets. ## 0.11.0 - The scenario, its delivery pathways and the Carbon Reduction Plan measure the commitment from the baseline: initiatives cover the whole committed reduction from the baseline's own sources, and today's emissions are shown for reference. Scenarios already signed off are unchanged. ## 0.10.0 - The Carbon Reduction Plan is designed from the organisation's brand guidelines and saved for future plans, with a contents page, a sign-off page and richer baseline, scenario and action plan content. The user can ask for a new look. ## 0.9.0 - The organisation can now ask for its Carbon Reduction Plan once both delivery pathways are signed off: a document covering an executive summary, the baseline, the SBTi criteria and targets, the least ambitious scenario, and the action plan and initiatives, produced only on request through CRP Plan Report. ## 0.8.0 - The entry gate reads the least ambitious targets from `organization/me/targets/sbti/least-ambitious.json`; emissions reports and scenarios live under `organization/me/` in memory. ## 0.7.0 - The entry gate reads the organisation's least ambitious targets from `targets/sbti/least-ambitious.json`, and the scenario is kept in memory as one file per commitment tier under `carbon-reduction-scenarios/`. ## 0.6.0 - Each signed-off delivery pathway's steps are added to the organisation's action plan as tasks for its team, and an optional yearly agent task reports progress against the pathways. - A scope whose proposed initiatives could not be used now says so on the checkpoint, instead of reading as if none was proposed. ## 0.5.0 - After the initiatives are agreed, the blueprint builds a delivery pathway for each commitment: the organisation answers at most three questions about itself, and signs off each commitment's pathway on its own. ## 0.4.1 - The agent tells the user what their data shows, never the files, paths or fields it is kept in. The scenario approval card names the scenario analysis document rather than its file. ## 0.4.0 - The blueprint now stops once a decarbonisation scenario is agreed. CRP Select Initiatives, CRP Contextualise Initiatives and CRP Compose Report are gone; `scenario.json` and its checkpoint document are the deliverable. Turning the agreed scenario into a Carbon Reduction Plan against the organisation's own template is a separate request naming `scenario.json` as its input. ## 0.3.0 - The initiative list is now contextualised against the organisation's registry assessments before report composition. Registry assessments are optional and enrich the plan without blocking it. ## 0.2.0 - Report appearance is configurable: colour, type and page in the stylesheet, chart geometry and titles in their own settings file. ## 0.1.0 - initial release Initial release of the Carbon Reduction Plan blueprint, binding CRP Assemble Figures, CRP Select Initiatives and CRP Compose Report into one installable service. 10/2/2026
• v49 # Changelog ## 0.18.0 - A second quick action, "Generate carbon reduction plan report": no sign-off question, every sign-off accepted, the existing scenario used when there is one. - Automatic sign-off is the default. - Three Carbon Reduction Plans, one for each version of the Scope 3 deep dive -- fixed categories, focused (95% of Scope 3) and broad (99%) -- with how they differ spelt out. - The scenario analysis is no longer pasted into the thread at the checkpoint; the plan carries it as its scenario analysis section, and it is shown in full as the run's last message. ## 0.17.0 - One question at the start: accept every sign-off in the run automatically. - The Carbon Reduction Plan is produced at the end of every run, laid out by the reports agent first; the agent's own drawn design follows only when the user turns that plan down. ## 0.16.0 - The plan is drawn as a board document, with the faults seen in real plans named. - A design the user turns down can be rendered by the reports agent instead. ## 0.15.1 - Design proofs show in the reply, the publisher's mark sits small in the footer, and a plan whose brand guidelines never name the organisation asks which name it carries. ## 0.15.0 - The Carbon Reduction Plan is designed by the agent, with charts from the chart agents. - Projections are reconciled with their own percentages, so none is shown marked for checking. - Skills are referenced by name again. ## 0.14.0 - The Carbon Reduction Plan's design is reviewed in a run of its own and revised against what the review faults, so a design that needs a second pass gets one. ## 0.13.2 - The Carbon Reduction Plan's design is drawn rather than timing out, and a design that could not be made says so plainly. ## 0.13.1 - The blueprint installs and upgrades again: CRP Plan Report no longer ships a binary file. ## 0.13.0 - The Carbon Reduction Plan's standard design, and every design drawn for it, starts from the colours in the organisation's logo. ## 0.12.0 - The Carbon Reduction Plan is made in three steps that each end with the user: approve or change the design proof, approve or edit the narrative, then receive the plan. Every figure prints to the decimal places the reporting standard sets. ## 0.11.0 - The scenario, its delivery pathways and the Carbon Reduction Plan measure the commitment from the baseline: initiatives cover the whole committed reduction from the baseline's own sources, and today's emissions are shown for reference. Scenarios already signed off are unchanged. ## 0.10.0 - The Carbon Reduction Plan is designed from the organisation's brand guidelines and saved for future plans, with a contents page, a sign-off page and richer baseline, scenario and action plan content. The user can ask for a new look. ## 0.9.0 - The organisation can now ask for its Carbon Reduction Plan once both delivery pathways are signed off: a document covering an executive summary, the baseline, the SBTi criteria and targets, the least ambitious scenario, and the action plan and initiatives, produced only on request through CRP Plan Report. ## 0.8.0 - The entry gate reads the least ambitious targets from `organization/me/targets/sbti/least-ambitious.json`; emissions reports and scenarios live under `organization/me/` in memory. ## 0.7.0 - The entry gate reads the organisation's least ambitious targets from `targets/sbti/least-ambitious.json`, and the scenario is kept in memory as one file per commitment tier under `carbon-reduction-scenarios/`. ## 0.6.0 - Each signed-off delivery pathway's steps are added to the organisation's action plan as tasks for its team, and an optional yearly agent task reports progress against the pathways. - A scope whose proposed initiatives could not be used now says so on the checkpoint, instead of reading as if none was proposed. ## 0.5.0 - After the initiatives are agreed, the blueprint builds a delivery pathway for each commitment: the organisation answers at most three questions about itself, and signs off each commitment's pathway on its own. ## 0.4.1 - The agent tells the user what their data shows, never the files, paths or fields it is kept in. The scenario approval card names the scenario analysis document rather than its file. ## 0.4.0 - The blueprint now stops once a decarbonisation scenario is agreed. CRP Select Initiatives, CRP Contextualise Initiatives and CRP Compose Report are gone; `scenario.json` and its checkpoint document are the deliverable. Turning the agreed scenario into a Carbon Reduction Plan against the organisation's own template is a separate request naming `scenario.json` as its input. ## 0.3.0 - The initiative list is now contextualised against the organisation's registry assessments before report composition. Registry assessments are optional and enrich the plan without blocking it. ## 0.2.0 - Report appearance is configurable: colour, type and page in the stylesheet, chart geometry and titles in their own settings file. ## 0.1.0 - initial release Initial release of the Carbon Reduction Plan blueprint, binding CRP Assemble Figures, CRP Select Initiatives and CRP Compose Report into one installable service. 10/1/2026
• v48 # Changelog ## 0.18.0 - A second quick action, "Generate carbon reduction plan report": no sign-off question, every sign-off accepted, the existing scenario used when there is one. - Automatic sign-off is the default. - Three Carbon Reduction Plans, one for each version of the Scope 3 deep dive -- fixed categories, focused (95% of Scope 3) and broad (99%) -- with how they differ spelt out. - The scenario analysis is no longer pasted into the thread at the checkpoint; the plan carries it as its scenario analysis section, and it is shown in full as the run's last message. ## 0.17.0 - One question at the start: accept every sign-off in the run automatically. - The Carbon Reduction Plan is produced at the end of every run, laid out by the reports agent first; the agent's own drawn design follows only when the user turns that plan down. ## 0.16.0 - The plan is drawn as a board document, with the faults seen in real plans named. - A design the user turns down can be rendered by the reports agent instead. ## 0.15.1 - Design proofs show in the reply, the publisher's mark sits small in the footer, and a plan whose brand guidelines never name the organisation asks which name it carries. ## 0.15.0 - The Carbon Reduction Plan is designed by the agent, with charts from the chart agents. - Projections are reconciled with their own percentages, so none is shown marked for checking. - Skills are referenced by name again. ## 0.14.0 - The Carbon Reduction Plan's design is reviewed in a run of its own and revised against what the review faults, so a design that needs a second pass gets one. ## 0.13.2 - The Carbon Reduction Plan's design is drawn rather than timing out, and a design that could not be made says so plainly. ## 0.13.1 - The blueprint installs and upgrades again: CRP Plan Report no longer ships a binary file. ## 0.13.0 - The Carbon Reduction Plan's standard design, and every design drawn for it, starts from the colours in the organisation's logo. ## 0.12.0 - The Carbon Reduction Plan is made in three steps that each end with the user: approve or change the design proof, approve or edit the narrative, then receive the plan. Every figure prints to the decimal places the reporting standard sets. ## 0.11.0 - The scenario, its delivery pathways and the Carbon Reduction Plan measure the commitment from the baseline: initiatives cover the whole committed reduction from the baseline's own sources, and today's emissions are shown for reference. Scenarios already signed off are unchanged. ## 0.10.0 - The Carbon Reduction Plan is designed from the organisation's brand guidelines and saved for future plans, with a contents page, a sign-off page and richer baseline, scenario and action plan content. The user can ask for a new look. ## 0.9.0 - The organisation can now ask for its Carbon Reduction Plan once both delivery pathways are signed off: a document covering an executive summary, the baseline, the SBTi criteria and targets, the least ambitious scenario, and the action plan and initiatives, produced only on request through CRP Plan Report. ## 0.8.0 - The entry gate reads the least ambitious targets from `organization/me/targets/sbti/least-ambitious.json`; emissions reports and scenarios live under `organization/me/` in memory. ## 0.7.0 - The entry gate reads the organisation's least ambitious targets from `targets/sbti/least-ambitious.json`, and the scenario is kept in memory as one file per commitment tier under `carbon-reduction-scenarios/`. ## 0.6.0 - Each signed-off delivery pathway's steps are added to the organisation's action plan as tasks for its team, and an optional yearly agent task reports progress against the pathways. - A scope whose proposed initiatives could not be used now says so on the checkpoint, instead of reading as if none was proposed. ## 0.5.0 - After the initiatives are agreed, the blueprint builds a delivery pathway for each commitment: the organisation answers at most three questions about itself, and signs off each commitment's pathway on its own. ## 0.4.1 - The agent tells the user what their data shows, never the files, paths or fields it is kept in. The scenario approval card names the scenario analysis document rather than its file. ## 0.4.0 - The blueprint now stops once a decarbonisation scenario is agreed. CRP Select Initiatives, CRP Contextualise Initiatives and CRP Compose Report are gone; `scenario.json` and its checkpoint document are the deliverable. Turning the agreed scenario into a Carbon Reduction Plan against the organisation's own template is a separate request naming `scenario.json` as its input. ## 0.3.0 - The initiative list is now contextualised against the organisation's registry assessments before report composition. Registry assessments are optional and enrich the plan without blocking it. ## 0.2.0 - Report appearance is configurable: colour, type and page in the stylesheet, chart geometry and titles in their own settings file. ## 0.1.0 - initial release Initial release of the Carbon Reduction Plan blueprint, binding CRP Assemble Figures, CRP Select Initiatives and CRP Compose Report into one installable service. 9/29/2026
• v47 # Changelog ## 0.18.0 - A second quick action, "Generate carbon reduction plan report": no sign-off question, every sign-off accepted, the existing scenario used when there is one. - Automatic sign-off is the default. - Three Carbon Reduction Plans, one for each version of the Scope 3 deep dive -- fixed categories, focused (95% of Scope 3) and broad (99%) -- with how they differ spelt out. - The scenario analysis is no longer pasted into the thread at the checkpoint; the plan carries it as its scenario analysis section, and it is shown in full as the run's last message. ## 0.17.0 - One question at the start: accept every sign-off in the run automatically. - The Carbon Reduction Plan is produced at the end of every run, laid out by the reports agent first; the agent's own drawn design follows only when the user turns that plan down. ## 0.16.0 - The plan is drawn as a board document, with the faults seen in real plans named. - A design the user turns down can be rendered by the reports agent instead. ## 0.15.1 - Design proofs show in the reply, the publisher's mark sits small in the footer, and a plan whose brand guidelines never name the organisation asks which name it carries. ## 0.15.0 - The Carbon Reduction Plan is designed by the agent, with charts from the chart agents. - Projections are reconciled with their own percentages, so none is shown marked for checking. - Skills are referenced by name again. ## 0.14.0 - The Carbon Reduction Plan's design is reviewed in a run of its own and revised against what the review faults, so a design that needs a second pass gets one. ## 0.13.2 - The Carbon Reduction Plan's design is drawn rather than timing out, and a design that could not be made says so plainly. ## 0.13.1 - The blueprint installs and upgrades again: CRP Plan Report no longer ships a binary file. ## 0.13.0 - The Carbon Reduction Plan's standard design, and every design drawn for it, starts from the colours in the organisation's logo. ## 0.12.0 - The Carbon Reduction Plan is made in three steps that each end with the user: approve or change the design proof, approve or edit the narrative, then receive the plan. Every figure prints to the decimal places the reporting standard sets. ## 0.11.0 - The scenario, its delivery pathways and the Carbon Reduction Plan measure the commitment from the baseline: initiatives cover the whole committed reduction from the baseline's own sources, and today's emissions are shown for reference. Scenarios already signed off are unchanged. ## 0.10.0 - The Carbon Reduction Plan is designed from the organisation's brand guidelines and saved for future plans, with a contents page, a sign-off page and richer baseline, scenario and action plan content. The user can ask for a new look. ## 0.9.0 - The organisation can now ask for its Carbon Reduction Plan once both delivery pathways are signed off: a document covering an executive summary, the baseline, the SBTi criteria and targets, the least ambitious scenario, and the action plan and initiatives, produced only on request through CRP Plan Report. ## 0.8.0 - The entry gate reads the least ambitious targets from `organization/me/targets/sbti/least-ambitious.json`; emissions reports and scenarios live under `organization/me/` in memory. ## 0.7.0 - The entry gate reads the organisation's least ambitious targets from `targets/sbti/least-ambitious.json`, and the scenario is kept in memory as one file per commitment tier under `carbon-reduction-scenarios/`. ## 0.6.0 - Each signed-off delivery pathway's steps are added to the organisation's action plan as tasks for its team, and an optional yearly agent task reports progress against the pathways. - A scope whose proposed initiatives could not be used now says so on the checkpoint, instead of reading as if none was proposed. ## 0.5.0 - After the initiatives are agreed, the blueprint builds a delivery pathway for each commitment: the organisation answers at most three questions about itself, and signs off each commitment's pathway on its own. ## 0.4.1 - The agent tells the user what their data shows, never the files, paths or fields it is kept in. The scenario approval card names the scenario analysis document rather than its file. ## 0.4.0 - The blueprint now stops once a decarbonisation scenario is agreed. CRP Select Initiatives, CRP Contextualise Initiatives and CRP Compose Report are gone; `scenario.json` and its checkpoint document are the deliverable. Turning the agreed scenario into a Carbon Reduction Plan against the organisation's own template is a separate request naming `scenario.json` as its input. ## 0.3.0 - The initiative list is now contextualised against the organisation's registry assessments before report composition. Registry assessments are optional and enrich the plan without blocking it. ## 0.2.0 - Report appearance is configurable: colour, type and page in the stylesheet, chart geometry and titles in their own settings file. ## 0.1.0 - initial release Initial release of the Carbon Reduction Plan blueprint, binding CRP Assemble Figures, CRP Select Initiatives and CRP Compose Report into one installable service. 9/29/2026
• v46 # Changelog ## 0.18.0 - A second quick action, "Generate carbon reduction plan report": no sign-off question, every sign-off accepted, the existing scenario used when there is one. - Automatic sign-off is the default. - Three Carbon Reduction Plans, one for each version of the Scope 3 deep dive -- fixed categories, focused (95% of Scope 3) and broad (99%) -- with how they differ spelt out. - The scenario analysis is no longer pasted into the thread at the checkpoint; the plan carries it as its scenario analysis section, and it is shown in full as the run's last message. ## 0.17.0 - One question at the start: accept every sign-off in the run automatically. - The Carbon Reduction Plan is produced at the end of every run, laid out by the reports agent first; the agent's own drawn design follows only when the user turns that plan down. ## 0.16.0 - The plan is drawn as a board document, with the faults seen in real plans named. - A design the user turns down can be rendered by the reports agent instead. ## 0.15.1 - Design proofs show in the reply, the publisher's mark sits small in the footer, and a plan whose brand guidelines never name the organisation asks which name it carries. ## 0.15.0 - The Carbon Reduction Plan is designed by the agent, with charts from the chart agents. - Projections are reconciled with their own percentages, so none is shown marked for checking. - Skills are referenced by name again. ## 0.14.0 - The Carbon Reduction Plan's design is reviewed in a run of its own and revised against what the review faults, so a design that needs a second pass gets one. ## 0.13.2 - The Carbon Reduction Plan's design is drawn rather than timing out, and a design that could not be made says so plainly. ## 0.13.1 - The blueprint installs and upgrades again: CRP Plan Report no longer ships a binary file. ## 0.13.0 - The Carbon Reduction Plan's standard design, and every design drawn for it, starts from the colours in the organisation's logo. ## 0.12.0 - The Carbon Reduction Plan is made in three steps that each end with the user: approve or change the design proof, approve or edit the narrative, then receive the plan. Every figure prints to the decimal places the reporting standard sets. ## 0.11.0 - The scenario, its delivery pathways and the Carbon Reduction Plan measure the commitment from the baseline: initiatives cover the whole committed reduction from the baseline's own sources, and today's emissions are shown for reference. Scenarios already signed off are unchanged. ## 0.10.0 - The Carbon Reduction Plan is designed from the organisation's brand guidelines and saved for future plans, with a contents page, a sign-off page and richer baseline, scenario and action plan content. The user can ask for a new look. ## 0.9.0 - The organisation can now ask for its Carbon Reduction Plan once both delivery pathways are signed off: a document covering an executive summary, the baseline, the SBTi criteria and targets, the least ambitious scenario, and the action plan and initiatives, produced only on request through CRP Plan Report. ## 0.8.0 - The entry gate reads the least ambitious targets from `organization/me/targets/sbti/least-ambitious.json`; emissions reports and scenarios live under `organization/me/` in memory. ## 0.7.0 - The entry gate reads the organisation's least ambitious targets from `targets/sbti/least-ambitious.json`, and the scenario is kept in memory as one file per commitment tier under `carbon-reduction-scenarios/`. ## 0.6.0 - Each signed-off delivery pathway's steps are added to the organisation's action plan as tasks for its team, and an optional yearly agent task reports progress against the pathways. - A scope whose proposed initiatives could not be used now says so on the checkpoint, instead of reading as if none was proposed. ## 0.5.0 - After the initiatives are agreed, the blueprint builds a delivery pathway for each commitment: the organisation answers at most three questions about itself, and signs off each commitment's pathway on its own. ## 0.4.1 - The agent tells the user what their data shows, never the files, paths or fields it is kept in. The scenario approval card names the scenario analysis document rather than its file. ## 0.4.0 - The blueprint now stops once a decarbonisation scenario is agreed. CRP Select Initiatives, CRP Contextualise Initiatives and CRP Compose Report are gone; `scenario.json` and its checkpoint document are the deliverable. Turning the agreed scenario into a Carbon Reduction Plan against the organisation's own template is a separate request naming `scenario.json` as its input. ## 0.3.0 - The initiative list is now contextualised against the organisation's registry assessments before report composition. Registry assessments are optional and enrich the plan without blocking it. ## 0.2.0 - Report appearance is configurable: colour, type and page in the stylesheet, chart geometry and titles in their own settings file. ## 0.1.0 - initial release Initial release of the Carbon Reduction Plan blueprint, binding CRP Assemble Figures, CRP Select Initiatives and CRP Compose Report into one installable service. 9/29/2026
• v45 # Changelog ## 0.18.0 - A second quick action, "Generate carbon reduction plan report": no sign-off question, every sign-off accepted, the existing scenario used when there is one. - Automatic sign-off is the default. - Three Carbon Reduction Plans, one for each version of the Scope 3 deep dive -- fixed categories, focused (95% of Scope 3) and broad (99%) -- with how they differ spelt out. - The scenario analysis is no longer pasted into the thread at the checkpoint; the plan carries it as its scenario analysis section, and it is shown in full as the run's last message. ## 0.17.0 - One question at the start: accept every sign-off in the run automatically. - The Carbon Reduction Plan is produced at the end of every run, laid out by the reports agent first; the agent's own drawn design follows only when the user turns that plan down. ## 0.16.0 - The plan is drawn as a board document, with the faults seen in real plans named. - A design the user turns down can be rendered by the reports agent instead. ## 0.15.1 - Design proofs show in the reply, the publisher's mark sits small in the footer, and a plan whose brand guidelines never name the organisation asks which name it carries. ## 0.15.0 - The Carbon Reduction Plan is designed by the agent, with charts from the chart agents. - Projections are reconciled with their own percentages, so none is shown marked for checking. - Skills are referenced by name again. ## 0.14.0 - The Carbon Reduction Plan's design is reviewed in a run of its own and revised against what the review faults, so a design that needs a second pass gets one. ## 0.13.2 - The Carbon Reduction Plan's design is drawn rather than timing out, and a design that could not be made says so plainly. ## 0.13.1 - The blueprint installs and upgrades again: CRP Plan Report no longer ships a binary file. ## 0.13.0 - The Carbon Reduction Plan's standard design, and every design drawn for it, starts from the colours in the organisation's logo. ## 0.12.0 - The Carbon Reduction Plan is made in three steps that each end with the user: approve or change the design proof, approve or edit the narrative, then receive the plan. Every figure prints to the decimal places the reporting standard sets. ## 0.11.0 - The scenario, its delivery pathways and the Carbon Reduction Plan measure the commitment from the baseline: initiatives cover the whole committed reduction from the baseline's own sources, and today's emissions are shown for reference. Scenarios already signed off are unchanged. ## 0.10.0 - The Carbon Reduction Plan is designed from the organisation's brand guidelines and saved for future plans, with a contents page, a sign-off page and richer baseline, scenario and action plan content. The user can ask for a new look. ## 0.9.0 - The organisation can now ask for its Carbon Reduction Plan once both delivery pathways are signed off: a document covering an executive summary, the baseline, the SBTi criteria and targets, the least ambitious scenario, and the action plan and initiatives, produced only on request through CRP Plan Report. ## 0.8.0 - The entry gate reads the least ambitious targets from `organization/me/targets/sbti/least-ambitious.json`; emissions reports and scenarios live under `organization/me/` in memory. ## 0.7.0 - The entry gate reads the organisation's least ambitious targets from `targets/sbti/least-ambitious.json`, and the scenario is kept in memory as one file per commitment tier under `carbon-reduction-scenarios/`. ## 0.6.0 - Each signed-off delivery pathway's steps are added to the organisation's action plan as tasks for its team, and an optional yearly agent task reports progress against the pathways. - A scope whose proposed initiatives could not be used now says so on the checkpoint, instead of reading as if none was proposed. ## 0.5.0 - After the initiatives are agreed, the blueprint builds a delivery pathway for each commitment: the organisation answers at most three questions about itself, and signs off each commitment's pathway on its own. ## 0.4.1 - The agent tells the user what their data shows, never the files, paths or fields it is kept in. The scenario approval card names the scenario analysis document rather than its file. ## 0.4.0 - The blueprint now stops once a decarbonisation scenario is agreed. CRP Select Initiatives, CRP Contextualise Initiatives and CRP Compose Report are gone; `scenario.json` and its checkpoint document are the deliverable. Turning the agreed scenario into a Carbon Reduction Plan against the organisation's own template is a separate request naming `scenario.json` as its input. ## 0.3.0 - The initiative list is now contextualised against the organisation's registry assessments before report composition. Registry assessments are optional and enrich the plan without blocking it. ## 0.2.0 - Report appearance is configurable: colour, type and page in the stylesheet, chart geometry and titles in their own settings file. ## 0.1.0 - initial release Initial release of the Carbon Reduction Plan blueprint, binding CRP Assemble Figures, CRP Select Initiatives and CRP Compose Report into one installable service. 9/29/2026
• v44 # Changelog ## 0.18.0 - A second quick action, "Generate carbon reduction plan report": no sign-off question, every sign-off accepted, the existing scenario used when there is one. - Automatic sign-off is the default. - Three Carbon Reduction Plans, one for each version of the Scope 3 deep dive -- fixed categories, focused (95% of Scope 3) and broad (99%) -- with how they differ spelt out. - The scenario analysis is no longer pasted into the thread at the checkpoint; the plan carries it as its scenario analysis section, and it is shown in full as the run's last message. ## 0.17.0 - One question at the start: accept every sign-off in the run automatically. - The Carbon Reduction Plan is produced at the end of every run, laid out by the reports agent first; the agent's own drawn design follows only when the user turns that plan down. ## 0.16.0 - The plan is drawn as a board document, with the faults seen in real plans named. - A design the user turns down can be rendered by the reports agent instead. ## 0.15.1 - Design proofs show in the reply, the publisher's mark sits small in the footer, and a plan whose brand guidelines never name the organisation asks which name it carries. ## 0.15.0 - The Carbon Reduction Plan is designed by the agent, with charts from the chart agents. - Projections are reconciled with their own percentages, so none is shown marked for checking. - Skills are referenced by name again. ## 0.14.0 - The Carbon Reduction Plan's design is reviewed in a run of its own and revised against what the review faults, so a design that needs a second pass gets one. ## 0.13.2 - The Carbon Reduction Plan's design is drawn rather than timing out, and a design that could not be made says so plainly. ## 0.13.1 - The blueprint installs and upgrades again: CRP Plan Report no longer ships a binary file. ## 0.13.0 - The Carbon Reduction Plan's standard design, and every design drawn for it, starts from the colours in the organisation's logo. ## 0.12.0 - The Carbon Reduction Plan is made in three steps that each end with the user: approve or change the design proof, approve or edit the narrative, then receive the plan. Every figure prints to the decimal places the reporting standard sets. ## 0.11.0 - The scenario, its delivery pathways and the Carbon Reduction Plan measure the commitment from the baseline: initiatives cover the whole committed reduction from the baseline's own sources, and today's emissions are shown for reference. Scenarios already signed off are unchanged. ## 0.10.0 - The Carbon Reduction Plan is designed from the organisation's brand guidelines and saved for future plans, with a contents page, a sign-off page and richer baseline, scenario and action plan content. The user can ask for a new look. ## 0.9.0 - The organisation can now ask for its Carbon Reduction Plan once both delivery pathways are signed off: a document covering an executive summary, the baseline, the SBTi criteria and targets, the least ambitious scenario, and the action plan and initiatives, produced only on request through CRP Plan Report. ## 0.8.0 - The entry gate reads the least ambitious targets from `organization/me/targets/sbti/least-ambitious.json`; emissions reports and scenarios live under `organization/me/` in memory. ## 0.7.0 - The entry gate reads the organisation's least ambitious targets from `targets/sbti/least-ambitious.json`, and the scenario is kept in memory as one file per commitment tier under `carbon-reduction-scenarios/`. ## 0.6.0 - Each signed-off delivery pathway's steps are added to the organisation's action plan as tasks for its team, and an optional yearly agent task reports progress against the pathways. - A scope whose proposed initiatives could not be used now says so on the checkpoint, instead of reading as if none was proposed. ## 0.5.0 - After the initiatives are agreed, the blueprint builds a delivery pathway for each commitment: the organisation answers at most three questions about itself, and signs off each commitment's pathway on its own. ## 0.4.1 - The agent tells the user what their data shows, never the files, paths or fields it is kept in. The scenario approval card names the scenario analysis document rather than its file. ## 0.4.0 - The blueprint now stops once a decarbonisation scenario is agreed. CRP Select Initiatives, CRP Contextualise Initiatives and CRP Compose Report are gone; `scenario.json` and its checkpoint document are the deliverable. Turning the agreed scenario into a Carbon Reduction Plan against the organisation's own template is a separate request naming `scenario.json` as its input. ## 0.3.0 - The initiative list is now contextualised against the organisation's registry assessments before report composition. Registry assessments are optional and enrich the plan without blocking it. ## 0.2.0 - Report appearance is configurable: colour, type and page in the stylesheet, chart geometry and titles in their own settings file. ## 0.1.0 - initial release Initial release of the Carbon Reduction Plan blueprint, binding CRP Assemble Figures, CRP Select Initiatives and CRP Compose Report into one installable service. 9/29/2026
• v43 # Changelog ## 0.18.0 - A second quick action, "Generate carbon reduction plan report": no sign-off question, every sign-off accepted, the existing scenario used when there is one. - Automatic sign-off is the default. - The scenario analysis is no longer pasted into the thread; the plan carries it as its scenario analysis section. ## 0.17.0 - One question at the start: accept every sign-off in the run automatically. - The Carbon Reduction Plan is produced at the end of every run, laid out by the reports agent first; the agent's own drawn design follows only when the user turns that plan down. ## 0.16.0 - The plan is drawn as a board document, with the faults seen in real plans named. - A design the user turns down can be rendered by the reports agent instead. ## 0.15.1 - Design proofs show in the reply, the publisher's mark sits small in the footer, and a plan whose brand guidelines never name the organisation asks which name it carries. ## 0.15.0 - The Carbon Reduction Plan is designed by the agent, with charts from the chart agents. - Projections are reconciled with their own percentages, so none is shown marked for checking. - Skills are referenced by name again. ## 0.14.0 - The Carbon Reduction Plan's design is reviewed in a run of its own and revised against what the review faults, so a design that needs a second pass gets one. ## 0.13.2 - The Carbon Reduction Plan's design is drawn rather than timing out, and a design that could not be made says so plainly. ## 0.13.1 - The blueprint installs and upgrades again: CRP Plan Report no longer ships a binary file. ## 0.13.0 - The Carbon Reduction Plan's standard design, and every design drawn for it, starts from the colours in the organisation's logo. ## 0.12.0 - The Carbon Reduction Plan is made in three steps that each end with the user: approve or change the design proof, approve or edit the narrative, then receive the plan. Every figure prints to the decimal places the reporting standard sets. ## 0.11.0 - The scenario, its delivery pathways and the Carbon Reduction Plan measure the commitment from the baseline: initiatives cover the whole committed reduction from the baseline's own sources, and today's emissions are shown for reference. Scenarios already signed off are unchanged. ## 0.10.0 - The Carbon Reduction Plan is designed from the organisation's brand guidelines and saved for future plans, with a contents page, a sign-off page and richer baseline, scenario and action plan content. The user can ask for a new look. ## 0.9.0 - The organisation can now ask for its Carbon Reduction Plan once both delivery pathways are signed off: a document covering an executive summary, the baseline, the SBTi criteria and targets, the least ambitious scenario, and the action plan and initiatives, produced only on request through CRP Plan Report. ## 0.8.0 - The entry gate reads the least ambitious targets from `organization/me/targets/sbti/least-ambitious.json`; emissions reports and scenarios live under `organization/me/` in memory. ## 0.7.0 - The entry gate reads the organisation's least ambitious targets from `targets/sbti/least-ambitious.json`, and the scenario is kept in memory as one file per commitment tier under `carbon-reduction-scenarios/`. ## 0.6.0 - Each signed-off delivery pathway's steps are added to the organisation's action plan as tasks for its team, and an optional yearly agent task reports progress against the pathways. - A scope whose proposed initiatives could not be used now says so on the checkpoint, instead of reading as if none was proposed. ## 0.5.0 - After the initiatives are agreed, the blueprint builds a delivery pathway for each commitment: the organisation answers at most three questions about itself, and signs off each commitment's pathway on its own. ## 0.4.1 - The agent tells the user what their data shows, never the files, paths or fields it is kept in. The scenario approval card names the scenario analysis document rather than its file. ## 0.4.0 - The blueprint now stops once a decarbonisation scenario is agreed. CRP Select Initiatives, CRP Contextualise Initiatives and CRP Compose Report are gone; `scenario.json` and its checkpoint document are the deliverable. Turning the agreed scenario into a Carbon Reduction Plan against the organisation's own template is a separate request naming `scenario.json` as its input. ## 0.3.0 - The initiative list is now contextualised against the organisation's registry assessments before report composition. Registry assessments are optional and enrich the plan without blocking it. ## 0.2.0 - Report appearance is configurable: colour, type and page in the stylesheet, chart geometry and titles in their own settings file. ## 0.1.0 - initial release Initial release of the Carbon Reduction Plan blueprint, binding CRP Assemble Figures, CRP Select Initiatives and CRP Compose Report into one installable service. 9/28/2026
• v42 # Changelog ## 0.17.0 - One question at the start: accept every sign-off in the run automatically. - The Carbon Reduction Plan is produced at the end of every run, laid out by the reports agent first; the agent's own drawn design follows only when the user turns that plan down. ## 0.16.0 - The plan is drawn as a board document, with the faults seen in real plans named. - A design the user turns down can be rendered by the reports agent instead. ## 0.15.1 - Design proofs show in the reply, the publisher's mark sits small in the footer, and a plan whose brand guidelines never name the organisation asks which name it carries. ## 0.15.0 - The Carbon Reduction Plan is designed by the agent, with charts from the chart agents. - Projections are reconciled with their own percentages, so none is shown marked for checking. - Skills are referenced by name again. ## 0.14.0 - The Carbon Reduction Plan's design is reviewed in a run of its own and revised against what the review faults, so a design that needs a second pass gets one. ## 0.13.2 - The Carbon Reduction Plan's design is drawn rather than timing out, and a design that could not be made says so plainly. ## 0.13.1 - The blueprint installs and upgrades again: CRP Plan Report no longer ships a binary file. ## 0.13.0 - The Carbon Reduction Plan's standard design, and every design drawn for it, starts from the colours in the organisation's logo. ## 0.12.0 - The Carbon Reduction Plan is made in three steps that each end with the user: approve or change the design proof, approve or edit the narrative, then receive the plan. Every figure prints to the decimal places the reporting standard sets. ## 0.11.0 - The scenario, its delivery pathways and the Carbon Reduction Plan measure the commitment from the baseline: initiatives cover the whole committed reduction from the baseline's own sources, and today's emissions are shown for reference. Scenarios already signed off are unchanged. ## 0.10.0 - The Carbon Reduction Plan is designed from the organisation's brand guidelines and saved for future plans, with a contents page, a sign-off page and richer baseline, scenario and action plan content. The user can ask for a new look. ## 0.9.0 - The organisation can now ask for its Carbon Reduction Plan once both delivery pathways are signed off: a document covering an executive summary, the baseline, the SBTi criteria and targets, the least ambitious scenario, and the action plan and initiatives, produced only on request through CRP Plan Report. ## 0.8.0 - The entry gate reads the least ambitious targets from `organization/me/targets/sbti/least-ambitious.json`; emissions reports and scenarios live under `organization/me/` in memory. ## 0.7.0 - The entry gate reads the organisation's least ambitious targets from `targets/sbti/least-ambitious.json`, and the scenario is kept in memory as one file per commitment tier under `carbon-reduction-scenarios/`. ## 0.6.0 - Each signed-off delivery pathway's steps are added to the organisation's action plan as tasks for its team, and an optional yearly agent task reports progress against the pathways. - A scope whose proposed initiatives could not be used now says so on the checkpoint, instead of reading as if none was proposed. ## 0.5.0 - After the initiatives are agreed, the blueprint builds a delivery pathway for each commitment: the organisation answers at most three questions about itself, and signs off each commitment's pathway on its own. ## 0.4.1 - The agent tells the user what their data shows, never the files, paths or fields it is kept in. The scenario approval card names the scenario analysis document rather than its file. ## 0.4.0 - The blueprint now stops once a decarbonisation scenario is agreed. CRP Select Initiatives, CRP Contextualise Initiatives and CRP Compose Report are gone; `scenario.json` and its checkpoint document are the deliverable. Turning the agreed scenario into a Carbon Reduction Plan against the organisation's own template is a separate request naming `scenario.json` as its input. ## 0.3.0 - The initiative list is now contextualised against the organisation's registry assessments before report composition. Registry assessments are optional and enrich the plan without blocking it. ## 0.2.0 - Report appearance is configurable: colour, type and page in the stylesheet, chart geometry and titles in their own settings file. ## 0.1.0 - initial release Initial release of the Carbon Reduction Plan blueprint, binding CRP Assemble Figures, CRP Select Initiatives and CRP Compose Report into one installable service. 9/28/2026
• v41 # Changelog ## 0.17.0 - One question at the start: accept every sign-off in the run automatically. - The Carbon Reduction Plan is produced at the end of every run, laid out by the reports agent first; the agent's own drawn design follows only when the user turns that plan down. ## 0.16.0 - The plan is drawn as a board document, with the faults seen in real plans named. - A design the user turns down can be rendered by the reports agent instead. ## 0.15.1 - Design proofs show in the reply, the publisher's mark sits small in the footer, and a plan whose brand guidelines never name the organisation asks which name it carries. ## 0.15.0 - The Carbon Reduction Plan is designed by the agent, with charts from the chart agents. - Projections are reconciled with their own percentages, so none is shown marked for checking. - Skills are referenced by name again. ## 0.14.0 - The Carbon Reduction Plan's design is reviewed in a run of its own and revised against what the review faults, so a design that needs a second pass gets one. ## 0.13.2 - The Carbon Reduction Plan's design is drawn rather than timing out, and a design that could not be made says so plainly. ## 0.13.1 - The blueprint installs and upgrades again: CRP Plan Report no longer ships a binary file. ## 0.13.0 - The Carbon Reduction Plan's standard design, and every design drawn for it, starts from the colours in the organisation's logo. ## 0.12.0 - The Carbon Reduction Plan is made in three steps that each end with the user: approve or change the design proof, approve or edit the narrative, then receive the plan. Every figure prints to the decimal places the reporting standard sets. ## 0.11.0 - The scenario, its delivery pathways and the Carbon Reduction Plan measure the commitment from the baseline: initiatives cover the whole committed reduction from the baseline's own sources, and today's emissions are shown for reference. Scenarios already signed off are unchanged. ## 0.10.0 - The Carbon Reduction Plan is designed from the organisation's brand guidelines and saved for future plans, with a contents page, a sign-off page and richer baseline, scenario and action plan content. The user can ask for a new look. ## 0.9.0 - The organisation can now ask for its Carbon Reduction Plan once both delivery pathways are signed off: a document covering an executive summary, the baseline, the SBTi criteria and targets, the least ambitious scenario, and the action plan and initiatives, produced only on request through CRP Plan Report. ## 0.8.0 - The entry gate reads the least ambitious targets from `organization/me/targets/sbti/least-ambitious.json`; emissions reports and scenarios live under `organization/me/` in memory. ## 0.7.0 - The entry gate reads the organisation's least ambitious targets from `targets/sbti/least-ambitious.json`, and the scenario is kept in memory as one file per commitment tier under `carbon-reduction-scenarios/`. ## 0.6.0 - Each signed-off delivery pathway's steps are added to the organisation's action plan as tasks for its team, and an optional yearly agent task reports progress against the pathways. - A scope whose proposed initiatives could not be used now says so on the checkpoint, instead of reading as if none was proposed. ## 0.5.0 - After the initiatives are agreed, the blueprint builds a delivery pathway for each commitment: the organisation answers at most three questions about itself, and signs off each commitment's pathway on its own. ## 0.4.1 - The agent tells the user what their data shows, never the files, paths or fields it is kept in. The scenario approval card names the scenario analysis document rather than its file. ## 0.4.0 - The blueprint now stops once a decarbonisation scenario is agreed. CRP Select Initiatives, CRP Contextualise Initiatives and CRP Compose Report are gone; `scenario.json` and its checkpoint document are the deliverable. Turning the agreed scenario into a Carbon Reduction Plan against the organisation's own template is a separate request naming `scenario.json` as its input. ## 0.3.0 - The initiative list is now contextualised against the organisation's registry assessments before report composition. Registry assessments are optional and enrich the plan without blocking it. ## 0.2.0 - Report appearance is configurable: colour, type and page in the stylesheet, chart geometry and titles in their own settings file. ## 0.1.0 - initial release Initial release of the Carbon Reduction Plan blueprint, binding CRP Assemble Figures, CRP Select Initiatives and CRP Compose Report into one installable service. 9/28/2026
• v40 # Changelog ## 0.15.1 - Design proofs show in the reply, the publisher's mark sits small in the footer, and a plan whose brand guidelines never name the organisation asks which name it carries. ## 0.15.0 - The Carbon Reduction Plan is designed by the agent, with charts from the chart agents. - Projections are reconciled with their own percentages, so none is shown marked for checking. - Skills are referenced by name again. ## 0.14.0 - The Carbon Reduction Plan's design is reviewed in a run of its own and revised against what the review faults, so a design that needs a second pass gets one. ## 0.13.2 - The Carbon Reduction Plan's design is drawn rather than timing out, and a design that could not be made says so plainly. ## 0.13.1 - The blueprint installs and upgrades again: CRP Plan Report no longer ships a binary file. ## 0.13.0 - The Carbon Reduction Plan's standard design, and every design drawn for it, starts from the colours in the organisation's logo. ## 0.12.0 - The Carbon Reduction Plan is made in three steps that each end with the user: approve or change the design proof, approve or edit the narrative, then receive the plan. Every figure prints to the decimal places the reporting standard sets. ## 0.11.0 - The scenario, its delivery pathways and the Carbon Reduction Plan measure the commitment from the baseline: initiatives cover the whole committed reduction from the baseline's own sources, and today's emissions are shown for reference. Scenarios already signed off are unchanged. ## 0.10.0 - The Carbon Reduction Plan is designed from the organisation's brand guidelines and saved for future plans, with a contents page, a sign-off page and richer baseline, scenario and action plan content. The user can ask for a new look. ## 0.9.0 - The organisation can now ask for its Carbon Reduction Plan once both delivery pathways are signed off: a document covering an executive summary, the baseline, the SBTi criteria and targets, the least ambitious scenario, and the action plan and initiatives, produced only on request through CRP Plan Report. ## 0.8.0 - The entry gate reads the least ambitious targets from `organization/me/targets/sbti/least-ambitious.json`; emissions reports and scenarios live under `organization/me/` in memory. ## 0.7.0 - The entry gate reads the organisation's least ambitious targets from `targets/sbti/least-ambitious.json`, and the scenario is kept in memory as one file per commitment tier under `carbon-reduction-scenarios/`. ## 0.6.0 - Each signed-off delivery pathway's steps are added to the organisation's action plan as tasks for its team, and an optional yearly agent task reports progress against the pathways. - A scope whose proposed initiatives could not be used now says so on the checkpoint, instead of reading as if none was proposed. ## 0.5.0 - After the initiatives are agreed, the blueprint builds a delivery pathway for each commitment: the organisation answers at most three questions about itself, and signs off each commitment's pathway on its own. ## 0.4.1 - The agent tells the user what their data shows, never the files, paths or fields it is kept in. The scenario approval card names the scenario analysis document rather than its file. ## 0.4.0 - The blueprint now stops once a decarbonisation scenario is agreed. CRP Select Initiatives, CRP Contextualise Initiatives and CRP Compose Report are gone; `scenario.json` and its checkpoint document are the deliverable. Turning the agreed scenario into a Carbon Reduction Plan against the organisation's own template is a separate request naming `scenario.json` as its input. ## 0.3.0 - The initiative list is now contextualised against the organisation's registry assessments before report composition. Registry assessments are optional and enrich the plan without blocking it. ## 0.2.0 - Report appearance is configurable: colour, type and page in the stylesheet, chart geometry and titles in their own settings file. ## 0.1.0 - initial release Initial release of the Carbon Reduction Plan blueprint, binding CRP Assemble Figures, CRP Select Initiatives and CRP Compose Report into one installable service. 9/24/2026
• v39 # Changelog ## 0.15.1 - Design proofs show in the reply, the publisher's mark sits small in the footer, and a plan whose brand guidelines never name the organisation asks which name it carries. ## 0.15.0 - The Carbon Reduction Plan is designed by the agent, with charts from the chart agents. - Projections are reconciled with their own percentages, so none is shown marked for checking. - Skills are referenced by name again. ## 0.14.0 - The Carbon Reduction Plan's design is reviewed in a run of its own and revised against what the review faults, so a design that needs a second pass gets one. ## 0.13.2 - The Carbon Reduction Plan's design is drawn rather than timing out, and a design that could not be made says so plainly. ## 0.13.1 - The blueprint installs and upgrades again: CRP Plan Report no longer ships a binary file. ## 0.13.0 - The Carbon Reduction Plan's standard design, and every design drawn for it, starts from the colours in the organisation's logo. ## 0.12.0 - The Carbon Reduction Plan is made in three steps that each end with the user: approve or change the design proof, approve or edit the narrative, then receive the plan. Every figure prints to the decimal places the reporting standard sets. ## 0.11.0 - The scenario, its delivery pathways and the Carbon Reduction Plan measure the commitment from the baseline: initiatives cover the whole committed reduction from the baseline's own sources, and today's emissions are shown for reference. Scenarios already signed off are unchanged. ## 0.10.0 - The Carbon Reduction Plan is designed from the organisation's brand guidelines and saved for future plans, with a contents page, a sign-off page and richer baseline, scenario and action plan content. The user can ask for a new look. ## 0.9.0 - The organisation can now ask for its Carbon Reduction Plan once both delivery pathways are signed off: a document covering an executive summary, the baseline, the SBTi criteria and targets, the least ambitious scenario, and the action plan and initiatives, produced only on request through CRP Plan Report. ## 0.8.0 - The entry gate reads the least ambitious targets from `organization/me/targets/sbti/least-ambitious.json`; emissions reports and scenarios live under `organization/me/` in memory. ## 0.7.0 - The entry gate reads the organisation's least ambitious targets from `targets/sbti/least-ambitious.json`, and the scenario is kept in memory as one file per commitment tier under `carbon-reduction-scenarios/`. ## 0.6.0 - Each signed-off delivery pathway's steps are added to the organisation's action plan as tasks for its team, and an optional yearly agent task reports progress against the pathways. - A scope whose proposed initiatives could not be used now says so on the checkpoint, instead of reading as if none was proposed. ## 0.5.0 - After the initiatives are agreed, the blueprint builds a delivery pathway for each commitment: the organisation answers at most three questions about itself, and signs off each commitment's pathway on its own. ## 0.4.1 - The agent tells the user what their data shows, never the files, paths or fields it is kept in. The scenario approval card names the scenario analysis document rather than its file. ## 0.4.0 - The blueprint now stops once a decarbonisation scenario is agreed. CRP Select Initiatives, CRP Contextualise Initiatives and CRP Compose Report are gone; `scenario.json` and its checkpoint document are the deliverable. Turning the agreed scenario into a Carbon Reduction Plan against the organisation's own template is a separate request naming `scenario.json` as its input. ## 0.3.0 - The initiative list is now contextualised against the organisation's registry assessments before report composition. Registry assessments are optional and enrich the plan without blocking it. ## 0.2.0 - Report appearance is configurable: colour, type and page in the stylesheet, chart geometry and titles in their own settings file. ## 0.1.0 - initial release Initial release of the Carbon Reduction Plan blueprint, binding CRP Assemble Figures, CRP Select Initiatives and CRP Compose Report into one installable service. 9/23/2026
• v38 # Changelog ## 0.15.0 - The Carbon Reduction Plan is designed by the agent, with charts from the chart agents. - Projections are reconciled with their own percentages, so none is shown marked for checking. - Skills are referenced by name again. ## 0.14.0 - The Carbon Reduction Plan's design is reviewed in a run of its own and revised against what the review faults, so a design that needs a second pass gets one. ## 0.13.2 - The Carbon Reduction Plan's design is drawn rather than timing out, and a design that could not be made says so plainly. ## 0.13.1 - The blueprint installs and upgrades again: CRP Plan Report no longer ships a binary file. ## 0.13.0 - The Carbon Reduction Plan's standard design, and every design drawn for it, starts from the colours in the organisation's logo. ## 0.12.0 - The Carbon Reduction Plan is made in three steps that each end with the user: approve or change the design proof, approve or edit the narrative, then receive the plan. Every figure prints to the decimal places the reporting standard sets. ## 0.11.0 - The scenario, its delivery pathways and the Carbon Reduction Plan measure the commitment from the baseline: initiatives cover the whole committed reduction from the baseline's own sources, and today's emissions are shown for reference. Scenarios already signed off are unchanged. ## 0.10.0 - The Carbon Reduction Plan is designed from the organisation's brand guidelines and saved for future plans, with a contents page, a sign-off page and richer baseline, scenario and action plan content. The user can ask for a new look. ## 0.9.0 - The organisation can now ask for its Carbon Reduction Plan once both delivery pathways are signed off: a document covering an executive summary, the baseline, the SBTi criteria and targets, the least ambitious scenario, and the action plan and initiatives, produced only on request through CRP Plan Report. ## 0.8.0 - The entry gate reads the least ambitious targets from `organization/me/targets/sbti/least-ambitious.json`; emissions reports and scenarios live under `organization/me/` in memory. ## 0.7.0 - The entry gate reads the organisation's least ambitious targets from `targets/sbti/least-ambitious.json`, and the scenario is kept in memory as one file per commitment tier under `carbon-reduction-scenarios/`. ## 0.6.0 - Each signed-off delivery pathway's steps are added to the organisation's action plan as tasks for its team, and an optional yearly agent task reports progress against the pathways. - A scope whose proposed initiatives could not be used now says so on the checkpoint, instead of reading as if none was proposed. ## 0.5.0 - After the initiatives are agreed, the blueprint builds a delivery pathway for each commitment: the organisation answers at most three questions about itself, and signs off each commitment's pathway on its own. ## 0.4.1 - The agent tells the user what their data shows, never the files, paths or fields it is kept in. The scenario approval card names the scenario analysis document rather than its file. ## 0.4.0 - The blueprint now stops once a decarbonisation scenario is agreed. CRP Select Initiatives, CRP Contextualise Initiatives and CRP Compose Report are gone; `scenario.json` and its checkpoint document are the deliverable. Turning the agreed scenario into a Carbon Reduction Plan against the organisation's own template is a separate request naming `scenario.json` as its input. ## 0.3.0 - The initiative list is now contextualised against the organisation's registry assessments before report composition. Registry assessments are optional and enrich the plan without blocking it. ## 0.2.0 - Report appearance is configurable: colour, type and page in the stylesheet, chart geometry and titles in their own settings file. ## 0.1.0 - initial release Initial release of the Carbon Reduction Plan blueprint, binding CRP Assemble Figures, CRP Select Initiatives and CRP Compose Report into one installable service. 9/23/2026
• v37 # Changelog ## 0.15.0 - The Carbon Reduction Plan is designed by the agent, with charts from the chart agents. - Projections are reconciled with their own percentages, so none is shown marked for checking. - Skills are referenced by name again. ## 0.14.0 - The Carbon Reduction Plan's design is reviewed in a run of its own and revised against what the review faults, so a design that needs a second pass gets one. ## 0.13.2 - The Carbon Reduction Plan's design is drawn rather than timing out, and a design that could not be made says so plainly. ## 0.13.1 - The blueprint installs and upgrades again: CRP Plan Report no longer ships a binary file. ## 0.13.0 - The Carbon Reduction Plan's standard design, and every design drawn for it, starts from the colours in the organisation's logo. ## 0.12.0 - The Carbon Reduction Plan is made in three steps that each end with the user: approve or change the design proof, approve or edit the narrative, then receive the plan. Every figure prints to the decimal places the reporting standard sets. ## 0.11.0 - The scenario, its delivery pathways and the Carbon Reduction Plan measure the commitment from the baseline: initiatives cover the whole committed reduction from the baseline's own sources, and today's emissions are shown for reference. Scenarios already signed off are unchanged. ## 0.10.0 - The Carbon Reduction Plan is designed from the organisation's brand guidelines and saved for future plans, with a contents page, a sign-off page and richer baseline, scenario and action plan content. The user can ask for a new look. ## 0.9.0 - The organisation can now ask for its Carbon Reduction Plan once both delivery pathways are signed off: a document covering an executive summary, the baseline, the SBTi criteria and targets, the least ambitious scenario, and the action plan and initiatives, produced only on request through CRP Plan Report. ## 0.8.0 - The entry gate reads the least ambitious targets from `organization/me/targets/sbti/least-ambitious.json`; emissions reports and scenarios live under `organization/me/` in memory. ## 0.7.0 - The entry gate reads the organisation's least ambitious targets from `targets/sbti/least-ambitious.json`, and the scenario is kept in memory as one file per commitment tier under `carbon-reduction-scenarios/`. ## 0.6.0 - Each signed-off delivery pathway's steps are added to the organisation's action plan as tasks for its team, and an optional yearly agent task reports progress against the pathways. - A scope whose proposed initiatives could not be used now says so on the checkpoint, instead of reading as if none was proposed. ## 0.5.0 - After the initiatives are agreed, the blueprint builds a delivery pathway for each commitment: the organisation answers at most three questions about itself, and signs off each commitment's pathway on its own. ## 0.4.1 - The agent tells the user what their data shows, never the files, paths or fields it is kept in. The scenario approval card names the scenario analysis document rather than its file. ## 0.4.0 - The blueprint now stops once a decarbonisation scenario is agreed. CRP Select Initiatives, CRP Contextualise Initiatives and CRP Compose Report are gone; `scenario.json` and its checkpoint document are the deliverable. Turning the agreed scenario into a Carbon Reduction Plan against the organisation's own template is a separate request naming `scenario.json` as its input. ## 0.3.0 - The initiative list is now contextualised against the organisation's registry assessments before report composition. Registry assessments are optional and enrich the plan without blocking it. ## 0.2.0 - Report appearance is configurable: colour, type and page in the stylesheet, chart geometry and titles in their own settings file. ## 0.1.0 - initial release Initial release of the Carbon Reduction Plan blueprint, binding CRP Assemble Figures, CRP Select Initiatives and CRP Compose Report into one installable service. 9/22/2026
• v36 # Changelog ## 0.3.0 - The initiative list is now contextualised against the organisation's registry assessments before report composition. Registry assessments are optional and enrich the plan without blocking it. ## 0.2.0 - Report appearance is configurable: colour, type and page in the stylesheet, chart geometry and titles in their own settings file. ## 0.1.0 - initial release Initial release of the Carbon Reduction Plan blueprint, binding CRP Assemble Figures, CRP Select Initiatives and CRP Compose Report into one installable service. 9/21/2026
• v35 # Changelog ## 0.3.0 - The initiative list is now contextualised against the organisation's registry assessments before report composition. Registry assessments are optional and enrich the plan without blocking it. ## 0.2.0 - Report appearance is configurable: colour, type and page in the stylesheet, chart geometry and titles in their own settings file. ## 0.1.0 - initial release Initial release of the Carbon Reduction Plan blueprint, binding CRP Assemble Figures, CRP Select Initiatives and CRP Compose Report into one installable service. 9/21/2026
• v34 # Changelog ## 0.3.0 - The initiative list is now contextualised against the organisation's registry assessments before report composition. Registry assessments are optional and enrich the plan without blocking it. ## 0.2.0 - Report appearance is configurable: colour, type and page in the stylesheet, chart geometry and titles in their own settings file. ## 0.1.0 - initial release Initial release of the Carbon Reduction Plan blueprint, binding CRP Assemble Figures, CRP Select Initiatives and CRP Compose Report into one installable service. 9/21/2026
• v33 # Changelog ## 0.3.0 - The initiative list is now contextualised against the organisation's registry assessments before report composition. Registry assessments are optional and enrich the plan without blocking it. ## 0.2.0 - Report appearance is configurable: colour, type and page in the stylesheet, chart geometry and titles in their own settings file. ## 0.1.0 - initial release Initial release of the Carbon Reduction Plan blueprint, binding CRP Assemble Figures, CRP Select Initiatives and CRP Compose Report into one installable service. 9/20/2026
• v32 # Changelog ## 0.3.0 - The initiative list is now contextualised against the organisation's registry assessments before report composition. Registry assessments are optional and enrich the plan without blocking it. ## 0.2.0 - Report appearance is configurable: colour, type and page in the stylesheet, chart geometry and titles in their own settings file. ## 0.1.0 - initial release Initial release of the Carbon Reduction Plan blueprint, binding CRP Assemble Figures, CRP Select Initiatives and CRP Compose Report into one installable service. 9/19/2026
• v31 # Changelog ## 0.3.0 - The initiative list is now contextualised against the organisation's registry assessments before report composition. Registry assessments are optional and enrich the plan without blocking it. ## 0.2.0 - Report appearance is configurable: colour, type and page in the stylesheet, chart geometry and titles in their own settings file. ## 0.1.0 - initial release Initial release of the Carbon Reduction Plan blueprint, binding CRP Assemble Figures, CRP Select Initiatives and CRP Compose Report into one installable service. 9/18/2026
• v30 # Changelog ## 0.3.0 - The initiative list is now contextualised against the organisation's registry assessments before report composition. Registry assessments are optional and enrich the plan without blocking it. ## 0.2.0 - Report appearance is configurable: colour, type and page in the stylesheet, chart geometry and titles in their own settings file. ## 0.1.0 - initial release Initial release of the Carbon Reduction Plan blueprint, binding CRP Assemble Figures, CRP Select Initiatives and CRP Compose Report into one installable service. 9/17/2026
• v29 # Changelog ## 0.3.0 - The initiative list is now contextualised against the organisation's registry assessments before report composition. Registry assessments are optional and enrich the plan without blocking it. ## 0.2.0 - Report appearance is configurable: colour, type and page in the stylesheet, chart geometry and titles in their own settings file. ## 0.1.0 - initial release Initial release of the Carbon Reduction Plan blueprint, binding CRP Assemble Figures, CRP Select Initiatives and CRP Compose Report into one installable service. 9/17/2026
• v28 # Changelog ## 0.3.0 - The initiative list is now contextualised against the organisation's registry assessments before report composition. Registry assessments are optional and enrich the plan without blocking it. ## 0.2.0 - Report appearance is configurable: colour, type and page in the stylesheet, chart geometry and titles in their own settings file. ## 0.1.0 - initial release Initial release of the Carbon Reduction Plan blueprint, binding CRP Assemble Figures, CRP Select Initiatives and CRP Compose Report into one installable service. 9/17/2026
• v27 # Changelog ## 0.3.0 - The initiative list is now contextualised against the organisation's registry assessments before report composition. Registry assessments are optional and enrich the plan without blocking it. ## 0.2.0 - Report appearance is configurable: colour, type and page in the stylesheet, chart geometry and titles in their own settings file. ## 0.1.0 - initial release Initial release of the Carbon Reduction Plan blueprint, binding CRP Assemble Figures, CRP Select Initiatives and CRP Compose Report into one installable service. 9/17/2026
• v26 # Changelog ## 0.3.0 - The initiative list is now contextualised against the organisation's registry assessments before report composition. Registry assessments are optional and enrich the plan without blocking it. ## 0.2.0 - Report appearance is configurable: colour, type and page in the stylesheet, chart geometry and titles in their own settings file. ## 0.1.0 - initial release Initial release of the Carbon Reduction Plan blueprint, binding CRP Assemble Figures, CRP Select Initiatives and CRP Compose Report into one installable service. 9/17/2026
• v25 # Changelog ## 0.3.0 - The initiative list is now contextualised against the organisation's registry assessments before report composition. Registry assessments are optional and enrich the plan without blocking it. ## 0.2.0 - Report appearance is configurable: colour, type and page in the stylesheet, chart geometry and titles in their own settings file. ## 0.1.0 - initial release Initial release of the Carbon Reduction Plan blueprint, binding CRP Assemble Figures, CRP Select Initiatives and CRP Compose Report into one installable service. 9/16/2026
• v24 # Changelog ## 0.3.0 - The initiative list is now contextualised against the organisation's registry assessments before report composition. Registry assessments are optional and enrich the plan without blocking it. ## 0.2.0 - Report appearance is configurable: colour, type and page in the stylesheet, chart geometry and titles in their own settings file. ## 0.1.0 - initial release Initial release of the Carbon Reduction Plan blueprint, binding CRP Assemble Figures, CRP Select Initiatives and CRP Compose Report into one installable service. 9/15/2026
• v23 # Changelog ## 0.3.0 - The initiative list is now contextualised against the organisation's registry assessments before report composition. Registry assessments are optional and enrich the plan without blocking it. ## 0.2.0 - Report appearance is configurable: colour, type and page in the stylesheet, chart geometry and titles in their own settings file. ## 0.1.0 - initial release Initial release of the Carbon Reduction Plan blueprint, binding CRP Assemble Figures, CRP Select Initiatives and CRP Compose Report into one installable service. 9/14/2026
• v22 # Changelog ## 0.3.0 - The initiative list is now contextualised against the organisation's registry assessments before report composition. Registry assessments are optional and enrich the plan without blocking it. ## 0.2.0 - Report appearance is configurable: colour, type and page in the stylesheet, chart geometry and titles in their own settings file. ## 0.1.0 - initial release Initial release of the Carbon Reduction Plan blueprint, binding CRP Assemble Figures, CRP Select Initiatives and CRP Compose Report into one installable service. 9/14/2026
• v21 # Changelog ## 0.3.0 - The initiative list is now contextualised against the organisation's registry assessments before report composition. Registry assessments are optional and enrich the plan without blocking it. ## 0.2.0 - Report appearance is configurable: colour, type and page in the stylesheet, chart geometry and titles in their own settings file. ## 0.1.0 - initial release Initial release of the Carbon Reduction Plan blueprint, binding CRP Assemble Figures, CRP Select Initiatives and CRP Compose Report into one installable service. 9/14/2026
• v20 # Changelog ## 0.3.0 - The initiative list is now contextualised against the organisation's registry assessments before report composition. Registry assessments are optional and enrich the plan without blocking it. ## 0.2.0 - Report appearance is configurable: colour, type and page in the stylesheet, chart geometry and titles in their own settings file. ## 0.1.0 - initial release Initial release of the Carbon Reduction Plan blueprint, binding CRP Assemble Figures, CRP Select Initiatives and CRP Compose Report into one installable service. 9/11/2026
• v19 # Changelog ## 0.3.0 - The initiative list is now contextualised against the organisation's registry assessments before report composition. Registry assessments are optional and enrich the plan without blocking it. ## 0.2.0 - Report appearance is configurable: colour, type and page in the stylesheet, chart geometry and titles in their own settings file. ## 0.1.0 - initial release Initial release of the Carbon Reduction Plan blueprint, binding CRP Assemble Figures, CRP Select Initiatives and CRP Compose Report into one installable service. 9/10/2026
• v18 # Changelog ## 0.3.0 - The initiative list is now contextualised against the organisation's registry assessments before report composition. Registry assessments are optional and enrich the plan without blocking it. ## 0.2.0 - Report appearance is configurable: colour, type and page in the stylesheet, chart geometry and titles in their own settings file. ## 0.1.0 - initial release Initial release of the Carbon Reduction Plan blueprint, binding CRP Assemble Figures, CRP Select Initiatives and CRP Compose Report into one installable service. 9/8/2026
• v17 # Changelog ## 0.3.0 - The initiative list is now contextualised against the organisation's registry assessments before report composition. Registry assessments are optional and enrich the plan without blocking it. ## 0.2.0 - Report appearance is configurable: colour, type and page in the stylesheet, chart geometry and titles in their own settings file. ## 0.1.0 - initial release Initial release of the Carbon Reduction Plan blueprint, binding CRP Assemble Figures, CRP Select Initiatives and CRP Compose Report into one installable service. 9/6/2026
• v16 # Changelog ## 0.3.0 - The initiative list is now contextualised against the organisation's registry assessments before report composition. Registry assessments are optional and enrich the plan without blocking it. ## 0.2.0 - Report appearance is configurable: colour, type and page in the stylesheet, chart geometry and titles in their own settings file. ## 0.1.0 - initial release Initial release of the Carbon Reduction Plan blueprint, binding CRP Assemble Figures, CRP Select Initiatives and CRP Compose Report into one installable service. 9/4/2026
• v15 # Changelog ## 0.3.0 - The initiative list is now contextualised against the organisation's registry assessments before report composition. Registry assessments are optional and enrich the plan without blocking it. ## 0.2.0 - Report appearance is configurable: colour, type and page in the stylesheet, chart geometry and titles in their own settings file. ## 0.1.0 - initial release Initial release of the Carbon Reduction Plan blueprint, binding CRP Assemble Figures, CRP Select Initiatives and CRP Compose Report into one installable service. 9/1/2026
• v14 # Changelog ## 0.3.0 - The initiative list is now contextualised against the organisation's registry assessments before report composition. Registry assessments are optional and enrich the plan without blocking it. ## 0.2.0 - Report appearance is configurable: colour, type and page in the stylesheet, chart geometry and titles in their own settings file. ## 0.1.0 - initial release Initial release of the Carbon Reduction Plan blueprint, binding CRP Assemble Figures, CRP Select Initiatives and CRP Compose Report into one installable service. 9/1/2026
• v13 # Changelog ## 0.3.0 - The initiative list is now contextualised against the organisation's registry assessments before report composition. Registry assessments are optional and enrich the plan without blocking it. ## 0.2.0 - Report appearance is configurable: colour, type and page in the stylesheet, chart geometry and titles in their own settings file. ## 0.1.0 - initial release Initial release of the Carbon Reduction Plan blueprint, binding CRP Assemble Figures, CRP Select Initiatives and CRP Compose Report into one installable service. 9/1/2026
• v12 # Changelog ## 0.3.0 - The initiative list is now contextualised against the organisation's registry assessments before report composition. Registry assessments are optional and enrich the plan without blocking it. ## 0.2.0 - Report appearance is configurable: colour, type and page in the stylesheet, chart geometry and titles in their own settings file. ## 0.1.0 - initial release Initial release of the Carbon Reduction Plan blueprint, binding CRP Assemble Figures, CRP Select Initiatives and CRP Compose Report into one installable service. 9/1/2026
• v11 # Changelog ## 0.3.0 - The initiative list is now contextualised against the organisation's registry assessments before report composition. Registry assessments are optional and enrich the plan without blocking it. ## 0.2.0 - Report appearance is configurable: colour, type and page in the stylesheet, chart geometry and titles in their own settings file. ## 0.1.0 - initial release Initial release of the Carbon Reduction Plan blueprint, binding CRP Assemble Figures, CRP Select Initiatives and CRP Compose Report into one installable service. 8/31/2026
• v10 # Changelog ## 0.3.0 - The initiative list is now contextualised against the organisation's registry assessments before report composition. Registry assessments are optional and enrich the plan without blocking it. ## 0.2.0 - Report appearance is configurable: colour, type and page in the stylesheet, chart geometry and titles in their own settings file. ## 0.1.0 - initial release Initial release of the Carbon Reduction Plan blueprint, binding CRP Assemble Figures, CRP Select Initiatives and CRP Compose Report into one installable service. 8/28/2026
• v9 # Changelog ## 0.3.0 - The initiative list is now contextualised against the organisation's registry assessments before report composition. Registry assessments are optional and enrich the plan without blocking it. ## 0.2.0 - Report appearance is configurable: colour, type and page in the stylesheet, chart geometry and titles in their own settings file. ## 0.1.0 - initial release Initial release of the Carbon Reduction Plan blueprint, binding CRP Assemble Figures, CRP Select Initiatives and CRP Compose Report into one installable service. 8/28/2026
• v8 # Changelog ## 0.3.0 - The initiative list is now contextualised against the organisation's registry assessments before report composition. Registry assessments are optional and enrich the plan without blocking it. ## 0.2.0 - Report appearance is configurable: colour, type and page in the stylesheet, chart geometry and titles in their own settings file. ## 0.1.0 - initial release Initial release of the Carbon Reduction Plan blueprint, binding CRP Assemble Figures, CRP Select Initiatives and CRP Compose Report into one installable service. 8/28/2026
• v7 # Changelog ## 0.3.0 - The initiative list is now contextualised against the organisation's registry assessments before report composition. Registry assessments are optional and enrich the plan without blocking it. ## 0.2.0 - Report appearance is configurable: colour, type and page in the stylesheet, chart geometry and titles in their own settings file. ## 0.1.0 - initial release Initial release of the Carbon Reduction Plan blueprint, binding CRP Assemble Figures, CRP Select Initiatives and CRP Compose Report into one installable service. 8/28/2026
• v6 # Changelog ## 0.3.0 - The initiative list is now contextualised against the organisation's registry assessments before report composition. Registry assessments are optional and enrich the plan without blocking it. ## 0.2.0 - Report appearance is configurable: colour, type and page in the stylesheet, chart geometry and titles in their own settings file. ## 0.1.0 - initial release Initial release of the Carbon Reduction Plan blueprint, binding CRP Assemble Figures, CRP Select Initiatives and CRP Compose Report into one installable service. 8/28/2026
• v5 # Changelog ## 0.3.0 - The initiative list is now contextualised against the organisation's registry assessments before report composition. Registry assessments are optional and enrich the plan without blocking it. ## 0.2.0 - Report appearance is configurable: colour, type and page in the stylesheet, chart geometry and titles in their own settings file. ## 0.1.0 - initial release Initial release of the Carbon Reduction Plan blueprint, binding CRP Assemble Figures, CRP Select Initiatives and CRP Compose Report into one installable service. 8/27/2026
• v4 # Changelog ## 0.3.0 - The initiative list is now contextualised against the organisation's registry assessments before report composition. Registry assessments are optional and enrich the plan without blocking it. ## 0.2.0 - Report appearance is configurable: colour, type and page in the stylesheet, chart geometry and titles in their own settings file. ## 0.1.0 - initial release Initial release of the Carbon Reduction Plan blueprint, binding CRP Assemble Figures, CRP Select Initiatives and CRP Compose Report into one installable service. 8/25/2026
• v3 # Changelog ## 0.2.0 - Report appearance is configurable: colour, type and page in the stylesheet, chart geometry and titles in their own settings file. ## 0.1.0 - initial release Initial release of the Carbon Reduction Plan blueprint, binding CRP Assemble Figures, CRP Select Initiatives and CRP Compose Report into one installable service. 8/14/2026
• v2 # Changelog ## 0.1.0 - initial release Initial release of the Carbon Reduction Plan blueprint, binding CRP Assemble Figures, CRP Select Initiatives and CRP Compose Report into one installable service. 8/12/2026
• v1 # Changelog ## 0.1.0 - initial release Initial release of the Carbon Reduction Plan blueprint, binding CRP Assemble Figures, CRP Select Initiatives and CRP Compose Report into one installable service. 8/11/2026