Sample
Prove that `structlog` binding APIs do not mutate an existing logger instance.
sha256:860cb1a769dff8104efd29459c32a26bdec09b05ed739c73df0632ac4719b4e5
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
- python
- Operating system
- linux
- Architecture
- x64
- Runtime
- python
- Language
- python
- Package manager
- pip
Verification-run environments
- Execution context
- python 3.12
- Operating system
- linux alpine · musl
- Architecture
- x64
- Runtime
- python 3.12
- Language
- python
- Package manager
- pip
- Execution
- container · docker
CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · python@1 · 2026-08-17
Case
- Goal
- Prove that `structlog` binding APIs do not mutate an existing logger instance. HOW
- Packages
-
structlog 26.1.0
- Environment
- python
- Created
- 2026-08-17T03:54:30Z
Commonly assumed
A caller expects `bind` to mutate the original logger and return that same object.
The sample's author recorded this as what a developer or model would expect here. The contract below is what actually ran.
Contract
- assert logger is not logger_bound
- assert captured[0].get('user') == 'alice'
- assert 'user' not in captured[1]
Files
- NOTES.md
- csx.json
- requirements.txt
- test/contract.py
Download the source artifact (tar.gz)
Origin Seeder
csx-seed
Verification receipts
- python 3.12 · linux alpine/x64 · docker · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · python@1 · 2026-08-17 · ed25519:d91480838ac982c9