HydroRoll-Team / HydroRoll-Team/OneRoll

Decide the exact-analysis capability matrix

Open
#33 0 comments 0 reactions 0 assignees View on GitHub
area:language area:statistics blocked priority:p2 type:rfc workflow:hitl
Dominant language
Python
Stars
3
Forks
1
Avg merge
3d 4h
Merged PRs (30d)
2

Description

## Parent

- #3

## What to decide

Review the exact-distribution prototype and make the product decision for which v2 constructs, limits, and failure modes OneRoll will support in v2.1 without silent approximation.

## Review inputs

- `docs/rfcs/0006-capability-matrix.json`
- `docs/rfcs/0006-analysis-contract.json`
- `docs/rfcs/0006-distributions.json`
- Prototype measurements and exhaustive-enumeration evidence from #32

## Required decisions

- Resolve every provisional `bounded` entry to supported-with-normative-limits or unsupported.
- Accept or revise state, support, operation, byte, and rational-bit ceilings.
- Accept the one-Instruction exact boundary and AnalysisValue materialization.
- Accept sequential weighted unique semantics.
- Confirm that exact mode never samples, truncates, prunes, or returns partial results.
- Move RFC-0006 from Draft to Review only after prototype evidence is complete.

## Acceptance criteria

- [ ] Each language construct has a final status and reason.
- [ ] Complexity ceilings and resource errors are normative and evidence-backed.
- [ ] The API never substitutes Monte Carlo output for an exact request.
- [ ] The final decision is incorporated into RFC-0006 and user documentation.
- [ ] Human review records explicit acceptance.

## Blocked by

- #32

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reading docs/rfcs/0006-capability-matrix.json, docs/rfcs/0006-analysis-contract.json, and docs/rfcs/0006-distributions.json, then review the prototype measurements and exhaustive-enumeration evidence from #32. Resolve each provisional entry and record the accepted limits, failure modes, and exact-mode guarantees in RFC-0006 and user documentation; done requires explicit human acceptance and moving the RFC from Draft to Review.

Written by the indexing model from the issue text.

Assessment

Tech stack
python, rust
Domain
backend-api-design, documentation
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.