A small external comment turned into a useful control-layer correction.
After publishing the Self-Evo v0.1.1 document package, one issue became sharper:
witness separation is not enough.
A witness may be formally separate and still be captured if its resources, access, standing, or continuity depend on the system it is supposed to challenge.
So the rule is simple:
A witness that cannot survive saying “no” is not independent.
This became the basis for a new Self-Evo WDC v0.1.2 release-candidate package.
WDC means Witness Dependency Capture.
The package adds a focused control surface around:
- Witness Dependency Capture
- Witness Resource Floor
- Challenge Survivability Test
- Witness Resource Change Gate
- checker vocabulary harmonization
- fixture-surface verification
- contradiction and open-issue tracking
- package assembly and boundary / nonclaim controls
This is not a conformance certificate.
It is not deployment authorization.
It is not proof that any live system is witness-independent.
It is a documentation and package-control layer for making this specific failure mode visible, testable, and harder to hide.
Zenodo DOI: https://zenodo.org/records/20975581
Website entry: https://ivankotov.eu/publications/self-evo-wdc-v0-1-2/
GitHub package: https://github.com/Kot141078/advanced-global-intelligence/tree/main/official/self-evo/v0.1.2/
The useful part, for me, is that the package did not start as a planned release.
It started as a critique.
That is exactly how a governance corpus should grow.