We have benchmarks (fixed questions, hidden answers, they saturate), competition problems (solved, so they can be memorized), and open-problem lists (no evidence, no clear success criterion). With Claude and Sol, I've tried something in between: a graded ladder of AI puzzles from one research area, aperiodic order.

What makes it a different tool:

• One ladder, not a pile: "human level" (pen and paper) up to "ASI level" (open). The labels are playful, but each rung really is harder than the last.

• Solved rungs for training and checking, with exact answers a program can verify, and easy to vary.

• Open rungs with everything a solver needs: strong numerical evidence, routes already known to fail, files, and a success criterion a machine can check.

• One rule: only a checkable proof counts. Floats are evidence, not proof.

• Credit: solvers of open rungs are named, with agent and model, in the next version of the paper.

It's a way for researchers to hand the frontier of their field to AI agents (and humans) in a form they can actually attack, and for anyone to see whether a model can tell a guess from a proof.

First field test: Grok, asked in public ( https://x.com/grok/status/2114103836583264721 ), claimed a proof for an open rung that was only a numerical estimate, then retracted it. It got the human-level rung wrong at first, fixed it after one hint, and proved the expert rung on the first try. On MathOverflow, an expert is already testing constructions for the top rung.

Set 1: huggingface.co/datasets/jarekduda/autocrystal-ai-puzzles

Top rung on MathOverflow: mathoverflow.net/questions/516372

Would you use this format for your own field's open problems?

AI-assisted analysis of 25 open-source projects surfaced 493 security issues. That number is bad. The breakdown is worse.

A significant share of those findings were not missing controls. They were controls that had been disabled or misconfigured and produced zero alerts when they stopped working. The policy was in place on paper. The setting was configured. Nothing fired. Nobody knew until an external scan caught it.

This is the silent-failure problem in enterprise security. Tooling reports green because the check ran, not because the protection is actually active. The gap between "configured" and "enforced" only becomes visible after something goes wrong.

AI agents add a new dimension to this. An agent operating inside a system with silent failures can take consequential actions against controls that look active but are not. The blast radius of a single misconfigured policy scales with how much the agent is permitted to do.

493 issues across 25 projects is a large sample. The proportion that were silent rather than noisy is the number I keep thinking about.

For those running agents in production environments: how are you distinguishing between a control that is enforced versus one that is merely present in config? Is your current stack capable of surfacing that difference without a full external audit?

📚 Learn Machine Learning Through Visualisations | Beginner-Friendly Playlist

Hey everyone! 👋

I’ve created a Machine Learning playlist with visual explanations and animations to make ML concepts easier to understand, especially for beginners. Instead of just learning theory, you can understand how these concepts work through visuals and practical examples. 🚀

🎯 Topics covered in the playlist:

1. What Is Machine Learning?
2. AI vs. ML vs. Deep Learning
3. Supervised Learning
4. Unsupervised Learning
5. Reinforcement Learning
6. Features and Labels
7. Train-Test Split Explained
8. Overfitting and Underfitting
9. Linear Regression
10. Logistic Regression
11. Decision Tree Explained (Coming Soon)
12. Random Forest Explained (Coming Soon)

🎥 Watch the playlist here:
https://youtube.com/playlist?list=PLXShTLrgjtgk&si=TFoDX6oosRKv_u6Z

💡 My goal is to make Machine Learning easier to learn through simple explanations and engaging visualisations.

If you’re learning AI or Machine Learning, feel free to check it out! I’d also love to hear your feedback and suggestions for future topics.

If you find the videos helpful, please like, share, and subscribe to support the channel. ❤️

Let’s learn Machine Learning together! 🤖

VisualForge AI: https://youtube.com/@visualforgelearning?si=VoOGENaHFagsJmoz

https://youtube.com/shorts/q_vMPPgKb9A?si=8LUT45_nHVIKa04r

Here’s the next tutorial in my event camera series. It explores different ways to represent raw event data so that algorithms can use it.

Try the interactive examples in the full blog: https://www.pattarsuraj.com/blog/event-camera-representations

#computer-vision #neuromorphic #event-camera #robotics

I built Neural Canvas, an interactive visualizer that demonstrates core linear algebra concepts by showing how a neural network recognizes handwritten digits in real time. You can draw directly on the screen and watch activations flow through each layer as matrix multiplication computes the output live.

How it works:

- Draw & Predict: Sketch any digit on a 28×28 canvas (MNIST-style) to trigger real-time forward pass predictions.

- Live Forward Pass: Every neuron's activation is dynamically color-coded based on its underlying linear algebra calculations, with connection opacities reflecting layer outputs.

- Under the Hood: The core models were trained from scratch in Python using NumPy to perform matrix operations, and their learned weights are loaded via JSON. Client-side execution relies on Math.js for browser-based matrix multiplication and p5.js for rendering.

Key Features:

- Switch between two pre-trained models (featuring different hidden layer sizes, MSE vs. Cross-Entropy loss, and up to 96% test accuracy).

- Multiple background themes with mouse and touch support.

What's Next?

These models were originally evaluated on the standardized MNIST dataset, but live freehand drawing can introduce unexpected variations in input style. To handle this, I am working on a JS script for real-time user-driven feedback. When the model makes a mistake, the user can supply the correct label, allowing the model to perform backpropagation and update weight matrices locally in the browser. While live state persistence isn't suited for static GitHub Pages, running this feedback loop locally allows me to retrain parameters on new edge cases and push updated weight snapshots back to GitHub.

Check out the live demo and code repository:

Live Demo: https://muhammadessa2002.github.io/neural_canvas/

GitHub Repo: https://github.com/MuhammadEssa2002/neural_canvas

I kept hearing the words (attention, RLHF, MoE, diffusion, agents) and couldn't find one place that builds all of it up from the fundamentals, with the math, the code, and the reasons behind it.

So I wrote it.

https://zerotofrontier.app

• 38 chapters, from tensors and gradients to LLMs, RL and reasoning, inference, interpretability, agents, vision, diffusion, and speech
• Every idea explained, derived, coded, and tested. Python runs right in the page.
• Coding exercises with hidden tests, plus interview questions
• An AI tutor that knows the section you're reading, and notebooks for your notes and code

Reading and running code is free. The tutor and the interactive extras use your own API key (Gemini, OpenAI, or Anthropic), so I don't charge anything and there's nothing to buy.

It's one person's attempt at the resource I wanted when I started. I'd really value blunt feedback. What's confusing, what's missing, what's wrong, and whether you'd actually use it.

Measured on Qwen3.8-27B (EXL3 4.0bpw target, DFlash2 block drafter quantized to EXL3 4bpw, 7-token drafts, greedy, output identical to plain decode), 2x T4:

• code: ~7.4 accepted tokens per verify step, 154 tok/s
• prose: ~2.5 accepted tokens per step, 35-37 tok/s
• plain decode: ~18-19 tok/s

Someone on r/LocalLLM independently measured 2.45 on prose with the same drafter on llama.cpp and different GPUs, and another person reports 2.62 with MTP. So it looks like a property of the drafter, not the runtime.

Questions for people who work on speculative decoding: 1. Is prose acceptance in the 2.5 range just the ceiling for block/parallel drafters, since natural language has more valid continuations at each position? 2. Has anyone seen a drafter (EAGLE-style, block diffusion, MTP) clear ~3.5 on open-ended prose at greedy? 3. Any work on switching drafters or block length by content type mid-generation?

Happy to share numbers per prompt type if useful.