This page gives a deliberately sober view of the public project status. It separates existing research and system substance from the tests that still need to be completed for Version 2. Readers should not have to infer a maturity level from individual figures that the project itself does not yet claim.
A credible assessment starts with boundaries. The public presentation therefore distinguishes existing substance, development objectives and claims that are deliberately not made.
The project already contains a substantial body of rules, tests, historical comparison paths and documentation. At the same time, the exact work that turns a research and reference core into a more production-oriented architecture is still outstanding.
Status should change because validation gates have been passed, not because new labels have been introduced. The following gate logic shows the substantive dependencies: some work can proceed in parallel, but its conclusions only become robust once the required reference and execution state is fixed.
The existing calculation logic is reimplemented independently and compared result by result with the documented reference state.
Acceptance criterion: Identical data and the same rule version reproduce the same reference results, or every difference is fully explained and documented.
Intraday ordering, entry, target, stop, break-even and trailing are processed in actual sequence; commissions and slippage are introduced separately.
Acceptance criterion: Event ordering and economic frictions are deterministic and their effects can be reported separately.
The current synthetic control is reproduced and extended with alternative null models so that the comparison does not depend on a single generator family.
Acceptance criterion: Control series and additional null models are reproducibly documented and comparable under identical evaluation rules.
APS is measured against the same trading and execution path without APS while signal and execution conditions remain unchanged.
Acceptance criterion: Differences between baseline and APS variant can be attributed specifically to the risk layer.
Parallel work is possible: Gate 3A and Gate 3B can be pursued independently once a stable reference and execution state exists.
The rules are tested on data and time windows that were not used to develop those same rules.
Acceptance criterion: Results on new data and across successive walk-forward windows are fully versioned and documented without retrospective mixing with development data.
Once the system version is sufficiently defined and reproducible, a professional trading and research office is intended to capture real orders, fills, fees, risk and version data.
Acceptance criterion: The real execution path is continuously traceable; a live track record adds to the preceding evidence but does not replace it.
After technical revalidation, an operating validation stage is planned: a clearly versioned system state is intended to be used under real market conditions and documented from decision through execution. In parallel, the organisation is intended to structure technology, IP, research, documentation and operating processes so that they can later be reviewed and transferred as a coherent unit.
Build a transaction-ready operating unit and enable complete corporate acquisition where strategic fit exists.
AlternativeIf no suitable transaction emerges, own operation, institutional licensing and a separate retail product remain possible later commercialisation paths.
Live validation & strategy in detail →Python, relational databases, API boundaries or a specific user interface are technical working directions. They are not sold as immutable product properties. What matters is that data, rules, results and versions remain clearly separated and that the calculation logic can be reproduced and tested.
A technical decision counts as progress only when it improves testability, maintainability or integration capability. Changing the programming language alone does not increase methodological maturity.
Versions 0.x.x document the pre-release development of the current website and its public information model. Historical work remains visible as development history, but is not silently equated with the current framework and evidence status. Website 1.0.0 freezes the first fully released public overall state. Subsequent versions document substantive, methodological or technical changes in a traceable manner.
Audience-facing language was revised, metrics were explained more clearly and the English version was added.
Technology, development, documentation, FAQ and visible evidence statuses were expanded.
Project status, glossary and detailed methodological research notes extend the public review layer.
A bilingual Executive Overview, staged information access and a source-based publication history add a public document layer.
Public claims are tied to evidence status, limitations and a concrete next validation step. A separate Evidence & Validation Brief makes that review logic shareable.
Potential institutional perspectives, build-versus-buy framing, staged disclosure, transaction readiness and a one-page Institutional Fact Sheet add the strategic decision layer.
Terminology, metadata, mobile navigation, accessibility, favicons, loading behaviour and technical consistency were reviewed and refined without changing the Framework’s substantive architecture.
The planned trading and research office, live track record, preferred transaction objective and alternative commercialisation paths are classified as distinct later layers without changing today's evidence status.
Historical APS primary publications were integrated as original sources, the six synthetic control series were refined on the basis of their actual generator logic as different trend regimes, and the test matrix was documented transparently as 94 real instruments plus six synthetic control series with 6,000 test combinations in total. The public Framework documents were aligned with this state in content and visual identity.
First fully released overall state of the repositioned Plagge Consulting website. Content architecture, bilingual presentation, source, evidence and documentation structure, legal pages, visual identity and technical implementation are consolidated and form the binding public baseline for all subsequent versions.
The complete public content is reorganised into a numbered manual structure. Existing pages and content remain available but receive explicit chapter and subchapter roles, a visible content date, local chapter navigation, breadcrumbs and a linear previous/next reading path. Reference areas and legal information are separated from the technical chapters. This release freezes the public data and navigation state of 19 August 2026.
Patch release of 20 August 2026: the German and English legal pages are synchronised and updated, editorial responsibility is stated more precisely, and the new AI-generated portrait of Andreas Plagge receives a direct disclosure. Architecture, Framework content, research evidence and public technical documents remain substantively unchanged.
Technical patch of 20 August 2026: the CSP conflict on the profile pages is removed by formatting the portrait disclosure exclusively through an external stylesheet. HSTS with a one-year max-age is added. Legal texts, Framework content, evidence and public technical documents remain unchanged.
Patch release of 21 August 2026: Chapter 9 is renamed in the visible navigation from “About” to “Profile”, with the German equivalent changed from “Über uns” to “Profil”. Existing URLs, content, legal pages, Framework structure and technical security measures remain unchanged.
Patch release of 21 August 2026: the existing NinjaTrader® Ecosystem vendor status was first documented on the profile page.
Compliance release of 21 August 2026: dedicated NinjaTrader® and Kinetick® information pages, preferred platform/brokerage/market-data positioning, permanent Ecosystem risk disclosure, and prominent hypothetical-performance disclosures are integrated. Quantitative Framework PDFs containing simulated results receive an additional compliance cover and result-page reference without altering the underlying research content.
Minor release of 21 August 2026: a central bilingual legal page consolidates provider information and privacy notices for the business social-media presences as well as WhatsApp, Messenger, SMS, Zoom and Microsoft Teams. The website privacy policy remains concise and links to this external-channel layer.
Minor release of 22 August 2026: the architecture is condensed without additional image files by adding explicit hand-offs between the six layers and removing the redundant second architecture presentation. The next material proof points are reorganised as a gate-based validation path with acceptance criteria, while the institutional review process makes increasing information depth and confidentiality visible. Typography, core design, legal pages and research PDFs remain unchanged.
Patch release of 22 August 2026: the full hypothetical-performance disclosure is limited to pages that present specific historical, simulated or backtest-derived performance figures and is rendered once immediately before the relevant result area. General FAQ, documentation, documents, publication-history and research-overview pages no longer present specific performance figures and therefore no longer carry the full-page disclosure. The permanent NinjaTrader® Ecosystem risk disclosure in the footer remains unchanged.
Patch release of 24 August 2026: the German and English glossaries are expanded from 29 to 48 terms. Additions include the full project name, Framework, Oscillator, Trading Platform, NinjaTrader®, Broker, Market-data feed, OHLC/OHLCV, Futures, Evidence, Audit Trail, Due Diligence, Governance, Reproducibility, Rule Version, Signal, Synthetic Control Series and Test Matrix. Existing technical architecture, evidence, legal pages, performance disclosures, design and downloads remain unchanged.
