Payne limitations

Payne supports one target dataset and one confirmed replacement per Shutdown Gate. The complete live path is the bundled local finance scenario, one consumer contract shape, one PostgreSQL compatibility artifact, and one bounded sandbox and re-ingestion workflow.

Payne does not claim:

• total dependency coverage; analysis is bounded to current capabilities, three downstream hops, and 25 discovered consumers;
• a production deployment profile or universal safety guarantee;
• arbitrary SQL, dbt, repository, pipeline, or warehouse code generation;
• automatic production application, merge, deployment, or dataset deletion;
• support for arbitrary DataHub versions, deployment topologies, inference providers, Gemini/Ollama models, warehouses, or contract shapes;
• that fixture output is current evidence;
• that a prepared or accepted artifact was applied;
• that a mutation response was verified without a fresh matching read;
• external notification delivery beyond the implemented in-app record.

An open gate is Open under current evidence, not universally or permanently safe. An accountable human retains retirement authority.