The QAE Project & Decade Pack Launch
The QAE Project Beta Launch | The QAE Report | The QAE Decade Pack | The QAE Decade Pack Bundle | Quintile Analysis Engine
Welcome to the QAE Project early-access beta launch. Key documents to translate the system are the QAE System Blueprint Wireframe and the QAE Cheat-Sheet. This website is currently mostly a system description and targeted towards for two audiences:
- Pattern Investigators who already know their industry datasets
- Dataset Architects already adept at patterns matching, who also like to experiment and create datasets
The Main Objects / Products To View:
- Decade Pack – A stitched historical archive of ten independent Seasonal Back-Stitch Page tiles, 10 x PDFs
- Decade Pack Product Bundle – See DP Purchase Tab for Decade Pack Bundle Details
- Standard QAE Report – An historical static 2 page PDF artefact containing:
- Leading Edge Page – This draws attention towards the most recent newest calendar date
- Seasonal Back-Stitch Page – This draws attention towards older historically context with back-stitching tile extensions
The QAE Ecosystem:
QAE (Quintile Analysis Engine) is a deterministic, domain-agnostic inspection instrument engineered to transform calendar-based cardinal data-tables into static ordinal visual geometry. In short it is a “Pattern Intel” tool. This computational output is viewable on screen or as a fixed layout data display panel (digital view) and then exported as a high-fidelity QAE Report Artefact PDF (archived). It is not a predictive AI, nor is it a subjective dashboard; it operates strictly as a historical machine and display panel. By transposing raw cardinal metrics into time-indexed ordinal positions, the engine exposes intrinsic behavioral patterns within a closed one-year envelope. QAE treats data as material geometry rather than statistical probability.
QAE Extended Automated System:
The QAE Extended Automated System is under development and being documented. The current Decade Pack Launch includes 2 primary PDF based products with demos which Users can download and engage with. Demos for the Standard QAE Reports and Decade Pack are provided to view / download freely to inspect. QAE Reports all have a standard template with an optional skin for different purposes and industries. This launch produces 2 non-automated PDF products as a partial beta release within the larger framework. The choice was made to be transparent by providing a BluePrint for the early beta product to promote engagement and validation of methods. Users can easily simulate ordinal ranking, quintile binning / labeling and sort into timeframes on any spreadsheet.
The Deterministic Promise:
QAE has no dependencies and discards the noise of absolute scale to focus purely on structural reality. It refuses to average, smooth, or ‘clean’ data. By preserving original Structural Integrity, QAE reveals authentic patterns through time-indexed ordinal geometry. This transformation exposes the intrinsic behavioral patterns latent within the historical dataset.
How QAE Treats Time and Data:
As a pattern intel tool, QAE requires a fixed historical event package, not a live data stream — it needs an event snapshot to work with. That snapshot is a dataset bounded within a fixed one-year calendar envelope. While comparable to a photographer capturing a historical moment, a more accurate metaphor is amber — as fluid resin hardens around its environment, it creates a permanent, unaltered light refractive time capsule of that historical event, sealed and preserved for future inspection without decay. QAE is an inspection tool which unpacks historical events using calendar-based dataset packages through Fixed Lens Prisms to reveal geometric messages.
–QAE SYSTEM TABLE OF CONTENTS (TOC)
For Users: Standard section links work normally. For links pointing to tabs please right click then select open in a new tab. The correct tab will then position itself as the fresh webpage reloads content.
- SECTION A: QAE PROJECT HEADER, HERO, LOGO
- SECTION B: QAE PROJECT WELCOME AND QAE PROJECT TABLE OF CONTENTS (TOC)
- SECTION C: QAE PROJECT OVERVIEW – (WITH TAB-SET 1)
—— Tab-set 1 w/ 5 parts ——
- SECTION D: QAE SYSTEM OVERVIEW – (WITH TAB-SET 2)
KEY DOCUMENTS: QAE SYSTEM BLUEPRINT WIREFRAME AND QAE CHEAT-SHEET
—— Tab-set 2 w/ 6 psrts ——
- SECTION E: QAE REPORT DEMO 1 – (WITH TAB-SET 3)
—— Tab-set 3 w/ 4 psrts ——
QAE Project Overview
-
QAE Project
-
QAE Report Demo 1
-
QAE Decade Pack Demo 2
-
DP Bundle Purchase
-
About | Contact
How To Use QAE Website - A Suggestion:
This website is the technical overview of the QAE system in engineering terms for the duration of the beta. It wasn't intended to be this dense, resulting in a wall of text, but as a solo dev this is how the docs currently are as a beta release. In an ideal world, visitors will read all the documentation and educate themselves naturally, but in reality, a new system requires a few User visits before any trust is established and the documentation is taken seriously. The wall of text causes an initial friction issue and conversely also creates a laboratory environment where Users can place all the pieces into an LLM, then ground the LLM in order to quickly form a basic opinion about QAE: Is QAE potentially useful for projects Yes/No?
- Step 1 - Look at the demo samples before reading mechanics. They show the finished product used for different purposes, printed with different skins, containing data from different industries.
- Step 2 - Become familiar with the project as a whole by reading the intro top tab section about products, the Standard QAE Report, the Decade Pack and the Decade Pack Bundle.
- Step 3 - Become familiar with the QAE Blueprint as much as possible. Focus on how the signal pipeline of four operational layers delivers the QAE Report. Users should know the input query via the Report Summary to rapidly decode and intellectually absorb the message / meaning within geometric output.
- Step 4 - Become familiar with the QAE Cheat-sheet as much as possible to grasp the primary QAE elements in blocks with a visual legend. Learning the Q-Band strength scale, lens symbols, overlays, how time works, badges and borders ensures Users cognitively engage with what they are looking at quickly.
- Step 5 - Set up an LLM Lab to support testing with the full website documentation. Copy or download the entire website text, then download the QAE Blueprint, QAE Cheat-Sheet and other items in the sidebar and demos. QAE's documents attempt to be deterministic and verifiable, meaning the LLM should act as a docs navigator, guide, and reviewer all in one, but only to a limited extent. Be patient to ground the LLM to ensure it is correctly focused.
This is an imperfect way to get a technical grasp of the QAE System although it will allow an opinion form quickly saving time. Forming a quick opinion and using the tool correctly are different things.
To understand the system more deeply and how this structure is preserved, we need to look at the System Blueprint and the four operational layers traversed by an event pipeline – the SIGNAL TRANFORMATION PIPELINE. This pipeline initiates QAE Engine with a dataset submission, cuts through the 4-layer stack with three handshakes in sequence, then terminates. This now bridges to the heavier documentation below.
Demo 1: The QAE Report, Report Template and Template Skins
The purpose of Demo 1 lower down on this homepage is to demonstrate the QAE Report. The standard template utilizes generic labelling. The QAE visual panel is editable which facilitates updating generic metrics labels on the standard template to become industry specific terminology metric labels creating new Template Skins. These 4 QAE Report Demos are current early beta and will improve and expand over time.
* Tab 1: QAE Report NVDA with Standard Template
* Tab 2: QAE Report NVDA with Stock Market Skin
* Tab 3: QAE Report VIX with Standard Template (edge case synthetic)
* Tab 4: QAE Report NOAA with wind speed skin (atmospheric dataset)
Further templates will be made later as combination templates are available right now for | M1-BL & M2-BL | M1-RL & M2-RL | . QAE Engine Reshaper works with other interesting formulas too. This means the current architecture is currently under deployed which is correct for early beta.
Here we need to focus on what is most important initially which is the standard QAE report template containing a quality known dataset. NVDA was chosen to flagship QAE because it is globally known with massive activity over the past decade creating discernable patterns in the QAE reports. QAE functions best when the metrics pairing is elegant and from a QAE perspective NVDA M1-BL Volume & M2-RL Close Price USD are ideal. USD Stocks, the NYSE and NASDAQ using Volume and Daily Close Price as the 2 primary indicators makes sense mathematically in the financial world. It is also hard-coded into how people think, traders are trained to think this way before they begin trading so it is also a normalized / adopted behaviour accepted globally. In contrast during the demo QAE as a domain agnostic data analysis tool QAE will show industry skins and a dataset decoupled from humans altogether applied directly to physics from The National Oceanic and Atmospheric Administration NOAA, which is another strong metrics pairing. We will also investigate the edge case of the VIX anomoly which is a single synthetic metric with an imbalanced algorithm.
To begin the process we must apply the Layer A rules. The User must know / absorb the numbers in the query in order to understand the geometry in the QAE Report. Numbers are numbers and patterns are patterns. Users do not need to understand everything about QAE and the Report Wireframe Summary to see the patterns in the visual geometry. Let the patterns speak for themselves in the beginning, deeper awareness comes after more sessions and use.
test
Purchase
QAE About | Roadmap | Contact
Important Notes
- QAE Engine cannot advise or predict anything at all, it just crunches numbers similar to a calcultor. As QAE Engine does not know what the future is or undrestand what different industries are, it is incapable of assigning meaning. Assigning meaning and dealing with real world consequences are 100% the User domain of Interpretation Responsibility
- This homepage contains tabbed DOM content making this homepage more suitable for humans to navigate but not ideal for bots and LLM’s. A Table of Contents with a full link index is being installed this week to resolve the issue
- This is an early version beta website and beta product for an ongoing development
- The website is not device responsive, it is not optimized for use for phones or tablets at this time
- Minor structural problems have been noticed so the demos will all be replaced very soon along with a report version update note
QAE System Overview
-
The Signal
-
Layer A
-
Layer B
-
Layer C
-
Layer D
-
Cheat-Sheet
QAE First Principle
.
Preserve Signal Integrity During Transformation:
The way QAE operates is easily visualized as a 4 layer cake with a pole running through the center crossing the path of all 4 layers. It is an event pipeline running through four operational Layers A to D. This naturally creates 3 boundaries or interfaces between the layers. Each boundary requires a handshake in one direction to keep the operation functional. This Signal Pipeline is the mechanism that transforms a user's initial Query into a geometric Message ready for inspection and interpretation.
A User needs to know the Query (Layer A) within the QAE 4 Layer Signal Pipeline architecture in order to decode the geometric Message (Layer D) delivered from the machine in response to the Query. The User selects / knows the required metrics which form a dataset Query to submit to QAE Engine --> Computation (Layer B) preserves the quality of data-tables transforming the dataset into visual geometry (within Layer C) within the event pipeline --> Quantile unpacking (Layer B) in the pipeline exposes patterns creating a Message for the User (Layer D) in response to the Query --> The Message is delivered to be rapidly re-engaged with by viewing the QAE Report (Layer D).
QAE System Blueprint
- This Blueprint below is a condensed text overview of the QAE System Beta for The Decade Pack Product Launch. Click to the blueprint to enlarge the image in a new tab or find a text copy from the side bar
- Preserving the integrity of the SIGNAL throughout this journey is the most critical requirement, enabling the User to parse the visual geometry, extract the embedded MESSAGE, and intellectually satisfy the original QUERY

