Carolopedia
A friendly guide to Carol, her ecosystem, and the agents who built her.
📖What it means
The track's logic is already generic, and everything specific to this estate has been pulled out into the instance-config seam. A client project gets it by writing one config file naming its own paths, stores and identities — no code is copied, forked or changed. This is the level the reusability arc moves tracks TO.
⚖️What it is NOT
The neighbours this word is most often confused with, and the line between them.
Not: seam-refactor
Same generic logic, but its binding facts are still hard-coded — a config file would be ignored because nothing reads one yet.
Not: as-is
As-is needs no config at all, only credentials.
🧭The nuance
A grade must not flatter the code: a track is config-only only once a second instance has actually run on its own config, not because the refactor was attempted.
🗣️Also called
instance-config awayone config file away