Poesis
Domain Intelligence Platform · Solution
The IT Intelligence Platform — AI governance for IT.
The IT Intelligence Platform: a shared, governed account of the IT landscape, with planned analysis, appraisal, sourcing and generation.
An authenticated shell and account foundations exist. Domain workflows, scoped policy enforcement and integrated SIE access remain planned; hosted availability is not established.
The digital-twin ambition distinguishes accepted intent, inspected source revisions and fresh deployed observations.
Values
Shared definitions and reviewable evidence for IT decisions.
- Value Partial
Keep governance closer to its evidence.
Bring shared definitions, reviewed candidates and scoped appraisal together to simplify reconciliation. For running systems, keep observation coverage and freshness visible.
Supported by Affordances(2)
Supported by Capabilities(2)
- Value Partial
Give AI attributable context.
Ground planned read-only answers in authorized, versioned definitions, with citations and abstention for review. Build that context through direct authoring or reviewed sourcing.
Supported by Affordances(1)
Supported by Capabilities(2)
Supported by Features(1)
- Value Planned
Coordinate IT work around shared definitions.
Reuse common inputs across appraisal, analysis and document generation so profiles can review decisions against the same definitions. Outputs and scenarios remain subject to review.
Supported by Capabilities(1)
Supported by Features(3)
- Value Partial
Review obligations together.
Reuse selected packages in one scoped review, with applicability, conflicting obligations and missing evidence visible for resolution.
Supported by Affordances(1)
Supported by Capabilities(1)
Supported by Features(1)
Capabilities
Planned inventory, composition, sourcing, appraisal, reasoning and generation.
- Capability Partial
Governed IT definition inventory
Maintain a shared IT inventory whose typed definitions, review decisions and access responsibilities stay connected across framework views. Browser authoring, tenant/object policy and identity synchronization remain planned beyond the existing authentication foundations.
Addresses Pain points(4)
- The architecture repository is out of date the day it’s written.
- Anything can change anything — there is no approval trail.
- Reviewers work from different selections and lose related decisions across meeting notes.
- Architecture, compliance, and quality tools don’t speak to each other.
Supports Values(10)
- Keep consequential changes attributable
- Keep governance closer to its evidence.
- Give AI attributable context.
- A shared workspace for IT decisions.
- Make shared context attributable.
- Use evidence to inform revisions.
- Make transitions inspectable.
- Separate exploration from acceptance.
- Repeatable review boundaries
- Coherent records of related decisions
Serves Use cases(2)
Used by Actor types(3)
- Capability Planned
IT governance fabric composition
Compose selected frameworks and internal obligations against a shared IT inventory, review overlaps and gaps, and retain revision-bound adoption decisions. Composition does not itself evaluate or enforce compliance.
Addresses Pain points(2)
Supports Values(3)
Serves Use cases(1)
Used by Actor types(3)
Realized by Features(3)
- Capability Planned
Evidence-backed IT definition sourcing
Reconcile evidence-backed candidates from selected code revisions into reviewable IT definition drafts, with collection coverage, source age and recoverable runs visible throughout. Analysis and client-owned draft registration are planned; inspected source is not deployed reality.
Addresses Pain points(2)
Supports Values(3)
Serves Use cases(1)
Used by Actor types(3)
- Capability Planned
Scoped IT compliance evaluation
Appraise scoped IT definitions, carry versioned findings into accountable corrective reviews, and reappraise revised proposals. Preserve applicability and unknown states; continuous live-system assurance additionally requires observations and scheduling.
Addresses Pain points(3)
Supports Values(6)
Serves Use cases(3)
Used by Actor types(5)
- Capability Planned
IT dependency analysis and decision support
Assess proposed IT changes by combining dependency and obligation paths with cited, read-only answers over authorized definitions. Planned analysis exposes missing boundaries and insufficient evidence; causal simulation additionally needs validated scenario dynamics and explicit uncertainty.
Addresses Pain points(2)
Supports Values(3)
Serves Use cases(1)
Used by Actor types(3)
Realized by Features(2)
- Capability Planned
IT artifact generation
Turn a selected IT baseline into consistent architecture and evidence document families, then review outputs against the definitions and decisions they cite. Recurring production retains pinned inputs and exposes incomplete jobs; generation is not substantive acceptance.
Addresses Pain points(2)
Supports Values(3)
Serves Use cases(1)
Used by Actor types(3)
Realized by Features(3)
Products
Two products for the IT governance workflow.
- Product · recorded v0.1 Partial Web Application
Bring IT definitions, evidence and decisions into one shared workspace.
Product features- Feature · milestone v1.1 Planned IT artifact factory
- Feature · milestone v1.3 Planned IT compliance evaluation
- Feature · milestone v1.4 Planned IT Copilot
- Feature · milestone v1.5 Planned IT impact analysis and planned simulation
- Feature · milestone v1.2 Planned GSM Definitions sourcing management
- Feature · milestone v1.0 Planned GSM Definitions management
- Feature · milestone v1.0 Planned GSM Ontology management
- Feature · milestone v1.0 Partial Authentication and planned RBAC/ABAC
- Feature · milestone v1.x Planned Identity-provider synchronization
- Feature · milestone v1.x Planned Governance review sessions
- Product · recorded v0.0 Planned Definition Blackboard Code Sourcer
Turn inspected code revisions into evidence-backed definition proposals.
Product features- Feature · milestone v1.0 Planned GSM Definitions candidate sourcing from code repos
Qualities
What ITIP asserts, and what it declines to assert.
- Accepted intent Planned What the organization has agreed
Reviewed definitions carry the authority of an accepted decision. Acceptance records intent; it does not assert that the estate already matches it.
- Inspected revision Planned What a pinned source says
Sourced candidates stay bound to the revision they were read from. A source revision is not deployed reality and is reconciled before registration.
- Observed deployment Planned What was seen running, and when
Deployed observations need an identity, an observation time and a stated coverage. Absent observations are reported as unknown rather than compliant.
Usage
IT decision and review use cases
- Use case Planned
Configure repository collection boundaries
Select repository branches, paths and revision boundaries so inspected evidence matches the intended acquisition scope.
Supported by Features(1)
Addresses Pain points(1)
Realizes Values(2)
Performed by Actor types(2)
- Use case Planned
Diagnose and recover incomplete collection
Identify failed or partial acquisition runs, correct their causes and resume collection without presenting missing evidence as complete coverage.
Supported by Features(1)
Addresses Pain points(1)
Realizes Values(1)
Performed by Actor types(1)
- 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.
Supported by Features(1)
Addresses Pain points(2)
Realizes Values(2)
Performed by Actor types(2)
- Use case Partial
Review operation-specific privileges
Review tenant, object and action permissions against assigned responsibilities and remove unnecessary authority.
Supported by Features(1)
Addresses Pain points(1)
Realizes Values(4)
Performed by Actor types(2)
- Use case Planned
Restore identity-provider synchronization
Reconcile external identity and group changes with local access assignments, inspect synchronization failures and verify revoked access is no longer granted.
Supported by Features(1)
Addresses Pain points(1)
Realizes Values(1)
Performed by Actor types(2)
- Use case Planned
Prepare and conduct a multi-item governance session
Prepare a related decision agenda, record participation and retain each revision-bound decision and condition without treating a meeting vote as authorization by itself.
Supported by Features(1)
Addresses Pain points(1)
Realizes Values(1)
Performed by Actor types(3)
- Use case Planned
Resolve a blocked change request
Inspect blocking validation and lifecycle findings, correct the proposal and submit the revised scope for renewed review.
Supported by Features(1)
Addresses Pain points(1)
Realizes Values(1)
Performed by Actor types(2)
- Use case Planned
Define and reuse a scoped review lens
Save explicit subject-selection and dependency-traversal rules and reuse them with visible snapshot boundaries across reviews.
Supported by Features(1)
Addresses Pain points(1)
Realizes Values(1)
Performed by Actor types(2)
- Use case Planned
Inspect one subject across framework perspectives
Compare architecture, security and quality classifications of the same identified subject without confusing classification with obligation applicability.
Supported by Features(1)
Addresses Pain points(2)
Realizes Values(1)
Performed by Actor types(3)
- Use case Planned
Compose and reuse a governance selection
Save a pinned selection of governance packages and reuse it while separately reviewing applicability for each adopting scope.
Supported by Features(1)
Addresses Pain points(1)
Performed by Actor types(2)
- Use case Planned
Resolve competing obligations before adoption
Compare overlapping requirements, record interpretations and obtain an accountable resolution of incompatible obligations before adoption.
Supported by Features(1)
Addresses Pain points(1)
Performed by Actor types(3)
- Use case Planned
Identify gaps in selected vocabulary coverage
Compare selected vocabulary against an explicit subject and concern inventory, exposing uncovered areas without claiming legal completeness.
Supported by Features(1)
Addresses Pain points(1)
Performed by Actor types(2)
- Use case Planned
Author and maintain reusable output bindings
Define versioned template fields and source bindings that produce consistent named artifact families from pinned definitions.
Supported by Features(1)
Addresses Pain points(2)
Realizes Values(1)
Performed by Actor types(2)
- Use case Planned
Preview bindings before generating an artifact
Inspect sample binding resolution and missing inputs before accepting a template for document generation.
Supported by Features(1)
Addresses Pain points(1)
Realizes Values(1)
Performed by Actor types(2)
- Use case Planned
Set grounding constraints for generated narrative
Specify source requirements and editorial constraints for generated fields, then review citations and unsupported statements before accepting output.
Supported by Features(1)
Addresses Pain points(1)
Realizes Values(1)
Performed by Actor types(2)
- Use case Planned
Operate recurring report production
Schedule version-pinned report production and detect failed or late runs before a review depends on the output.
Supported by Features(1)
Addresses Pain points(2)
Realizes Values(1)
Performed by Actor types(2)
- Use case Planned
Investigate partial or failed generation
Inspect job completion, errors and partial outputs to decide what can be reused and what must be regenerated and reviewed.
Supported by Features(1)
Addresses Pain points(1)
Realizes Values(1)
Performed by Actor types(2)
- Use case Planned
Turn uncovered obligations into corrective proposals
Turn scoped findings into owned definition-change proposals and verify resolution through a subsequent appraisal rather than merely closing a task.
Supported by Capabilities(1)
Addresses Pain points(1)
Realizes Values(1)
Performed by Actor types(3)
- Use case Planned
Bind selected obligations to an organizational scope
Establish the subjects, conditions and accountable interpretation that make selected obligations applicable to a specific adopting scope.
Supported by Features(1)
Addresses Pain points(1)
Realizes Values(3)
Performed by Actor types(2)
- Use case Planned
Assess application decommissioning prerequisites
Identify dependent consumers, retained obligations and missing evidence before approving an application retirement boundary; execution remains a separate operation.
Supported by Features(1)
Addresses Pain points(1)
Realizes Values(1)
Performed by Actor types(3)
- Use case Partial
Reconcile code evidence into reviewed definitions
Turn competing source-revision candidates into attributable definition drafts for review.
Supported by Affordances(1)
Addresses Pain points(2)
Realizes Values(9)
- 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.
Performed by Actor types(3)
- Use case Planned
Review a scoped IT appraisal
Review versioned findings with explicit applicability, input identity and missing evidence.
Supported by Features(1)
Addresses Pain points(1)
Realizes Values(6)
Performed by Actor types(3)
- Use case Planned
Review recurring patient-portal appraisal
Compare successive portal appraisal results, review corrective proposals and decide what needs reappraisal. Operational conclusions require supplied deployment observations with explicit coverage and freshness; recurring scheduling is a separate prerequisite.
Supported by Capabilities(1)
Addresses Pain points(2)
Realizes Values(4)
Performed by Actor types(3)
- Use case Planned
Inspect a change before committing to it
Trace affected definitions and obligations, then record what remains unknown before deciding.
Supported by Features(1)
Addresses Pain points(1)
Realizes Values(3)
Performed by Actor types(3)
- Use case Planned
Ask an IT question and inspect its sources
Obtain a read-only answer whose claims can be checked against authorized definition snapshots.
Supported by Features(1)
Addresses Pain points(1)
Realizes Values(3)
Performed by Actor types(2)
- Use case Planned
Generate and review an architecture decision pack
Assemble an ADR pack and evidence summary from the same pinned inputs, then review the substantive result.
Supported by Features(1)
Addresses Pain points(1)
Realizes Values(3)
Performed by Actor types(2)
- Use case Partial
Deliver a reviewed artifact through a local workflow
Produce a scoped artifact through an attributable local method, checks and human review.
Supported by Affordances(1)
Addresses Pain points(2)
Realizes Values(8)
Performed by Actor types(3)
- Use case Planned
Extract definition candidates from a code revision
Analyze a pinned repository revision and inspect candidate subjects, relationships, provenance and uncertainty before any client promotes a draft. Inspected source is not evidence of deployed behavior.
Supported by Features(1)
Addresses Pain points(2)
Realizes Values(2)
Performed by Actor types(2)
- Use case Partial
Maintain a governed IT definition inventory
Keep typed IT definitions, their review lenses, authorizations and decision sessions coherent so every review works from the same attributable inventory.
Supported by Capabilities(1)
Addresses Pain points(2)
Realizes Values(4)
Performed by Actor types(3)
- Use case Planned
Compose an IT governance fabric for an adopting scope
Apply a pinned package selection to a shared subject inventory, inspect overlaps and uncovered concerns through review lenses, and retain adoption decisions against exact revisions. Composition is distinct from evaluation and enforcement.
Supported by Capabilities(1)
Addresses Pain points(2)
Realizes Values(3)
Performed by Actor types(3)
- Use case Planned
Source IT definitions from inspected evidence
Run revision-pinned acquisition, review its coverage limits and register the resulting candidates as drafts, keeping source revision distinct from deployed reality.
Supported by Capabilities(1)
Addresses Pain points(2)
Realizes Values(3)
Performed by Actor types(3)
- Use case Planned
Run a scoped IT compliance appraisal
Appraise selected definition revisions, review findings and unknown states with accountable owners, carry corrective proposals through a decision session and reappraise the revised scope. Supplied observations are needed for live-system conclusions.
Supported by Capabilities(1)
Addresses Pain points(2)
Realizes Values(3)
Performed by Actor types(3)
- Use case Planned
Answer an IT question from the governed model
Assess a proposed IT change by combining dependency and obligation paths with cited read-only answers over the same authorized definitions. Compare affected parties and unresolved evidence before choosing an option; graph traversal is not causal simulation.
Supported by Capabilities(1)
Addresses Pain points(2)
Realizes Values(3)
Performed by Actor types(3)
- Use case Planned
Produce a named IT document family from pinned definitions
Select an IT baseline and its recorded decisions, bind a versioned document family to those inputs, and review generated packs together for consistency and missing evidence. Recurring jobs preserve the same inspection and acceptance boundaries.
Supported by Capabilities(1)
Addresses Pain points(2)
Realizes Values(3)
Performed by Actor types(3)
- Use case Partial
Review selected obligations together
Bring source-linked frameworks, regulations and internal obligations into the same scoped review, compare overlaps and uncovered concerns, and retain accountable adoption decisions without claiming automatic conflict resolution or legal completeness.
Supported by Affordances(1)
Addresses Pain points(2)
Realizes Values(3)
Performed by Actor types(3)
- Use case Partial
Review candidates from selected sources
Compare code-derived and delivery-derived candidates against their pinned source evidence, retain competing contributions and acquisition gaps, and select what may proceed to draft review. Confidence does not settle truth or establish deployed reality.
Supported by Affordances(1)
Addresses Pain points(3)
Realizes Values(3)
Performed by Actor types(3)
- Use case Partial
Evaluate identified inputs against supported Norms
Combine reproducible Norm verdicts with scoped IT measures and findings to identify accountable corrective work and judge a subsequent appraisal. Preserve rule/input identity, applicability and unknown states; operational conclusions require observation evidence.
Supported by Affordances(1)
Addresses Pain points(2)
Realizes Values(3)
Performed by Actor types(3)
- Use case Partial
Generate artifacts through declared workflows
Produce a grounded document or software artifact through assigned roles, bounded workflow execution and explicit deliverable contracts, then obtain the required revision-bound review before advancement. Technical checks, substantive acceptance and authorized deployment remain separate decisions.
Supported by Affordances(1)
Addresses Pain points(3)
Realizes Values(3)
Performed by Actor types(4)