research/dashboard

Project Dashboard

Imported from research wiki.

  • research
  • status
  • dashboard

APO Research Dashboard

Last updated: 2026-04-09

This is a non-canonical orientation page for the current APO workspace. It is meant to answer three questions:

  1. What do we already have?
  2. What is the current bottleneck?
  3. What should we do next?

1. Current Tracking Surface

The intended human-readable workflow already exists in outline form:

  • Working/research/wiki/ for track summaries and dashboards
  • Working/research/questions/ for one-question-per-file briefs
  • Working/research/outputs/ for produced memos
  • Working/research/reviews/ for adversarial or council-style review
  • Working/research/raw/ for imported external materials

Current reality:

  • wiki/ exists and contains track stubs
  • questions/ exists and contains three pilot briefs
  • outputs/ does not exist yet
  • reviews/ does not exist yet
  • raw/ does not exist yet
  • .omx/plans/ does not exist yet

Interpretation:

  • The repository already has the workflow shape.
  • It does not yet have a populated progress ledger.
  • The next useful move is not to redesign the system, but to start filling it.

2. Canon Snapshot

Source of truth: APO_MASTER_INDEX.md

High-level state as of Version 2.0, March 24, 2026:

  • 13 PROVEN/FORCED/THEOREM items in the core physics chain
  • 12 DERIVED items
  • 3 ARGUED items in the core chain
  • Gravity chain closed structurally
  • c no longer free
  • Yang-Mills mass gap derived within APO
  • sin^2(theta_W) = 1/3 argued
  • Two active satellite tracks: Navier-Stokes and Riemann Hypothesis

Still load-bearing or unresolved:

  • Fermion generations: argued, not fully closed
  • Weinberg angle: argued, not fully closed
  • Newton’s constant G: still free
  • Cosmological constant Lambda: still free
  • Standard Model parameter set: still free
  • RH route: main load-bearing gap is Step 10f, the dynamic drive toward sigma = 1/2
  • NS route: main rigor concern is the epsilon-discretization step for KC on continuous velocity fields

3. Existing Track Lanes

APO Core

Existing wiki page:

  • Working/research/wiki/apo-core.md

Existing pilot brief:

  • Working/research/questions/apo-core-pilot.md

Actual stated next question:

  • Identify which open or argued dependency chain in APO_MASTER_INDEX.md most deserves the next focused non-canonical memo.

Best immediate use:

  • Produce one memo selecting a single target chain and justifying it.

Existing wiki page:

  • Working/research/wiki/navier-stokes.md

Existing pilot brief:

  • Working/research/questions/ns-pilot.md

Actual stated next question:

  • Build a first-pass literature and problem-map memo without editing protected NS documents.

Best immediate use:

  • Create a problem decomposition memo and isolate the epsilon-discretization rigor issue from the master index.

Riemann Hypothesis

Existing wiki page:

  • Working/research/wiki/riemann-hypothesis.md

Existing pilot brief:

  • Working/research/questions/rh-pilot.md

Actual stated next question:

  • Build a route-comparison memo without editing protected RH documents.

Best immediate use:

  • Write a route memo centered on the Step 10f bottleneck and candidate routes such as the Bhattacharyya-Bessel correspondence.

The cleanest operating pipeline for this repo is:

  1. Read APO_MASTER_INDEX.md for current canon and open items.
  2. Select one track only: APO Core, NS, or RH.
  3. Start from the matching brief in Working/research/questions/.
  4. Produce one memo into Working/research/outputs/.
  5. If the memo makes a strong claim, create a challenge memo into Working/research/reviews/.
  6. Update or add a wiki dashboard page in Working/research/wiki/.
  7. Only after the non-canonical memo survives review should any canonical edit be proposed.

This keeps progress legible and prevents the repo from dissolving into scattered one-off notes.

5. Practical Next Queue

If the goal is to reduce confusion fast, the next queue should be:

Immediate

  • Create Working/research/outputs/
  • Create Working/research/reviews/
  • Create Working/research/raw/
  • Produce exactly one first memo from one existing pilot brief

Best first memo candidates

  • APO Core: choose the single best argued dependency chain to attack next
  • NS: write the discretization-rigor memo
  • RH: write the Step 10f route-comparison memo

Near-term canon-facing items already named by the master index

  • NS discretization remark
  • Notation remark in apo_master.tex
  • Master paper revision incorporating March 24 results

6. Recommendation

Do not invent a new tracking system.

Use the one already present:

  • wiki pages for orientation
  • question files for bounded tasks
  • outputs for memos
  • reviews for challenge passes

What is missing is not a workflow. It is the first populated cycle through that workflow.