Module components 

Component Compiler (EPIC-040, docs/SYSTEM_DESIGN.md §7).

Deterministic MVP signals:

1. explicit intent (.scc/intent.yaml components with paths)
2. package.json workspace members
3. docker-compose service build contexts
4. top-level directory boundaries

Each component aggregates: responsibilities (routes owned, docstrings INFERRED, intent DECLARED), ownership (store write edges), dependency edges (cross-component calls), and implementation (paths/symbols).

Structs

ComponentCandidate

ComponentSignal

One plugin component signal (§31 ComponentSignalProvider): a component candidacy claim. name is the component name, dirs the repo-relative directories it owns. Plugin candidates enter with the plugin boundary kind (rank 1, same as packages — never above declared/deployment/cli), merge by name with builtin candidates, and lose every conflict: a plugin may nominate architecture, never rename it.

Constants

BOUNDARY_CLI

BOUNDARY_CODE_REGION

BOUNDARY_DECLARED

Evidence class that created a component candidate (Wave 5, plan §27-30). The boundary_kind attribute records it on every compiled component; code-region is the bare top-level directory fallback and is never authoritative architecture.

BOUNDARY_DEPLOYMENT

BOUNDARY_PACKAGE

BOUNDARY_PLUGIN

Boundary kind for plugin-nominated candidates. Rank 1 (package tier): visible in compilation, never overriding declared/deployment/cli.

BOUNDARY_ROOT

LAYER_CODE_REGION

LAYER_COMPONENT

LAYER_SERVICE

LAYER_SUBSYSTEM

MERGE_THRESHOLD

Greedy merge threshold for the first (subsystem) pass.

RELPREFIX

SERVICE_THRESHOLD

Greedy merge threshold for the second (service) pass.

Functions

compile_components

compile_components_with_signals

compile_components plus plugin component signals. Signals merge by name into the builtin candidate set before clustering; empty names and empty dir lists are skipped (a contributor that cannot name a component abstains).

component_for_path

Determine the component for a path: longest matching dir prefix wins. Returns a String (candidate names are owned).

component_role

is_production_path

True when no path segment places the path outside production.

parse_prov

path_role

Repository role of a component from its implementation paths, by generic directory convention (never repository names): test, fixture, benchmark, example, and docs trees are structure, not production architecture. A single non-production role when every path shares it, mixed when production and non-production mix, production otherwise. Deterministic. Repository role of ONE path by generic directory convention (never repository names). None means no non-production segment matched — the caller maps that to production. Shared by component aggregation, skeleton labeling, and atlas scope filtering so all three agree on what “fixture” (etc.) means.

prov_rank

rel