Poesis
Affordances
What the platform makes possible
- Affordance Partial
Governed organizational context
Work from shared, typed definitions
Establish a common semantic basis for decisions across authors and tools by connecting typed IT inventory, retained definition versions, shared vocabulary and cited dependency analysis. Direct authoring and reviewed sourcing are alternative inputs; integrated authorized selection, interchange and answer quality need acceptance, and accepted intent is not observed live state.
Addresses Pain points(3)
Supports Values(4)
Serves Use cases(1)
Used by Actor types(4)
- Affordance Partial
Scoped governance composition
Review selected obligations together
Bring obligations from selected frameworks and internal policies into a shared scope so adopters can review applicability, overlaps and gaps against the same IT subjects. Sourced vocabulary and templates support planned composition and accountable interpretation; selection establishes neither conflict freedom, legal completeness nor compliance enforcement.
Addresses Pain points(2)
Supports Values(3)
Serves Use cases(1)
Used by Actor types(3)
Realized by Capabilities(2)
- Affordance Partial
Governance lifecycle
Make review and activation boundaries explicit
Connect proposals to accountable review and activation through governance grammar, lifecycle controls and human decision gates. Transition controls exist, while authenticated revision-bound decisions need identity and policy integration; sealing closes collection rather than approving definitions, and research affects model revision only through separately accepted Change Proposals.
Addresses Pain points(2)
Supports Values(3)
Serves Use cases(1)
Used by Actor types(4)
- Affordance Partial
Evidence-backed definition sourcing
Review candidates from selected sources
Build a reviewable account of IT and delivery work by comparing and reconciling code-derived and delivery-derived evidence as retained candidates with provenance. End-to-end acquisition, review and draft registration are planned; confidence is not truth, source history is not deployed reality, and draft promotion remains separate from acceptance.
Addresses Pain points(3)
Supports Values(10)
- Keep governance closer to its evidence.
- Give AI attributable context.
- Reduce manual candidate authoring.
- Relate definitions to inspected revisions.
- Inspect the basis of proposals.
- Use evidence to inform revisions.
- Compare contributed partial views.
- Separate exploration from acceptance.
- Trace retained proposal evidence.
- Inspect acquisition scope and freshness
Serves Use cases(2)
Used by Actor types(3)
- Affordance Partial
Scoped Norm evaluation
Evaluate identified inputs against supported Norms
Produce decision-ready compliance appraisal by combining pure verdicts over pinned rules and inputs with scoped IT measures, findings and corrective review. Planned evaluation preserves unknown and not-applicable states; running-system claims additionally need deployed identity, fresh observations and coverage, continuous appraisal needs scheduling, and results are not compliance certification.
Addresses Pain points(2)
Supports Values(3)
Serves Use cases(1)
Used by Actor types(3)
Realized by Capabilities(2)
- Affordance Partial
Bounded generative delivery
Generate artifacts through declared workflows
Produce grounded artifacts from selected definitions through bounded workflow orchestration, declared operations, artifact contracts and accountable review, retaining outputs and execution evidence in a local delivery baseline. Local controls exist; integrated generation, effect safety and authenticated human gates need acceptance. Reviewed documents do not establish tested code, authorized deployment or operational feedback; hosting is optional.
Addresses Pain points(3)
Supports Values(9)
- Delegate bounded work with evidence and recourse
- Build toward traceable delivery.
- Make agentic work reviewable.
- Inspect control decisions.
- Catch invalid declared artifacts earlier.
- Clarify responsibilities.
- Make expectations inspectable.
- Keep decisions attributable.
- Distinguish generated output from accepted completion
Serves Use cases(2)
Used by Actor types(4)