LAYER A: BLUEPRINT EXTENSION (System Mechanics & Metric Pairing)
.
The Genesis & The Package: The formulation of the dataset QUERY begins with the primary task of capturing a static historical event snapshot bounded within a fixed one-year calendar envelope. To format the MnM Package, this requires selecting two distinct, symbiotic daily metrics that form a natural pairing to represent that specific 366-day historical instance.
The Natural Metric Pairing (M1 & M2): To create useful geometry, the QAE Engine requires useful data possessing real-world meaning. The selection of metrics is not strictly constrained to specific data types; rather, the objective is capturing a good, repeatable pairing that establishes a known relationship. It does not matter if the pairing is a traditionally learned market behavior or a fundamentally robust physical law. Provided the pairing makes sense to the Baseline Lens and Reaction Lens, capturing this natural relationship creates the geometric value within the QAE Report.
M1 (Baseline Lens) — Absolute Environmental State: Metric 1 defines the absolute state, physical volume, or absolute environmental participation over the bounded one-year calendar envelope. It acts as the structural landscape, capturing the absolute cardinal magnitude of the event to anchor the environment of the dataset.
M2 (Reaction Lens) — Daily Velocity of Change: Metric 2 must include a daily measurement strictly associated with the calendar. It defines the daily reaction as the response or velocity of change relative to the prior state (t-1). *(During Layer B Computation, M2 is deterministically processed through the Metric Reshaper formula—[Current State - Prior State] / Prior State—which extracts the pure proportional intensity of the daily reaction from the immediately preceding active day)*.
Handshake 1 (MnM Gate): The submission of the MnM Package at the gate. Validated ingress officially activates the SIGNAL PIPELINE, moving the data from the External Domain into the Machine Domain.
.
LAYER A: USER INSTRUCTIONS (The Dataset Query)
.
The Full System: In the full system architecture, a dataset QUERY begins with a User experiencing an 'aha moment' that generates a query to solve a problem. With QAE, that Query Dataset contains deterministic cardinal data bounded within a fixed one-year calendar envelope, using two symbiotic metrics to capture a historical event snapshot. The User invests time, energy, and intent to select the timeframe and a natural metric pairing—M1 Baseline and M2 Reaction—driven by precise knowledge of the relationship between those two metrics. To create geometric value, this pairing must establish an interaction between the absolute environment as a whole (M1 Baseline Lens: the absolute state over the year) and the intensity of the resulting daily movement (M2 Reaction Lens: the daily velocity of change relative to the prior state).
The M1 Baseline Lens simply applies ordinal ranking to the metric data and bins it into five symmetric 20% Q-Bands named Weak | Moderate | Median | Strong | Peak.
The M2 Reaction Lens is the Daily Velocity of Change, which you will see in Layer B. M2 is deterministically processed through the Metric Reshaper. This M2 metric should contain patterns at the daily time interval regarding the velocity of change, response intensity, or proportional violence relative to the prior state (t-1).
The Current Beta Status: In this early launch phase, the datasets for the demos have already been curated and processed for you. Even so, you should absorb what you can from the QAE Dataset Summary provided with each report. The more you understand the raw numbers going into the machine, the better you will understand the visual geometry coming out of the machine.
The QAE Engine only provides deterministic structure; it does not assign meaning. To extract true insight, it is highly beneficial to conceptually own the prepared SIGNAL before it enters the pipeline at Layer A. When you understand the event snapshot timeframe, both metrics, the metric pairing, Layer B math, and the Cheat-Sheet, you naturally own the interpretation of the geometric patterns in the QAE Report.
LAYER B: QAE COMPUTATION (The Machine)
.
Metric: A non-negative, measurable value derived from physical reality or industry participation (e.g., Volume or Price).
Cardinal Value: An absolute, independent measurement that answers the question "How much?".
Bipolar Value: A signed numerical result (+ or -) generated by the Metric Reshaper formula before it is normalized into a non-negative magnitude for ranking.
Directional Polarity: The independent visual binary (▲ Green / ▼ Red) extracted from a Bipolar Value that anchors the direction of a move without contaminating its ranked intensity.
Ordinal Value: A relative structural rank (e.g., Weak to Peak) that answers "Compared to what?" within a closed 365/366-day envelope.
Ordinal Geometry: The stabilized visual arrangement of ordinal values into fixed architectural coordinates and time-indexed containers.
The Ingress - Lens Classifications M1-BL & M2-RL: The inbound dataset package must be a 3 column metrics data-table | Date | Metric 1 BL | Metric 2 RL | . The package only needs to include Active Days, and metadata required is a Newest Date and a UTC Timezone offset. The title and logo are useful and optional metadata. Datasets can be encrypted by multiplying the metrics with a complex number. The Ordinal Geometry holds pattern, although the metrics overlays would have distorted values.
Computation transforms measurable real world metrics into quantile structure using time-indexed ordinal geometry with overlays. The metrics one-year daily interval dataset contains Metric 1 Baseline Lens and Metric 2 Reaction Lens. This metrics pairing enters the computation pipeline as a Deterministic Cardinal Historical Snapshot, not a data-stream. QAE Engine processes both - Metric 1 is processed directly through the Baseline Lens to establish the absolute environmental state - While Metric 2 is routed through the Metric Reshaper creating Bipolar Values as reaction intensity relative to the prior state (t-1), additionally also preserve directional polarity binaries. As illustrated in the Reaction Lens Classification map, this allows QAE Engine to process the dataset from two distinct angles of reality.
The Physics of Reverse Chronology: The QAE Engine operates using Reverse Chronology as a design choice which can be changed later on if required. The Newest Date serves as the primary temporal anchor for the dataset envelope and may be either an Active or Inactive Day. The computation anchors to the Newest Date from the metadata and reaches backward through formula exactly 1 year to establish the Oldest Date. This temporal anchor ensures that every Q-Band Count and seasonal distribution is derived from a closed historical envelope, preventing the engine from "hallucinating" trends, blending or looking into the future.
Handshake 2 (Ordinal Geometry Data-tables): Upon the completion of the cardinal-to-ordinal transposition, the machine generates the Ordinal Geometry Data-tables. These flat data-tables contain the finalized Q-Band Counts, Metric Overlays, and Directional Polarity Bias Overlays. This marks the internal handover (Handshake 2) where the Computation is exported to Layer C for visual rendering.
.
LAYER B: USER ORIENTATION
.
Day Qualification Logic: The QAE Engine recognizes three distinct day types. Active Days are daily observations where both metrics are present and are processed by the engine. Inactive Days (weekends or holidays) are skipped without breaking the mathematical sequence; the "Prior State" (t-1) is always the immediately preceding Active Day. Disqualified Days, where a single metric is present and another is missing, are rejected as invalid at the submission gate, and the MnM Package will be declined via an error report.
The Core Math (Cardinal to Ordinal): QAE Engine focuses on structural reality. It deterministically transposes cardinal measurements into Ordinal Geometry using five symmetric 20% Q-Bands: Weak | Moderate | Median | Strong | Peak. The QAE Engine creates time-indexed geometry where each of the Q-Bands is tested against various fixed timeframes to create the Q-Band Counts rendered in the final charts and tables.
The M2 Metric Reshaper Pipeline: To measure the proportional violence of transitions, the M2 raw metrics are transformed using the formula: (Current State - Prior State) / Prior State. As shown in the Reaction Lens Classification map, this formula creates a bipolar value encoding both magnitude and direction. The engine then normalizes these values to all be positive values, ensuring the system ranks pure Proportional Violence—treating a massive crash and a massive spike as identical "force" for quantile placement.
Directional Polarity Decoupling: Before ranking the intensity, the engine extracts the mathematical sign (+ or -) as an independent Directional Polarity Overlay (▲ Green for up, ▼ Red for down), this facilitates Directional Polarity Counts for vaious timeframes. This separation ensures that directional bias never contaminates or masks the ranked intensity of the reaction.
Baseline Lens MapClick map to englarge |
Reaction Lens MapClick map to englarge |
Layer C: Visual Rendering & QAE Report Handover
.
Layer C documentation is not yet completed, so for the time being here are important bullet points. This section will be completed soon. It will be extended with a comprehensive Container Map, detailing the exact layout of all pages, containers, and elements.
.
- Layer C performs visual panel construction picking up from Layer B computation. It is strictly an assembly phase, translating the computed ordinal data-tables from Layer B into a fixed layout digital display panel.
This representational process organizes the deterministic outputs using structured combinations of data, symbols, containers, badges, aesthetic color systems, and spatial arrangement. See QAE Cheat-Sheet. - The fixed layout relies on placement discipline, assigning coordinates to elements so the structure makes sense and becomes easier to cognitively engage with after some sessions.
- Container Architecture utilizes specific borders and badges to securely isolate data scope and prevent unrelated structures from blending together.
- Invariant visual grammar relies on strict aesthetic color systems: Purple for the Baseline Lens ◯_BL_M1, Blue for the Reaction Lens △_RL_M2, and dedicated colors for fixed timeframe badges and borders.
The 5-tier ranked Q-Bands are aesthetically displayed using a consistent light-to-dark color gradient ranging from Weak to Peak. - Directional Polarity Indicators (up/down or higher/lower) are placed as ▲ ▼ Arrows in M2 Q-Bands, while charts display Directional Polarity Counts utilizing Green for a positive move and Red for a negative move. This physical placement ensures Directional Polarity never visually or mathematically contaminates the quantile output in the ordinal geometry.
- Template Skins allow domain-specific semantic labels (such as "Volume" or "Mean Wind") to be applied to the surface without altering the underlying mechanics of the engine.
- Layer C officially terminates at Handshake 3 (QAE Report Handover), exporting the static QAE Report Artefact PDF and transferring full operational responsibility outward to the User for interpretation Layer D.
Layer D: User Interpretation
.
Layer D documentation is not yet completed, so for the time being here are important bullet points.
Part 1: Subconscious Parsing
Subconscious parsing is built on reliable, repeatable patterns. When someone learns to drive, they spend time normalizing to the controls and displays. After a few sessions, drivers begin to operate automatically — able to daydream or multitask occasionally, then later on with more practice multitask frequently. This happens because the ergonomic design of car controls aligns with the human body, allowing the subconscious to take over routine tasks.
A similar thing happens when learning one new language, after a certain amount of practice learners start thinking in that new language without the mental load of translation to the default language because their subconscious became structured enough to bypass using the previous dominant default language.
A similar principle applies to QAE. It projects a consistent, repeatable layout geometry that the subconscious can quickly internalize. By enforcing an invariant visual grammar through strict placement discipline, the architecture establishes a stable perceptual field. After some sessions and usage, people start instinctively knowing what they are looking at and where everything is. This biological division of labor assists rapid re-engagement, allowing the brain to significantly reduce searching for where information lives thereby freeing the mind to concentrate on data content and the underlying query.
.
Part 2: Interpretation & System Support
.
- The Boundary of Interpretation: The machine's mechanical responsibility strictly terminates at QAE Report Handover, marking the point where full operational responsibility returns to the User. The engine builds geometry and delivers a report. It does not offer advice, generate predictive models, or assign value. Meaning is entirely the User's domain.
- System Support & Education: Because the engine only provides deterministic structure and never interprets the data, the QAE ecosystem currently provides early version support and educational articles alongside the report. These resources will grow and improve.to assist Users in understanding the dataset details and the underlying mechanics needed to decode the messages and meanings within QAE Reports..
- Conscious Deduction: Interpretation is the conscious act of translating geometric patterns into actionable, real-world consequences based on specific domain knowledge. The system provides the visual invariant, while the User provides the deduction.
- Connecting Dual Realities: The true power of interpretation happens when the User connects relative Ordinal Position (the Q-Bands) back to absolute Cardinal Magnitude (the raw metric text overlays). Because the QAE Report displays both realities together for total contextual awareness, inspecting a Peak Q-Band rank paired with a historically tiny absolute raw metric reveals that the entire underlying dataset is tightly compressed.
- Pattern Recognition & Systemic Conviction: With the noise of absolute scale removed, the conscious mind is completely free to focus on structural anomalies and behavioral clustering. For example, observing a day where a Peak Baseline rank perfectly aligns with a Peak Reaction rank reveals a moment of massive systemic conviction.
- Seasonal Recurrence & Decay: By engaging with the historical viewports, the User can observe specific clusters of bands occurring in the exact same calendar month across Back-Stitched years. This allows the User to interpret reliable seasonal decay, persistence patterns, and macro regime shifts across an entire decade.
QAE Cheat-Sheet
Click the links to open in a new tab or right click to 'save file as'
Download PDF | Download Image 2560px Tall | Download Image 4000px Tall

