Classification
Carry the organisation’s own labels and handling language on the content rather than inventing a marketing taxonomy.
Content governance
Governance becomes operational when the content itself carries the context needed for a decision. Casewelt is designed so classification, retention and hold can influence what the product allows people and systems to do with an object.
Example
The contract is created in procurement and given the organisation’s contract classification. A retention rule applies from the agreed business event. Later, a dispute requires the document to be held.
At that point deletion should not depend on whether someone saw a note in another system. The object state should make the conflict visible and the attempted deletion should fail safely until the hold is properly released.
Lifecycle controls
Carry the organisation’s own labels and handling language on the content rather than inventing a marketing taxonomy.
Associate a keep period with the object and the business event that starts the clock.
Freeze deletion when a dispute, investigation or other authorised hold requires preservation.
Let sharing, deletion and other actions consider governance state rather than operating independently.
Record material lifecycle transitions so later review can explain what changed and when.
Combine lifecycle decisions with organisation-level placement requirements where those controls apply.
A useful distinction
Teams already have meaningful terms — contract, restricted, internal, board, personnel, matter number, retention class. A content platform should carry that language reliably and make it available to policy.
Governance still depends on the customer’s policy, legal basis and operating model. Certifications can support assurance, but they do not define the organisation’s retention and hold rules.
Explore the wider governance modelTest a lifecycle
Bring the classification, retention or hold requirement and walk through the resulting product behaviour.