Aranisdocs
aranis.ai
Docs/Continuity/Continuity action plan

Continuity action plan

How a coverage gap or a plan drift becomes work with an owner and a deadline.

Updated on August 18, 2026

No new mechanism

The continuity action plan is the same action plan used everywhere else on the platform, scoped to continuity. The tasks, the states, and the overdue warnings are identical to the supplier and organizational plans — whoever runs one runs this.

Where items come from

Three origins. Processes with no recovery strategy, from coverage. Primary strategies never validated or overdue, also from coverage. And drift between the published plan and live data.

In every case the item arrives with its origin context intact, so whoever picks it up knows where the gap came from without having to reconstruct it.

Clicking twice does not duplicate

Drift findings are recalculated on every read, so they carry no stored identity of their own. If each read drew a fresh identifier, the same problem would become a different item every time and duplicate detection would never fire.

So the identifier is derived from the finding's content. The same drift always produces the same identifier, and clicking the same finding twice does not open two items for one problem.