Aster Vale Register
One workspace for what you run, what it depends on, and what you can prove about both.
Inventory
The register holds the systems that matter — applications, infrastructure, data stores and the vendor services sitting behind them. Each entry carries an owner, a criticality rating, a recovery objective and a review date.
The review date is the part that does most of the work. An inventory without one degrades silently: entries stay in place while the reality behind them changes, and nobody discovers the drift until it matters. Overdue reviews surface as a working list rather than an annual surprise.
Dependency mapping
Relationships are recorded explicitly and in both directions, so a service knows what it needs and what needs it.
Two things tend to emerge from the first pass. The first is a set of dependencies recorded in one direction only — a team knows what it relies on, but the service it relies on has no record of them as a consumer. The second is a shared component several tiers deep that nothing lists as critical, because each individual team's exposure to it looks small.
Continuity records
Recovery procedures, tested dates, and the assumptions each procedure rests on are attached to the systems they describe rather than kept in a separate document set. Where a procedure assumes something — that a backup is current, that a failover has capacity, that a vendor will answer out of hours — the assumption is recorded as a statement that can be checked.
Audit evidence
Evidence export produces the artefacts an assessment normally asks for: system inventories with ownership, dependency records, recovery objectives and their test history, and a change trail showing when each was last confirmed.
The intent is narrow. The Register does not interpret a framework or tell you whether you comply with it. It removes the fortnight usually spent assembling evidence that already exists in a form nobody can export.