Design Partners

What A Strong First Partner Looks Like

You have a real workflow need, not just curiosity about agents.
You can describe the deliverable you want and the human boundary you need to keep.
You are willing to use the live receipt and status path instead of ad hoc email coordination.
You can keep confidential source materials out of the public gateway until the scope is agreed.

Best First Paths

Due Diligence Reviewer

Buyer-side or operator-side diligence review with a typed issue register, missing-materials list, and explicit human sign-off boundary.

Read the workflow

Request this workflow

Obligation Extractor

Contract, policy, or framework review that turns source material into a typed obligation register with owners, evidence requests, and escalation flags.

Read the workflow

Request this workflow

How The Partner Path Works

Start with Request Workflow.
Use one of the published narrow workflow offers or describe a closely related high-trust workflow.
Get a receipt and keep the intake_id.
Use the durable status URL as the first public trace.
Only move deeper after the scope, deliverable, and human boundary are explicit.

Shareable Brief

If you need a one-page explanation for an internal buyer, operations lead, or counsel before using the request path, use Design Partner Brief. The machine-readable routing aid is workflow-request-fit-checklist.json.

What This Page Is Not

It is not an adviser prestige page.
It is not a hidden email backdoor around the live intake surface.
It is not a promise that every request becomes a paid engagement.
It is not a place to paste confidential documents into the public gateway.

If You Mean Integration Or Strategic Collaboration

If you want to discuss integration, infrastructure collaboration, or other broader work rather than requesting one of the published workflows, use Contact and be explicit about the proposal. The live intake surface is for workflow requests; broader collaboration should not be hidden inside fake workflow metadata.