Skip to content

Rank batteries have no place in the flagship twin-validate gate / report #24

Description

@johnjosephhorton

Severity: medium.

What happened
twin-validate covers twin-probability-job only. Ranking — a major part of this survey (a 10-message and a 16-feature MaxDiff-style battery) — lives in a separate rank-utility-twin-job path (rank.py) that the main agent-workflow guide barely references, so the headline report validated none of the ranking questions.

Suggested fix
Fold rank-utility validation into twin-validate / report build (or clearly document the parallel rank flow and link it from the report index).


Found while building a digital-twin validation for a 33-respondent SMB survey (smb.csv) end-to-end via zwill guide (survey → import → commit → one-shot marginals → twin-probability job → twin-validate → report). File/line refs are from zwill/ at that checkout.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requesttwin-workflow-reviewFindings from end-to-end survey->twin validation dogfooding (smb.csv)

    Type

    No type

    Fields

    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