Poesis
Systemic Agentic Framework · Solution
The Systemic Agentic Framework — local agentic SAFe workflows.
The Systemic Agentic Framework: local agentic workflows, explicit artifact contracts and planned evidence-backed SIE integration.
Deterministic decisions support probabilistic agents on declared hosts. Artifact quality, authenticated human gates and effect safety need acceptance; documents are not automatically tested or deployed systems.
Roles and workflows support local work. The three local-tool products use Apache-2.0; the planned SIE bridge has a separate BUSL-1.1 boundary.
Insights · agentic SAFe — running the Scaled Agile Framework with AI agents →
Values
Reviewable methods and explicit control boundaries.
- Value Partial
Build toward traceable delivery.
Generate reviewable artifacts through bounded workflows, then carry evidence forward through separate build, deployment and re-observation stages.
Supported by Affordances(1)
Supported by Capabilities(1)
- Value Partial
Make agentic work reviewable.
Combine role contracts, workflow decisions and artifact evidence, with planned authenticated human gates bound to exact revisions.
Supported by Affordances(1)
Supported by Capabilities(1)
Supported by Features(2)
- Value Partial
Coordinate through shared artifacts.
Collaborate through versioned contracts and Git-backed artifacts, reconciling separate journals, merges and version differences explicitly.
Supported by Capabilities(1)
Supported by Features(1)
- Value Partial
Control local delivery data.
Choose local tools and Git workflows, with explicit policies for model/tool egress, telemetry, remotes and backups.
Supported by Affordances(1)
Supported by Capabilities(2)
Supported by Features(2)
- Value Partial
Reuse delivery evidence.
Derive candidates from pinned artifacts and journals through the planned bridge, then review and promote them through a client-owned stage.
Supported by Capabilities(1)
Capabilities
Local controls and method content, with planned approval and sourcing integrations.
- Capability Implemented
Deterministic workflow controls
Coordinate eligible workflow steps, task-specific model routes and resolved guidance against recorded outcomes, making local orchestration decisions traceable. Resolution and journals exist on supported adapters; hosts dispatch work, guidance does not prove adherence, and generated content remains probabilistic.
Addresses Pain points(2)
Supports Values(3)
Serves Use cases(1)
Used by Actor types(3)
- Capability Partial
Scoped artifact contract checks
Turn shared artifact schemas and templates into checks on mediated write sets so delivery outputs can be validated against declared contracts. Structured-data and Markdown-metadata checks exist; contract resolution, parsing and atomicity remain integration boundaries, while substantive prose quality and unmediated writes are outside their coverage.
Addresses Pain points(1)
Supports Values(3)
Serves Use cases(1)
Used by Actor types(2)
Realized by Features(2)
- Capability Partial
Agentic SAFe operating model
Organize agentic delivery responsibilities and ceremonies through a shared catalogue of roles, workflow sequences, practice playbooks and versioned instructions. Role and guidance content exists; workflow alignment and behavioral quality remain under integration, and execution needs accepted harness, template and host combinations.
Addresses Pain points(1)
Supports Values(3)
Serves Use cases(1)
Used by Actor types(3)
Realized by Features(4)
- Capability Partial
Human-gated advancement
Make workflow advancement depend on review decisions bound to exact revisions and scope, supported by eligible-step resolution, agent write grants and recorded outcomes. Authenticated human approval is planned; existing sequencing, grants and journals do not prove human identity or acceptance.
Addresses Pain points(2)
Supports Values(3)
Serves Use cases(1)
Used by Actor types(3)
Realized by Features(4)
- Capability Partial
Local-first delivery plane
Maintain a local delivery baseline by combining Git-backed artifacts, separate execution journals and contract checks when agent outputs are reconciled. Manual setup is available; collaboration, contract integration and transaction behavior remain incomplete. Installer and CI/publication pipelines are planned optional extensions, independent of hosted offerings.
Addresses Pain points(2)
Supports Values(5)
Serves Use cases(2)
Used by Actor types(2)
- Capability Partial
Delivery evidence sourcing
Combine versioned workspace artifacts with captured execution journals to derive reviewable definition candidates carrying provenance and uncertainty. Bridge inference and draft promotion are planned; evidence covers captured work only, and contributions establish neither accepted definitions nor tested or deployed systems.
Addresses Pain points(2)
Supports Values(4)
Serves Use cases(2)
Used by Actor types(2)
Realized by Features(3)
Products
Four products with distinct local and planned integration scopes.
- Product · recorded v1.0 Implemented Agentic Harness
Give local agentic work explicit steps, artifact checks and traceable decisions.
Product features- Feature · milestone v1.0 Implemented Workflow & step resolution
- Feature · milestone v1.0 Implemented Skill and instruction prompt injection
- Feature · milestone v1.0 Implemented LLM resolution
- Feature · milestone v1.0 Implemented Artifact validation
- Feature · milestone v1.0 Implemented Agent write authorization
- Feature · milestone v1.0 Implemented Logging
- Product · recorded v0.1 Partial SAFe Agentic Organization
Organize agentic delivery around clear roles, shared practices and reviewable artifacts.
Product features- Feature · milestone v1.0 Implemented Agents
- Feature · milestone v1.0 Partial Skills
- Feature · milestone v1.0 Partial Workflows
- Feature · milestone v1.0 Implemented Instructions
- Feature · milestone v1.0 Partial Artifacts
- Product · recorded v0.0 Partial Agentic Workspace
Keep delivery artifacts in your working tree with a repeatable path to setup and checks.
Product features- Feature · milestone v1.0 Partial Workspace data plane
- Feature · milestone v1.0 Planned Installer
- Feature · milestone v1.0 Planned CI/CD artifacts pipelines
- Product · recorded v0.0 Planned SAF SIE Bridge
Turn captured delivery history into proposals for governed context.
Product features- Feature · milestone v1.0 Planned Harness history sourcing
Qualities
What runs locally, and what waits for a human.
- Runs where you work Partial No delivery-plane tenancy to adopt
The harness and workspace operate on local checkouts under Apache-2.0. Hosts and model routes are declared rather than assumed.
- Human-gated advancement Planned Agents propose; people advance
Workflow advancement passes through explicit gates. Authenticated gates and effect safety need acceptance before autonomous progression is claimed.
- Contracted artifacts Partial Written artifacts are checked against a schema
Mediated writes are validated against matched schemas. Scope is structured data and Markdown metadata; prose quality has a separate boundary.
Usage
Reviewed agentic delivery use cases
- Use case Implemented
Approve an agent resource and action mandate
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.
Supported by Features(1)
Addresses Pain points(1)
Realizes Values(6)
Performed by Actor types(3)
- Use case Implemented
Qualify model routing for a workload
Compare candidate model routes against workload-specific quality, cost and disclosure criteria using retained evaluation evidence.
Supported by Features(1)
Addresses Pain points(1)
Realizes Values(4)
Performed by Actor types(2)
- Use case Implemented
Qualify instruction delivery on another host
Verify that a target host receives the pinned instructions and declared checks, distinguishing delivery from model adherence before migration.
Supported by Features(1)
Addresses Pain points(1)
Realizes Values(2)
Performed by Actor types(2)
- Use case Partial
Reconcile conflicting parallel agent outputs
Resolve overlapping edits against a shared baseline while retaining attribution and revalidating the combined artifacts before acceptance.
Supported by Features(1)
Addresses Pain points(1)
Realizes Values(1)
Performed by Actor types(2)
- 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 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 Partial
Set up a workspace and publish checked artifacts
Reproduce a pinned local delivery environment and carry the same declared artifact checks into controlled CI publication.
Supported by Capabilities(1)
Addresses Pain points(1)
Realizes Values(4)
Performed by Actor types(2)
- Use case Partial
Reuse captured delivery evidence as definition proposals
Turn a pinned artifact and its captured journal into inspectable candidates without confusing generated work with deployed behavior.
Supported by Capabilities(1)
Addresses Pain points(2)
Realizes Values(4)
Performed by Actor types(2)
- Use case Implemented
Resolve the next eligible workflow step
Resolve eligible steps from workflow configuration and recorded outcomes on a supported adapter; leave dispatch to the host rather than treating resolution as execution.
Supported by Features(1)
Addresses Pain points(1)
Realizes Values(1)
Performed by Actor types(2)
- Use case Implemented
Validate a mediated artifact write
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.
Supported by Features(1)
Addresses Pain points(1)
Realizes Values(1)
Performed by Actor types(2)
- Use case Implemented
Inspect a captured harness invocation sequence
Read correlated session-journal records to reconstruct captured harness invocations and their outcomes, distinguishing absent records from evidence that no action occurred.
Supported by Features(1)
Addresses Pain points(1)
Realizes Values(1)
Performed by Actor types(2)
- Use case Implemented
Assign a delivery responsibility from the role catalog
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.
Supported by Features(1)
Addresses Pain points(1)
Realizes Values(1)
Performed by Actor types(2)
- Use case Partial
Select a practice playbook for a delivery task
Choose a domain or practice playbook for a named task and inspect its applicability and required evidence; reusable guidance does not prove agent adherence.
Supported by Features(1)
Addresses Pain points(1)
Realizes Values(1)
Performed by Actor types(2)
- Use case Partial
Define a delivery ceremony and its handoffs
Specify the sequence of roles, context and artifacts for a ceremony, identifying human-decision checkpoints separately from the planned implementation that authenticates them.
Supported by Features(1)
Addresses Pain points(1)
Realizes Values(1)
Performed by Actor types(2)
- Use case Implemented
Select versioned instructions for an engineering role
Identify the versioned instructions governing a role's engineering work and distinguish advisory guidance from requirements enforced by separate executable gates.
Supported by Features(1)
Addresses Pain points(1)
Realizes Values(1)
Performed by Actor types(2)
- Use case Partial
Define a deliverable schema and template
Select a schema and Markdown template for a named deliverable and inspect required metadata, content and references before using them as a write contract.
Supported by Features(1)
Addresses Pain points(1)
Realizes Values(1)
Performed by Actor types(2)
- Use case Planned
Install a pinned agentic workspace
Set up a selected harness, organization and host combination while preserving existing work, checking version compatibility separately from the manual setup route.
Supported by Features(1)
Addresses Pain points(1)
Realizes Values(1)
Performed by Actor types(1)
- Use case Planned
Publish artifacts through configured CI checks
Run pinned artifact contracts and environment-specific checks through a configured publication pipeline, inspecting failures before publication; publication is not production deployment acceptance.
Supported by Features(1)
Addresses Pain points(1)
Realizes Values(1)
Performed by Actor types(2)
- Use case Planned
Extract definition candidates from delivery history
Derive typed Blackboard candidates from supplied pinned artifacts and journals, inspecting provenance and uncertainty before the separate client-owned draft-promotion step.
Supported by Features(1)
Addresses Pain points(1)
Realizes Values(1)
Performed by Actor types(2)
- Use case Implemented
Run an agentic workflow with deterministic controls
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.
Supported by Capabilities(1)
Addresses Pain points(2)
Realizes Values(3)
Performed by Actor types(3)
- Use case Partial
Check a produced artifact against its contract
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.
Supported by Capabilities(1)
Addresses Pain points(1)
Realizes Values(3)
Performed by Actor types(2)
- Use case Partial
Adopt the agentic SAFe operating model
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.
Supported by Capabilities(1)
Addresses Pain points(1)
Realizes Values(3)
Performed by Actor types(3)
- Use case Partial
Gate an advancement on an authenticated human decision
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.
Supported by Capabilities(1)
Addresses Pain points(2)
Realizes Values(3)
Performed by Actor types(3)
- Use case Partial
Deliver from a local-first, reproducible plane
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.
Supported by Capabilities(1)
Addresses Pain points(2)
Realizes Values(3)
Performed by Actor types(2)
- Use case Partial
Turn delivery history into definition candidates
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.
Supported by Capabilities(1)
Addresses Pain points(2)
Realizes Values(3)
Performed by Actor types(2)
- Use case Partial
Make review and activation boundaries explicit
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.
Supported by Affordances(1)
Addresses Pain points(2)
Realizes Values(3)
Performed by Actor types(4)
- 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
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)