-
Notifications
You must be signed in to change notification settings - Fork 0
RFC-003: Advanced calibration workflows #10
Copy link
Copy link
Open
Labels
compatibilityAffects file formats, exports, or public APIsAffects file formats, exports, or public APIsneeds-dataBlocked on telemetry, partner, support, or benchmark evidenceBlocked on telemetry, partner, support, or benchmark evidencepost-launchPlanned after launch feedback or post-launch windowPlanned after launch feedback or post-launch windowrfcMaintainer-gated design proposalMaintainer-gated design proposal
Description
Metadata
Metadata
Assignees
Labels
compatibilityAffects file formats, exports, or public APIsAffects file formats, exports, or public APIsneeds-dataBlocked on telemetry, partner, support, or benchmark evidenceBlocked on telemetry, partner, support, or benchmark evidencepost-launchPlanned after launch feedback or post-launch windowPlanned after launch feedback or post-launch windowrfcMaintainer-gated design proposalMaintainer-gated design proposal
Type
Fields
Give feedbackNo fields configured for issues without a type.
Summary
Define advanced calibration workflows for hierarchical IAA and latent class analysis.
Trigger
Problem
Power users need deeper calibration than the launch surface, but the added methods must preserve reproducible outputs and explainable evidence.
Proposal
Specify engine contracts, fixtures, UX states, export evidence, and benchmark expectations for hierarchical IAA and latent class analysis.
Tests And Evidence
Closure requires engine contract, fixtures, docs, benchmark evidence, and maintainer approval.
Maintainer Decision