Repository navigation
docs(plans): propose F06 G0 readiness-gate values for owner review (D6) - #284
Conversation
|
Important Review skippedAuto incremental reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the
|
8dab0ff to
56e29e8
Compare
Review: F06 G0 proposal — Approve (merge before #283)Documents only; no code. The proposal keeps every value labelled PROPOSED with provenance (HYPOTHESIS / CEILING / PROPOSED-OWNER-JUDGMENT) and separates owner-judgment values from mechanical ones.
Generated by Claude Code |
|
@coderabbitai review |
Action not completed
|
There was a problem hiding this comment.
Note
Copilot was unable to complete this review at the selected tier due to model policy or plan restrictions.
🟡 Changes recommended
The documentation contains a mismatched serialized enum value (intersect-withs vs the implemented intersects-with), which could mislead readers and propagate incorrect strings into downstream usage.
1 open issue
What changed in this PR
Adds a new planning document that drafts PROPOSED F06 G0 readiness-gate values (G0-1…G0-10 + G0-11 checklist) for owner review per decision D6, including rationale, provenance tags, and evidence expectations.
Changes:
- Introduces a comprehensive proposal enumerating all G0 gates with proposed thresholds/settings and supporting rationale.
- Separates owner-judgment sign-off items from purely mechanical procedures and ties each proposal to cited sources/implementation ceilings.
| File | Description |
|---|---|
| docs/plans/2026-11-13-f06-g0-proposal.md | Adds a new D6 proposal document defining PROPOSED F06 G0 readiness-gate values, procedures, and evidence requirements for owner review. |
Review effort: Balanced
e74d945 to
e35d664
Compare

Summary
Drafts PROPOSED F06 G0 readiness-gate values for owner review, per decision D6 (delegate: draft proposed G0 values first, then approve). Documents only — no approval recorded, no participants contacted, no code changes.
Deliverable:
docs/plans/2026-11-13-f06-g0-proposal.md.What's in the proposal
All ten D6 gates (G0-1…G0-10) plus the G0-11 facilitator checklist row, each with a proposed value/setting, rationale, owner-judgment-vs-mechanical classification, and the evidence that satisfies it. Every numeric value is labeled PROPOSED and tagged by provenance:
src/suggest/eval/,src/suggest/run.rs).Highlights:
f06-rubric/1): five dimensions from the design packet's forms, two-independent-adjudicator rule, F-D third-resolver conflict resolution (no majority vote).f06-profile/1): all eight finite fields, ceiling-pinned where an implementation bound exists, consistent with §7.6.forge-f06-split-v1, 50/25/25 proportions.A top-of-file owner decision checklist separates the sign-off surface (owner-judgment values) from mechanical procedure.
Owner must decide
Sign-off required: G0-1 rights defaults; G0-2 rubric; G0-4 split/seed/floors; G0-6 all thresholds/floors/deltas; G0-7 non-ceiling profile fields; G0-9 mapping-execution deferral acknowledgment; G0-10 counterbalancing + timing. Mechanical (no number sign-off): G0-3, G0-5, G0-8, G0-11.
Status
PROPOSED — nothing approved. Draft PR; do not merge. Ticket veans
#8(id 1396). Closes no gate, enables no generation, makes no quality/usefulness claim.