Skip to content

Project records, risk and hosting

The agent keeps project records in your repository. During setup, it creates a masterplan describing the tool’s purpose and risks; each piece records its result, decisions and risk areas. Approval records retain your words and the date in a local Git file that is not committed. The records remain part of your project.

The agent asks who could be affected if the tool fails, what data it uses and how you would recover. It records the applicable risk areas, and each piece identifies those it affects.

For a risk you can judge, the agent explains who could be affected and what would normally prevent harm. You can take that precaution, remove the affected work from scope or continue with the risk. If you continue, the agent records your acceptance and proceeds with the work; the risk remains listed.

The tool goes live through a hosting recipe, which fixes the services that run it and the steps for deployment, backup, restoration and rollback. You create and control the service accounts. Outside a recipe, the kit states that it provides no guarantees.

Read the rules that apply in every project.