Forget an organisation
Run ./lens forget-org <org> --reason '<why>' --yes from the installation directory, while the installation is running. In one transaction, it deletes the organisation’s read modelRead modelThe database tables used by the map, Ask and Find. NovusLens rebuilds these tables from its history of recorded changes., evidence bodies, sealed identity joinSealed identity joinStored links between employee fingerprints and teams or services. The fingerprints replace readable employee identifiers. Product pages do not show the links for individual people., agent evidence, meaning entriesMeaning entryA stored written account supplied by the organisation, such as a policy or definition. Answers can cite it without treating it as a measured fact. and notifications. The same transaction deletes its accounts and the audit rows those accounts wrote. One audit row under the operator’s identity records the act and its reason. The organisation is marked forgotten, so nothing rebuilds it from the log. Its identifier cannot be reused: a later materialise for that identifier refuses aloud.
Development and rehearsal only: ./lens ops --version dev exec -- uv run python -m conway_graph forget-org --org <org> --allow-reuse --reason='<why>' --yes erases the same rows without the mark, so a walk or a rehearsal can rebuild the organisation from nothing. It is audited as steward.forget-org-allow-reuse. A customer host never uses it.
What forgetting does not reach: the canonical logCanonical logThe permanent history of changes to an organisation’s model. New entries are added at the end. Earlier entries stay when the database is rebuilt. in the meshMeshA set of connected Mycelium services that exchange updates and keep the NovusLens log. volumes is append-only and still carries the organisation’s commits. Backups taken earlier still hold the organisation too. Erasing the log means removing the mesh volumes, which affects every organisation on the installation. On a single-organisation pilot host that is the host’s decommissioning, and the pilot agreement says so.
Accounts and stewardship describes the act in the order of the other stewardshipStewardshipCare of recorded information, such as correcting or withdrawing entries. The action allowed depends on the record type and the reader’s role. tasks.