Protocol-Driven Development: Governing Generated Software Through Invariants and Continuous Evidence
Automated program synthesis lowers the cost of producing implementations but introduces a harder governance problem: determining which generated artifacts are admissible. Natural-language specifications are ambiguous, and example-based tests sample only part of the behavioral space. Used alone, neither provides a sufficient control boundary. We introduce Protocol-Driven Development (PDD), where the primary software artifact is a machine-enforceable protocol rather than code. We define a protocol
Record details
Published: 13 May 2026
Source: arXiv
Category: Research
Topics: Regulation
Retrieved: 14 July 2026
Related evidence
These records share source-supplied organisations, an exact publisher byline, automatic topics or regions. The reason is shown on every link; related does not mean supporting, agreeing with or verifying this record.
Verifiable Agentic Infrastructure: Proof-Derived Authorization for Sovereign AI Systems
arXiv · 13 May 2026
Beyond Memory: A Transactional Continuity Kernel for Long-Lived AI Agents
arXiv · 12 August 2026
Semantic Quorum Assurance: Collective Certification for Non-Deterministic AI Infrastructure
arXiv · 6 June 2026
OpenKedge: Governing Agentic Mutation with Execution-Bound Safety and Evidence Chains
arXiv · 7 April 2026
Replicating Belief, Not Bits: Epistemic State Replication for Agentic Systems
arXiv · 3 July 2026
Revisiting Reinforcement Learning with Verifiable Rewards from a Contrastive Perspective
arXiv · 13 May 2026
How to cite this record
ethics.ai (13 May 2026), “Protocol-Driven Development: Governing Generated Software Through Invariants and Continuous Evidence,” evidence record 4417, https://ethics.ai/record/4417 (originally published by arXiv).
Use and limitations
This page is a stable index and citation surface for a source record. ethics.ai did not author the underlying report and has not independently verified every claim. Automatic topics may be imperfect. For consequential use, quote and cite the original publisher.