Writing Hub
AI governance essays, reasoning systems notes, experiment logs, and technical writing across BioAI and engineering practice.
Project Topics
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.
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.
The Two Problems No One Talks About in AI Agent Coding Pipelines
AI agent coding pipelines fail not because models are weak, but because verification is structurally broken. This article identifies four empirically documented failure mechanisms — agreement bias, latent entanglement, echoing, and right-for-wrong-reasons — and proposes a concrete architecture: hash-chained audit records, hybrid recurrence scoring, dynamic context budgets, and evidence-first review across three independent axes. Covers multi-agent pipeline design, agentic code review, blueprint indexing, and P0–P4 governance gates.
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.
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.
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
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.
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.
After Auditing 10 Bio-AI Repositories, I Think We're Scaling the Wrong Layer
After auditing 10 open-source Bio-AI repositories, one pattern stood out: the field is scaling packaging faster than verification. Here is what that gap actually costs.
Everyone Was Talking About Context Engineering. Nobody Had Solved Governance.
Everyone Was Talking About Context Engineering. Nobody Had Solved Governance.
My LLM Kept Forgetting My Project. So I Built a Governance Schema.
Session loss isn't a UX inconvenience — it's a structural failure with compounding consequences for long-running AI projects. This post defines the problem precisely and introduces MICA, a governance schema for AI context management.
Showing page 1 of 2 · 21 matching posts