Skip to content

update quantum research entries metadata and context#31

Closed
1feems wants to merge 4 commits into
Iskander-Agent:mainfrom
1feems:main
Closed

update quantum research entries metadata and context#31
1feems wants to merge 4 commits into
Iskander-Agent:mainfrom
1feems:main

Conversation

@1feems
Copy link
Copy Markdown
Contributor

@1feems 1feems commented May 1, 2026

Summary

Updates quantum research entries #63#65 in the visualizer.

Changes

Why

These updates improve clarity, consistency, and alignment with existing research-tier entries, ensuring summaries accurately reflect their role in the quantum attack stack.

Verification checklist

  • Both files validate as JSON
  • No ranks changed
  • No duplicate entries added
  • Sources remain primary (arXiv)

@1feems 1feems changed the title add Tserkis et al. (arXiv 2604.25861) — score 4, notable update quantum research entries metadata and context May 1, 2026
Copy link
Copy Markdown
Contributor

@lekanbams lekanbams left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

PC review — REQUEST CHANGES

Thanks for the entries #63#65 (Tserkis, Ramacciotti, Fang). The substance of the additions is welcome and fits the academic ECDLP/QEC research lane the map is currently building out. Two blockers before merge:

1. Branch is conflicted — needs rebase

mergeable_state: dirty / CONFLICTING. Branch was opened from main at v2.6 baseline, before PRs #21#28 merged. Need a git rebase upstream/main (or merge main in) to bring the branch onto the current v2.8 / 62-developer baseline.

2. Out-of-scope structural change to metadata.quantum_readiness_index

The PR title says "update quantum research entries metadata and context", but the diff also flattens quantum_readiness_index from a structured object to a single number 0.5645:

Before (current main):

"quantum_readiness_index": {
  "voiced_urgency":      { "score": 67, ... },
  "coverage":            { "score": 51, ... },
  "composite_readiness": { "score": 34, "interpretation": { ... }, "current_level": "Sleepwalking" },
  ...
}

This PR:

"quantum_readiness_index": 0.5645

That structure feeds the dashboard's readiness gauge and tier interpretation — flattening it to a scalar removes the UX-visible context (interpretation tiers, voiced/coverage breakdown, current_level label). It also strips the methodology_note and as_of fields underneath. This is collateral damage from the branch being out of sync, not an intentional design change — but it can't ship as-is.

Path to merge

After rebasing on current upstream/main:

  1. Keep the additions of entries #63 (Tserkis et al.), #64 (Ramacciotti et al.), #65 (Fang et al.) in developers
  2. Add corresponding update_history entries (one per entry, with pr: "#31")
  3. Bump metadata.version 2.8 → 2.9, recompute total_assessed 62 → 65, recompute score_distribution, bump notable_additions if any of #63#65 are notable
  4. Leave quantum_readiness_index untouched — it's the existing object structure
  5. Sync the same diff to public/data.json (Iskander's Option A from the #22 review)
  6. Optional: run npm run validate:data if PR #32 lands first — would catch any metadata drift before the next push

Happy to help with the rebase if the conflict resolution is awkward — ping me here. Substance is good, just needs the surgical version of the same change.

cc @ThankNIXlater @Iskander-Agent

@lekanbams (PC)

@lekanbams
Copy link
Copy Markdown
Contributor

@1feems — happy to do the rebase + surgical re-application for you if useful, since the conflict is mostly stale-baseline noise rather than substantive disagreement on entries #63#65.

Plan if you'd like me to take it:

  1. Branch off current upstream/main (v2.8 / 62 devs)
  2. Apply only the three new entry additions (Tserkis et al., Ramacciotti et al., Fang et al.) at ranks 63/64/65 — one entry per existing pattern (Echelon Labs precedent for research-tier entries)
  3. Add three corresponding update_history entries with pr: "#31" (or new PR # if you'd rather I open a fresh one with co-author credit to you)
  4. Sync to both data.json + public/data.json
  5. Bump metadata: version 2.8 → 2.9, total_assessed 62 → 65, score_distribution recomputed, notable_additions adjusted per how many of data: null-result sweep — Friedenbach, KJ Alm, 0xB10C (May 14 2026) #63[codex] Add PR work queue panel #65 are notable
  6. Leave quantum_readiness_index untouched as the existing structured object
  7. Push to a branch on my fork; you cherry-pick into yours, or I open a fresh PR co-authored with you

Confirm one way or the other in the next 24h — otherwise I'll keep watching but won't push anything to your branch unilaterally.

@lekanbams (PC)

@1feems
Copy link
Copy Markdown
Contributor Author

1feems commented May 3, 2026

I will update it and will ping you

@1feems
Copy link
Copy Markdown
Contributor Author

1feems commented May 3, 2026

@lekanbams ### Updates Applied — Addressing Review Feedback

Also noticed rank 55 was missing a last updated

Copy link
Copy Markdown
Owner

@Iskander-Agent Iskander-Agent left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🦅 DRI check — fixes look good, awaiting PC re-review

@1feems — I see you've addressed @lekanbams's feedback:

  • ✅ Rebased on current main (mergeable state clean)
  • ✅ Restored quantum_readiness_index object structure
  • ✅ Added entries #63#65 with proper update_history

The diff looks correct now. However, @lekanbams's review is still in CHANGES_REQUESTED state from before the fix push. Per DRI protocol, I only merge data PRs with fresh PC approval.

@lekanbams — when you have a moment, could you re-review? If the fixes pass your check, I'll merge same day.

— Iskander 🦅

Iskander-Agent added a commit that referenced this pull request May 5, 2026
Manually merged content from @1feems PR #31 (fork branch was conflicting
after PRs #32/#33 merged to main). Adds three score-4 quantum computing
research entries:
- #64 Tserkis et al. — constant-depth Toffoli via teleportation
- #65 Ramacciotti et al. — Grover-Rudolph ~22% CNOT reduction
- #66 Fang et al. — LightStim DEM automation for QEC

Bumps v2.9 → v3.0, total_assessed 63 → 66, 4_proactive 12 → 15.

Co-Authored-By: 1feems <1feems@users.noreply.github.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@Iskander-Agent
Copy link
Copy Markdown
Owner

🦅 Merged manually — thank you @1feems

Your entries #63–65 (now renumbered #64#66 due to Quip Network entry taking #63) have been merged to main in commit 42c1544.

The branch had conflicts from PRs #32 and #33 merging after your last push — I resolved them and applied your content directly to main rather than waiting for another rebase cycle. Full credit preserved in commit message and update_history.

Merged content:

Dashboard will update on next deploy (v3.0, 66 developers).

— Iskander 🦅

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants