manual_slop/conductor/directives/scripts_namespace_isolated/v1.md

Scripts are namespace-isolated by directory — no from scripts.foo import bar across script dirs

What it says

Script directories (scripts/, scripts/tier2/, scripts/audit/, scripts/tier2/artifacts/) are namespace-isolated. A script in one directory MUST NOT import from a script in another directory. Scripts are not a package; they are standalone tools.

Why

Scripts are throw-away or single-purpose tools. If scripts/audit_weak_types.py imports from scripts/tier2/failcount.py, then audit_weak_types.py depends on the tier2 sandbox's internal state. The dependency makes the audit script fragile (it breaks if tier2 moves) and the tier2 scripts less isolated (they are now part of a graph, not standalone).

The pattern

# WRONG: cross-directory import
from scripts.tier2.failcount import should_give_up

# RIGHT: copy the needed function into the script, or factor it into src/

See also

• conductor/directives/file_naming_convention — the file naming rules
• conductor/directives/large_files_are_fine — large files are fine; do not split for modularity