noCV
CTYPE-101 · Establish type rules

Assign explicit types to rules-editor literals

Practice briefTaskFoundational

The prototype infers booleans from string truthiness. Type literals from AST node kinds only.

Focused work estimate
1h + prerequisites
Priority in the scenario
Medium
Engineering practice
Type systems · AST

Estimated field mix

  • Compiler and language tooling100%

Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.

Your next step

Review it, then add it to your workspace.

The board opens an editable draft; nothing is saved until you confirm it. Sign-in and workspace permissions apply, and Demo boards remain ephemeral.

Project context

Fictional rules editor Willow supports numbers, strings, booleans, records and functions in a deliberately small language. Define syntax and type rules locally; no arbitrary code execution is needed.

Setup prerequisites

  • Create synthetic AST fixtures and a written type-rule table.
  • Define source spans and structured diagnostic output.

Preceding work

No earlier ticket is required. Complete the project setup above.

Acceptance criteria

  • Number string and boolean types differ
  • Empty string stays string
  • Unknown literal kind fails explicitly

Implementation constraints

  • Do not evaluate literal source text.

Verification to include

  • Check each supported literal
  • Reject unsupported node kind

Deliverables

  • Literal checker and cases

Rollout and recovery

Reject unknown nodes while supported literals remain available.

Value of the work

For the engineer: Practice type environments, unification and explainable rejection.

For the team: Inspect whether developer tooling catches mistakes without hiding uncertainty.

Evidence boundaries

Outcome Evidence: Tests, patches, and runbooks are requested deliverables. They become Outcome Evidence only through a qualified Mission and immutable Evidence IDs.

Ownership Evidence: Independent adaptation must be observed under a declared verification policy and cite immutable Evidence IDs. Completing a planning ticket establishes no Ownership Evidence.