System Research · Forward Evidence

Aura Research

Member results are individual stories. Research is how the system itself is documented: timestamped, versioned and reviewable. Nothing below is claimed before it is recorded, and nothing here is a performance promise.

Why research is separate from results

The Member Results page shows what individual members and the founder chose to share, with permission. It is real, and it is not evidence that a system works. Research asks a different question: given what the engines read and the state they posted, what did price do next, across many sessions, with the version recorded? That question is answered in public, with dates, or not at all.

Standard

Every research entry carries the instrument, the session, the engine versions and the timestamp of the posted state. Entries are logged forward (before the outcome is known) and are never edited after the fact.

Research program

Forward evidenceForward session studiesSessions logged in advance, then reviewed: what the engines read, what state was posted, what price did.
Publishing soon
StatisticsSetup statisticsCounted outcomes per setup and state, published only once a dated sample exists.
Publishing soon
ExamplesTimestamped examplesReal NQ and Gold examples with the time, session and engine state at each decision.
Publishing soon
ReviewsLive session reviewsPost-session walk-throughs of what the live intelligence said and when it changed state.
Publishing soon
Decision qualityDecision-quality reviewsWas the state change justified by the evidence available at the time, regardless of outcome?
Publishing soon
ArchiveSetup archivesA searchable record of posted states and their resolution, by instrument and session.
Publishing soon
ComparisonHistorical comparisonHow the same session type behaved across months, and what changed between versions.
Publishing soon
MethodMethodology notesHow Anchor Rails, SKELETON and Black Book are defined and how the state machine moves.
Publishing soon
VersionsVersion historyWhat changed in each engine release and why. Every study references the version it ran on.
Publishing soon

How the system is built to be studied

The Aura backend stores every reconciled market state with its inputs, so a session can be replayed after the fact: what Direction, Location and Execution each reported, when the state moved from WATCH to ARMED, and what invalidated it. That persistence is what makes forward studies possible without rewriting history.

Read how the AuraBot system works for the architecture, or start with the doctrine that every study is judged against: destination is not entry.

Questions

Why is nothing published yet?

Because a study needs a dated forward sample before it means anything. The program is public now so the standard is visible before the first entry.

Will research include win rates?

Only as counted outcomes from a dated, versioned sample, with the sample size shown. Never as a headline number.

Are member results part of research?

No. Member results are individual and shared with permission. Research covers the system's posted states, not any member's account.