Representative Foreword

After the Code, the Structure Remains

The representative foreword of this blog: security now fails less at finding issues than at absorbing, sustaining, and acting on what has already been found.

This essay frames the entire site first. The posts on technical analysis, method, and governance all start from this same problem statement.

After the Code, the Structure Remains

Detection, Method, Governance

🔥 A Mind That Dissects Systems

🔥 Trust and Culture Beyond Technology

🔥 Code That Fixes, Not Just Runs

English timeline of PHP memory-safety research 2016–2026, original researchers, contributors, and acknowledgments

A Decade of PHP Memory-Safety Bugs: Why Do the Same Failures Keep Returning?

A technical retrospective on a decade of PHP memory-safety research, crediting original discoverers and maintainers while examining failure atomicity, re-entrancy, bailout recovery, and cross-request ownership.

October 24, 2026 · 7 min · 1474 words

PHP Memory-Safety Research Notes (2016–2026): Discoverers, Root Causes, Fixes and Evidence

A source-based provenance map of PHP memory-safety findings from 2016 to 2026, crediting original researchers and maintainers while separating issue status, reproducibility, exploitability, and patch verification.

October 24, 2026 · 7 min · 1407 words