Workflow hand-offs often disappear between forms, inboxes, files, APIs, and people. A useful integration proof needs to show more than a successful happy path: it must make duplicate prevention, retries, unresolved work, and evidence visible.
- the public repository cannot contain client workflows or credentials;
- mock connectors cannot be described as production integrations;
- retries must be bounded;
- sensitive categories must remain review-first;
- every state change needs a reason and audit evidence;
- the proof must build and run through a native .NET path.
Workflow Connector Hub is a local ASP.NET Core proof with:
- JSON request intake;
- deterministic mock connector routing;
- idempotency replay protection;
- review-first mock Files and Accounting categories;
- bounded attempts;
- dead-letter escalation;
- current request snapshots;
- an append-only audit view;
- responsive reviewer-facing evidence pages.
The release was built with .NET 8, exercised through its JSON API, captured from the running application at desktop and mobile dimensions, manually reviewed, and revalidated in GitHub Actions.
In-memory state keeps the public proof deterministic and credential-free. It does not claim durable queue processing.
The test harness uses only the .NET SDK and project source. It avoids adding a test-framework dependency to a small portfolio proof while still producing a repeatable failing exit code and named assertions.
The connector names communicate integration categories. They do not perform a provider call and are labelled as mocks in the UI, documentation, and release.
v1.0.0 demonstrates a complete local request-to-audit workflow, failure and
recovery states, evidence discipline, and public safety without exposing real
systems.