Pegesis Agents

Specialists that think, collaborate, and act — with policy.

Design domain experts, wire their tools, and let the Cognitive Loop coordinate decisions across your stack. Every step is traced, approved, and reversible.

Agent Library

Start with proven specialists

Mix and match prebuilt roles. Tune goals, policy, and tools — then deploy in minutes.

Ops & Routines

Schedulers, service timetables, incident triage, runbook executors.

Operations agent
ApprovalsSLA-aware

Vision & Robotics

Deploy agents that see and act — from thermal and optical detection for safety and maintenance, to autonomous patrols, inventory checks, and robotic manipulators on Orin and Edge devices. Each action follows policy and operates within guardrails.

Vision agent
ROS Edge NVIDIA Orin Thermal AI

Data & Knowledge

ETL, schema induction, graph synthesis, retrieval planning, report drafting.

Knowledge agent
ProvenanceRAG++

Compliance & Audit

IAM checks, least-privilege enforcement, continuous audit, red-team simulations.

Compliance agent
AGS++Trace

Agent Blueprint

Define behavior in a few lines

Agents are declared with roles, capabilities, tools, and policy. Pegesis generates the runtime, connects to the Signal Bus, and enforces AGS++ rules.

Tip: keep goals crisp; let policy govern risks. Use handoff for delegation.
# agents/cleaning-supervisor.yaml
name: cleaning-supervisor
role: "Oversee service routes and ensure SLA compliance"
skills:
  - plan_tasks
  - verify_service
  - summarize_findings
policy:
  approvals:
    - action: dispatch_worker
      require: supervisor
  limits:
    max_zone_radius_m: 50
    max_priority: 3
memory:
  persistence: project
  retrieval:
    strategy: graph+routing
    filters: [site:carlington]
triggers:
  - event: zone_marker.detected
    where: { zone: [5,6,7,8,10] }
  - cron: "*/10 * * * *" # every 10 minutes
handoff:
  - to: compliance-auditor
    when: risk.score >= 0.7
  - to: robotics-patrol
    when: requires_patrol == true
tools:
  - name: work_orders
    actions: [create, assign, close]
  - name: occupancy_api
    actions: [read]
  - name: notifier
    actions: [email, sms]

Composition

Chain specialists. Share context. Reach consensus.

Use playbooks to connect agents into plans. The Cognitive Loop coordinates delegation, critiques, and conflict resolution.

Playbooks

Graph of steps with guardrails, retries, and human-in-the-loop approvals.

  • Plan → Act → Verify → Report
  • Branch on risk / missing data

Delegation

Handoff by policy, capability match, or load. Preserve trace across agents.

  • Critic/Executor pairs
  • Auto-escalate on SLA breach

Consensus

Voting, weighted expertise, or confidence aggregation for high-stakes tasks.

  • k-of-n approvals
  • Risk-aware quorum

Multi-Agent Orchestrator

Shared context over the Signal Bus

All agents read and write to a shared context fabric, streamed over the Signal Bus. The Cognitive Loop runs scheduling, contention control, and drift detection.

  • Backpressure & rate limits per tool
  • Transactional side-effects with dry-run mode
  • Signed decision traces for every step
Orchestrator diagram

Tools & Connectors

Bring your stack

Agents call tools via typed interfaces. Permissions come from AGS++ roles; secrets never leave the vault.

Data

SQL/NoSQL, S3, Blob, Graph, Streams

Operations

Work Orders, CMMS, ITSM, Slack/Email

Perception

Vision, Thermal, IoT/LoRa, ROS

Security

IAM, KMS, Audit, DLP

Safety

AGS++: guardrails, checks, and approvals

Define what agents may see and do. Policies gate tool calls, cap scope, require approvals, and record signed traces for audit.

zone ≤ 50m non-destructive by default require human for priority ≥ 3
{
  "role": "cleaning-supervisor",
  "allow": ["read:occupancy", "create:work_order"],
  "deny": ["delete:work_order"],
  "requireApproval": [{"action":"dispatch_worker","by":"supervisor"}],
  "limits": {"zoneRadiusM":50, "priorityMax":3}
}

