Skip to content
View abdulrahimiqbal's full-sized avatar

Block or report abdulrahimiqbal

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Maximum 250 characters. Please don’t include any personal information such as legal names or email addresses. Markdown is supported. This note will only be visible to you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
abdulrahimiqbal/README.md

Rahim Iqbal

I build product and research systems where the requirements are unclear, the work crosses disciplines, and the result has to survive contact with the real world.

Recent work includes:

  • helping build a World ID-enabled rewards marketplace that reached 250,000+ users and a verified peak of 201,637 token transactions in one day;
  • shaping client products from discovery and market study through launch and iteration at Rolu Labs;
  • launching robotics and automation systems at Amazon and Tesla; and
  • building machine-checkable research workflows for AI-assisted science.

The deployment work and its evidence are collected at rahimiqbal.com, with a case study and crawlable resume.

On the research side, I'm interested in what happens after a model says something plausible.

Can the claim be checked? Can it fail cleanly? Can it be repaired? Can part of it be made formal?

The cleanest place to start is claim-checking-trace-lab: a small repo where I am keeping the trail from claim to check to result.

Two current traces:

  • Trace 001: bounded Kerr horizon claim -> numeric sanity checks -> Lean proof-status check.
  • Trace 002: overbroad Kerr claim -> missing discriminant assumption -> repaired theorem -> Lean check.

The repos below are different pieces of the same question: generate candidates, test them, and keep enough evidence that someone else can inspect the result.

Start Here

Central Trace

claim-checking-trace-lab

This is where the traces live. They are intentionally small: one claim, one check, what passed or broke, and what still isn't proved.

Trace 001:

AI-selected Kerr horizon claim
-> deterministic numeric sanity check
-> Lean proof check
-> explicit proof boundary

Trace 002:

overbroad Kerr claim
-> failed discriminant assumption
-> repaired theorem
-> Lean check with explicit assumption

Generate

aristotle_new_orchestrator

LLM-driven Lean/Aristotle research orchestration.

First-click sample campaign: docs/sample_campaign_erdos_44.md

Test

OpenAtoms

A reproducibility layer for AI-driven science and empirical research loops.

First-five-minutes trace: examples/first_five_minutes.py

Verify

KerrFormalization

Lean/formalization work around Schwarzschild and Kerr black-hole geometry.

Proof-status map: PROOF_STATUS.md

First checked claim:

KerrFormalization.Kerr.outerHorizonIsDeltaRoot

Contact

Pinned Loading

  1. OpenAtoms OpenAtoms Public

    Reproducible, inspectable experiment traces for AI-assisted science.

    Python 1

  2. numbridge_ascent numbridge_ascent Public

    NumBridge Ascent: symbolic number-language bridges formalized with Python experiments and Lean proofs

    Python

  3. PrimeVisuals PrimeVisuals Public

    JavaScript