internal/

Package config loads strictcode.toml through the strictspec-generated reader and implements the consumer-native checks the schema cannot express (DESIGN.md section 12.3):

Package engine is the stateless batch pipeline (DESIGN.md section 9): load config (hard errors), read the workspace from disk, extract the one shared relation, run the enabled checks, produce findings.

Package extract builds the interaction relation from a loaded workspace: the import-graph extractors for the language trio (DESIGN.md sections 6.2-6.4, schema/SPEC.md).

Package findings is the output layer: the findings model, the schema-valid machine document (self-validated through the strictspec findings reader before it is handed to the framework, which validates it again against the declared payload schema), the human-readable text rendering, and the exit-code rule.

Package fix is the tier-1 fix engine (DESIGN.md section 7, SPEC.md section 7): a whitelist of hand-proven transforms plus mechanical re-verification.

Package fixture builds on-disk workspace fixtures for tests: a map of relative paths to file contents, written into a temp directory.

Package registrydump renders the committed registry artifacts: REGISTRY.json (the machine-readable rule registry the CI release diff classifies bumps from) and docs/MATRIX.md (the language x feature support matrix generated from the registry and the language profiles).

Package relation implements the interaction relation — the primary artifact of extraction (schema/SPEC.md).

Package rules is the rule registry: the Go declarations behind CATALOG.md.

Package testctx implements the shared test-context predicate (DESIGN.md section 6.4): one definition of "non-production", computed on the slash-separated path relative to the project root, shared by every check and every extractor.

Package treesitter is strictcode's single parsing path: a thin, disciplined layer over the official tree-sitter CGo bindings (the binding-benchmark winner; see BUILDLOG.md).

Package workspace loads the analysis inputs strictcode reconstructs from disk (DESIGN.md section 6.6): the rlsbl workspace file (.rlsbl-monorepo/workspace.toml) when present, the per-member manifests (pyproject.toml, package.json, go.mod), declared dependency scopes, and manifest-declared entry points.