# Gooo 0.6.12 candidate: four native platforms

[Readiness run 37784414260](https://github.com/kimjooyoon/meta-ontology-go/actions/runs/37784414260)
passed all four native jobs and evidence aggregation at
`c42ebae1eb15b4e2bbb9612f8ba9f413c6c12093`. It was a candidate dispatch.
The release PR's submitted-head CI and post-merge push-to-dev readiness are
separate steps before publication.

The original platform ZIPs were downloaded, checked against the exact digests in
`candidate-artifacts.json`, and the selected JSON records retained. The binary
archives were not extracted or retained. The small original eligibility ZIP is
also checksum-verified. `candidate-readiness.json` preserves the terminal run.

`caller-observations.tar.gz` contains each platform's fresh and saved caller
construction outputs and receipt, the local baseline records, and independent
Gooo source/case files. `compare-platforms.go` checks exact JSON numbers and
compares selected source, generated program, masks, local case values, native
caller traces, four evaluation values, input separation and new inference.

All eight CI command records matched the local candidate's behavior. Each
construction retained helper 1/1 and caller 0/1 then 1/1. Four evaluation rows
matched, including the large integer case, and saved replay made zero new
predictions. These are four input rows repeated across platforms and modes.
They do not form eight independent programs or a new model quality study.

The baseline was clean local candidate `2246ec35`; the CI candidate adds the
retained research observations. Bringing merged feature PR 1384 into the release
branch produced `6d656a75cf608f732e8e8716c1080714462bb6c7` with the same file tree
as `c42ebae1`. [PR 1385](https://github.com/kimjooyoon/meta-ontology-go/pull/1385)
tracks that release preparation.

Extract the archive to a new directory, then run:

```sh
go run compare-platforms.go /path/to/extracted darwin-amd64 windows-amd64 linux-amd64 darwin-arm64
```

The observer compares saved actual readings; native execution occurred in the
linked platform jobs. The exact comparison output is in `platform-comparison.txt`.