Poesis
Usage / Use case Implemented
Agree evidence-preservation requirements
Agree retention purpose, duration, access and disposal constraints for decision evidence, distinguishing agreed policy from demonstrated enforcement.
CISO / Security leadership / Operational knowledge owner / IT risk owner
Platform
What serves this use case
Features
- Definition Manager: GSM Definitions retention Implemented
Values
Values composed with this use case
- Value Implemented
Proportionate evidence preservation
Agree justified preservation periods, access and disposal constraints while keeping policy decisions distinct from verified retention enforcement.
Supported by Features(1)
Realized through Use cases(1)
- Value Partial
Reduce evidence reconstruction effort
Bring linked snapshots, decisions and provenance into a stated audit scope, with completeness assessed against that review rather than inferred from history alone.
Supported by Capabilities(1)
Supported by Features(2)
- Value Partial
Control sourcing data exposure.
Bound the planned sourcing workflow with explicit policies for tool/model egress, credentials, telemetry and retention, including any data leaving the local process.
- Value Implemented
Reuse retained lifecycle evidence.
Start review from retained version history. Linking actors, rationale and retention policy completes the evidence needed for a stated audit scope.
Supported by Features(1)
Realized through Use cases(2)
Pains
Pain points
- Pain point Implemented
Evidence is discarded too early or retained indefinitely without a justified preservation policy.
Historical decisions become unreviewable or unnecessary retained information creates avoidable exposure.
Addressed by Features(1)
Experienced by Actor types(3)
Addressed through Use cases(1)