ProcessScout

Business-process orchestration

One business rule. All the way to execution.

Explore the Northstar example workspace. Follow an invoice-routing rule through six stages, then open the generated workflow and recorded sandbox results.

Book a walkthroughCheck execution targets

Need help identifying the right change? Start with an Edge guided assessment.

ProcessScout/ Northstar Office SupplyExample workspace · Sandbox run
01 / 06 · Capture

Start with the work, as it happens.

Capture meetings, screen walkthroughs, documents and example data. Keep every business rule connected to the work behind it.

Record the context. Keep the detail.Video + screen + transcript
Project Kickoff — example transcript

  1. Project leadLet’s start with the work we want to improve: invoice handoffs and the time spent chasing missing information.

  2. OperationsWe’ll bring the current SOP, walk through the process and compare a few example invoices.

  3. Process ownerKeep the final approval with the team. First, make sure every invoice reaches the right reviewer.

1 hour process walkthrough — example transcript

  1. WalkthroughExample excerpt from a process walkthrough. The screen content is obscured.

  2. Process stepReview the working document and identify the information needed at the next handoff.

  3. Evidence noteConnect the observed step to a process rule for the team to review.

Northstar / Evidence

Meeting recording · Example excerpt

Project Kickoff

A shared starting point: the goal, the people and the evidence to gather.

Read the example transcript

  1. Project leadLet’s start with the work we want to improve: invoice handoffs and the time spent chasing missing information.

  2. OperationsWe’ll bring the current SOP, walk through the process and compare a few example invoices.

  3. Process ownerKeep the final approval with the team. First, make sure every invoice reaches the right reviewer.

Illustrative, silent 12-second excerpt with captions and an AI-generated meeting image.

Northstar / Evidence

Screen recording · Example excerpt

1 hour process walkthrough

Follow the real sequence of work, with source content kept private.

Read the example transcript

  1. WalkthroughExample excerpt from a process walkthrough. The screen content is obscured.

  2. Process stepReview the working document and identify the information needed at the next handoff.

  3. Evidence noteConnect the observed step to a process rule for the team to review.

Illustrative, silent 12-second excerpt with captions. Screen text is permanently obscured.

Invoice evidence lineageSources → business rule
Invoice evidence lineage PS-SRC-02 / DOCUMENTInvoice handling SOPOwner + amount rules PS-SRC-01 / CONVERSATIONTeam walkthroughHow the handoff happens PS-SRC-03 / EXAMPLE DATAExample invoicesContext from the work PS-RULE-01Missing owner takesprecedence over amount.Sources retained for review linksHuman review

Source IDs match the linked workflow evidence package.

PS-SRC-02Invoice handling SOPOwner required · Manager review above $1,000↗
PS-SRC-01Walkthrough notesIncomplete invoices return for information↗
PS-SRC-03Example invoicesOwned, unowned and threshold cases↗
PS-RULE-01

“Missing owner takes precedence over amount.”

Open the source notes
PS-SRC-02 → PS-RULE-01Northstar · PS-RULE-01
02 / 06 · Understand

An absent owner sends work backwards.

Follow the invoice handoff and see where missing information creates rework. Connect each step to the evidence behind it.

Invoice routing logicRule → review queue
Invoice routing logicPS-RULE-01 / INVOICE QUEUE CLASSIFICATION INPUTInvoice receivedOwner + amount Ownerpresent? Request informationneeds_information yesno Amount> $1,000? Manager reviewmanager_reviewStandard reviewstandard_review yesnoMissing owner takes precedence

Queue classification only · approval stays with the team.

Supporting evidence

The SOP and walkthrough notes connect the missing-owner rule to the information the next reviewer needs.

Inspect the rework evidence
Missing owner → request informationNorthstar · PS-RULE-01
03 / 06 · Decide

Fix the process. Then choose the right automation.

Compare a clearer checklist with an automated queue rule. Choose consistent routing while keeping invoice approval with the team.

Scenario comparisonAlternatives → decision
Scenario comparisonA / PROCESS CHANGEClarify the checklistApproachManual checkDependencyTeam adoptionReviewProcess owner B / SUPPORTED AUTOMATIONClassify the review queueApproachRule-based routingDependencySystem accessReviewTests + approval Selected: route for human review

Invoice example · see the linked decision record.

Decision record

Every invoice gets a review queue: request information, manager review or standard review. The team makes the approval decision.

Read the decision and alternatives
Decision → route to the right reviewerNorthstar · PS-RULE-01
04 / 06 · Build

A business rule becomes an executable artifact.

Turn the designed owner and amount rules into native n8n JSON. Inspect the generated workflow and trace it back to the decision.

Invoice routing logicRule → review queue
Invoice routing logicPS-RULE-01 / INVOICE QUEUE CLASSIFICATION INPUTInvoice receivedOwner + amount Ownerpresent? Request informationneeds_information yesno Amount> $1,000? Manager reviewmanager_reviewStandard reviewstandard_review yesnoMissing owner takes precedence

Queue classification only · approval stays with the team.

Workflow IR → ProcessScout compiler → native n8n JSONInspect generated artifact
Open the workflow IRSee conversion findings
PS-RULE-01 → n8n native outputNorthstar · PS-RULE-01
05 / 06 · Validate

Test the rule before the handoff.

Check the workflow structure, review the conversion report and compare expected queues with real n8n engine results.

Workflow readinessStructure + conversion + execution
Workflow readinessREADINESS / SEPARATE CHECKS, ONE RELEASE DECISION 01 / SCHEMAWorkflow structureInputs + graph02 / CONVERSIONTarget mappingsExact · adapted · review03 / ENGINESandbox executionExpected vs actual RELEASE GATE / STILL REQUIREDReview target readinessConfigured access · approved version · human decision