Observability

Every thought leaves a trace

Agents retain memory, reason through structured chains of thought, and act within policy. Each decision is logged, explainable, and auditable — ensuring accountability without opacity.

  • Persistent memory with recall and context alignment
  • Chain-of-thought transparency and replay
  • Policy enforcement and compliance trails
Reasoning trace visualization

Developer SDK

Ship agents in hours, not months

Use the Python SDK to register agents, declare tools, and run policy-bound decisions with memory, structured chain-of-thought, and audit-ready logs.

Python

# pip install pegesis
from pegesis import Agent, tool, Memory, Policy

# 1) Declare a tool (auditable, typed I/O)
@tool(name="work_orders.create", version="1.0.0")
def create_work_order(site: str, zone: int, note: str) -> dict:
    # Implementation lives in your infra; SDK records the call and return.
    return {"status": "queued", "site": site, "zone": zone, "note": note}

# 2) Load policy & attach memory (short- and long-term)
policy = Policy.from_file("policies/facilities.json")
mem    = Memory.window(capacity=1024).with_vector_index("events", dims=384)

# 3) Register an agent with chain-of-thought style and compliance guardrails
agent = Agent(
    name="vision-guard",
    role="Detect hazards and escalate within policy",
    policy=policy,
    memory=mem,
    cot="structured"   # structured chain-of-thought trace stored in audit log
)

# 4) Subscribe to events and act under policy
@agent.on("thermal.alert")
def on_thermal(ctx):
    # Retrieve similar incidents for rationale (memory read)
    prior = agent.memory.search("events", query=ctx.signature, k=3)

    # Policy gate: only create work orders when severity meets contract
    if ctx.severity >= policy["SLA.minSeverity"]:
        # Every tool call is recorded with input/output for audit
        return create_work_order(site=ctx.site, zone=ctx.zone, note="Thermal anomaly")

    # Otherwise, store observation and exit
    agent.memory.append("events", {"site": ctx.site, "kind": "thermal", "ok": True})
    return {"status": "observed"}

# 5) Hand-off with full reasoning trace and policy context
@agent.on("vision.object.detected")
def on_object(ctx):
    if ctx.label in policy["restrictedObjects"]:
        return agent.handoff("compliance-auditor", ctx, reason="Restricted object detected")

# 6) Run once or as a service (streamed decisions with signed traces)
if __name__ == "__main__":
    agent.serve(":8081")

Policy (excerpt)

{
  "SLA": { "minSeverity": 0.7, "minCoverage": 0.85 },
  "restrictedObjects": ["weapon", "open_flame"],
  "schema_contract": {
    "audit": { "signed_traces": true, "pii_redaction": "standard" },
    "tools": {
      "work_orders.create": {
        "allowed_hours": "06:00-22:00",
        "required_fields": ["site", "zone", "note"]
      }
    }
  }
}

Memory & CoT

• Short-term window memory for the active run
• Long-term vector index for retrieval (events, incidents, SOPs)
• Structured chain-of-thought captured as a signed reasoning trace
• Policy-aware recall (e.g., PII redaction, retention limits)
• Full audit trail of inputs, tool calls, and outcomes

Deployment

Edge, cloud, or hybrid — your choice

Run agents on GPUs, Apple silicon, or edge boxes (Orin/ARM). Central policy & secrets, local execution.

Cloud

Autoscale workers, observability baked in.

On-prem

Air-gapped runtime with signed updates.

Edge

Low-latency control for robots & sensors.

FAQ

Common questions

How do agents differ from tools?
Tools are typed capabilities (APIs, actuators). Agents are decision-makers that call tools under policy.
Can I require human approval?
Yes. Use AGS++ approvals by action or priority. Every approval is traced and signed.
Do agents run concurrently?
Yes. The orchestrator schedules work, applies backpressure, and resolves conflicts on shared resources.

Put agents to work

See how Pegesis coordinates specialists with end-to-end safety and traceability.