Panout review packOverviewFinal memoMVPLive outputsJudge roundsAppendicesDecisions

Source: docs/research/2026-09-03-defensibility/appendices/K-market-update-2026-09-04.md

Appendix K: Market and incumbent update (2026-09-04)

Scope: changes since the 2026-09-03 pass. CONFIRMED = read on the page; UNCONFIRMED = search snippet only. Quotes are verbatim.

What changed since 2026-09-03

1. Incumbent moves since ~2026-06-01

GitHub

Cursor

Anthropic (Claude Code)

OpenAI (Codex)

Google — Antigravity 2026-08-20, CONFIRMED. https://cloud.google.com/blog/products/ai-machine-learning/expanding-google-antigravity-for-enterprise-customers — "Enable comprehensive audit logging with a single toggle, capturing prompts, agent responses, and metadata for compliance reporting." Jules: nothing found.

Amazon — Kiro Crew open-sourced 2026-08-04, CONFIRMED via InfoQ 2026-08-30 https://www.infoq.com/news/2026/08/kiro-crew-coding-agents/ — ships "an OS-level sandbox, denied-by-default commands ... and a signed audit log of every action."

GitLab — 19.2, 2026-07-16, CONFIRMED. https://docs.gitlab.com/releases/19/gitlab-19-2-released/ — AI audit event report (beta) captures "Inputs", "Model and configuration context", "The chronological event timeline", "Outputs"; "download the underlying session artifact."

Net: every incumbent logs agent sessions; GitHub alone stamps the commit; none records a human committing past a failing check.

2. New entrants

3. Compliance drivers

(a) EU AI Act. CONFIRMED. https://www.cooley.com/news/insight/2026/2026-08-03-eu-ai-act-transparency-obligations-take-effect-2-august-2026 (2026-08-03): Article 50 applies to "providers (those who develop and place an AI system on the market) and deployers (those who use an AI system under their own authority)"; fines "up to €15 million or 3% of worldwide annual turnover, whichever is higher"; guidelines adopted "20 July 2026". Stibbe (UNCONFIRMED): companies "using coding assistants ... will inevitably be confronted with these obligations" — but Art. 50 is content labelling, not change control. Omnibus — CONFIRMED. https://www.hunton.com/privacy-and-cybersecurity-law-blog/eu-digital-omnibus-on-ai-enters-into-force (2026-07-28): in force 2026-07-27; Annex III to 2027-12-02; Annex I to 2028-08-02. No Art. 26 logging duty reaches a company merely using coding agents in 2026.

(b) SOC 2 / ISO 27001. No AICPA, Vanta, Drata, Secureframe or Big 4 guidance on evidencing review of AI-generated changes found. Snippets (UNCONFIRMED) say the AICPA "hasn't issued AI-specific criteria". Only consultancy blogs address the CC8.1 gap.

(c) ISO/IEC 42001. CONFIRMED (secondary, no registry): "more than 350 organisations globally hold ISO 42001 certificates" through April 2026 (https://aicompliancevendors.com/blog/iso-42001-certified-companies-list, 2026-05-17); same figure "as of mid-2026" (https://www.dsalta.com/resources/ai-compliance/iso-42001-certification-cost-timeline-requirements-2026, 2026-08-03).

(d) Regulators. OCC Bulletin 2026-13, 2026-04-17 — CONFIRMED. https://www.occ.gov/news-issuances/bulletins/2026/bulletin-2026-13.html — "Generative AI and agentic AI models are novel and rapidly evolving. As such, they are not within the scope of this guidance." RFI on "generative AI and agentic AI" promised "in the near future." FCA — CONFIRMED secondary (2025-12-18) https://www.bclplaw.com/en-US/events-insights-news/ai-regulation-in-financial-services-turning-principles-into-practice.html — "guidance on audit trails, and human-in-the-loop protocols is likely in 2026." No FCA publication found. SEC, PRA, EBA, FFIEC: nothing in 2026 on AI-generated code controls. APRA 2026-04-30 letter — UNCONFIRMED.

4. Incidents (2026)

5. Pricing signals

6. Demand signals

Reaction counts are 0–6 everywhere. Demand is articulate but thin, and vendors keep closing it "not planned".

Claims that would change the Panout memo

  1. Weakens (precision): Claude Code (claude_code.tool_decision) and Codex (codex.tool_decision) already record approval decisions per tool call with a config-vs-user source. The memo must narrow to: nobody records the decision at the commit boundary against a named failing contract; and Claude's config bucket "doesn't indicate which of these sources matched", so auto-mode approvals are unrecoverable from the stream.
  2. Weakens (competitor): Arnica's "digitally signed review record for every PR as built-in compliance evidence" is a signed per-change record sold as audit evidence. PR-layer and security-scoped; Panout must show why commit-time, contract-level, human-override capture differs.
  3. Strengthens: GitHub's resolution reasons prove the override moment is capturable and valuable, yet GitHub routes it to "the product team", not the customer. The customer-owned override record is unclaimed.
  4. Strengthens: Copilot approvals now count toward required approvals, Macroscope auto-approves routine PRs, and Claude auto mode is default with a 97% human approve rate. The merge gate is going agent-on-agent; the override is the last human signal left.
  5. Weakens (buyer pull): No regulator or SOC 2 body compels this in 2026 (Omnibus deferral, OCC carve-out, no AICPA guidance, FCA guidance still "likely"). The buyer is internal risk (Amazon, PocketOS, Sol), not compliance.