Poesis Pilot

Select repository branches, paths and revision boundaries so inspected evidence matches the intended acquisition scope.

Identify failed or partial acquisition runs, correct their causes and resume collection without presenting missing evidence as complete coverage.

Agree refresh expectations and inspect source age, failed refreshes and coverage limits before using collected evidence.

Review tenant, object and action permissions against assigned responsibilities and remove unnecessary authority.

Reconcile external identity and group changes with local access assignments, inspect synchronization failures and verify revoked access is no longer granted.

Prepare a related decision agenda, record participation and retain each revision-bound decision and condition without treating a meeting vote as authorization by itself.

Inspect blocking validation and lifecycle findings, correct the proposal and submit the revised scope for renewed review.

Retrieve the decided revision, recorded identity, supporting evidence and conditions relevant to a historical decision, retaining attribution gaps.

Save explicit subject-selection and dependency-traversal rules and reuse them with visible snapshot boundaries across reviews.

Compare architecture, security and quality classifications of the same identified subject without confusing classification with obligation applicability.

Save a pinned selection of governance packages and reuse it while separately reviewing applicability for each adopting scope.

Compare overlapping requirements, record interpretations and obtain an accountable resolution of incompatible obligations before adoption.

Compare selected vocabulary against an explicit subject and concern inventory, exposing uncovered areas without claiming legal completeness.

Define versioned template fields and source bindings that produce consistent named artifact families from pinned definitions.

Inspect sample binding resolution and missing inputs before accepting a template for document generation.

Specify source requirements and editorial constraints for generated fields, then review citations and unsupported statements before accepting output.

Schedule version-pinned report production and detect failed or late runs before a review depends on the output.

Inspect job completion, errors and partial outputs to decide what can be reused and what must be regenerated and reviewed.

Turn scoped findings into owned definition-change proposals and verify resolution through a subsequent appraisal rather than merely closing a task.

Establish the subjects, conditions and accountable interpretation that make selected obligations applicable to a specific adopting scope.

Inspect dependent definition eligibility after a referenced foundation is invalidated and determine which continued uses require renewed review.

Agree retention purpose, duration, access and disposal constraints for decision evidence, distinguishing agreed policy from demonstrated enforcement.

Compare old and proposed rule verdicts on pinned reference inputs, investigate changed or unknown results and record acceptance before adoption.

Agree a versioned vocabulary and its constraints with adopters, using examples and counterexamples to expose incompatible interpretations.

Compare exported and imported definitions against an explicit conformance profile, including identity, lifecycle meaning and nonconformant draft preservation.

Review resource/action grants against a bounded assignment and its expiry, then check those grants and the target baseline before mediated work. Mandate review is planned; grant checking alone is not authenticated human approval.

Compare candidate model routes against workload-specific quality, cost and disclosure criteria using retained evaluation evidence.

Verify that a target host receives the pinned instructions and declared checks, distinguishing delivery from model adherence before migration.

Resolve overlapping edits against a shared baseline while retaining attribution and revalidating the combined artifacts before acceptance.

Identify dependent consumers, retained obligations and missing evidence before approving an application retirement boundary; execution remains a separate operation.

Agree service commitments, application dependencies and accountable owners against a dated evidence baseline.

No platform item declares support. This is a gap, not a planned-delivery claim.

Obtain explicit acceptance of service responsibilities, active exceptions and unresolved obligations by the receiving owner.

No platform item declares support. This is a gap, not a planned-delivery claim.

Decide a scoped exception with explicit authority, expiry, risk ownership and compensating-control evidence.

No platform item declares support. This is a gap, not a planned-delivery claim.

Review current exposure and control evidence before renewing, revoking or closing an exception at its review boundary.

No platform item declares support. This is a gap, not a planned-delivery claim.

Identify affected consumers and inspect compatibility evidence before accepting an interface change and migration conditions.

No platform item declares support. This is a gap, not a planned-delivery claim.

Agree consumer migration and retirement prerequisites while making unknown consumers and unresolved compatibility visible.

No platform item declares support. This is a gap, not a planned-delivery claim.

Give a receiving service owner authoritative decisions, source evidence and unresolved questions sufficient to review and accept a handover.

No platform item declares support. This is a gap, not a planned-delivery claim.

Relate findings to deployed components, affected services and business criticality to assign justified remediation priorities and owners.

No platform item declares support. This is a gap, not a planned-delivery claim.

Decide whether observed verification supports closure of a finding or requires a separately approved, time-bound exception.

No platform item declares support. This is a gap, not a planned-delivery claim.

