Skip to content

feat(holmes): add native evidence review CLI over weslaw artifacts #542

Description

@flyingrobots

Rust-native audit disposition

Kept and renamed from the migrated cool-ideas wording.

Rust Holmes has native domain/application substrate for weslaw evidence artifacts, but the public executable surface is still behind the architecture story. This is a current v0.3 assurance-positioning task.

Current task

Add a native evidence review command that consumes Wesley-produced weslaw artifacts and emits deterministic diagnostics/report output.

Candidate command shape:

wesley holmes review --bundle <path> --json <path>

The final command name may differ if the CLI architecture chooses a separate Holmes binary, but the shipped surface must be native and documented.

Acceptance criteria

  • Command shape is documented before or with implementation.
  • The command consumes producer facts from files instead of recomputing them.
  • Fixture bundles cover pass, warning, failure, and unavailable-evidence states.
  • JSON output is versioned and stable enough for CI.
  • Human output is plain enough for a reviewer who has not read the full glossary.
  • The command preserves Wesley's boundary: Holmes validates and summarizes evidence; it does not own target runtime semantics.

Out of scope

  • GitHub integration.
  • MCP integration.
  • Runtime target execution.

Activity

  1. coderabbitai commented on Jun 1, 2026

    @coderabbitai
    🔗 Related PRs

    #187 - fix(ci): repair holmes comment template indentation [merged]
    #526 - feat: add rust-native doctor command [merged]
    #644 - fix(holmes): remove capability-report alias [merged]
    #686 - docs: add plain Wesley onboarding path [merged]
    #687 - docs: publish assurance capability matrix [merged]


    📝 Issue Planner

    Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.

    • Create Plan

    🧪 Issue enrichment is currently in open beta.

    You can configure auto-planning by selecting labels in the issue_enrichment configuration.

    To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

    issue_enrichment:
      auto_enrich:
        enabled: false

    💬 Have feedback or questions? Drop into our discord!

  2. added
    triage:cool-ideasExploratory idea intake that still needs scheduling, closure, or a repo move
    on Jun 24, 2026
  3. flyingrobots commented on Jun 25, 2026

    @flyingrobots
    OwnerAuthor

    Triage decision: keep this in Wesley and move it out of the inbox into lane:v0.3.0 / Goalpost: Make It Truthful.

    Rationale: A Holmes evidence review CLI is a real evidence consumer surface as long as it validates producer facts instead of inventing domain semantics.

    This is scheduled core Wesley work now, not an inbox item. The triage label is being removed as part of this state change.

  4. added
    v0.3.0Scheduled work for the v0.3.0 release.
    and removed
    triage:cool-ideasExploratory idea intake that still needs scheduling, closure, or a repo move
    on Jun 25, 2026
  5. changed the title [-]cool-ideas: add a Holmes evidence review CLI over weslaw artifacts[/-] [+]feat(holmes): add native evidence review CLI over weslaw artifacts[/+] on Jul 6, 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

    enhancementNew feature or requestfeatureNew feature or requestholmesHOLMES scoring + workflowslegend:EVIDENCEEvidence/Holmes/CI/proof worklegend:PLATFORMPlatform/infrastructure worklegend:SPECSpecification/design workpkg:wesley-clipkg:wesley-holmesv0.3.0Scheduled work for the v0.3.0 release.work:enablerCreates capability needed for a later product slicework:productDirectly improves a sponsor actor outcome

    Projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions