Skip to main content

Console V2: Prototype Walkthrough & Operations Notes

:::info Archived Prototype Documentation This document preserves the operations guide, process execution workflows, and dashboard interface procedures from the Console V2 (Weave) research prototype for technical reference. Console V2 is not available as a public commercial service, and live SaaS endpoints have been decommissioned. :::

1. The Process Studio Interface​

In the V2.5 / V2.6 architecture, the primary interface centered around the Process Studio rather than an agent chatbot directory.

┌────────────────────────────────────────────────────────────────────────┐
│                        WEAVE PROCESS STUDIO                            │
├────────────────────┬───────────────────────────────────────────────────┤
│ Processes          │ Process: Invoice Reconciliation & Payout (v1)     │
│ ├── Active         ├───────────────────────────────────────────────────┤
│ ├── Drafts         │ [Webhook Ingress]                                 │
│ └── Archived       │        │                                          │
│                    │        ▼                                          │
│ Triggers           │ [Skill: InvoiceExtractor] (agentictools/skills)   │
│ ├── Webhooks       │        │                                          │
│ └── Schedules      │        ▼                                          │
│                    │ [Condition: Amount > $10,000?]                    │
│ Approvals          │       ├── YES ──► [Approval: CFO Sign-off] ──┐    │
│ ├── Pending (3)    │       └── NO  ───────────────────────────────┤    │
│ └── History        │                                              ▼    │
│                    │                           [Tool: Stripe Payout]   │
│ Telemetry          │                                              │    │
│ └── Live Runs      │                                              ▼    │
│                    │                           [Step: Complete]        │
└────────────────────┴───────────────────────────────────────────────────┘

2. Step-by-Step Process Workflows​

Workflow 1: Composing a Business Process​

Processes could be drafted via the visual canvas, programmatic REST endpoints, or natural-language composition:

  1. Natural-Language Drafting: Post a plain-English workflow description to /api/processes/compose/.
  2. Graph Assembly: The composer synthesizes a new Process record with a draft ProcessVersion and linked ProcessStep nodes.
  3. Step Configuration: Operators configure each node's step type (e.g., webhook, skill, tool, condition, approval).
  4. Publishing: Triggering /api/process-versions/<uuid>/publish/ freezes the version into an immutable graph, preventing accidental mid-run mutations.

Workflow 2: Executing & Monitoring a ProcessRun​

Once published, processes execute through the validated state machine:

  1. Trigger Ingress: An inbound event hits the UUID-scoped trigger endpoint (/api/processes/trigger/<uuid>/).
  2. Run Initialization: The runtime instantiates a ProcessRun in the running state and creates an ExecutionContext populated with the inbound payload.
  3. Step Execution: The ExecutionRuntime traverses the DAG:
    • Evaluates prerequisite step completions.
    • Dispatches tool operations to the ToolRunner, sandboxing file output under MEDIA_ROOT/generated/.
    • Records per-step execution metrics in StepRun and metered token counts in ExecutionUsage.
  4. Terminal Outcome: Once all terminating branches finish, an Outcome record is persisted with the final execution status (completed, failed, or cancelled).

Workflow 3: Managing the Governance Approval Queue​

When a process step of type approval executes or when the PolicyEngine intercepts an action exceeding safety thresholds:

  1. The ProcessRun transitions from running to paused.
  2. An approval card is registered in the ApprovalQueue (core/models.py).
  3. Operator Inspection:
    • The dashboard displays the pending step details, tool arguments, risk level, and prompt lineage.
  4. Resolution:
    • Approve: Post to /api/process-runs/<uuid>/resume/ to continue graph traversal.
    • Reject / Cancel: Post to /api/process-runs/<uuid>/cancel/ to terminate the execution with a failed outcome.

Workflow 4: Deploying the Monica Customer Support Widget​

Monica operated as the standalone customer-facing support surface:

  1. FAQ RAG Setup: Upload customer support manuals and knowledge bases in the Monica settings panel for retrieval-augmented generation.
  2. Widget Embedding: Embed the public chat widget on company web properties: 
    <script 
      src="https://static.pluggedspace.org/widgets/monica.js" 
      data-public-key="YOUR_MONICA_PUBLIC_KEY" 
      async>
    </script>
  3. Origin Allow-List: For security, the backend validates that requests bearing monica_public_key originate from approved domain origins configured in the workspace settings.

3. Preserved REST API Reference​

The core endpoints powering the process runtime include:

RouteMethodsOperational Purpose
/api/processes/GET, POSTList and create tenant processes.
/api/processes/<uuid>/versions/GET, POSTManage process versions; POST creates a draft version.
/api/processes/compose/POSTDraft a process graph from natural language.
/api/processes/trigger/<uuid>/POSTUnauthenticated webhook ingress endpoint.
/api/process-versions/<uuid>/publish/POSTFreeze and publish an immutable process version.
/api/process-runs/<uuid>/start|cancel|resume/POSTExecute state transitions on a process run.
/api/process-runs/<uuid>/step-runs/GETRetrieve step-level audit logs and execution lineage.
/api/process-templates/GETBrowse pre-built process templates.

4. Archive References​