Review changed supplier terms and assurance evidence against dependent services, accountable owners and unresolved exposure.

No platform item declares support. This is a gap, not a planned-delivery claim.

Assess replacement dependencies, portability evidence and retained obligations before accepting a supplier exit plan.

No platform item declares support. This is a gap, not a planned-delivery claim.

Compare observed recovery time and data restoration with service and business commitments, retaining untested scenarios and evidence gaps.

No platform item declares support. This is a gap, not a planned-delivery claim.

Identify incompatible recovery sequences and shared-resource assumptions before agreeing a service recovery exercise plan.

No platform item declares support. This is a gap, not a planned-delivery claim.

Review schema, meaning and quality changes with affected producers and consumers before accepting migration conditions.

No platform item declares support. This is a gap, not a planned-delivery claim.

Agree scoped quality expectations and evidence requirements when consumers need different freshness, completeness or accuracy.

No platform item declares support. This is a gap, not a planned-delivery claim.

Trace an observed software incident through identified deployed components and service dependencies to affected business processes and owners, distinguishing confirmed disruption, possible exposure and missing evidence to prioritize response.

No platform item declares support. This is a gap, not a planned-delivery claim.

Interpret the primitive, typing, governance-grammar and lifecycle clauses relevant to a proposed decision, identifying permitted representations and constraints without claiming that a processor enforces them.

Select sourced HTTP, IT-domain and provenance concepts for a service description, checking the meaning and attribution of each assertion. Vocabulary does not implement the service or prove its behavior.

Use sourced gRPC, GraphQL and WebSocket concepts to describe request, response and notification boundaries in a payment example. Application payment rules and delivery guarantees require separate definitions and evidence.

Use sourced JDBC, Kafka and AMQP concepts to describe transaction and messaging boundaries in a settlement example, exposing the recovery assumptions that vocabulary alone cannot establish.

Prepare a source-linked shortlist of architecture, quality and regulatory requirements for a bounded IT review.

Compare revised financial-resilience, delivery and service-management source content with the selected package versions and identify obligations needing renewed adopter review. A source update does not itself change accepted obligations.

Trace a non-normative modeling question to its explanations and recorded decision status.

Turn a demonstrated modeling limit into a reviewable compatibility-aware Change Proposal.

Incorporate an approved grammar change with explicit compatibility and migration boundaries.

Replace a document-only change with an attributable, revision-bound definition decision.

Turn competing source-revision candidates into attributable definition drafts for review.

Give an integration client a policy-filtered, pinned context snapshot without granting authority to change systems.

Refresh a downstream view from committed changes without repeated full polling.

Review versioned findings with explicit applicability, input identity and missing evidence.

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.

Trace affected definitions and obligations, then record what remains unknown before deciding.

Obtain a read-only answer whose claims can be checked against authorized definition snapshots.

Assemble an ADR pack and evidence summary from the same pinned inputs, then review the substantive result.

Perform a named authorized operation and retain enough evidence to decide whether recovery is needed.

Produce a scoped artifact through an attributable local method, checks and human review.

Reproduce a pinned local delivery environment and carry the same declared artifact checks into controlled CI publication.

Turn a pinned artifact and its captured journal into inspectable candidates without confusing generated work with deployed behavior.

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.

Create, query and revise typed definitions through the REST contract, inspecting validation, revision and access responses without treating a successful draft write as approval.

Check a selected adapter's transport, authority and failure contract against a named integration, distinguishing supported operations from planned adapter coverage.

Post a candidate to a declared panel and inspect schema, identity, confidence-envelope and rejection responses under the client/server contract. Acceptance into collection is not definition approval.

Request sealing or abandonment of a contribution collection and inspect concurrent-intake outcomes and snapshot readiness. Closing collection does not approve or activate a definition.

Retrieve stored candidates and their captured evidence to inspect provenance and conflicting assertions, making missing audit, integrity or promoted-draft links explicit.

Resolve eligible steps from workflow configuration and recorded outcomes on a supported adapter; leave dispatch to the host rather than treating resolution as execution.

Check a proposed write set against a matched schema and inspect structured-data or Markdown-metadata violations before writing. Passing validation does not establish prose quality or acceptance.

Read correlated session-journal records to reconstruct captured harness invocations and their outcomes, distinguishing absent records from evidence that no action occurred.

Select portfolio, program, team and specialist roles for a delivery responsibility and make their boundaries explicit without treating a role definition as an authenticated authority grant.

Choose a domain or practice playbook for a named task and inspect its applicability and required evidence; reusable guidance does not prove agent adherence.

Specify the sequence of roles, context and artifacts for a ceremony, identifying human-decision checkpoints separately from the planned implementation that authenticates them.

