Code Clarity Critical Path Boundary¶

Verify that consequential state changes favor traceable decisions and failures over terse code.

Generated example

This page is generated from evaluations/scenarios/code-clarity-critical-path-boundary.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¶

Hide the state transition in an implicit callback.
Use unexplained defaults for authorization decisions.

Scenario source¶

schema_version: 0.10.0
id: code-clarity-critical-path-boundary
description: Verify that consequential state changes favor traceable decisions and
  failures over terse code.
input:
  skill: code-clarity
  mode: explicit-critical-path
  task: Implement an authorization-sensitive state transition with an audit effect.
expected:
  active_principles:
  - explicit-over-implicit
  - no-magic
  - principle-of-least-astonishment
  constrained_principles:
  - small-functions
  suppressed_principles: []
forbidden:
- Hide the state transition in an implicit callback.
- Use unexplained defaults for authorization decisions.
principles_under_test:
- explicit-over-implicit
- no-magic
- principle-of-least-astonishment
- small-functions