TAG ARCHIVE
harness-driven-development
4 MARIA OS blog articles tagged harness-driven-development, 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.
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.
動的ハーネス駆動開発により保守されるアプリケーション
Runtime evidenceを収集し、改修計画へ変換し、AI支援プロダクトを安定運用するための汎用モデル
このアプリは動的ハーネス駆動開発により保守されています。Harness結果を運用証跡として扱い、失敗を境界付きの改修計画へ変換し、内部実装の詳細を公開せずに学習を残す方法です。
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.
ハーネス駆動開発：Runtime Evidenceから逆算してAgentic Systemを作る
実装より先にscenario、gate、scorecard、repair boundaryを設計する開発方法論
ハーネス駆動開発では、dynamic harnessをテスト補助ではなく主仕様として扱う。promptやtoolを書く前に、runtime episode、failure taxonomy、scorecard、authority boundaryを定義し、実装を測定可能な振る舞いへ収束させる。