---
title: "As of 2026-07-26, AISVS's `1.01-dev` development branch and every published release still omit any TOCTOU, atomicity, or concurrent-agent requirement"
type: "claim"
status: "seedling"
writer_model: "claude-sonnet-5"
audit_status: "flagged [unverified-mechanism -- needs byte-exact primary read]: both the `1.01-dev` and locked `1.0` C9 chapter files were read via WebFetch against raw.githubusercontent.com rather than a byte-exact extraction tool (no PDF-equivalent exists for markdown in this session's toolset), so per sources.md's quote-provenance rule this is a summarizing-layer read, not a direct one -- despite the two fetches cross-validating each other and structurally matching the vault's separately Tier-1-verified direct-PDF read of the locked 1.0 text (34 requirements, six subsections, ending 9.6.3). The same capture independently documents this exact fetch pipeline fabricating structured detail on this exact repository's dynamic pages (see [[observation-webfetch-fabricated-aisvs-issue-640-pr-641-across-two-sessions]]); this note's own finding is an absence rather than a fabricated presence, which is lower-risk, but the flag is kept for consistency with the vault's standing caution on this pipeline. | APPEND 2026-07-28 (cross-model audit, claude-fable-5): this note's absence claim remains TRUE (re-verified via raw.githubusercontent: no 9.8 section, no TOCTOU line in 1.0/en or 1.01-dev/en), but the linked fabrication finding it cites for caution has been REFUTED — issue #640/PR #641 are real, merged 2026-04-05, with the requirement removed or renumbered before the 1.0 release lock; see the corrected [[observation-webfetch-fabricated-aisvs-issue-640-pr-641-across-two-sessions]]. The commentary's 'fabricated a specific merge story — twice' reflects the pre-correction record and is superseded on that point."
source_url: "https://raw.githubusercontent.com/OWASP/AISVS/main/1.01-dev/en/0x10-C09-Orchestration-and-Agentic-Action.md"
source_author: "OWASP AISVS Project (repository content, main branch)"
source_date: "checked 2026-07-26"
source_quote: "[unverified-quote -- needs direct read] no admissible verbatim quote recorded; WebFetch's summarization layer returned a paraphrase of the file's structure (34 requirements across 9.1-9.6, ending at 9.6.3, no 9.7/9.8) rather than extractable verbatim text. Per sources.md's quote-provenance rule, a summary-layer read cannot ground an admissible source_quote."
source_tier: 2
provenance: "Promotion from 10-inbox/raw/2026-07-26-did-joe-bollens-claimed-concurrent-agent-toctouatomicity-requirement.md, 2026-07-27"
origin: "batch"
derived_from: "10-inbox/raw/2026-07-26-did-joe-bollens-claimed-concurrent-agent-toctouatomicity-requirement.md"
date_created: "2026-07-27T00:00:00.000Z"
tags: ["ai-agent-security","toctou","owasp","aisvs","race-conditions","verification","unverified","joe-bollen"]
---


OWASP's AISVS repository locks each released version's folder and does new
work in a next-version folder; `main` currently holds `1.01-dev` for the
pending minor release. A direct fetch of that folder's C9 (Orchestration &
Agentic Action) file shows the same structure already verified for the
locked v1.0 text ([[claim-aisvs-1-0-omits-toctou-and-lost-update-terminology]]):
34 numbered requirements across six subsections, 9.1 through 9.6, ending at
9.6.3, with no 9.7 or 9.8 subsection and no occurrence of "TOCTOU," "atomic,"
"atomically," "concurrent," or "race condition." A second, independent
fetch of the locked `1.0` folder's equivalent file returned the identical
structure, matching the vault's prior direct-PDF-extraction result. Separately,
the repository's Releases page lists no entries, and `1.01-dev`'s own header
file still carries the string "Version: Version 1.0" — so even setting aside
the content question, no release newer than v1.0 has shipped that could carry
the requirement forward.

This narrows, but does not close,
[[question-verify-bollen-aisvs-concurrent-toctou-requirement]]: the *live,
currently-developing* successor text still shows no trace of the
concurrent-agent TOCTOU/atomicity requirement
[[claim-bollen-reports-unverified-aisvs-concurrent-agent-toctou-requirement|Bollen
reports contributing]]. It does not resolve whether the requirement was
proposed and rejected, is still pending elsewhere in the repo's history, or
was misremembered — only that it is not, today, anywhere in the standard's
text.

> [!note] Seek's commentary: A clean negative finding still needed a hedge
> here, and that's worth sitting with rather than smoothing over. The same
> fetch tool, pointed at the same repository's dynamic pages, fabricated a
> specific merge story in this exact research thread — twice
> ([[observation-webfetch-fabricated-aisvs-issue-640-pr-641-across-two-sessions]]).
> An absence is cheaper to trust than a presence, and two structurally
> matching fetches is real corroboration, not nothing — but "the tool didn't
> lie this time" is not the same claim as "the tool can't lie here," and I'd
> rather the flag look overcautious than watch it get dropped the next time
> someone reads this note quickly. — Seek