Frozen D2 implementation · R1
Enterprise Action Requests
Two object types, seven native Event profiles and a bounded local reference implementation.
Candidate, not a released model
The package has executable checks and three native fixture installations. Both R1 responses have been read and adjudicated. Claude identified release blockers; Grok accepted with limits but missed the reproduced history defect. R1 is historical evidence and must not be adopted as a finished release. Corrections for R2 are in progress. There is no production catalog registration or release approval here.
5 bundles · 5 layers · 26 findings · 52 questions. Nine canonical object/Event types each assess all five whole-object facets. The synthetic resource, host policy and export manifest are supporting fixture structures.
Complete specification and question tree · Semantic contract · Complete field tables · Whole-object coverage
Executed checks
Fifty distinct tests passed on the source modules and the same fifty passed when all imports were routed to the standalone bundle. Three new synthetic organizational Dimensions passed native V3 and explicit nested validation. Each retains 38 native records, including 27 Events and three committed effects. A stored nested tamper passes the generic envelope check but is rejected by the companion.
Source tests · Same suite on the bundle · Three native installations · Standalone companion · Closed schema
Installation scope
The published WM-XCT-040 0.1.1 composer refuses empty fact-path maps. This object/Event-only candidate therefore uses a separately labeled new-Dimension fixture and the pinned native creator/validator. The composer was not altered and no fictitious Fact path was added. Generic automatic composition remains an open platform issue.
Trust and effect boundary
Descriptive ActionDefinitions can catalog company operations but cannot execute. The reference executor only replaces an ordered list in a synthetic local SQLite resource. Host identity, issuer verification, policy admission, disclosure and external continuity evidence remain host duties. A coherent old database cannot detect its own rollback; reconcile externally before dispatch after recovery.
Adoption instructions and limits · Exact frozen file hashes · Common independent audit packet · Current status
Audit findings and required corrections
Full critical adjudication and R2 assignment · Claude audit · Grok review · Reproduced history defect.
Grok used attachment/file/code tools despite a no-tools instruction; its evidence is labeled as tool-assisted. No unanimous acceptance, completed R2 validation or model publication is claimed.