Workflow templates
Use-case-first packaging, without hiding the machinery.
Seven opinionated templates — three developer-oriented, four packaged for startup ops teams. Every template ends with a proof card, evidence status, open questions, and a citable record.
Developer templates
For builders composing from protocol primitives.
findBestFitFind my best-fit options
Unify fragmented discovery, rank source-backed options, and generate the next best action. Pauses for user selection; resumes to Bridge and Pay.
View templateauditDisputedClaimAudit this disputed claim
Build an evidence map, identify contradictions, request missing proof, and package a proof card. Escalates to Proxy when human review is needed.
View templatecoordinateHumanProcessCoordinate this human process
Route human logistics, collect outcome proof, and resume Resolve with a source-of-truth callback. Voice, message, and logistics-directed.
View templateOperator templates
For startup ops teams adopting without designing from primitives.
vendorDueDiligenceScore a vendor before you sign.
Policy-first scoring, contradiction detection, and a citeable proof card — packaged for procurement and legal teams without API primitives.
View templateoperatorDecisionLogEvery decision, every path not taken — preserved.
Log every option considered, the rejected paths, and the rationale. Portable cite ref compatible with Decionis-style audit ledgers.
View templatecomplianceAuditExportFrom task record to audit-ready report.
Pull any completed task into a sealed proof pack — evidence, receipts, decision log, citations — ready for a regulator, auditor, or board.
View templateprocurementHandoffHunt, verify, pay — with a receipt at the end.
Issue a spend mandate and get a finance-ready receipt. Hunt → Resolve → Pay in one call, policy-enforced without custom guard code.
View templateEvery template outputs the same structure
Proof card. Evidence status. Open questions. Cite ref.
Whether you run Hunt to buy an iPhone or Compliance Audit Export for a board review, the output shape is consistent — so external systems, ops dashboards, and decision ledgers can consume the same format regardless of which template produced it.
Consistent proof card output
{
"proofCard": {
"cardId": "card_...",
"evidenceStatus": "sourceBound" | "verified" | "partial",
"confidence": 0.91,
"openQuestions": [...],
"recommendedRestraint":"proceedSafely" | "proceedWithCaution" | ...,
"cite": "patchr:proofCard:card_...#v1",
"citeRef": "patchr:decisionLog:...", // operator templates
"escalation": { "recommended": false, ... }
}
}