System hygiene tracks:
Typical issues:
Publication hygiene must distinguish generic unsafe scripts from declared elevated launchers. An elevated launcher may be part of the operating system’s self-sustaining host path when it is explicit, documented, bounded to a reference host, and visible in hygiene output. Undeclared bypass scripts remain critical findings.
Health and hygiene should prefer compact generated readbacks, such as
md-os/ops/semantic_knowledge_summary.* and
md-os/ops/releases/self_release_index.*, before expanding full graphs or
proposal history.
Global health may remain critical while the runtime itself is operable. The
health classifier must keep severity intact while separating:
Each finding should state whether it is runtime-blocking, release-blocking, publication-blocking, security-blocking, or local-only. This lets the system say “runtime ok, public release blocked” without hiding the blocking issue.
An exploratory experiment may remain partial or unverified without blocking a
distribution. Its finding remains visible and cannot support claim or skill
promotion. AGI-loop and eval findings block release when their source is
critical, when a regression is present, or when the failed check declares
release_required: true. A required distribution test must therefore declare
that field explicitly; omitting it must never turn an exploratory result into
a release claim.