Structural Intelligence
MDL and EDL describe observed system structure, evidence state and change through time. The current public workspace monitors BNB without turning structure into a price forecast.
Architecture
One Evidence Core, multiple research domains.
StructEvidence keeps provenance, dual clocks, corrections, supersession, hash verification and release governance in one core. Structural Intelligence and Technical Risk add domain-specific states without creating separate truth systems.
Evidence domains
Shared integrity, domain-specific meaning
Technical Risk / CML
Identity, lifecycle events, engineering dependency, alternatives and qualification requirements use the same Evidence Core and public Verify model.
Layer Inventory
| Layer | Purpose | What it controls | What it does NOT claim | Current version |
|---|---|---|---|---|
| RDL | Defines how research questions, evidence, experiments, negative results, publication gates, corrections and supersession are governed. | Questions, evidence levels, publication gates, corrections, negative result preservation, human review. | Does not determine market state, entity truth, solvency, fraud, credit quality or investment merit. | RDL_METHOD_PILOT_v0.1 |
| RTP | Records who acted, what artifact was used, where a result came from, what transformation occurred and whether the chain can be reproduced. | Actor identity, source identity, artifact identity, SHA-256, timestamps, transformation history. | Does not certify that artifact contents are true or independently authored. | RTP_METHOD_PILOT_v0.1 |
| Structural Dynamics | Studies how real systems change in structure, state, flow and constraint. | State framing, transition language, structural dimension boundaries. | Does not predict price, issue trading signals or assign risk grades. | STRUCTURAL_DYNAMICS_METHOD_PILOT_v0.1 |
| MDL | The first Structural Dynamics domain lab, focused on evolving market structure rather than price prediction. | Capital, liquidity, behavior, consensus, time, risk and information domain boundaries. | Does not produce buy, sell, hold, timing, liquidation or return forecasts. | MDL_METHOD_PILOT_v0.1 |
| Evidence Dynamics | Studies how claims, observations, revisions and source relationships evolve around the same entity or system. | Claim normalization, observation alignment, source dependency, semantic and temporal boundaries. | Does not turn consistency into truth and does not infer misconduct from inconsistency. | EVIDENCE_DYNAMICS_METHOD_PILOT_v0.1 |
| ECL | Tests whether public claims and observations remain mutually reconcilable after time, scope, numerical, semantic and source-dependency normalization. | Temporal consistency, numerical reconciliation, semantic consistency, cross-source consistency, ACH and counter-evidence search. | Does not determine truth, legal liability, fraud, solvency or universal entity health. | ECL_METHOD_PILOT_v0.1 |
| ECN | Defines how external users contribute observations, datasets, replications, contradictions, corrections and method challenges. | Contribution taxonomy, provenance requirements, review readiness and future submission boundaries. | Public evidence challenges are accepted against defined Open Evidence Gaps. Submissions enter human review and never change claim state automatically. | ECN_PLANNED_v0.1 |
Governance Document / Charter
Answers what is allowed, what is prohibited, how research is governed, what qualifies as evidence, what may be published and how corrections are handled.
Technical Whitepaper / Specification
Answers how the system is implemented, which data models and states exist, what gates apply, what can fail and what reproduction requires.