Better Together: Permit Sheriff and Procore

THE PARTNERSHIP01 / 10

Better Together: Permit Sheriff + Procore

Evidence-backed permit readiness inside the construction project workflow.

A human decides precisely which Finding becomes a private Procore Observation.

Permit Sheriff + Procore · Technical Feasibility · October 8, 2026 · Sandbox proof dated October 7
JOINT VALUE02 / 10

One reviewed finding. A clearer project action.

For general contractors, architects, engineers, preconstruction and project-management teams.

Source-linked findings can reduce manual re-entry and keep provenance in context.

Customer savings remain an unmeasured hypothesis.

Permit Sheriff + Procore · Technical Feasibility · October 8, 2026 · Sandbox proof dated October 7
CUSTOMER CHALLENGE03 / 10

From scattered evidence to accountable follow-through

The friction: scattered documents, uncertain revisions, late permit gaps, manual handoffs.

The path: customer upload, Permit Sheriff readiness assessment, human verification and exact approval, Procore private Observation and read-back.

Permit Sheriff + Procore · Technical Feasibility · October 8, 2026 · Sandbox proof dated October 7
PRACTICAL USE CASES04 / 10

A workflow that fits human review

Package readiness: verify actionable gaps against evidence.

Agent-assisted review: an eligible agent may propose a verified finding; the human explicitly chooses whether to act.

Project follow-through: the approved issue is visible as a Procore Observation.

Permit Sheriff + Procore · Technical Feasibility · October 8, 2026 · Sandbox proof dated October 7
OBSERVED PROOF05 / 10

The sandbox handoff is real

Observation 367145, Quality / Deficiency, Initiated and Private.

Human consent 18:08:27 UTC; STRONG read-back 18:08:29 UTC; zero retries or recorded errors.

Developer sandbox, October 7. Seeded synthetic PDF/Finding, not customer upload or measured ROI.

Permit Sheriff + Procore · Technical Feasibility · October 8, 2026 · Sandbox proof dated October 7
CONTROLLED ACTION06 / 10

Evidence in. Human control. Verified result out.

Evidence references and revisions retained.

Permit Sheriff and Procore permissions, selected destination and payload revalidated.

Exactly approved private write; uncertain outcomes block blind resends.

Permit Sheriff + Procore · Technical Feasibility · October 8, 2026 · Sandbox proof dated October 7
REVIEW RESOURCES07 / 10

One coherent integration story

The workflow diagram shows directionality, user roles, allowed create/read actions and data ownership.

This digital deck is a browser companion to the dated v4 PDF; the PDF is supplied separately through Procore's Technical Feasibility workflow.

The public /procore page also links to the actual protected sign-in workspace.

Permit Sheriff + Procore · Technical Feasibility · October 8, 2026 · Sandbox proof dated October 7
SANDBOX RECORD08 / 10

What Procore actually received

[Permit Sheriff] Signed structural calculations required.

Synthetic source: “Provide signed structural calculations before resubmission.”

Observation 367145 · company 4290476 · Sandbox Test Project 369402 · Distribution/Assignee empty.

The historical screenshot is preserved in the original dated PDF, not replicated here.

Permit Sheriff + Procore · Technical Feasibility · October 8, 2026 · Sandbox proof dated October 7
MCP HUMAN REVIEW09 / 10

MCP proposes. A human decides.

An authenticated agent proposes one verified Finding for an already bound destination.

A separately authenticated reviewer inspects the exact preview, then manually executes the write.

Agent sees only its correlated saved status and cannot approve, execute, retry or fetch fresh provider state.

Implemented by merged PR #941; tools disabled by default and not exercised in run06.

Permit Sheriff + Procore · Technical Feasibility · October 8, 2026 · Sandbox proof dated October 7
STAGED QUALIFICATION10 / 10

Technical Feasibility now, certification later

Proven: synthetic-source human consent, sandbox OAuth, private Observation creation, independent read-back.

Still pending: production OAuth ingress-logging treatment, customer intake and tenant/evidence access, current v2 read-back and recovery, retention commitments and Procore certification.

Documents import, RFIs and autonomous writes are outside Phase 1.

Accessible digital presentation companion to the October 8 v4 PDF. The illustrated original PDF is supplied separately in Procore's Technical Feasibility workflow; this page does not host the formal assessment or constitute production certification.