core

Provenance

• Source: .spec/spexcode/.plugins/core/spec.md
• Source SHA-256: 3386b16a2987d81d736d8b41f898c002d0c04b3750c4db119c046592ffca6e19

Use noun-first CLI commands; spex help is the authoritative command map.

Anything a human needs to inspect, whether a file or a local webpage, goes out through spex session files add or spex session web add: never paste an absolute path or host:port, and never start a static server yourself.

When this session has a clearly running child session (active or parked), the parent is supervising rather than finished: declare park, not done/awaiting, until the child reports a settled state.

1. Spec first: before governed code, read its spec body with spex spec owner <path> or spex spec search. Update that current-state body with any changed intent.
2. Commit before declare: commit the code and spec it justifies before done or merge; independent intent gets its own node.
3. Keep the loss signal honest: run spex spec lint (the blocking correctness gate) and spex eval lint --changed. Measure changed scenarios through the real product, commit the verified tree, then file with spex eval add; the reading's codeSha must name that commit.