Archived supporting record · Earlier methodology

This dated note retains preparation evidence, not a separate research story. SDK and Microsoft examples are separate technical material, not this incident's evidence chain, next stage or repair. Read the continuing incident case

Supporting record 04 · Methods and making · Topic 01

An evidence graph without a truth score

A conceptual map keeps source claims, approaches, attempts and outcomes apart. Its first job is to preserve uncertainty, not to manufacture confidence.

What changed

Task 7 began as a deferred representation task. We now have conceptual revision G-2: a typed node and edge dictionary, a mapping of the three seed families and six existing assertion IDs, correction rules, and a measurement dictionary. The complete methods artifact records the specification and its limits. Download G-2.

Follow a claim without upgrading it

Source inspection, upstream reported test results and a study's own execution are separate assessments. The SDK has a real source-described repair but no admitted study attempt. The Microsoft article supplies conditional guidance with no observed customer outcome. The incident has reported behavior, uncertain context and no verified safe remedy. Missing nodes stay missing.

X records the problem and acceptance criteria; Y holds context and version; Z identifies an approach revision; A is an actual authorized attempt; B is its observed or attributed outcome; C contains separate evidence assessments. C-01 through C-06 are assertion IDs, distinct from variable C. Two document formats do not make twelve independent assertions.

Define a measure before filling it

Outcome-return rate needs a prespecified mature cohort, follow-up deadline and missing-return count. Verified-success yield needs documented runtime assessment as well as frozen success criteria. Paired quality and effort require genuinely comparable tasks, equal information and explicit missing-data rules. All these values are currently undefined: no runtime cohort exists. Zero attempts is a count, not a 0% success rate.

Review and remaining gates

A separate methods reviewer accepted G-2 with limits inside the same AI-assisted workflow. This is conceptual methods review, not external validation, a fresh independent source audit, or proof of usability or benefit. The page rendering was assessed separately as publication software. No graph database, simulation, fitted transition model or numerical truth score has been produced.

The supplied review identified source-artifact SHA-256 56c8049a3cfe1dba8e792ce408f46aa42df8b8edceb7c5adbf307c9450ee11f7. The public Markdown was hashed after transcription and matches that reviewed artifact exactly. The public artifact metadata records both checksums.

At this methods milestone, a future comparison required both ordinary-document and structured conditions to receive the new v0.22.1 release fact and repeat content-equivalence checks. The later C-paper-2 milestone records that document update and its repeated check. Historical C-paper-1 stays historical. Independent corpus and representation review, runtime admission and empirical testing remain open. The conceptual artifact grants no execution authority.