CodeSampleX

Sample

PersistentPreRun and PersistentPostRun hooks do not cascade hierarchically; intermediate and leaf definitions shadow ancestor hooks entirely, executing only the nearest hook.

sha256:37621daef2c59c6541a26f603ca227a0a4c9ca669ae8669090859a929c393a3e

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
PersistentPreRun and PersistentPostRun hooks do not cascade hierarchically; intermediate and leaf definitions shadow ancestor hooks entirely, executing only the nearest hook. HOW
Packages
github.com/spf13/cobra 1.10.2
Environment
go
Created
2026-08-17T18:26:15Z

Commonly assumed

Defining PersistentPreRun on a subcommand or group executes in addition to ancestor PersistentPreRun hooks in hierarchical root-to-leaf order.

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