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.
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.
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.
Everyone Was Talking About Context Engineering. Nobody Had Solved Governance.
Everyone Was Talking About Context Engineering. Nobody Had Solved Governance.
The Model Already Read the README. MICA v0.1.8 Made It a Protocol
v0.1.7 made scoring a contract with fail-closed gates. v0.1.8 recognized that README-first behavior could serve as invocation — and formalized it as a schema-level protocol. This article uses simplified examples to show how the invocation gap that had existed since v0.0.1 was finally closed
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.
Your Agentic Stack Has Two Layers. It Needs Three.
Most agentic stacks cover tools and skills, but miss intent governance. Learn why a third layer is needed to stop AI drift, scope creep, and technically correct systems heading in the wrong direction.
LOGOS LawBinder: From Governed Reasoning to Audit-Grade Execution
This article explains how LOGOS v1.4.1 improves production AI reasoning with multi-engine orchestration, complexity-aware governance, and audit-friendly failure tracing.
LawBinder v1.3.0: Governance as a Kernel (Not a Guardrail)
LawBinder v1.3.0 shows how AI governance can run like a kernel, using deterministic Rust-based enforcement, replayable audit signatures, and bounded-latency policy checks in the critical path.
Turning a Research Paper into a Runnable System
Turn a research paper into a runnable system. This article shows how HRPO’s core equations were implemented with bounded policy lag, KL rejection, and execution checks to test real-world fidelity.
When My AI Got Smarter — But Also Slower
Smarter. Slower. More trustworthy. What happened when I tested SR9/DI2 on 5.0—and why progress in AI is about persistence, not perfection.
Showing page 1 of 2 · 14 matching posts