QAE Website Quick Links to Key Details & Downloads
Decade Pack Product
Beta Statement
Decade Pack Product
Legal Notes
The QAE
System Blueprint
The QAE Report, Plus
Templates & Skins
The Decade Pack
Using NVDA Data
QAE Sytem
Cheat-Sheet
The Decade Pack
Product Bundle
Download All Website
As A Single Text File
Sample QAE Report &
Decade Pack Images
Demo 1: The QAE Report, Report Template and Template Skins
These 4 Demos explore QAE from different angles using differing data types, templates / skins and edge case testing
- Tab 1: – The QAE Report using NVDA stock data with the Standard Template. This will later be updated each trading day after midnight New York time. This is a quality metrics pairing with strong patterns showing.
- Tab 2: The QAE Report using NVDA stock data with the Stock Market Skin. This will later be updated each trading day after midnight New York time. This is a quality metrics pairing with strong patterns showing.
- Tab 3: VIX is an example of a experimental edge case with the Standard Template. VIX is a single synthetic metric fed into both QAE metric inputs M1 and M2. The algorythm which generates the synthetic CBOE VIX metric has a flattening in the central area caused by its own algorythm making VIX an edge case and potentially unreliable, or less reliable than others dataset types This will later be updated each trading day after midnight Chicago time and Users can decide if VIX works well with QAE or not.
- Tab 4: NOAA is an example of QAE being domain / industry agnostic with the NOAA (National Oceanic and Atmospheric Administration) Skin. QAE has no dependencies and doesn’t know or care which industry the daily data comes from. M1 is average wind speed and M2 is maximum gust. This is not updated demo and functions as a cross domain example of a QAE Report. This NOAA QAE Report has the NOAA Skin.
QAE Report Demo Featuring NVDA, VIX & NOAA
-
NVDA Std Template
-
NVDA Stocks Skin
-
Experiments
-
VIX Std Template
-
Houston IAH Dew Point Skin
Dataset SummaryNVDA 2025-01-01 — 2025-12-31 |
NVDA QAE ReportQAE Standard Template |
Dataset SummaryNVDA 2025-01-01 — 2025-12-31 |
NVDA QAE ReportQAE Standard Template |
QAE Engine and the Dataset Dance
The Key Validation is Symmetrical Q-Band Distribution
QAE Engine partitions one year of daily metrics into five equal parts through quintile binning, which are then labelled Q-Bands. To produce a report with pattern depth, QAE Engine needs a certain resolution depth and range to establish patterns—no excessive duplicates, no excessive zeros. Also, the M2 Peak Cutoff Value can explode into thousands of percent if the calm state of the M2 metric sits near zero (examples could be wind, wave, rain data), the baseline ground zero of that metric can optionally be raised with a Ground Zero Constant Offset this resolves to the Peak Cutoff Value having a perceptually realistic value.
M2 has a peculiar problem: It measures change, so if consecutive M2 rows have identical values, nothing changed in the real world and therefore there is nothing to measure. Those instances create a zero in the pipeline which fractures Q-Band distribution.
Q-Band Distribution Rules:
- For 365 active days the required split is 73·73·73·73·73.
- For 251 active days (common for stocks) the split must be 50·50·50·51·50 (the 51 may sit in any Q-Band).
- Q-Bands must be equal or all values can never be more than 1 in difference such as this valid distribution 61·61·60·61·60.
- These are examples of failed Q-Band distributions for 365 days, 73·75·72·73·72 fails. Or for 250 active days, an incorrect distribution could be 48·50·51·52·49.
Every QAE Report self-validates on the Leading Edge page, 4th row of bar charts, on the 1-year timeframe. These Q-Band Count aggregates show the complete Q-Band distribution for the 1-year timeframe. If the counts match the required split, the dataset is valid. No further checks, no changes.
If the counts do not match, the dataset has failed step 1 which leads to --> Diagnose --> Resolve OR Reject.
The 2 Zero Problems
- Duplicate zeros break distribution: Zeros are immune to Multiplicative Bidirectional Random Micro Jitter (multiplying zero leaves zero). Therefore when zeros appear as duplicates that break the distribution, we must use Additive Random Micro Jitter for Zeros Only—tiny random numbers added solely to the zero values.
- Near-zero values create M2 denominator extremes: The M2 Reshaper formula is (Current – Prior)/Prior. When the prior state is very close to zero, the denominator is tiny and the result can exceed 1000%, producing a meaningless Peak cutoff. This does not damage the underlying geometry, but it creates an unnecessary perception distortion of the M2 Peak Cutoff value. The fix is to optionally apply a Ground Zero Constant Offset to the whole metric, moving the floor away from zero before the Reshaper runs.
Metric Classes Anaolog and Industrial
Pure Analog Class – Natural physical metric measurements: Wind speed, wave height, temperature. These are continuous and natural. True duplicates and absolute zeros do not exist in natural analog metrics. A broken distribution with Pure Analog Metrics means human recording has likely truncated and applied data—rounding destroying the original resolution in the data. NOAA public data is an example of this as they record and store temperature as °F integers.
Industrial Class – man made, commercial, financial metrics: Production counts, defect tallies, transaction volumes, prices. These are discrete. Legitimate zeros and identical consecutive values are normal. A broken distribution in this class reflects a dataset with an inability to form useful patterns due to a lack of resolution. QAE Engine has a thirst for resolution to render patterns.
Industrial High-resolution: Major stocks, financial data and commodities retain high-liquidity with high resolution in digits over a very workable range. This is why there are so many successful financial data analysis tools. Financial data usually bottoms out well above zero and they use the identical formula as QAE Engine to express the daily percentage close price movements on the news. NVDA daily volume and close price naturally possesses minimal duplicate clustering and passes QAE distribution check without changes every time.
Diagnostic Checklist
Use only when a distribution has failed. Use checklist to comment where appropriate to resolve Q-Band distribution problem
- No excessive duplicate clusters in raw M1 or M2
- No excessive zeros in raw M1 or M2
- No excessive identical consecutive values in raw M2 (creates zeros in the reshaped pipeline breaking distribution)
- Sufficient range resolution (guideline: data spans a range capable of distinguishing patterns, leaning towards at least a 999-value range)
- Sufficient digit resolution (guideline: digits before and after the zero are capable of distinguishing patterns, leaning towards at least a 999-value range)
- Primary physics measurement type where applicable – Kelvin functions far better than °C or °F in QAE Engine. °C/°F are useful but not primary; they also place the zero in an awkward position.
- M2 floor somewhat above zero, optional fix (near-zero prior states often create Reshaper denominator extremes)
Dataset Response Card: One card per dataset, showing actual values against each requirement.
- Distribution | X, X, X, X, X | PASS or FAIL
- Duplicate count M1 | number
- Duplicate count M2 | number
- Zero count M1 | number
- Zero count M2 | number
- M2 adjacent duplicates (identical consecutive rows) | number
- Resolution digits | left number & right number
- Resolution range | lowest number → highest number
- Class M1 | Analog / Industrial
- Class M2 | Analog / Industrial
Fix Map For Broken Q-Band Distribution
- M1 / M2 clean non zero duplicates Multiplicative Bidirectional Random Micro Jitter
- M1 / M2 clean zero duplicates Additive Random Micro Jitter for Zeros Only
- M2 clean adjacent identical values Multiplicative Bidirectional Random Micro Jitter
- Metric Type Corrections Convert from °C / °F to °K (Kelvin)
- M2 floor too close to zero Ground Zero Constant Offset (optional as this does not break distribution, this is cosmetic to QAE Engine)
- No applicable fix Hard Fail – dataset rejected
Ingestion Flow
- Submit dataset
- Check Q-Band distribution
- Pass → valid. No changes needed. Proceed to report
- Fail → complete Diagnostic Checklist and Dataset Response Card
- Match failures to the Fix Map. Apply fix(es) and resubmit
- Fix resolves distribution → valid. Proceed
- No fix available, or distribution still broken → hard fail. Discard
VIX - An Edge Case Anomoly. Point 2 — The Flat Spot: VIX spends extended periods compressed between approximately 12 and 20 — a low volatility regime where daily readings cluster with minimal variation. This produces a dense band of near-identical cardinal values in the middle of the range, partially defeating ordinal differentiation. The structural information in VIX lives at the extremes — the fear spikes and the floor — not in the middle where most observations sit. Volume and wind speed distribute across their full ranges with natural variation, giving ordinal ranking genuine structural separation throughout. Point 3 — Derived Not Observed: Volume and wind speed are direct physical observations of real events — a share changed hands, air moved at a measurable speed. VIX is calculated from options bid/ask midpoints — forward-looking sentiment prices approximating expected future volatility, not recordings of events that actually occurred. The cardinal input is one step removed from physical reality before it even enters QAE. Point 4 — Structural Asymmetry: The K0 term in the CBOE formula treats puts and calls identically across all strikes despite their structurally different implied volatilities at different strike distances. Combined with discrete strike approximation errors that accumulate during extreme market stress, this creates a built-in asymmetric calculation — VIX spikes fast and decays slow — which is structural not incidental, and present in every dataset submitted. |
The Houston IAH Dataset ExperimentGeorge Bush Intercontinental Airport (Houston TX) - Dew Point Skin °FPairing Concept -> ASHRAE Psychrometric Concept -> Moisture Lens -> Thermal Lens -> QAE Dual-Lens Geometry This experiment is inspired by the moisture–temperature pairing used within ASHRAE psychrometric design methods for commercial HVAC systems. In its original engineering context, psychrometric analysis is performed indoors using highly controlled measurements, typically collected at hourly intervals or finer resolution. QAE is not attempting to replicate psychrometric engineering calculations. Instead, it is adapting the same conceptual framework—a moisture lens paired with a thermal lens—and applying it to district-scale outdoor climate telemetry using NOAA daily summary data at the 24-hour candle. The purpose of this experiment is to explore whether a thermodynamically related metric pairing can generate meaningful geometric structures within the QAE framework. At present, this remains an experimental demonstration rather than a validated atmospheric model. Metric 1 (M1) — Moisture Lens (Absolute Moisture State) Original HVAC Reference: Indoor Humidity Ratio conditions used to identify the annual hours containing the highest atmospheric moisture content. QAE M1 Input: Average Daily Dew Point (ADPT) Relationship: Both the HVAC reference metric and Daily Dew Point are fundamentally associated with the moisture state of the air mass. While they are not identical measurements, both are closely tied to the physical quantity of water vapor present within the atmosphere. Dew point is particularly useful because it is governed by the absolute moisture content of the air rather than short-term fluctuations in relative humidity. As a result, dew point typically exhibits greater physical inertia than temperature and often changes more gradually as air masses move through a region. Within the QAE framework, Daily Average Dew Point is therefore used as a district-scale moisture baseline. Changes in this baseline frequently reflect the arrival, departure, or modification of regional air masses and broader atmospheric moisture conditions. Metric 2 (M2) — Thermal Lens (Thermal Energy State) Original HVAC Reference: Mean Coincident Dry-Bulb (MCDB) Temperature, representing the thermal conditions occurring concurrently with selected high-moisture design periods. QAE Input: Average Daily Temperature (TAVG) Relationship: Both metrics represent thermal state measurements and therefore occupy the thermal side of the moisture–temperature pairing. However, Daily Average Temperature is not equivalent to Mean Coincident Dry-Bulb Temperature. MCDB is a specialised HVAC design measurement linked to specific moisture conditions and selected design-hour events. Daily Average Temperature is a broader district-scale climate measurement representing the average thermal state over a full 24-hour period. QAE therefore substitutes Daily Average Temperature as a macro-scale thermal lens rather than as a direct replacement for MCDB. The objective is not to reproduce psychrometric engineering calculations, but to preserve the conceptual pairing between atmospheric moisture conditions and thermal response. Within the QAE framework, Daily Average Temperature functions as the volatile thermal lens. Unlike dew point, temperature reacts rapidly to solar radiation, cloud cover, weather systems, and short-term environmental changes, making it an effective candidate for the Reaction Lens within the dual-lens architecture. |
This demo is made with the latest version of QAE 3.1. The Houston IAH Dew Point Skin QAE Report is derived from free public NOAA data delivered csv in Degrees Fahrenheit for M1 and M2. There are several reasons for this demo:
|
Demo 2: The Decade Pack Using NVDA Data with the Stock Market Skin
Explore how Back-Stichting works. Learn to rapidly view and assymillate macro historical distribution / behaviour over 10 years using the QAE Decade Pack. The individual yearly QAE Dataset Summaries are available to view as an image or download as a text file enabling a User to become familiar with the initial dataset query.
Decade Pack Downloads & Details
- Click the red links to download or view the Report Summaries (opens in new tab at 150%)
- Click Decade Pack Block 1 Image NVDA Jan 2016 – Dec 2020 (opens in new tab at 3600px tall)
- Click Decade Pack Block 2 Image NVDA Jan 2021 – Dec 2025 (opens in new tab at 3600px tall)
Beta Statement
Beta details here
FULL QAE SYSTEM SCHEMA FOR BOTS
FULL QAE SYSTEM SCHEMA FOR BOTS







