Wire it in as-is. Adopt the tool whole, work with its shape, accept its trade-offs.
What changes if we adopt it without modification?
Decisions about tech, made deliberately.
Every external tool, library, service, or framework that crosses the path of Pantheon or kastil-systems gets the same examination. We don't drift into adoption; we don't reflexively roll our own. We look, we ask four questions, and we decide.
This page is the index. Each entry below is a candidate technology examined under four lenses, with a verdict and the reasoning behind it.
Wire it in as-is. Adopt the tool whole, work with its shape, accept its trade-offs.
What changes if we adopt it without modification?
Find or build an alternative. The candidate is solving a real problem; the candidate may not be the right shape to solve it.
What does our version look like, and what does that cost?
Use it as a source. Study the internals, the architecture, the trade-offs they made — then build clean.
What can we learn from it that we couldn't learn ourselves in the same time?
Connect it to Pantheon / kastil-systems. Find the shape where the candidate joins the spine without distorting either side.
Where does it join? What contract does it speak? What does the join look like in code?