Poesis
Usage / Use case Planned
Set and review evidence-refresh expectations
Agree refresh expectations and inspect source age, failed refreshes and coverage limits before using collected evidence.
Platform
What serves this use case
Features
Values
Values composed with this use case
- Value Partial
Inspect acquisition scope and freshness
Distinguish inspected revisions from missing, failed or stale collection before relying on source evidence.
Supported by Affordances(1)
Supported by Capabilities(1)
Supported by Features(2)
Realized through Use cases(6)
- Value Partial
Relate definitions to inspected revisions.
Reconcile definitions against pinned source evidence. Relating them to running systems additionally requires deployed identity, configuration and fresh observations.
Supported by Affordances(1)
Supported by Features(1)
Realized through Use cases(2)
Pains
Pain points
- Pain point Partial
Collection scope, incomplete runs and stale evidence are mistaken for current coverage.
Reviews rely on uninspected or outdated inputs and repeat work when collection failures emerge late.
Addressed by Affordances(1)
Addressed by Capabilities(1)
Addressed by Features(2)
Experienced by Actor types(4)
Addressed through Use cases(6)
- Pain point Partial
Governance drifts from what actually runs.
The declared estate and the running estate diverge silently — until an audit or an incident exposes the gap.
Addressed by Affordances(1)
Addressed by Capabilities(3)
Addressed by Features(3)
Experienced by Actor types(6)
Addressed through Use cases(8)
- Set and review evidence-refresh expectations
- Reconcile code evidence into reviewed definitions
- Review recurring patient-portal appraisal
- Submit a contribution to a declared panel
- Close a contribution collection for review
- Collect competing contributions on a shared blackboard
- Obtain a reproducible verdict for supplied inputs
- Review candidates from selected sources