Content status: 24 August 2026Website 2.2.2
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 nine 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 · 9 pagesEnglish & German19 August 2026
PUBLIC EXECUTIVE OVERVIEW

The framework in nine 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 · 9 Seiten · Version 1.1 · 16.08.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.
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 · 9 Seiten · Version 6.0 · 15.08.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 7.0

Institutional Fact Sheet · Deutsch

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

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.

1
PUBLIC

Orientation

Website, Executive Overview, Evidence & Validation Brief, Evidence Map, project status, methodology, glossary and publication history. This layer answers whether the project is relevant enough for a discussion.

2
QUALIFIED DISCUSSION

Define the review question

The discussion establishes whether the interest is primarily domain, technical, strategic or transaction-related. Only then is it useful to decide which material is actually needed.

3
CONFIDENTIAL

Whitepaper & technical depth

A current confidential whitepaper exists for qualified discussions. Release is selective; sensitive material is not distributed merely because it exists.

4
DUE DILIGENCE

Reproducible evidence

As Version 2 progresses, replication and validation reports, data and test definitions, architecture documents and documented deviations are intended to become reviewable. Such material is labelled complete only after the relevant test has actually been completed.

5
CORE IP

Sensitive core substance

Complete rule sets, proprietary implementation details, source code or similarly sensitive material belong at the end of a serious review and are disclosed only to the extent required by the specific purpose.

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.