TAG ARCHIVE
dynamic-harness
5 MARIA OS blog articles tagged dynamic-harness, organized as a Bonginkan topic archive for search engines and LLM retrieval.
Judgment OS / Decision Intelligence OS
Core MARIA OS research on turning organizational judgment into executable decision systems.
Agentic Company Architecture
Research on human-agent organizations, delegation boundaries, role topology, and governed autonomy.
Responsibility Gates and AI Governance
Safety, accountability, fail-closed gates, auditability, and human-in-the-loop control for AI agents.
Multi-Agent Mathematics
Formal models for convergence, stability, game theory, graph dynamics, and multi-agent evaluation.
Evidence, RAG, and Knowledge Governance
Evidence bundles, retrieval architecture, Graph RAG, knowledge trust, and auditable reasoning pipelines.
Agentic R&D and Judgment Science
Research operations, simulation labs, judgment science, recursive improvement, and experimental AI governance.
Applications Maintained by Dynamic Harness-Driven Development
A general operating model for collecting runtime evidence, planning repairs, and keeping AI-assisted products stable
This application is maintained through dynamic harness-driven development. The method treats harness results as operational evidence, converts failures into bounded repair plans, and preserves learning without exposing internal implementation details.
Harness-Driven Development: Building Agentic Systems from Runtime Evidence Backward
A development method where scenarios, gates, scorecards, and repair boundaries are designed before implementation
Harness-driven development treats the dynamic harness as the primary specification. Instead of writing agent code first and testing it later, teams define runtime episodes, failure taxonomies, gates, and evidence contracts first, then let implementation converge toward measurable behavior.
Governed Auto-Implementation: How a Dynamic Harness Turns Research Intent into Code
From design note to implementation plan, patch, replay, and approval-gated merge
Automatic implementation becomes useful only when the system can prove what changed, why it changed, which runtime episodes improved, and which authority boundaries were touched. This article defines the governed auto-implementation loop inside a dynamic harness.
Autonomous Repair Harness: Turning Runtime Failures into Safe, Reviewable System Improvements
Failure episodes, repair proposals, rollback envelopes, and approval boundaries for self-healing agentic systems
Automatic repair is the next step after automatic implementation. A dynamic harness can observe runtime failures, classify drift, draft repairs, replay evidence, and route patches through rollback and approval boundaries without allowing agents to rewrite their own constitution.
Dynamic Harness and Phase-Space Control: From virtual-talent to MARIA OS
Reframing runtime episodes, failure taxonomies, dynamic scorecards, repair proposals, and controlled self-healing as phase control for agentic society
The central question for agentic systems is shifting from model intelligence to runtime phase control. This article defines the Dynamic Harness as a Runtime Governance Layer that observes, evaluates, and controls the phase space of an agent runtime, connecting MARIA OS research with implementation lessons from bonginkan/virtual-talent.