Dry-run first
Preview intent and surface assumptions before a production change is possible.
A copyable, AI-agent-ready safety template for workflows that have become too important to run on faith.
AI can help build a workflow. It should not hide the moment a script touches meaningful data. This template makes the inputs, outputs, warnings, and decisions around a run visible to the person responsible for it.
Use it when an ArcPy workflow has moved beyond a scratch file: it creates or updates data, supports an operational decision, or needs to be understood by someone besides its original author.
Preview intent and surface assumptions before a production change is possible.
Put a deliberate confirmation around operations that should never happen by accident.
Check expected datasets, fields, counts, and destinations before quiet bad output travels downstream.
Capture parameters, source data, counts, outputs, timestamps, and warnings in a readable record.
Keep tests and development work away from production geodatabases and destructive operations.
Give coding agents clear boundaries around what they may change and what they must preserve.
The Harness includes a copyable project structure, platform-neutral agent onboarding, preflight checks, dry-run defaults, explicit production confirmation, and JSON run receipts. It is not autonomous automation. It is a way to keep an assisted workflow inspectable and under human control.
Start with the workflow you already have, then let your preferred coding agent help configure a reviewable first dry run.
People responsible for a useful script that has become part of a repeatable workflow.
People who want stronger operational boundaries without turning a small automation into a platform project.
People trying to let a team move faster with AI while keeping review and accountability visible.
It will not replace data governance, formal change control, or expert review for high-consequence work.