noCV
CFORM-103 · Clarify fields

Remove obsolete shipping fields on procurement category changes

Practice briefBugIntermediate

Switching hardware to services retains a hidden shipping address in the payload. Make conditional removal explicit.

Focused work estimate
2h + prerequisites
Priority in the scenario
High
Engineering practice
Data modeling · Forms

Estimated field mix

  • Frontend80%
  • Privacy engineering20%

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 procurement team Northroom collects purchase requests in a browser form. Work uses local stubs and cannot place purchases.

Setup prerequisites

  • Create synthetic categories and conditional request fields.
  • Stub draft revisions and submission outcomes.

Preceding work

Complete these dependencies, or supply their agreed outputs before taking this ticket.

Acceptance criteria

  • Payload excludes inactive fields
  • Discard prompts identify entered data
  • Cancel preserves category

Implementation constraints

  • Hidden inputs are not a serialization policy.

Verification to include

  • Switch empty category
  • Cancel populated category switch

Deliverables

  • Conditional payload projection

Rollout and recovery

Disable category changes until removal is corrected.

Value of the work

For the engineer: Practice state boundaries and form schema transitions.

For the team: Inspect how hidden obsolete data and duplicate requests are prevented.

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.