Catalog view Human readable Agent manifest Open OKF
Workflow discovery Observe, capture, review, replay

Discovery .
Capture work as it runs

Observed steps become replayable evidence.

Point Discovery at the approval path you want to replace. It watches work move through screens, inboxes, spreadsheets, and approvals, then produces a reviewed manifest for Proto: entities, rules, exceptions, and the evidence behind each one.

Run a Discovery Open the record
Source evidence stays attached Rules need owner review Proto receives a manifest
Live Discovery [ DISC-3309 ]
1,284 Entities mapped
317 Rules in review
42 Workflow runs seen
Phase Scope Observe Extract Review
Snapshot [ ACTIVE ]
  • Source Workflow
  • Mode Observe
  • Gate Review
  • Output Manifest
Agent class DISC-X1
Record Extraction Review Handoff

Evidence record · Illustrative AP approval capture

Open one run. Follow every decision.

Discovery begins with a completed piece of work, not a blank workflow canvas. The record below keeps source, decision, uncertainty, and owner review in one reading path.

DISC-3309 Invoice approval · North region
Owner review
  1. Source
    Invoice enters the review queue

    Vendor, amount, purchase order, and supporting file are attached to the observed step.

    Evidence linked
  2. Decision
    Owner checks the matching rule

    The candidate rule names the fields consulted and preserves the route taken when the match fails.

    Rule drafted
  3. Question
    Exception ownership is ambiguous

    The unresolved branch stays outside the runnable manifest until Finance names an owner.

    Promotion held
  4. Handoff
    Reviewed logic moves to Proto

    Entities, gates, exception routes, and evidence references travel together.

    Pending review

The evidence stays closer than the abstraction.

Each candidate rule points back to a surface an operator actually used. Discovery does not turn incidental UI detail into policy without review.

Screen path Fields, actions, and branch points

What the operator saw and which path they chose.

Document trail Files, exports, and approval notes

What supported the decision outside the primary system.

System record Events, API reads, and queue state

What the underlying systems recorded before and after the step.

Review gate

Uncertainty remains visible.

A useful capture distinguishes an observed fact from a proposed rule. Questions do not disappear into generated workflow code.

Observed

The operator checked purchase-order status before approval.

Keep as evidence
Proposed

Invoices without a purchase order should route to Finance operations.

Needs owner decision
Blocked

The exception queue has no named escalation owner.

Exclude from manifest

Proto handoff

A manifest, not a mood board.

Proto receives the operating contract it needs to replay the work and the evidence people need to challenge it.

Entities
Invoice, vendor, purchase order, review queue, owner
Rules
Validated field checks, routes, thresholds, and exception branches
Gates
Named approvals, unresolved questions, and manual fallbacks
Evidence
Source references retained beside every promoted decision
Run Discovery Promote with evidence

Capture one workflow Then let Proto run it.

Start with a live process, keep the evidence attached, and promote only what survives review.

Start discovery See Proto