Skip to content

Validator: no way to express intentionally undecided decisions #24

@Mearman

Description

@Mearman

Problem

The validator reports decision has no selected option for every decision without a selected field, regardless of lifecycle state. Decisions in proposed or experimental lifecycle states are legitimately undecided — they haven't been resolved yet.

Reproduction

sysprom add decision --name "Organisation model" \
  --option "keep-current:Keep current model" \
  --option "introduce-orgs:Introduce Organisation entity"
sysprom update node DEC1 --lifecycle 'proposed=true'
sysprom validate

Output:

Found 1 issue(s):
  - DEC1 (Organisation model): decision has no selected option

Expected behaviour

Decisions with a lifecycle state of proposed, experimental, or deferred should not be flagged for missing selected — they are intentionally open. Only decisions in accepted, implemented, or adopted states should require a selected option.

Alternatively, support a --severity or --level flag on validate to distinguish warnings from errors, so intentionally undecided decisions can be acknowledged without treating them as validation failures.

Current workaround

Accept the validation exit code 1 and manually ignore the warnings, which makes it impossible to use sysprom validate in CI as a strict gate.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions