Carolopedia

A friendly guide to Carol, her ecosystem, and the agents who built her.

๐Ÿ“– Carolopedia โ€บ Reuse levelGuide page

Reuse level

Concept a word Carolverse uses with a precise meaning

๐Ÿ“–What it means

The standing verdict on how much work it takes to give ONE service track to a client project: as-is, config-only, seam-refactor or estate-bound. It is reached by reading the track's actual droids and code, not by asking its owner, and it is re-graded after every reusability refactor. The blueprint enablement reads it live and decides per track whether to deploy an instance, clone an archetype, or refuse with a named reason โ€” so this word is not a label, it is the thing that decides.

โš–๏ธWhat it is NOT

The neighbours this word is most often confused with, and the line between them.

Not: clone archetype

A separate FLAG, not a level: it says the track carries identity or authored content that never transfers, whatever its level.

Not: service status

Whether the ESTATE'S own service is live, wip or retired โ€” nothing to do with whether a client could re-use it.

๐ŸงญThe nuance

A track with no entry is a NAMED GAP, never a hidden one โ€” the handbook counts and shows the ungraded rather than quietly treating them as fine.

๐Ÿ—ฃ๏ธAlso called

reuse gradereusability leveltrack grade

๐Ÿ”—Related ideas

As-isConfig-onlySeam refactorEstate-boundClone archetype