Poesis
Usage / Use case Planned
Configure repository collection boundaries
Select repository branches, paths and revision boundaries so inspected evidence matches the intended acquisition scope.
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
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.
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)