idkmesh

Project continuation — refresh current priorities after evidence convergence

Date: 2026-08-28
Repository: MSKazemi/idkmesh

Owner request

Continue improving the public repository.

Repository state inspected

The live repository had advanced far beyond the older docs/planning/CURRENT_PRIORITIES.md snapshot.

Observed facts at this continuation point:

Diagnosis

The repository is no longer mainly bottlenecked by missing mechanisms.

The limiting state is now:

unprotected integration boundary
          +
canonical worker awaiting separate human review
          +
insufficient held-out real-task corpus
          +
zero external ACE descendants

This means the correct project posture is convergence + external evidence, not another controller, protocol, queue, or large theory layer.

Bounded action

Refresh docs/planning/CURRENT_PRIORITIES.md so it stops directing contributors toward already-completed or superseded work.

The refreshed ordering is:

  1. protect main in GitHub settings (#35);
  2. obtain separate human review of exact #91 evidence;
  3. put the real node behind the existing adapter boundary;
  4. add one trivial heterogeneous real adapter;
  5. execute/replay the first five frozen benchmark tasks;
  6. grow the held-out real corpus for #70/#30;
  7. measure diversity vs replication under fixed budgets;
  8. only then feed real measurements into scheduler/evolution policy.

In parallel, ACE remains HOLD_COHORT_1: recovered review capacity is not reproduction evidence.

Preserved invariants

Community impact

A current priority map reduces contributor misdirection and duplicate implementation. Newcomers and agents should now see that the highest-value work is no longer inventing mechanisms, but crossing the remaining protection, witness, benchmark, and external-community evidence gates.