Skip to content

docs(plans): propose F06 G0 readiness-gate values for owner review (D6) - #284

Merged
brianluby merged 2 commits into
mainfrom
docs/f06-g0-proposal
Nov 14, 2026
Merged

brianluby merged 2 commits into
mainfrom
docs/f06-g0-proposal

Conversation

@brianluby

Copy link
Copy Markdown
Collaborator

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:

  • HYPOTHESIS — quoted from PRD 066 Success Metrics / Goals (unapproved).
  • CEILING — pinned to an existing implementation limit (src/suggest/eval/, src/suggest/run.rs).
  • PROPOSED-OWNER-JUDGMENT — design leaves the number open; conservative value + rationale.

Highlights:

  • G0-2 rubric (f06-rubric/1): five dimensions from the design packet's forms, two-independent-adjudicator rule, F-D third-resolver conflict resolution (no majority vote).
  • G0-6 thresholds: per-task quality/safety values, sample floors, regression deltas, latency budget (live-model latency stays BLOCKED on F16), usefulness observation targets — all grounded in the cited PRD hypotheses; computation references protocol §7.1–§7.3 / §7.5.
  • G0-7 execution profile (f06-profile/1): all eight finite fields, ceiling-pinned where an implementation bound exists, consistent with §7.6.
  • G0-4 split: deterministic SHA256 family-hash algorithm, seed forge-f06-split-v1, 50/25/25 proportions.
  • G0-10 timing: 90 min / ≤4 cases / breaks, marked OWNER-JUDGMENT.

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.

@coderabbitai

coderabbitai Bot commented Nov 14, 2026 •

Copy link
Copy Markdown

Important

Review skipped

Auto incremental reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

Run configuration

  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: Organization UI
  • Review profile: ASSERTIVE
  • Plan: Advanced
  • Run ID: a1cffa3c-1f54-4a63-8650-9ef8b218f5aa

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • Trigger review
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

Copy link
Copy Markdown
Collaborator Author

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

@brianluby
brianluby marked this pull request as ready for review November 14, 2026 22:15
Copilot AI balanced review requested due to automatic review settings November 14, 2026 22:15
@brianluby

Copy link
Copy Markdown
Collaborator Author

@coderabbitai review

@coderabbitai

coderabbitai Bot commented Nov 14, 2026 •

Copy link
Copy Markdown
Action not completed

Already reviewed the last commit. Use @coderabbitai full review to rerun a review of the entire changeset.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

@brianluby
brianluby force-pushed the docs/f06-g0-proposal branch from e74d945 to e35d664 Compare November 14, 2026 23:39
@brianluby
brianluby merged commit eb60c95 into main Nov 14, 2026
20 of 21 checks passed
@brianluby
brianluby deleted the docs/f06-g0-proposal branch November 14, 2026 23:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants