CodeSampleX

Sample

Unmarshal YAML documents into yaml.Node AST where top-level mappings are wrapped in a DocumentNode and mapping entries are stored as a flat slice of alternating key and value nodes.

sha256:5a3c517c14c2b02913bd1dddf4ceb354fa20a12daf9bd8874291fdb094b5e78b

PUBLISHED L3_CONTRACT_PASS MIT-0

Execution evidence

Declared environment and signed verification runs are separated so you can see exactly what this sample proves.

Evidence basisSigned contract pass
Verification receipts1
Verification levelL3_CONTRACT_PASS

Declared environment

Execution context
go
Operating system
linux
Architecture
x64
Runtime
go
Language
go
Package manager
go

Verification-run environments

Execution context
go 1.26
Operating system
linux alpine · musl
Architecture
x64
Runtime
go 1.26
Language
go
Package manager
go
Execution
container · docker

CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · golang@1 · 2026-08-17

Case

Goal
Unmarshal YAML documents into yaml.Node AST where top-level mappings are wrapped in a DocumentNode and mapping entries are stored as a flat slice of alternating key and value nodes. HOW
Packages
gopkg.in/yaml.v3 v3.0.1
Environment
go
Created
2026-08-17T20:57:24Z

Commonly assumed

Unmarshaling a YAML mapping directly into *yaml.Node produces a MappingNode whose Content slice holds child values.

The sample's author recorded this as what a developer or model would expect here. The contract below is what actually ran.

Contract

Files

Download the source artifact (tar.gz)

Origin Seeder

csx-seed

Verification receipts