Writing Hub
AI governance essays, reasoning systems notes, experiment logs, and technical writing across BioAI and engineering practice.
Project Topics
Beyond M15: Why STEM BIO-AI Started Acting More Like a Governance Report in v1.8.x
STEM BIO-AI v1.8.x moved beyond M15 integration by turning its audit output into a clearer governance report with bounded scores, traceability, and release integrity.
AI Can Write the Code. It Still Cannot Place the Stone.
AI can now write code, patch files, and finish releases. But a real case from an AI-assisted release shows that the harder human work may be deciding what the system should expose, which output belongs to which reader, and how agent-generated work remains inspectable after the code is written.
The Quality Author: Taste as the Last Bottleneck in AI Development
On where craftsmanship went, why verification gaps appear in its absence, and the one practice AI cannot automate for you.
AI-SLOP-DETECTOR v3.8.1: When Code Generation Gets Cheap, Structural Trust Gets Expensive
SEO Description:AI-SLOP-DETECTOR v3.8.1 moves beyond AI code detection toward governed cleanup, safer scoring, cleanup confidence planning, manifest-aware dependency hygiene, layered architecture review, and fail-closed governance for AI-assisted software development.
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
Showing page 1 of 6 · 62 matching posts