Documentation
¶
Overview ¶
Package projectprofile holds the downstream-project conventions the kernel used to hardcode: how a project is recognised, which ledgers it keeps, and which verification command each changed path implies. Kernel packages read this table; they never name a project.
Index ¶
Constants ¶
This section is empty.
Variables ¶
This section is empty.
Functions ¶
Types ¶
type Profile ¶
type Profile struct {
ID string
Signals []string
FeaturesPath string
ScenariosPath string
ADRPrefix string
Gate string
WebAliasPrefix string
WebAliasRoot string
Commands []Command
}
Profile describes one downstream project. Signals are the paths that must all be present for the profile to be recognised; FeaturesPath and ScenariosPath name its record ledgers; ADRPrefix is the directory its decision records live under; Gate is the command that closes a verification plan; Commands are its path-specific verification rules.
WebAliasPrefix and WebAliasRoot carry the one bundler convention a reverse-import resolution needs and cannot derive: the module-specifier prefix a project's build tooling rewrites, and the repository-relative directory it rewrites it to. `GPK-V0-027` requires that pair to be read from here and NOT hardcoded to any one repository's source root, so a profile that declares no alias resolves no aliased specifier at all rather than borrowing another project's root.