Poesis
Usage / Use case Implemented
Retrieve the basis of a historical decision
Retrieve the decided revision, recorded identity, supporting evidence and conditions relevant to a historical decision, retaining attribution gaps.
Platform
What serves this use case
Features
- Definition Manager: GSM Definitions retention Implemented
Values
Values composed with this use case
- Value Partial
Coherent records of related decisions
Retain agendas, participation and per-revision decisions together while keeping discussion, voting and authorized lifecycle decisions distinct.
Supported by Capabilities(1)
Supported by Features(2)
- 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 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)
- Value Partial
Trace retained proposal evidence.
Revisit captured actors and sources, with reducer decisions and Ascription links extending the trail from proposal to accepted definition.
Supported by Affordances(1)
Supported by Capabilities(1)
Supported by Features(2)
Pains
Pain points
- Pain point Partial
Compliance is reconstructed in spreadsheets before every audit.
Posture exists only at audit time; between audits, nobody can answer what is actually covered.
Addressed by Affordances(1)
Addressed by Capabilities(2)
Addressed by Features(3)
Experienced by Actor types(7)
Addressed through Use cases(7)
- Retrieve the basis of a historical decision
- Review a scoped IT appraisal
- Review recurring patient-portal appraisal
- Inspect retained contribution evidence
- Run a scoped IT compliance appraisal
- Hold definitions as the authoritative, revision-bound source
- Evaluate identified inputs against supported Norms
- Pain point Partial
The reason for a decision stays in an email thread instead of reaching the next reviewer.
In a manual handoff, the next reviewer repeats interviews to recover assumptions and unresolved objections.
Addressed by Capabilities(2)
Addressed by Features(1)
Experienced by Actor types(7)
Addressed through Use cases(6)