Carolopedia

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

๐Ÿ“– Carolopedia โ€บ Estate-boundGuide page

Estate-bound

Concept a word Carolverse uses with a precise meaning

๐Ÿ“–What it means

The track's work is ABOUT an estate โ€” monitoring it, auditing it, governing it, billing it. Re-use does not mean copying code; it means pointing the same machinery at the PROJECT'S own records. Those records are the estate kernel: the project's own registry, scheduler, run-audit store and backlog. So an estate-bound track refuses until the project has a kernel, and deploys once it does.

โš–๏ธWhat it is NOT

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

Not: seam-refactor

A different blocker entirely โ€” hard-coded facts, not missing records. Installing a kernel does not help a seam-refactor track.

Not: estate kernel

The kernel is the four platform stores a project needs; estate-bound is the grade describing tracks that require them.

๐ŸงญThe nuance

Kernel-first ordering: the blueprint enablement refuses an estate-bound track by name while the project has no kernel, and that refusal is the law working, not a fault.

๐Ÿ—ฃ๏ธAlso called

about this estateneeds the project's own records

๐Ÿ”—Related ideas

Reuse levelEstate kernelSeam refactor