Contracts Tolerant Legacy Syntax¶

Preserve harmless legacy syntax while rejecting ambiguous meaning and normalizing one contract.

Generated example

This page is generated from evaluations/scenarios/contracts-tolerant-legacy-syntax.yaml. The scenario YAML remains the executable source of truth.

Request¶

Repository evidence¶

No repository signals.

Expected resolution¶

Resolution layer	Expected
Profile	—
Modifiers	—
Language adapters	—
Framework adapters	—

Normalized context¶

{}

Skill modes¶

None.

Conflict decisions¶

None.

Significant decisions¶

None.

Principles under test¶

Forbidden outcomes¶

Guess between conflicting semantic interpretations.
Propagate both representations into trusted code.

Scenario source¶

schema_version: 0.10.0
id: contracts-tolerant-legacy-syntax
description: Preserve harmless legacy syntax while rejecting ambiguous meaning and
  normalizing one contract.
input:
  skill: contracts-and-errors
  mode: tolerant-syntax-strict-semantics
  task: Continue accepting two documented spellings that map losslessly to one value.
expected:
  active_principles:
  - parse-dont-validate
  - design-by-contract
  constrained_principles:
  - postels-law
  - fail-fast
  suppressed_principles: []
forbidden:
- Guess between conflicting semantic interpretations.
- Propagate both representations into trusted code.
principles_under_test:
- parse-dont-validate
- design-by-contract
- postels-law
- fail-fast