Archimedes / DiscoForge

Philosophy

A research idea should identify its problem, evidence, difference from prior work and a way to be tested.

Architecture & control flow

1. 01

   Resolve a domain contract and route requirements to math, algorithms or architectures

2. 02

   Construct typed candidates; plan queries and build evidence graphs

3. 03

   Compare strongest priors and equivalence; demonstrate recurrent refinement and population meta-rules

4. 04

   Run route-specific Aurora gates, audit, then persist one package

Architecture outline derived from this version’s control flow.

What this version changes

Establishes the v6 contract, evidence-graph and candidate-experiment scaffolding.

Inputs & outputs

Inputs

A research direction, mode budget and replaceable retrieval client.

Outputs

Candidate genomes, evidence graphs, prior comparisons, gate reports and a discovery package.

Implementation & evidence scope

The default path uses offline evidence; numerical-success and architecture-smoke fields include synthetic values, so it does not establish empirically validated new equations or architectures.

Code & bundled material

The introduction draws on bundled notes, changelogs and central code. Software tests, synthetic diagnostics and scientific effectiveness use different evidence standards.