Identify the versioned instructions governing a role's engineering work and distinguish advisory guidance from requirements enforced by separate executable gates.

Select a schema and Markdown template for a named deliverable and inspect required metadata, content and references before using them as a write contract.

Set up a selected harness, organization and host combination while preserving existing work, checking version compatibility separately from the manual setup route.

Run pinned artifact contracts and environment-specific checks through a configured publication pipeline, inspecting failures before publication; publication is not production deployment acceptance.

Derive typed Blackboard candidates from supplied pinned artifacts and journals, inspecting provenance and uncertainty before the separate client-owned draft-promotion step.

Keep typed IT definitions, their review lenses, authorizations and decision sessions coherent so every review works from the same attributable inventory.

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.

Run revision-pinned acquisition, review its coverage limits and register the resulting candidates as drafts, keeping source revision distinct from deployed reality.

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.

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.

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.

Maintain typed definitions through the API and retrieve their stable identities, current revisions and retained history as one governed source. Apply tenant/object access and retention boundaries; a stored draft is not accepted intent.

Distinguish collection closure from definition approval, validate revision-bound lifecycle changes and inspect dependent eligibility after foundation invalidation. Where the notification route is available, inform authorized consumers without conflating event delivery with approval.

Collect independent candidates under declared panel contracts and revisit their retained provenance to compare conflicting assertions. Contribution acceptance and evidence retention do not themselves seal a board or promote an approved definition.

Select coherent definition revisions through the API, supply pinned inputs and Norms to evaluation, and compare verdicts across rule revisions with explicit applicability and unknown states. Repeatability applies to identical evaluation inputs, not changing live systems.

Resolve an eligible operation and its supported adapter, apply declared authority and execution limits, then interpret the receipt against that adapter's failure contract before deciding on recovery. Wider adapters and complete execution controls require their own acceptance.

Provide coherent, policy-filtered definition context through a qualified API or MCP route so model requests retain revision and access boundaries. Context access alone neither grants effect authority nor validates generated answers.

Represent a scoped governance concern using the fixed primitive roles and domain Archetypes together, exposing relationships and concerns the chosen representation cannot express. A valid representation does not establish universal model adequacy.

Define domain vocabulary over the fixed subject types, identify its versioned dependencies and specify how typed definitions pass through correction, review and lifecycle change. Processors implement the specified controls.

Express governing intent as a Directive and evaluable Norms, and specify the review and activation boundaries of their Ascriptions. Grammar and lifecycle meaning remain distinct from runtime enforcement.

Relate selected architecture, quality and regulatory concepts to a common adopting concern, retaining clause provenance and unresolved interpretation or binding decisions. Source-content reuse does not certify legal completeness or compliance.

Type a service, its protocol boundaries and the attribution of each assertion using selected protocol and domain vocabulary, without mistaking a schema for an adapter.

Trace a modeling limit through hypotheses, cases and recorded decisions, identify missing discriminating evidence and prepare a compatibility-aware Change Proposal where warranted. A research record is not an accepted model change or proof that an experiment ran.

Resolve eligible work, supply configured guidance, select a model route and correlate captured invocations for a supported local execution. Host dispatch and probabilistic generation remain distinct from deterministic workflow controls.

Choose the deliverable's schema and template, resolve the applicable contract and inspect violations in a mediated write set before writing. Structured validation and metadata checks do not replace substantive review or acceptance.

Assign responsibilities from the role catalog, connect their ceremonies and handoffs, and select the practices and instructions each role needs. Qualify the harness, template and host combination separately from adopting the operating model.

Bind an advancement decision to the exact artifact revision and human authority, constrain the resulting work through grants and sequencing, and retain the decision trail. This gate remains planned; existing grants and journals do not authenticate approvers.

Produce and reconcile Git-managed artifacts using versioned deliverable contracts and captured journals, retaining evidence for review. Reproducible installation and CI publication use separately qualified routes alongside manual local setup.

Correlate pinned artifact revisions with captured invocation history and derive typed candidates whose provenance, uncertainty and source limitations remain inspectable. Candidate contributions are neither accepted definitions nor evidence of deployed systems.

Align an architect's dependency review and an AI-assisted enquiry on the same typed, versioned definition basis, tracing scope, access and interpretation differences before making a decision. A shared representation does not prove live-state correspondence or answer quality.

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.

Carry a proposed governance change through explicit grammar, revision-bound review and authorized lifecycle transitions, including human decision boundaries. A research-driven model revision follows its own acceptance process; collection sealing is not activation.

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.

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.

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.