Read the recorded results below for the actual checks.

Workflow structureValidated with the product WorkflowIRDocument contract.passed
Target compatibilityTarget-specific mappings are ready for review.approval required
n8n engine executionNative workflow executed in the n8n sandbox.success
Business-rule acceptance5/5 queue assertions passed. Native n8n engine status: success.passed
Release checklist

Bring the tested workflow, target configuration and approved version together for release.

Read the complete validation result
Compiler report + target-engine checksNorthstar · PS-RULE-01
06 / 06 · Release

A tested result. A clear next step.

Explore the sandbox run, from invoice inputs to queue results. Carry the test record into an informed release decision.

n8n · Sandbox runpassed
INV-101standard_reviewpassed
INV-102manager_reviewpassed
INV-103needs_informationpassed
INV-104standard_reviewpassed

5/5 queue assertions passed. Native n8n engine status: success.

Open the engine execution record
Recorded sandbox run

Next: configure the target, complete environment checks and approve a locked version for release.

Sandbox run → recorded queue resultsNorthstar · PS-RULE-01

Explore the workflow · Open the compiler and run records

View the files

Open the evidence. Inspect the output.

See the complete package behind the example: source notes, workflow design, native n8n output and the sandbox execution record.

Example workspace · Sandbox run. Explore the authored source notes and workflow design, generated n8n artifact and recorded engine results. The package includes the tested source revision and reproduction steps.

Source notes

Fictional walkthrough, policy and invoice export.

source-notes.md

Decision

Authored option comparison and acceptance criteria.

decision.md

Workflow IR

Manually authored canonical input validated by the product contract.

workflow-ir.json

Generated n8n workflow

Untouched native content emitted by the existing compiler.

n8n-workflow.json

Validation result

Separate schema, fidelity and real behavior checks.

validation.json

Product fidelity report

Actual product mapping findings and approval-required disposition.

fidelity-report.json

Actual sandbox result

Five invoice cases with expected and actual queue values.

run-result.json

Raw native execution

Actual isolated n8n execution record.

n8n-execution.json

CLI execution log

Captured runtime output with only host-directory redaction if needed.

n8n-cli.log

CLI harness

Explicit manual entry wrapper; generated nodes remain unchanged.

sandbox-harness.json

IF mapping diagnostic

Separate untouched amount-branch compiler probe.

branch-diagnostic-n8n-workflow.json

IF diagnostic execution

Actual branch diagnostic record; compare with the pre-fix baseline.

branch-diagnostic-n8n-execution.json

Runtime provenance

Image digest, source hashes and commands.

runtime-environment.json

Synthetic invoices

Five acceptance inputs with separate expected queue values.

invoices.json

Reproduction instructions

Dependencies, commands, evidence boundaries and integrity verification.

README.md

Reproduction script

Imports the actual compiler and repeats the isolated run.

reproduce.py

Public sandbox replay

Replays the native harness using Docker and Python; no product source access required.

run-sandbox.py

File checksums

SHA-256 hashes for verifying the downloaded package.

SHA256SUMS

Unmodified compiler baseline

Pre-fix engine run with the original compiler for comparison.

baseline/run-result.json

The complete sequence

  1. Capture

    Capture meetings, screen walkthroughs, documents and example data. Keep every business rule connected to the work behind it.

  2. Understand

    Follow the invoice handoff and see where missing information creates rework. Connect each step to the evidence behind it.

  3. Decide

    Compare a clearer checklist with an automated queue rule. Choose consistent routing while keeping invoice approval with the team.

  4. Build

    Turn the designed owner and amount rules into native n8n JSON. Inspect the generated workflow and trace it back to the decision.

  5. Validate

    Check the workflow structure, review the conversion report and compare expected queues with real n8n engine results.

  6. Release

    Explore the sandbox run, from invoice inputs to queue results. Carry the test record into an informed release decision.

Recorded engine cases

CaseExpectedActualResult
INV-101{"invoice_id":"INV-101","queue":"standard_review"}standard_reviewpassed
INV-102{"invoice_id":"INV-102","queue":"manager_review"}manager_reviewpassed
INV-103{"invoice_id":"INV-103","queue":"needs_information"}needs_informationpassed
INV-104{"invoice_id":"INV-104","queue":"standard_review"}standard_reviewpassed
INV-105{"invoice_id":"INV-105","queue":"needs_information"}needs_informationpassed

5/5 queue assertions passed. Native n8n engine status: success.

Generated 2026-09-22T06:31:22.083646+00:00 · Compiler backend/services/workflow_ir/providers/n8n/compiler.py:N8nWorkflowCompiler 1.0.1 · n8n 2.39.10
Product source revision b7556e0ed1164186435816fa2ab7fd9c73aee069

One connected record of the work.

A rule carried into executable output
A documented business rule is represented in ProcessScout’s workflow IR, compiled into a native artifact and tested in n8n. The package records the compiler and engine versions.
Five invoice cases, tested
The sandbox run checks missing owners, amount thresholds and standard review. Compare every expected queue with the actual n8n result.
A clear release handoff
Keep the test record with the workflow. Add the target configuration, environment checks and approved version for the release owner to review.

See what your process could become.

Bring a workflow, a bottleneck or a client engagement. We’ll show you the route from evidence to an executable output.

Book a walkthroughExplore Edge
Build details
Build
os-bd3152dd322126ec
Built at
2026-10-16T00:50:39.151Z
Build record