PRINCIPLE // COMPLETENESS // HONESTY

Declared Variants Over Silent Substitution

A smaller tool may be correct. Pretending it is the same tool is not.

active principleeditorial
principlexkl:principle:declared-variantsrepresentation: html
Recommended Cognitive Lensrelease engineerpackage maintainersystems architect

The rule

A constrained environment may legitimately choose a smaller implementation. A production environment may legitimately choose a different implementation. The invariant is disclosure: material capability differences must be visible to the operator and machine-readable where practical.

CODE
IF capability differs materially:
    declare variant
    declare missing capability
    declare compatibility boundary
ELSE:
    do not manufacture distinction

Why XERXES cares

FOUNDER LENS // EDITORIAL

The problem is not minimalism. The problem is hidden diminution. If a system makes a tradeoff, the operator deserves to know the tradeoff exists.

This principle generalizes beyond editors or packages to model fallbacks, API subsets, security modes, generated artifacts, database adapters, and deployment targets.

Keep exploring // human pathways

Continue through adjacent ideas, products, principles, and historical lineages. These pathways preserve the relationships in the underlying knowledge graph while keeping exploration natural for a human reader.

principleCivilization Design // Build the Ground Before the Skyline

A founder-derived principle for designing coherent systems that combine durable foundations, simplicity, efficiency, effectiveness, beauty, human purpose, and long-horizon responsibility.

CONTINUE →principleFoundation Before Echelon

A XERXES design principle: preserve the lessons of foundational systems so advanced layers remain legible, efficient, repairable, and worthy of the civilization that depends on them.

CONTINUE →principleReproducible Infrastructure

A XERXES infrastructure principle: make ownership, configuration, dependencies, deployment, verification, rollback, and recovery explicit enough that systems do not become one-off artifacts understood by one operator.

CONTINUE →principleReproducible Modular Workflow

The XERXES founder philosophy that systems should be reproducible, modular, checkpointed, evidence-bearing, and resistant to one-off server craftsmanship.

CONTINUE →