Module paths 

Path rules for tools: normalisation, containment, secrets, and the protected set the model may never write.

Structs

Protected

The protected set, compiled once.

Refused

A path refused, with the reason the model is told.

Enums

Class

Why a path is protected.

Constants

REVIEW_FILE

The file a person’s spec review is recorded in, in a unit’s directory . The model never writes it — not while implementing, not while running a planning skill: an agent must not approve its own spec.

Functions

canonical_for_write

The file a write of rel reaches, workspace-relative: every existing ancestor’s symlinks resolved (they must stay inside root, which is canonical), the components that do not exist yet appended as written, and the target itself never a symlink. Every component that exists is named as the volume stores it, so on a case-insensitive volume Speccoder.toml answers speccoder.toml. Two spellings that reach the same file give the same answer; the same spelling after a directory was swapped for a symlink gives another.

is_test_path

Whether a normalised path is a test file by convention.

normalise

a/./b/ → a/b; refuses absolute paths, .., NUL and the empty path.

resolve_existing

An existing path inside root (symlinks resolved), for reading.

resolve_for_write

A path inside root to write: every existing ancestor must resolve inside the root, and the target itself must not be a symlink.