Documentation
Trust and continuity
Ownership and continuity
A building's memory should remain understandable when the people, companies, or teams working with it change.
Who information belongs to
Information documenting a building's history usually lives with the Place. Information intrinsic to a person or organization remains connected to that entity.
The key question is whether the item should remain with the building after a professional relationship ends.
Memory that outlasts teams
Accounts represent working teams; Places represent what is documented. Keeping them separate lets a team change without erasing accumulated memory.
Access changes do not rewrite the origin or history of existing items.
When a person or company leaves
When a relationship ends, its access and roles are closed with an end date rather than overwriting history.
Place information remains there, while the departing Account's internal data retains its privacy boundaries.
Portability and exit
Databitat should let each party obtain the data that belongs to them in useful, understandable formats.
Specific portability, handover, and closure procedures will be documented with the available features.