Hardcoded Configuration

Kind: anti-pattern

Layer: Enforcement Core

Record: architecture:hardcoded-configuration

Severity: discouraged

Scope: semantic_consistency, state_transaction

Formed by: Embed environment, path, credential, feature, service endpoint, or policy values directly into code, then duplicate those assumptions across runtime contexts.

Canonical: Ontology

A defect in which environment, credential or policy values are written into code instead of being supplied as configuration.

Listed in Architecture principles, after Implicit Contract and before Shared Mutable State.

Refactored by

• Externalize Configuration
• Configuration Schema
• Centralized Configuration
• Remove Secret from Code

Severity

• discouraged

Category

• Anti-patterns

Force

• Semantic consistency
• State transaction

Detected by

• codemods/entrypoints/location.entrypoint.ts
• rules/eslint/closure-paths-via-ssot.eslint.rule.ts
• rules/eslint/no-hardcoded-exclusions.eslint.rule.ts
• rules/eslint/no-inline-asset-path.eslint.rule.ts
• rules/eslint/no-port-literal.eslint.rule.ts
• rules/eslint/no-secret-value.eslint.rule.ts
• runtime/entrypoints/rule.entrypoint.ts
• runtime/entrypoints/credential.entrypoint.ts

Negated by

• Configuration Externalization
• Declarative Configuration

Violates

• Configuration Externalization

Linked from

• Semantic operations
• One home
• Anti-patterns
• Portability / Infrastructure / Deployment
• Metadata / Self-Description / Declarative Systems
• Control / Coordination / Centralization
• Security Privacy Compliance
• Severity levels
• The forces