SYSTEM 01 / CASE STUDY

← Back to systems

GOVERNED RESEARCH SYSTEM

Governed Multi-Agent Quantitative Research System

A multi-agent research platform where probabilistic models can propose, critique and rank research candidates while deterministic validation and explicit human authority retain control.

Agentic AILocal ModelsStructured OutputsTool ControlDeterministic Validation

Problem Class

Quantitative research with multiple AI agents operating under explicit scientific and operational constraints.

Engineering Challenge

Large language models can generate hypotheses, critique ideas and assist research, but probabilistic output must not automatically become scientific truth, empirical evidence or financial authority.

Architecture

The system separates AI reasoning from deterministic scientific execution. Local inference is the default path; an external provider is an explicitly controlled route for independent scientific adjudication when required.

01RESEARCH CONTEXTbounded input and task framing
02INDEPENDENT LOCAL ROLESspecialized proposers and critics
03STRUCTURED CANDIDATESprovider contracts around model output
04DETERMINISTIC VALIDATIONreproducible empirical execution
05CONTROLLED ADJUDICATIONindependent review when explicitly routed
06HUMAN SCIENTIFIC REVIEWauthority at consequential transitions
07DETERMINISTIC EMPIRICAL EXECUTIONstate and execution remain outside model authority
AUTHORITY BOUNDARY

Models may request allowed actions and return structured research output. A deterministic authorization layer validates tool arguments, issues approvals and controls state transitions.

My Responsibility

Hands-on architecture and implementation across the boundary between model reasoning and empirical execution.

  • 01ArchitectureDesigned the separation between specialized AI roles, deterministic validation and human scientific authority.
  • 02ImplementationImplemented the orchestration layer, structured provider contracts and controlled state transitions.
  • 03Provider / Tool IntegrationIntegrated local and external providers, role-based routing, a validated tool registry and permission modes.
  • 04ValidationKept backtest and empirical execution in deterministic software rather than model-generated computation.
  • 05GovernanceImplemented system-issued approvals, auditability, provenance and paid-provider guardrails.

Critical Decisions

DECISION 01

Independent proposers instead of a single model

WHY Research generation should not depend on one model family or one reasoning path.

TRADE-OFF / EFFECT Multiple local roles add orchestration complexity while creating a more explicit comparison boundary.

DECISION 02

Structured provider responses

WHY Free-form output and unstable terminal behavior cannot safely mutate research state.

TRADE-OFF / EFFECT The provider path moved behind a Python interface with structured JSON contracts, reducing parsing ambiguity.

DECISION 03

AI does not execute backtests

WHY Empirical results must remain reproducible and independent of a model deciding how execution occurs.

TRADE-OFF / EFFECT AI contributes research reasoning, while deterministic code owns validation and empirical execution.

DECISION 04

External models are an explicit route

WHY Local inference is the default, but independent scientific adjudication may require a separately routed provider.

TRADE-OFF / EFFECT External inference is deliberate and subject to authorization and cost guardrails rather than being an implicit dependency.

DECISION 05

Authority is external to the model

WHY Model output may express intent, but it cannot create legitimate approval state.

TRADE-OFF / EFFECT Approval metadata is created and validated by deterministic authorization logic.

Trust / Safety Boundaries

The system implements explicit boundaries between model intent and system authority.

PROBABILISTIC AI MAY

Propose, critique, rank, interpret and generate research candidates or request allowed actions.

DETERMINISTIC SOFTWARE OWNS

Validation, backtesting, permission enforcement, persistence, approval metadata and controlled state transitions.

HUMAN AUTHORITY

Scientific review and high-consequence research progression remain separate, explicit authority layers.

OUTSIDE MODEL AUTHORITY

Self-authorization, broker or live authority, capital deployment and uncontrolled consequential state mutation.

Failure / Constraint → Engineering Response

OBSERVED FAILURE / CONSTRAINT

Model-generated authorization data

A local model produced a syntactically plausible authorization identifier inside generated tool arguments.

ENGINEERING RESPONSE

System-issued authority

Model-provided identifiers are treated as untrusted input and removed before approval creation. Valid authority remains system-issued metadata controlled by the authorization layer.

OBSERVED FAILURE / CONSTRAINT

Unstable CLI orchestration

An early command-line provider path produced terminal noise, repetition and unstable JSON.

ENGINEERING RESPONSE

Structured request / response contract

The provider path moved to a Python interface using structured JSON responses, making model integration explicit rather than dependent on general terminal parsing.

A model may express intent or recommendation. It must not mint the authority that authorizes its own action.

Technology / Versions

Evidenced implementation detail is shown selectively. Exact versions not captured by the evidence are intentionally qualified rather than inferred.

System 01 technology evidence
TechnologyVersion / ModelRoleEvidence basis
PythonExact runtime version not capturedOrchestration and deterministic system logicVersion qualified
OllamaExact library/server version not capturedDefault local model providerVersion qualified
qwen3.5qwen3.5:9bIndependent local proposerEvidenced
DeepSeek R1deepseek-r1:8bIndependent local proposerEvidenced
Llama 3.1llama3.1:8bPreliminary critic / screening roleEvidenced
Granite 3.3granite3.3:8bResearch-priority ranking onlyEvidenced
OpenAIProvider integrationControlled external adjudication routeEvidenced
GPT-5.4 minigpt-5.4-miniIndependent scientific adjudicatorEvidenced

Evidence

This case study uses a sanitized public boundary. No private project tree, research artifact, strategy result or proprietary logic is linked here.

SANITIZED CASE STUDYPublic architecture abstractionApproved evidence covers architecture, model roles, engineering decisions, failure-response evidence, technology history and the controlled public disclosure boundary.

Scope Boundaries

SAFE TO DISCLOSE

Multi-agent architecture, model roles, local and external provider routing, structured outputs, permission design, deterministic validation, human scientific review, technology identities and abstract failure-response decisions.

KEPT PRIVATE

Research hypotheses, strategy logic, signal definitions, feature details, formulas, parameters, thresholds, portfolio construction, execution parameters, internal state and private prompts.

NOT CLAIMED / OUT OF SCOPE

Autonomous trading, autonomous capital deployment, broker authority, air-gapped operation, audited model training or fine-tuning, guaranteed performance and production-scale brokerage execution.