Skip to content

Migrate hidden-bipartite-graph-frontier-cs-algorithmic-106 #314

Description

@ifsheldon

Issue: migrate Hidden Bipartite Graph

Handle: hidden-bipartite-graph-frontier-cs-algorithmic-106
Source: algorithmic/problems/106

Provenance

  • Frontier-CS category: algorithmic
  • Source path: algorithmic/problems/106
  • Source files inspected: config.yaml, statement.txt, interactor.*, and testdata/
  • Original execution shape: interactive-style Frontier-CS benchmark

Agentics Migration

  • Mode: separated_evaluator
  • Target: linux-arm64-cpu
  • Solution protocol: zip_project with stdin/stdout
  • Evaluator: Python exact-reference checker that writes Agentics result.json
  • Public validation: one tiny committed smoke run with answer 0
  • Private benchmark: 3 official Frontier-CS-derived run(s) in official-runs.zip

Public/Private Split

Public bundle contains metadata, statement, evaluator code, and tiny validation data only. Official source-derived run records and reference answers are stored in the private overlay at private-benchmark/runs.json plus private answer files.

Acceptance Criteria

  • python3 scripts/validate_challenges.py passes in the challenge worktree.
  • Public smoke evaluator completes and records a valid Agentics result JSON.
  • Private overlay ZIP contains no symlinks or unsafe traversal paths.
  • No official private cases or reference answers are committed to Git.

Known Risks

  • The original task was interactive; this migration intentionally uses an offline exact-reference stdin/stdout contract, so query-efficiency behavior is not preserved.

Activity

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

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions