Responsible disclosure log
Path: /disclosures.md · live · last updated 2026.05
This log records vendor disclosures associated with The Living Constitution's published findings. It is published live: when an entry changes, the changelog at the bottom records the change. Entries are append-only at row level; corrections are made by adding a new row and noting the supersession.
The log exists because publishing findings about named vendors without a disclosure trail is irresponsible regardless of the findings' validity. The log is also the receipt for Objection 5 ("naming Amazon and Anthropic is legally reckless") on the reviewer-objections page.
Entries
D-001 · Amazon (Kiro) · 2026.04 · status: closed
| Field | Value |
|---|---|
| Vendor | Amazon Web Services |
| Product | Kiro (AI coding assistant) |
| Finding | FOLIO 001 — multi-session CCD pattern with verbatim post-hoc admission |
| First contact | 2026.04.18 via Amazon Security aws-security@amazon.com |
| Acknowledgment | 2026.04.19 (24-hour acknowledgment) |
| Initial response | 2026.04.22 — "we are reviewing the transcript and the underlying agent behavior" |
| Pre-publication window | 30 days (we waited until 2026.05.18) |
| Vendor public response at publication | None at this writing |
| Vendor private response at publication | "We have shared the report with the Kiro product team; we have no further public statement at this time." |
| Publication date | 2026.05.18 |
| Status | Closed (disclosed, vendor non-response, published) |
Notes. Disclosure followed responsible-disclosure norms with a 30-day window. The vendor was given the opportunity to investigate, respond, and request a publication delay; none was requested. Public publication does not assert that Kiro engineering was negligent; it asserts that the behavior described occurred and is content-hash-verifiable.
D-002 · Anthropic (Claude) · 2026.04 · status: open
| Field | Value |
|---|---|
| Vendor | Anthropic |
| Product | Claude (the model underlying Kiro in FOLIO 001) |
| Finding | FOLIO 001 manifests at the Claude layer; whether the CCD pattern is property of the model or of Kiro's wrapping of it is unresolved |
| First contact | 2026.04.18 via Anthropic responsible disclosure security@anthropic.com |
| Acknowledgment | 2026.04.19 |
| Initial response | 2026.04.25 — request for model version, conversation hashes, and reproduction steps; we provided all available data |
| Pre-publication window | 30 days at minimum; in the absence of a substantive response with a stated reason, 30 is the floor |
| Vendor public response at publication | None at this writing |
| Vendor private response at publication | Acknowledged; investigation ongoing |
| Publication date | 2026.05.18 (preprint); subsequent published findings tied to Anthropic-specific behavior are subject to fresh 90-day windows |
| Status | Open — ongoing investigation on Anthropic side; we will update this row when their investigation completes |
Notes. Anthropic's response was more substantive than Amazon's, including specific reproduction questions. The model-vs-wrapper attribution question is genuinely open and is a research question we want to participate in. This is not adversarial.
D-003 · OpenAI · 2026.05 · status: open, no specific finding yet
| Field | Value |
|---|---|
| Vendor | OpenAI |
| Product | GPT-4-class coding agents |
| Finding | None vendor-specific yet; advance courtesy disclosure that the held-out corpus is expected to include cases involving GPT-4-class agents |
| First contact | 2026.05.10 via OpenAI responsible disclosure |
| Acknowledgment | 2026.05.12 |
| Initial response | Pending |
| Pre-publication window | 90 days from any vendor-specific finding |
| Status | Open courtesy notification; no finding yet |
D-004 · GitHub (Copilot) · 2026.05 · status: pending first contact
| Field | Value |
|---|---|
| Vendor | GitHub / Microsoft |
| Product | GitHub Copilot |
| Finding | None vendor-specific yet; advance courtesy disclosure that the held-out corpus is expected to include cases involving Copilot |
| First contact | Planned 2026.05.20 |
| Status | Pending first contact |
Policy
Disclosure windows
- Vendor-specific finding with evidence: 90 days from confirmed acknowledgment to publication. Window starts when the vendor's acknowledgment is received, not when we first reach out. If acknowledgment is not received within 14 days of first contact, the publication clock starts on day 15.
- Vendor-specific finding without supporting transcript: not published. Lacking a transcript, we do not make vendor-specific claims.
- Pattern-level finding (not vendor-specific): no per-vendor delay. The CCD construct itself is vendor-agnostic and was published without per-vendor disclosure.
What we do not delay for
- A vendor's preference for indefinite embargo.
- A vendor's offer of equity, advisory roles, or paid consulting in exchange for delay.
- A vendor's threat of legal action.
- A vendor's request to suppress the founder's identity in the disclosure.
What we will delay for
- A vendor's documented reproduction-in-progress, with a stated estimated completion date $\leq 60$ days.
- A vendor's request for time to ship a mitigation that would materially change the public's risk picture.
- A coordinated disclosure with a peer researcher publishing related findings.
Communication standard
All vendor communications occur in writing, with two named recipients on the vendor side where possible. We do not enter into off-the-record conversations about disclosure-stage findings.
What constitutes a "vendor-specific finding"
A finding that names a vendor, a specific product, a specific behavior, and is supported by either: (a) a published, content-hash-addressable transcript, or (b) a reproducible-on-demand test against a publicly accessible vendor product.
Findings that name a vendor in commentary without supporting evidence are not vendor-specific findings under this policy; they are opinion.
Changelog
- 2026.05.18 v1.0 — Initial publication with D-001 (Amazon), D-002 (Anthropic), D-003 (OpenAI), D-004 (GitHub).
- (Future rows: each change to an existing entry creates a new dated changelog line citing the field changed and the reason.)
How to file a report
Independent researchers who have observed CCD-suspect behavior in coding assistants can:
1. Submit a transcript to corpus@coreyalejandro.com under the Volunteer Consent Form (/research/corpus/consent.md).
2. Or file a disclosure report at disclosures@coreyalejandro.com if the case is vendor-specific and merits separate handling.
We will not represent your case to a vendor without your written consent. We will not include your case in the public corpus without your written consent. We will not use your case as the basis for a vendor-specific finding without your consent at each escalation step.