The exit package: what you keep and how we check it

What the package holds

Each client has an exit package with a fixed set of documents. Every document has a link, a date and a place where it lives, so the client can see what exists and where.

When it counts as out of date

The oldest document sets the age of the package. Past the limit below, the panel marks the package as out of date and names the document that aged.

The exit test

The panel records an exit test: the date, who ran it, the minutes it took, whether it passed or failed, and what got in the way. The person who runs it is not the owner and follows only the continuity runbook. A record cannot be edited; a mistake is fixed with a new record.

A failed test stays failed whatever its age, and a test past its window shows as expired. Every day the system also checks, with no person involved, that the documents are registered and recent and that their links answer. That check does not replace the test: only the test shows that someone else can rebuild the project.

Leaving

To close the panel, the client confirms that each account is in its own name, removes each access and checks the package, then confirms with a fresh passkey. Closing ends every session; the activity record and the package stay with the client. Reopening takes the client's own confirmation.