Agentic workflow memory

The work keeps moving.
Understanding should remain.

Orbweaver gives workflows involving people, agents, CI, tickets, and operational systems a durable semantic review surface—without pretending to run those workflows.

Authoritative source on GitHub ↗

When responsibility is distributed, the work can be technically complete while remaining hard to explain. Orbweaver turns an approved, evidence-backed workflow snapshot into something people can inspect, compare, discuss, and retain.

meaning → review → memory
People, agents, CI, tickets, systemsexecution stays with the host↓Evidence-backed semantic snapshotstable identities, relationships, provenance↓Orbweaver review surfacevalidate, inspect, annotate, compare↓Durable artifactreview, decision record, portable HTML
01

The intended boundary

Host owns

Execution and facts

Authentication, data retrieval, orchestration, retries, action execution, retention, and the translation of domain records into evidence-backed semantic snapshots.

Orbweaver owns

Review and understanding

Validation, deterministic rendering, semantic inspection, annotations, comparison, and portable artifacts. It never needs to own your credentials or run your workflow.

Not a dashboard in disguise

“Live” means a current host-produced semantic snapshot—not an uncontrolled stream of changing pixels. The host decides when a snapshot is refreshed or retained.

02

Where it helps

01

Agent-assisted delivery

Intent, implementation, test evidence, review, release, rollback, and accountable human approval.

02

CI/CD review

Build, test, security, deployment, rollback, and evidence relationships without making Orbweaver the pipeline.

03

Incident recovery

Signals, hypotheses, mitigations, owners, decisions, and unresolved risks as a reviewable snapshot.

04

Legacy workflows

Business processes, exception paths, planning flows, and cross-application dependencies made inspectable.

03

A trustworthy workflow

Observed facts or approved AI proposalinference remains distinguishable from evidence↓Semantic graph with source referencesno coordinates or generated SVG↓Validate and inspectadd reviewable constraints, decisions, and risks↓Human review and explicit acceptancethen snapshot, compare, or publish

An agent may propose a graph, annotation, or revision. It does not establish that a relationship is factually true. Validation checks the contract; people and responsible systems still decide what to rely on.

04

The natural next question: what changed?

Stable entity and relationship IDs make workflow snapshots comparable over time. A changed approval gate, missing evidence path, new dependency, or recovered exception route can become an explainable semantic difference—not just a fresh diagram.

  • Retain stable identities across snapshots.
  • Carry status, evidence, annotations, and timestamped provenance as explicit data.
  • Compare semantic changes before interpreting operational significance.
  • Publish a portable artifact when a review or decision should outlive the host application.
Execution belongs to the workflow system. Shared understanding belongs in the semantic artifact.