Interactive workflow library

Choose the workflow first. Then decide whether to download, try, verify, or build it.

Start from the source material and operating problem—not a model name or generic service menu. The library recommends a workflow and exposes the honest next paths around it.

Choose the operating shape

Three decisions narrow the library to the right next step.

The recommendation is deterministic and runs entirely in this browser. It does not collect behavioral history or send the choices to a model.

1. What enters the workflow?
2. What matters most?
3. What do you need next?

Showing 5 matching workflows. The URL preserves this selection for sharing or return visits.

Starter downloads are direct and ungated. No email address is required.

Document intelligence

Evidence-linked document extraction

Best match

Turn recurring PDFs, scans, forms, invoices, or records into structured fields with source evidence, validation, review states, and an explicit downstream action.

The operating problem

Teams copy fields manually, lose provenance, and discover exceptions only after incorrect data has entered another system.

Why it matched

  • includes an ungated starter artifact

Operating loop

01 · Intake02 · Parse03 · Extract04 · Validate05 · Review06 · Export or act

Claim boundary. The starter is a scoping and quality artifact, not a production parser. The live mechanism handles a constrained synthetic pattern and does not represent the full OCR, layout, model, or evaluation stack.

Local-first document tools

Local signature and document handling

Extract and clean signature imagery, keep processing local where appropriate, place the result into a document, and preserve an operator-controlled export path.

The operating problem

Sensitive files move through disconnected image editors, uploaders, and PDF tools, increasing friction and weakening user control.

Why it matched

  • includes an ungated starter artifact

Operating loop

01 · Open file02 · Isolate mark03 · Clean image04 · Place05 · Review06 · Export

Claim boundary. The starter and live cleanup mechanism do not provide identity verification, certified electronic signing, legal assurance, or the complete SignKit desktop product.

Local-first knowledge capture

Meeting capture and searchable retrieval

Capture audio with clear consent, produce a transcript, retain source timing, make the session searchable, and export or recover the record without turning three disconnected tools into the workflow.

The operating problem

Meeting audio, transcripts, notes, and searchable context are split across tools, while recording state and recovery remain unclear to the operator.

Why it matched

  • includes an ungated starter artifact

Operating loop

01 · Consent02 · Capture03 · Transcribe04 · Index05 · Search06 · Export or recover

Claim boundary. No live meeting recorder is embedded on the portfolio. The starter and case explain the workflow boundary; consent, platform audio permissions, transcription quality, packaging, and recovery require the actual product environment.

Spatial simulation

Spatial visibility and coverage review

Model cameras, targets, obstacles, and operating zones so visibility or coverage changes can be simulated before a physical or operational decision is made.

The operating problem

Teams place cameras or define monitored zones from intuition, then discover blind spots, redundant coverage, or operational conflicts after installation.

Why it matched

  • includes an ungated starter artifact

Operating loop

01 · Map scene02 · Place sensors03 · Define targets04 · Simulate05 · Compare06 · Record decision

Claim boundary. The live mechanism is a two-dimensional line-of-sight example. It does not represent full 3D coverage, DORI, calibration, temporal simulation, path replay, or optimisation.

Computer vision foundations

Visual evidence inspection

Measure image properties and derived evidence before using a vision model, so semantic output can be compared against deterministic dimensions, luminance, contrast, edges, and source regions.

The operating problem

Vision workflows often jump directly to model descriptions without retaining enough measurable evidence to diagnose failures or support review.

Why it matched

  • includes an ungated starter artifact

Operating loop

01 · Decode locally02 · Measure03 · Derive edges04 · Attach evidence05 · Interpret06 · Review

Claim boundary. The live mechanism performs real browser-side pixel analysis but does not claim object detection, OCR, segmentation, or semantic scene understanding.

Still not sure where the boundary is?

Bring the source material, current handoff, failure examples, and desired outcome.

A consultation is for clarifying the workflow and next decision. A project is a separate bounded scope with implementation and acceptance evidence.

Discuss the workflow

Five ways to use the same workflow

The visitor chooses the depth of commitment instead of being forced into one funnel.

Download a starter

Take a practical operating artifact with states, contracts, failure tests, acceptance gates, and scoping questions. No email gate.

Try a live mechanism

Operate a deliberately small browser-contained function when one exists. The interface states its claim boundary instead of pretending to be the full product.

Review an audited case

Inspect current maturity, source revision, product decisions, constraints, and implementation evidence before accepting the broader claim.

Scope a custom build

Turn the selected workflow into a bounded implementation with source material, exclusions, acceptance evidence, delivery terms, and an explicit end condition.

Book a consultation

Use a focused conversation to clarify the workflow, identify the next decision, and determine whether a starter, existing product, or custom build is the right path.

Trust boundary

A useful starter is not a production claim.

The library makes small mechanisms and practical operating artifacts available without overstating them. Full product capability, production readiness, customer outcomes, and commercial scope remain tied to their actual evidence surfaces.

Working mechanisms

Real browser-executed functions with synthetic inputs and explicit limits. Review them in the Working Systems Lab.

Audited cases

Revision-pinned maturity, decisions, constraints, and implementation evidence. Browse Selected Work.

Commercial work

A consultation clarifies the workflow; a project defines the useful product boundary, implementation, acceptance evidence, exclusions, and delivery terms. Review Commercial Engagements.

Document wedge

For recurring PDFs, scans, forms, invoices, records, and signed documents, the focused offer remains Document Workflow Systems.

Bring the workflow, not a polished specification

Source material, handoffs, failures, and the desired operating outcome are enough to start.

Discuss a workflow