Agent-First Development (AFD): A Provider-Neutral Methodology, Portable Developer Twins, and a Cryptographic Layer-Isolation Protocol
Year: 2026
Type: article
Abstract: We introduce Agent-First Development (AFD), a software development methodology designed for teams where AI agents perform the majority of implementation work while humans retain authority over specification, review, and strategic decisions. AFD has three contributions. First, the Digital Twin: a persistent, developer-owned, portable representation of a developer’s coding style, accumulated knowledge, and skills, encoded as structured markdown files that travel with the developer across projects and employers. Second, a three-layer ownership and portability architecture with an explicit cryptographic isolation protocol built from provenance-tagged encrypted layers, an append-only transparency log per layer, and a runtime provenance gateway, which lets both the developer and the employer audit non-leakage of intellectual property without exposing plaintext. The protocol is specified against markdown layer files and generalises to any chunkable, provenance-addressable, append-only-auditable store, including note graphs, vector databases, knowledge graphs, and hierarchical agent-memory frameworks. Third, the Twin Economy: an analysis of the labor-economic implications of this model, advanced explicitly as a research hypothesis rather than a prediction. The methodology is defined as a provider-neutral protocol over abstract CI/CD primitives: spec store, task registry, change proposal, review gate, event bus, workflow runtime, agent execution environment, ticket store, and transparency log. The GitHub adapter is implemented and used in the POC; adapters for GitLab, Bitbucket, Azure DevOps, Gitea/Forgejo, and a self-hosted Git + Jenkins stack are specified at the protocol level. Validation of provider neutrality against a second concrete adapter is the highest-priority next experiment. We present empirical evidence from a production proof of concept (POC) on a commercial codebase (two features delivered through the full pipeline, with measured human-vs-agent action ratios and token-cost accounting) and we are explicit about the gap between this evidence and the multi-developer, multi-employer claims of the labor-economic framing. A reference implementation of the core cryptographic protocol (provenance-tagged AEAD layer envelopes, an RFC 6962 Merkle-anchored transparency log, two-tier Ed25519-signed checkpoints, a four-check provenance gateway that adds a semantic content check to the policy, AEAD, and provenance checks, an HTTP-fronted egress proxy, and a CT-style external witness that catches transparency-log truncation and fork attempts) is provided as the layer-gateway Go package and is summarised in Appendix B.10. TEE-backed key custody and the non-markdown instantiations of Appendix B.9 remain unimplemented.
Author: Kalfon, Oshri
Language: English
Subfield: Information Systems
Field: Computer Science
Domain: Physical Sciences
Open Access status: green
OpenAlex ID: W7212181278
FWCI:
Cites:
Cited by:
Related to: