Skip to content

L08-02 — Build deterministic no-provider policy over the same action space #62

Open

Description

@mberrys

Outcome

Implement a rules-only policy that answers the same #61 questions (operation head plus target heads, typed choices, reason codes) for selected tasks: explanation, eligible-route ordering, and safe-next-action fallback. The provider port treats it as one more provider, so a model can replace it without any consumer change. This is the parity baseline every model candidate in #63 must beat per task.

Parent and boundary

Parent: #9. Owner: proposed Decision module. This issue owns one bounded slice of Bounded Decision Worker; consume accepted upstream contracts and keep PDF/verdict/publication authority with Core.

Acceptance

  • The offline product stays useful, and every output cites Core evidence by row index.
  • Rules emit degenerate but valid distributions (or ABSTAIN with a reason) that pass the L08-01 — Define indexed decision state and one-request question contract #61 validator unchanged.
  • Failure case: provider absence cannot suppress a manual path or invent technical claims. A consumer that branches on "rules vs model" instead of the typed answer fails.

Required proof

No-provider parity tests (same request → same validated observation shape as a model provider) and evidence-citation tests. Record the exact source SHA, test command or hosted run, fixture/artifact identity, and any skipped or unavailable lane. Run the repository's mapped proof and check-change gate for a PR.

Handoff

Record changed files, observed result, remaining risk, and a 1–3 sentence anti-slop review. Completion means acceptance evidence, not merely a merged implementation.

Sources

Approved master roadmap · Legacy/research input (legacy #584) · North Star: jev-ultrafast@1231850a; see the translation table in #9.


Generated by Claude Code

Activity

  1. changed the title [-]L08-02 — Build deterministic no-provider baseline[/-] [+]L08-02 — Build deterministic no-provider policy over the same action space[/+] on Oct 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions