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
"The Algorithm Did It": How YouTube's Liability Playbook Is Coming for Every Developer
What a platform's war on audio creators tells us about the future of software accountability — and why the craftsman's seal is the only thing that survives.
The README Was a Protocol. The Entrypoint Was Still Optional.
README-as-Protocol solved explicit invocation at the schema level. It did not solve entry control at the workflow level. This version adds the missing hierarchy: natural, guided, and forced activation.
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
Building a Deterministic Governance Kernel: Separating Custody from Truth
CGF separates domain truth from custody mechanics, turning AI governance from Markdown/YAML policy language into deterministic, inspectable artifacts.
Role Separation Is Not Verification: The Structural Failures Hidden in Your Multi-Agent Pipeline
A research-backed breakdown of why agent role design alone does not produce reliable audits — and what actually does
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.
Each /slop Is a Calibration Signal — AI-SLOP Detector v3.6.0 and the Claude Code Skill
Every /slop invocation records to a project-scoped history. After 10 re-scanned files, bounded self-calibration adjusts detection weights for your codebase. Here is the mechanism, the data, and what actually shipped in v3.6.0.
The Sheepwave Has a New Shape: OpenMythos and the Rise of Architecture Hype
A technical-opinion essay on OpenMythos, Claude Mythos, README-driven AI hype, and why architecture claims need source-level verification before becoming public belief.
The Difference Between a Harness and a Leash
A practical essay on why most AI 'harnesses' are still leashes: guides shape behavior, but only justified external measurement creates a real governance boundary.
Showing page 1 of 5 · 58 matching posts