Skip to main content

System Design

Persisting provides durable infrastructure for Agent execution and trajectory history. This section focuses on the current public product path:

  • pVisor virtualizes and governs one Agent Run;
  • pChronicle organizes durable trajectory Sources into queryable Datasets.

Gateway, OverlayFS, and OverlayNet are pVisor runtime mechanisms. Where available, stable Run identity connects the domains, but each also has a standalone entry path.

Persisting product domains and integration

Cross-product contract​

Configured pVisor capture
  Gateway trajectory events ─┐
  pVisor lifecycle records ──┴─> canonical event Source ─┐
Pinned external Sources                                  │
  ATIF / ACTF / OpenAI Messages / Storyline ─────────────┴─> Snapshot
                                                               └─> normalized Dataset views

Attempt finalization writes a private, versioned Run Bundle and leaves Effects staged for later review/apply/drop without pChronicle. Configured capture sends Gateway trajectory events and pVisor lifecycle records, including the Evidence those records carry. The full Bundle and its Artifact, lineage, Effect, and broader Evidence inventory remain local unless moved separately.

External file and Storyline Sources are pinned and normalized directly without passing through pVisor or becoming canonical events. Each path retains source-specific guarantees; ingestion does not add Evidence that its Source did not provide.

The ownership boundary is deliberately simple:

  • pVisor owns execution. It defines one Run's boundary and its model, network, and filesystem runtime drivers. Its private Run Bundle remains useful even when no history is captured.
  • pChronicle owns history. It records canonical events and terminal facts, then provides Dataset queries, exchange, and revision lineage.

This separation is a practical choice for users: start with execution or history independently, and add the capture handoff only when the question you need to answer crosses both domains.

Continue by question​

Delivery state is reported in the product Design pages and Project Engineering Notes. Target architecture is not evidence that a capability is implemented.