Writing Hub
AI governance essays, reasoning systems notes, experiment logs, and technical writing across BioAI and engineering practice.
Project Topics
We Built AI Verification Infrastructure. Then It Found Our Blind Spots.
A technical account of the Flamehaven Verification Ledger — what it found, where it failed, and what we need the field to tell us
Stanford. Princeton. A bioRxiv Paper. So Why Did Nobody Ask Where the Data Goes?
BioClaw processes EHR data. Its primary showcase channel is WhatsApp. We audited the repository: 60/100, Tier 2 Caution. Here is what the bioRxiv paper says that the README does not.
Your Bio Repo Could Get You Fined. Here Is Why We Check Every Single One.
When a bio AI repository claims HIPAA compliance but the code says otherwise, the legal exposure falls on whoever deploys it. STEM-BIO-AI evaluated yorkeccak/bio — 322 stars, modern stack, one dangerous README line. Score: 48/100. T1 Quarantine. Full audit report with score matrix, regulatory traceability, and raw machine output.
From Repo Scanner to Audit Architecture: What Changed in STEM BIO-AI Through v1.7.8
A technical look at how STEM BIO-AI v1.7.8 became less Python-shaped, more semantically stable, and more inspectable across real audit output surfaces.
STEM-BIO-AI Audit Report: yorkeccak/bio
When a README Claim Meets a Deterministic Scanner
Beyond Repo Scanning: How AIRI Expanded the Risk Vocabulary in STEM BIO-AI 1.7.x
How STEM BIO-AI uses the MIT AI Risk Repository as a governed local risk-vocabulary layer without replacing deterministic repository scanning
When Control Becomes Authority: Calibration Governance in STEM BIO-AI 1.7.x
Why STEM BIO-AI treats calibration as governed policy instead of a free-form score-tuning console for bio and medical AI repository audits.
From Score to Workflow: Turning STEM BIO-AI Into a Local Audit System
Bio/medical AI trust should not collapse into one score. STEM BIO-AI v1.6.2 shows how deterministic auditing, evidence-led diagnostics, regulatory traceability, and bounded AI advisory can become an inspectable local workflow.
How Do You Trust the AI Auditor? STEM-AI v1.1.2 and Memory-Contracted Bio-AI Audits
STEM-AI v1.1.2 binds a bio/medical AI repository audit to a machine-checkable memory contract, then demonstrates it on a real open-source bioinformatics repository.
When an AI Pipeline Passes — But One Path Still Must Be Held: EXP-034
EXP-034 tested whether a method-locked Bio-AI governance pipeline could survive modal expansion, AlphaFold EBI observer wiring, and AG-live measurement without breaking its PASS/BLOCK judgment baseline.
The $100 Million Blind Spot: What No-Code Healthcare Builders Still Don't See
An analysis of how no-code and AI-generated healthcare apps create regulatory liability when patient data flows are deployed without prior mapping, auditability, or compliance architecture.
How Auditing 10 Bio-AI Repositories Shaped STEM-AI
After auditing 10 open-source Bio-AI repositories, we found blind spots in STEM-AI and expanded it from text-only review to code-aware trust evaluation.
Showing page 1 of 3 · 29 matching posts