docs/architecture/architecture_simplification.md

Architecture Simplification (Final Cleanup)

Objective

Refactor the current implementation to keep Creative Track innovations while removing low-value complexity that did not improve benchmark quality.

What Was Kept

• Strategic Coordinator
• Analyst Team (Schema, Domain, Document, Hypothesis, Verifier, Coordinator)
• Coordinator Synthesis artifacts
• Agreement score
• Disagreement visibility
• Replay artifacts
• Failure attribution
• Evaluation hardening
• AAT architecture and verification metrics

What Was Simplified

1) Auditors are observability-only

Filter/Schema/Aggregation auditors remain active but are diagnostics-only:

• They observe and report risk signals.
• They do not trigger retry/replan.
• They do not override coordinator decisions.
• They do not modify execution path or final action.

2) Actionable disagreement control removed

Disagreement is now a collaboration report, not an execution-control signal.

• Removed disagreement-driven control semantics.
• Disagreement records are now limited to meaningful cases only.

3) Coordinator simplified to synthesis role

Coordinator synthesis now:

• aggregates opinions,
• computes agreement score,
• summarizes disagreements,
• explains dominant analyst interpretation vs final runtime action.

Coordinator synthesis does not alter runtime execution flow.

4) Meaningful disagreement definition

A disagreement is recorded only when at least one condition is true:

• confidence spread > 0.50, or
• analysts recommend different interpretation buckets (approve/rework/request-evidence).

5) Eval output simplified

Primary verbose/research collaboration section now emphasizes:

• Mean Agreement Score
• Schema Participation Rate
• Domain Participation Rate
• Document Participation Rate
• Coordinator Syntheses Generated
• Tasks With Meaningful Disagreement

Noisy fields were removed from the primary collaboration section and moved to research diagnostics when retained.

Resulting Architecture Contract

Execution flow remains:

UNDERSTAND -> PLAN -> EXECUTE -> VERIFY -> SUMMARIZE

With additive observability:

• Analyst Team -> opinions
• Coordinator -> synthesis
• Auditors -> diagnostics only
• Replay + failure attribution -> explanation

No component except Planner / Executor / Verifier materially influences execution outcomes.