Content status: 16 September 2026Website 2.4.0
DOCUMENTS & REVIEW PATH

A strong first overview should be easy to understand. Sensitive depth should follow only when the review actually requires it.

The public website explains architecture, evidence, limitations and development status. The Executive Overview consolidates those elements into a document that can be shared internally. Deeper technical or confidential material is not published indiscriminately; access is staged according to the purpose and depth of the review.

Public overviewQualified discussionDeeper material by review need
EXECUTIVE OVERVIEW

A document that can be forwarded – when ten pages are more useful than nine browser tabs.

The public summary brings together six elements: the architecture, Version 1 evidence, APS, the Version 2 validation path, the planned later live-validation stage and documentation principles. It is available in English and German and is written for a professional reader without requiring knowledge of internal project terminology.

PDF · 10 pagesEnglish & GermanVersion 1.4 · 16 September 2026
PUBLIC EXECUTIVE OVERVIEW

The framework in ten pages – without burying the reader in internal project terminology.

The Executive Overview summarises the documented Version 1 research state, the APS Risk Layer, the Version 2 validation path, the planned later live-validation stage and the principles of traceable documentation. It is deliberately public: enough substance for an initial domain, technology or strategic assessment, without exposing sensitive core logic.

ÖffentlichPDF · 10 Seiten · Version 1.4 · Stand 16.09.2026

Executive Overview · Deutsch

German version with the same structure for German-language review and internal circulation.

Classification: The Executive Overview is not a sales prospectus and makes no return promise. Historical results are described only within the stated data, rule and test conditions.
Review path in the PDF: Since Version 1.3, steps 01–06 are explicitly identified as a condensed view and mapped to P0–P7, G1–G7 and the project phases. The PDF therefore no longer uses a separate fourth roadmap.
EVIDENCE & VALIDATION BRIEF

The second public document focuses less on project introduction and more on evidence discipline.

The brief classifies key statements by evidence status, limitation and next acceptance criterion. It allows a reviewer to see what is already documented and what Version 2 must still demonstrate before confidential material is needed.

ÖffentlichPDF · 10 Seiten · Version 1.1 · Stand 16.09.2026

Evidence & Validation Brief · Deutsch

German version with the same evidence structure for German-language review.

INSTITUTIONAL FACT SHEET

For initial internal circulation, one page is sometimes enough.

The compact Fact Sheet condenses the architecture, documented research state, potential institutional relevance and staged review process into a single A4 page. It deliberately remains an initial institutional snapshot; the subsequently added planned live-validation layer is explained on the website and in the updated Executive Overview. For substantive review, the Executive Overview and Evidence & Validation Brief remain the more important documents.

ÖffentlichPDF · 1 Seite · Version 1.1 · Stand 16.09.2026

Institutional Fact Sheet · Deutsch

German one-page version for German-language strategic discussions.

Document and website versioning: Public PDFs and the website are versioned independently. An older document date therefore does not automatically mean that its substance is obsolete. A PDF is updated when its own content changes; later website additions are not silently back-dated into an existing download. The content, version and status shown in each document remain authoritative for that document, while the clearly stated current website status covers web content added later.
Executive short view 01–06: The six steps in the Executive Overview are not an additional roadmap. They are a condensed reading view of the technical work packages P0–P7, validation gates G1–G7 and project phases explicitly mapped on the Project Status page. From Version 1.3, the document's deeper-review ladder uses the same binding six-stage master model as the Review Process page.
Data and third-party rights: A document’s release status does not depend on confidentiality alone. An NDA does not extend market-data or other third-party rights. Completed replication, intraday, cost, APS or live-execution reports are disclosed only to the extent permitted by the underlying rights; otherwise technical reproduction uses an appropriate data source licensed by the reviewer.
PUBLIC REVIEW LAYER

What can already be assessed without confidential material

Before a discussion, an interested party should have enough information to understand the core idea and the open validation work independently. Several public layers complement each other.

DEEPER REVIEW

More detail does not automatically mean more public disclosure.

For serious interest, information access should deepen with the review. This makes a discussion substantive without exposing source code, sensitive rules or proprietary implementation detail at first contact.

0
PUBLIC

Orientation

Website, Executive Overview, Evidence & Validation Brief, Fact Sheet, Evidence Map, project status, methodology, glossary and publication history establish whether the substance is relevant enough for a qualified discussion.

1
QUALIFICATION

Strategic fit

Use case, institution type, technical environment, review priorities and the potential role of the Framework are clarified. Only then is it useful to decide which material is required next.

2
CONFIDENTIALITY

NDA & targeted deepening

For serious interest, the confidential whitepaper and selected architecture or existing materials can be released selectively without opening complete core IP.

3
TECHNICAL REVIEW

Reproducibility & architecture

Test definitions, architecture, known limitations and – once actually completed – replication, intraday, cost, APS and later potentially live-execution reports are reviewed against concrete questions.

4
DUE DILIGENCE

Rights, data, code, security & handover

The IP chain, data rights, third-party components, code and dependencies, IT security, documentation and transferability are reviewed. Sensitive core substance is opened only to the extent required by the specific review purpose.

5
STRATEGIC DECISION

Partnership, investment, acquisition or option

Only at this stage are structure, rights, scope, handover, cooperation, potential exclusivity and economic terms negotiated in concrete form.

Master model: These six stages match the binding review path on the Review Process page. The documents page shows the same path from the information-access perspective; it does not use a second, competing stage model.
DOCUMENT STATUS

Not every later due-diligence document is already a finished document today – and that distinction should remain visible.

The document layer grows alongside revalidation. Existing material is separated from controlled material and from reports that can only be completed once the corresponding Version 2 validation work has been completed.

Available

Public layer

  • bilingual website with project status and methodology
  • German and English Executive Overview
  • German and English Evidence & Validation Brief
  • German and English Institutional Fact Sheet
  • institutional fit, review process, and live-validation strategy pages
  • public Evidence Map with claim and validation status
  • glossary and methodological research notes
  • historical APS publication record
Controlled

Deeper existing material

  • current confidential framework whitepaper
  • extensive internal knowledge and architecture documentation
  • historical APS source and simulation corpus

This layer is not intended as a public download area.

Development programme

Version 2 validation reports

  • reference-core replication report
  • intraday and cost validation
  • isolated APS comparison under identical conditions
  • out-of-sample and walk-forward reports
  • technical test, data and security documentation

These documents are created with the relevant validation work; they are not presented as complete in advance.

NEXT STEP

Read first, then deepen the review deliberately.

If the website and Executive Overview lead to concrete questions, they can be sent directly by email. This allows the discussion to start at the relevant project state instead of with a blanket data-room release.