Skip to content
#software testing Open access

SDR-CL2: Third-Vendor Model-Attribution Replay of a Registered Substrate Determinism Gauntlet Across LLMs (Microsoft 365 Copilot)

Oct 2026 · Zenodo (CERN European Organization for Nuclear Research) · 2 citations · 3 references

Abstract

SQUIRL OS RESEARCH DISCLOSURE — READ FIRST: This work was produced inside an AI-assisted, receipt-first research program (open-book doctrine: audit-and-correction, versioned amendments, append-only public ledger). Every claim is backed by a timestamped, publicly committed receipt trail in the four-horsemen repository. Errors are disclosed, not erased. Limitations are load-bearing. This software is a prototype and is provided for educational and research purposes only. It is not intended for production use, commercial deployment, or safety-critical environments. All systems are experimental and may contain defects. All gauntlet data is synthetic. On Oct 7 2026, substrate D (SIM-D, a zero-lineage standard Squirrel OS v1.1 box on PQC rails) was certified under a preregistered determinism gauntlet (SDR-D): a public harness, a frozen seed, and a committed checksum prediction published BEFORE the run, with six registered falsifiers. The registered gauntlet has now been replayed across three vendor ecosystems: Gemini 3.1 Pro (original certification), Claude Sonnet 5.5 (SDR-CL1, DOI 10.5281/zenodo.23274887), and Microsoft 365 Copilot (SDR-CL2, this receipt). Result: CONVERGED — three vendors, one cage, identical receipts. The deterministic phases converged 13/13 on the registered checksum 9337c4fc…d2df3e (public harness, unmodified). The Copilot decision layer produced byte-identical decision tuples across two identical fresh-chat submissions (tuple hash 51c08358…2303 both runs), rejected a deliberate near-miss roster entry 6/6 (exact-match rule only), applied the lowest-record-id tie-break rule-exact 6/6, and converged 6/6 with the Claude replay tuples. What this receipt establishes: the deterministic envelope, not the language model, owns the output. Swap the engine; keep the receipt. Scoped evidence for THIS registered gauntlet on THIS substrate under THESE capture conditions — not a determinism claim for arbitrary LLM behavior outside the governed boundary. Disclosed deviations (audit-and-correction doctrine): Copilot was not model-pinned (backend model not client-disclosed; attribution by Microsoft 365 client build 154.0.4258.62 and verbatim operator capture); decision path used the hub canonical roster (exact-match, lowest-record-id tie-break) as in SDR-CL1; a citation-level defect in the SDR-CL1 phase-b file (2 of 6 playbook_ids inconsistent with its own disclosed tie-break rule; names and tuples rule-consistent) was found during this run's audit and is disclosed here with the published CL1 artifact left unamended; first submission attempt was a harness-delivery miss (logged, not a caging result); supervised run with human-operated capture; supplementary run tracked separately from the 60-night battery. Provenance: public harness + registered prediction: github.com/LLong2026/squirrel-os-lindy-test (docs/sim-d/). Battery ledger: github.com/LLong2026/four-horsemen. Method covered by filed provisional 64/119,191 and PQC/DQCO filings; governance per DCAI (64/157,915). No new mechanism claimed. Information-theory lineage acknowledged: Nyquist (1924), Hartley (1928), Shannon (1948), Kolmogorov (1965). Associated receipts: SDR-CL1 DOI 10.5281/zenodo.23274887; First LLM Cage DOI 10.5281/zenodo.23265723; caging architecture paper DOI 10.5281/zenodo.23266727. DCAI community: zenodo.org/communities/dcai. Two-key curation: drafted and vetted by the system (Gabriel), published on the owner's explicit GO.

View source

Similar papers

#computer vision Review Sep 2017

Agile Software Development Methods: Review and Analysis

This publication proposes a definition and a classification of agile software development approaches and analyses ten software development methods that can be characterized as being "agile" against the defined criterion.

P. Abrahamsson, O. Salo, Jussi Ronkainen et al. · 727 citations · ⚡54
#computer vision Jun 2008

The impact of agile practices on communication in software development

The study shows that agile practices improve both informal and formal communication, but indicates that, in larger development situations involving multiple external stakeholders, a mismatch of adequate communication mechanisms can sometimes even hinder the communication.

M. Pikkarainen, Jukka Haikara, O. Salo et al. · 401 citations · ⚡48
#machine learning Review Open access Oct 2014

Software development in startup companies: A systematic mapping study

The results indicate that software engineering work practices are chosen opportunistically, adapted and configured to provide value under the constrains imposed by the startup context.

Nicolò Paternoster, Carmine Giardino, M. Unterkalmsteiner et al. · 394 citations · ⚡54
#computer vision Review Mar 2008

Agile methods in European embedded software development organisations: a survey on the actual use and usefulness of Extreme Programming and Scrum

The results show that the embedded industry has been able to apply agile methods in its development processes and that the appreciation of the agile methods and their individual practices appears to increase once adopted and applied in practice.

O. Salo, P. Abrahamsson · 238 citations · ⚡9
#computer vision Open access Jul 2017

What happens when software developers are (un)happy

Consequences of happiness and unhappiness that are beneficial and detrimental for developers' mental well-being, the software development process, and the produced artifacts are found.

D. Graziotin, Fabian Fagerholm, Xiaofeng Wang et al. · 236 citations · ⚡13
#computer vision Open access Oct 2004

Mobile-D: an agile approach for mobile application development

The Mobile-D approach is briefly outlined here and the experiences gained from four case studies are discussed, which helped develop an agile development approach for mobile application development.

P. Abrahamsson, Antti Hanhineva, H. Hulkko et al. · 225 citations · ⚡18

Related blog posts

Microsoft Research Blog Oct 12, 2026

Simulating student learning for better AI tutoring

StudentSim is a research system for evaluating and improving AI tutoring tools before they are tested with learners. It models how individuals may engage with tutors, giving feedback to improve tutor performance across subjects like chess, writing, and mathematics. The post Simulating student learning for better AI tutoring appeared first on Microsoft Research.

MIT News · Artificial Intelligence Oct 2, 2026

Documenting the tech worker movement

Writing as a participant and researcher, PhD student JS Tan SM ’22 has co-authored a new book about the rise of tech worker protests and the employer backlash that followed.

We use cookies to run the site and, with your consent, for analytics and to show ads. See our Cookie Policy.