Report missing rules-editor record fields without losing known fields
Reading an absent field turns the whole record into unknown and suppresses later valid diagnostics. Preserve field-level information.
- Focused work estimate
- 3h + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Type systems · Error recovery
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.
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
Complete these dependencies, or supply their agreed outputs before taking this ticket.
- CTYPE-101 · Assign explicit types to rules-editor literals
- CTYPE-102 · Resolve expression identifiers through lexical scope
- CTYPE-103 · Explain rules-editor operator operand mismatches
- CTYPE-104 · Check function calls for arity before argument inference
- CTYPE-105 · Unify rules-editor type variables with an occurs check
Acceptance criteria
- Existing field returns declared type
- Missing field names available keys within a cap
- Later checks retain known types
Implementation constraints
- Do not expose arbitrary source values in diagnostics.
Verification to include
- Access known field
- Access absent field then known field
Deliverables
- Record-access rule and recovery cases
Rollout and recovery
Reject absent-field expression only while preserving surrounding scope.
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.