A reviewer used to read every change. Code now writes itself at volume, so it is worth exploring how a team shows who vouched for what shipped.
Technology ran on code that humans wrote and humans reviewed. A change moved through review, testing and release, and support was a queue worked by people.
The old Container of Trust was the reviewer. Somebody who understood the system read the change, asked why, and put their name beside it.
Writing speed set the pace of change, so a reviewer could keep up because the author could only type so fast.
Code written and reviewed by humans.
Code, configuration and support produced by prompts and bots.
Code, application configuration and data pipelines are now built through prompts. Support is resolved by bots, and governance and lineage document themselves.
The speed is real in some settings and illusory in others. In a randomised trial with experienced open-source developers, those using AI tools took 19 percent longer on their own repositories, while believing the tools had sped them up.
Attackers have the same tools. In a study with human participants, fully automated AI spear phishing achieved a 54 percent click-through rate, matching human experts and far above the 12 percent of the control group.
Technology now builds faster than it verifies, and attackers write faster than defenders read. Both sides have added machines, and the contest is moving to machine speed.
The old Container of Trust assumed a human reviewer who understood each change. At this volume the reviewer reads the summary, and the code that ships may not have been read in full.
A reviewer read every change. A reviewer facing generated code at volume reads the summary.
Shift 01 · Change Review Receipt
A study of developers with AI assistants found that participants wrote less secure code and were more likely to believe it was secure.
Shift 02 · Confidence Calibration Record
In an early security assessment of an AI code assistant, about 40 percent of generated programs in security-relevant scenarios contained security flaws.
Shift 03 · Security Scan Seal
Code that imports a package that does not exist leaves a door open. A study of package hallucination found that commercial models invented package names at least 5.2 percent of the time, and open-source models 21.7 percent.
Shift 04 · Dependency Allowlist
A support agent knew when to escalate. A bot answers every ticket in the same confident voice, so errors read like answers.
Shift 05 · Support Escalation Rule
Data lineage was documented by the people who built the pipeline. Auto-documented lineage describes what the tool believes it built.
Shift 06 · Lineage Attestation
Secure development practice assumed human authors. The US standards body has had to publish a community profile extending its secure software development framework to generative AI and dual-use foundation models.
Shift 07 · Secure Practice Profile
A reviewer used to assume a human author. Generated code looks like any other, so a change has no marker of how much of it a machine wrote and with which tool.
Shift 08 · Code Origin Tag
The Container of Trust has moved from the reviewer to the pipeline. The person who once vouched for a change now configures the tools that generate and check it, and the pipeline holds the record of what was approved.
That leaves room to define accountability. If generated code opens a breach, the model wrote it, the developer accepted it, the scanner passed it and the security analyst, itself a model, missed it. A US standards body's generative AI profile lists information security among its twelve risks.
Every earlier era that met an abundance went on to build a Container of Trust, and technology has room to build one of its own. In The Series, its working name is the Secure Code Standard.
The name is a working label, and a better one may arrive. What matters here is what it would hold: how code was written, what it depends on and who stands behind it as secure.
The eight shifts for Technology in Market Signals come in two documents. See what is changing is the brief profile, a short map with one entry per shift. See what can be built is the detailed profile, the longer working record behind each shift.
Market Disruptions records what is happening in the information market. Market Signals shows the potential ahead, and for technology it comes as two documents. Both cover the same eight shifts, at different depth.
The pattern repeats across all sixteen functions. More output arrives, trust in it is tested, and someone builds the Container of Trust that lets people believe the output again. Start with the brief for the overview, or open the detailed profile for the working record.
The external sources behind this article, reviewed in October 2026. Links open in a new tab.
A randomised trial in which experienced developers using AI tools took longer while believing they were faster.
Compares AI-automated spear phishing with human experts and a control group.
Finds that participants with AI assistants wrote less secure code and were more confident in it.
Tests an AI code assistant on security-relevant scenarios and finds about 40 percent of generated programs vulnerable.
Measures how often code-generating models invent package names, which opens a route for supply chain attacks.
Extends NIST's secure software development framework to generative AI.
Names twelve risks specific to or made worse by generative AI.
Isyamba, V. (2026). Technology: Code by Prompt and a Way to Show Who Vouched for It. The Trust Ledger Project Series. GreenDeveX.com. https://greendevex.com/trust-ledger/market-disruptions/technology/
Isyamba, Victor. “Technology: Code by Prompt and a Way to Show Who Vouched for It.” The Trust Ledger Project Series, GreenDeveX.com, 2026, https://greendevex.com/trust-ledger/market-disruptions/technology/
Isyamba, Victor. “Technology: Code by Prompt and a Way to Show Who Vouched for It.” The Trust Ledger Project Series. GreenDeveX.com, 2026. https://greendevex.com/trust-ledger/market-disruptions/technology/
@misc{isyamba2026technology,
author = {Isyamba, Victor},
title = {Technology: Code by Prompt and a Way to Show Who Vouched for It},
year = {2026},
publisher = {GreenDeveX.com},
series = {The Trust Ledger Project Series},
url = {https://greendevex.com/trust-ledger/market-disruptions/technology/}
}
Note: The perspectives shared on GreenDeveX.com are the author's independent analytical interpretations of trust as a historical medium of exchange. This commentary is intended for conceptual exploration and does not constitute peer-reviewed academic research or commissioned institutional findings.