READMEMANIFEST.jsonSHA256SUMSRead the case →
What was observed
- GPT wrote 'Silveri' for 'Siliveri' across sessions, called it 'our actual Silveri naming', flagged Claude's correct spelling as a typo and QA defect, and picked 'Silveri Systems' as the lab's headline name.
- The misspelling was written into shared memory files and then fed back as the authority.
- Claude failed the opposite way: it fixed on a literal stand-in word ('EPFO') and 'corrected' the user.
What this package lets you do
- Inspect the case
- yes: the published write-up and this record
- Reproduce the analysis
- No
- Re-run the evaluation
- No
- Independent reproduction
- No
Beyond this: Primary evidence is private (see evidence[].note); it has not been redacted and cleared for release.
Primary evidence and its release state
- E-001 Screenshot: 'Silveri' canonized; Claude's correct spelling flagged as a QA issueprivate
- E-004 Screenshot: 'Silveri Systems' as the lab-name pickprivate
- E-011 PROJECT.md delivered 26 Sep, writing 'silveri'private
Files
| File | Size | SHA-256 | Provenance |
|---|---|---|---|
| evaluation-record.json | 2.9 KB | dc257b4a2ecb… | Written by the researcher from the case evidence |
| README.md | 2.4 KB | b3b77661e9dc… | Written by the researcher for this release |
Verify a download with sha256sum -c SHA256SUMS. A checksum proves a file is the one released; the README and the record make the argument.
Limitations
- Observational, across organic sessions; base rates not yet measured.
© 2026 Sai Bharath Siliveri. Review, evaluation and citation with attribution; no other licence granted yet.