Workflow Connector Hub

A public-safe ASP.NET Core integration proof that receives synthetic requests, routes them through deterministic mock connectors, protects against duplicate execution, applies bounded retries, escalates unresolved work for human review, and preserves an audit trail.

Status: released at v1.0.0 Portfolio lane: business systems, APIs, and workflow integration Stack: .NET 8, ASP.NET Core, C# Data: synthetic only

What it proves

• request validation and correlation;
• connector abstraction without fake production claims;
• idempotency-key replay protection;
• review-first routing for sensitive mock connector categories;
• bounded retries and dead-letter escalation;
• append-only submission, replay, and attempt evidence;
• native API, responsive evidence UI, deterministic tests, and CI.

Native workflow

The running application exposes:

GET  /health
GET  /api/status
GET  /api/demo
GET  /api/audit
GET  /api/requests/{idempotencyKey}
POST /api/requests
POST /api/requests/{idempotencyKey}/attempts

All connectors are local mocks. The project does not contain provider credentials and does not perform external writes.

Run locally

dotnet restore
dotnet build .\WorkflowConnectorHub.sln --configuration Release
dotnet run --configuration Release --project .\tests\WorkflowConnectorHub.Tests\WorkflowConnectorHub.Tests.csproj
.\tools\run-native-demo.ps1

Then open:

http://127.0.0.1:5088/overview.html

Verify the release

.\tools\verify-release.ps1

The release gate validates the native build, deterministic domain tests, two screenshot groups, manual-review hashes, documentation, and public boundary.

Evidence

SG01 - Intake, Routing, and Connector Execution

• native overview and metrics;
• live synthetic submission;
• replay protection;
• audit/review surface;
• responsive mobile workflow.

SG02 - Failure Recovery, Audit, and Release Evidence

• validation and retry gates;
• operational summaries;
• public safety and scope boundaries;
• responsive mobile assurance.

See docs/screenshot-groups.

Deliberate boundaries

• no real connector credentials;
• no live email, calendar, file, GitHub, or accounting write;
• no uncontrolled retry loop;
• no silent duplicate request creation;
• no automatic approval of review or dead-letter records;
• no client payloads or proprietary workflow rules;
• no claim of production deployment.

Architecture and evidence

• docs/ARCHITECTURE.md
• docs/CASE_STUDY.md
• docs/REPRODUCTION.md
• docs/LIMITATIONS.md
• BUILD_STATUS.md

Created and developed by Codie Shannon.