Skip to content

Generalize reorderer handling of statement-initial modifiers #24

@rmichaelthomas

Description

@rmichaelthomas

Severity: low (maintainability / process)

The reorderer assumes the verb is first (modulo leading articles). A statement-initial modifier breaks that assumption.

Context

Adding the inherited operator (PR #17), the build spec asserted "no reorderer change needed," but the CLI reorder path rejected a leading inherited as an invalid verb-prefix; parse() alone worked. A pass-through case was added: strip a leading inherited, reorder the remainder, re-prepend.

Why it matters

Any future statement-initial modifier (a negation, a modal, a second provenance word) will hit the same wall and need its own special case.

Recommendation

  • Generalize the reorderer's notion of a "leading modifier prefix" once, rather than special-casing each word.
  • Update the build-prompt/spec template to flag the reorderer explicitly whenever a new word can appear before the verb.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions