Skip to content
Projects

Loopera-ai/loopera has 550 GitHub stars and 84 forks. GitHot measured +1 in 7 days. Last checked 2026-11-09 21:58 UTC. Last push 2026-09-21.

How these counts are measured

面向基本面因子研究的智能体-A hypothesis-driven AI agent for fundamental factor research, with evidence-gated validation and research memory.

Measured star growth

in 24h
Update delayed
in 7 days
+1
in 15 days
Update delayed
in 1 month
Update delayed

Net star changes over overlapping periods, not daily totals. Missing measurements are left blank. Stars measure attention, not software quality.

README_EN.md

Original

简体中文 English

Loopera — Factor Mining, Infinite Insight

Loopera

Factor Mining, Infinite Insight
An intelligent agent for fundamental factor research
Fundamental research, engineered for evidence.

Visit the Loopera website Read the Loopera technical paper View the full research case study Watch the Loopera demo

Status: Public preview License: BSL 1.1 (not open source) Fundamental Research Hypothesis-driven Framework Evidence-gated Validation Memory-augmented Research

Product Overview · Product Framework · Research Inputs · Case Study · Boundaries


Repository scope: This repository contains public product and technical materials for Loopera; it is not a source-code distribution. It currently provides no runnable code, installer, CLI, or public API. The workflows and case studies in this README describe product capabilities and evidence boundaries.

Product Overview

Loopera works with public-company financial statements and operating information to help fundamental quantitative teams continuously perform research-direction discovery, economic-hypothesis formation, candidate-factor construction, trusted validation, and knowledge accumulation.

Core Value

Research Validate Remember Collaborate
Find explainable phenomena in cross-statement operating relationships Separate research logic from historical performance and filter candidates in stages Preserve results, failure reasons, and research lineage Let researchers review, intervene, and decide at critical checkpoints
Form interpretable and testable fundamental hypotheses Check timing, accounting treatment, stability, duplication, and incremental value Avoid repeated mistakes and continually identify research gaps Support both small tasks and multi-role collaborative research

Who It Is For

  • Fundamental quantitative teams: expand research coverage and establish a consistent, reviewable factor-research process;
  • Investment-research and fintech institutions: connect internal reports, research views, and data capabilities to a standardized validation pipeline;
  • Research leaders: track sources, decision rationales, failure reasons, and next steps—not just final backtest results.

Loopera AI Research Agent workflow
Loopera organizes research inputs, fundamental data, hypothesis discovery, factor design, trusted validation, and research memory into a continuously learning Agent research loop.

Its goal is not to mass-produce formulas or replace research judgment with one attractive backtest. Loopera asks whether a study has clear fundamental logic, survives multiple forms of scrutiny, and contributes information beyond existing research.

Loopera turns fundamental research from isolated manual experiments into a continuous process that can accumulate and evolve.

Why Start from Fundamentals

Prices reflect outcomes; fundamentals explain how a business creates, consumes, and reallocates value.

Loopera studies earnings quality, cash flow, balance-sheet structure, operating efficiency, capital investment, and changes in business conditions. Rather than looking only at market prices, it focuses on developments inside the business that may not yet be fully understood or priced.

Fundamental data is not simple. Relationships must be established across statements; the same accounting number can mean different things across industries and business stages; and the publication time of information determines whether a study could have used it in reality. Loopera brings these issues into one research process so that the Agent behaves more like a fundamental researcher than a generic curve-fitting tool.

What Loopera Can Do

Move from operating phenomena to trusted conclusions, then turn every study into team knowledge.
Discover → Hypothesize → Build → Validate → Remember → Evolve

🧭 Discover Research Directions

Start with operating anomalies, not random field combinations.

Search for explainable and underexplored phenomena in cross-statement relationships such as earnings versus cash flow, assets versus output, and liabilities versus operating pressure.

🧠 Form Fundamental Hypotheses

Explain the mechanism before constructing the factor.

Propose testable economic explanations, competing mechanisms, and failure conditions instead of packaging a single statistical correlation as a research conclusion.

🧩 Build Candidate Factors

Turn a research claim into a computable, reviewable object.

Map the hypothesis into a candidate construction while preserving the information used, expected direction, economic meaning, and key constraints.

🛡️ Run Trusted Validation

Make every candidate pass multiple evidence gates.

Check point-in-time availability, logical consistency, accounting treatment, robustness, duplication, and incremental value. One attractive backtest does not automatically become a conclusion.

🗂️ Accumulate Research Memory

Both success and failure become context for the next research cycle.

Record research lineage, failure reasons, untested leads, and relationships to existing results to reduce repeated mistakes.

🤝 Support Continuous Collaboration

The Agent expands the search space; researchers retain control of key decisions.

Support both rapid small-scale tasks and sustained collaboration among multiple research roles, with human review and intervention at critical checkpoints.

Three Inputs, One Research Thread

Topic  ·  Prompt  ·  PDF   →   Unified Research Input   →   Hypotheses, factors, and validation

View input methods and processing principles
  • Topic: autonomously explore themes such as cash-flow quality or operating efficiency;
  • Prompt: focus on a specified financial relationship, economic mechanism, or applicable industry;
  • PDF: extract research questions, economic claims, and explicit candidates while preserving provenance;
  • Mixed input: use a Topic to add a clear research anchor to text or PDF material.

Explicit formulas in a report can be prioritized for validation; the remaining content becomes background knowledge for further exploration. External material is always treated as research evidence to be tested and cannot alter Loopera's safety constraints, data scope, or validation standards.

Product Framework

Loopera turns research intent into evidence-qualified, reusable research assets.
Understand the business → Form a hypothesis → Test the evidence → Compound the knowledge

A Closed-Loop Product Workflow

flowchart LR
    A["Research Input<br/>Topic · Prompt · PDF"] --> B["Fundamental Understanding<br/>Fields · Statements · Industry Context"]
    B --> C["Intelligent Research<br/>Phenomena · Mechanisms · Candidates"]
    C --> D["Trusted Validation<br/>Timing · Logic · Robustness · Incremental Value"]
    D --> E["Research Memory<br/>Results · Failures · Lineage"]
    E -. "Feeds the next cycle" .-> C

    classDef input fill:#E8F7FF,stroke:#168CFF,color:#07142E,stroke-width:1.5px;
    classDef research fill:#F1ECFF,stroke:#7C3AED,color:#07142E,stroke-width:1.5px;
    classDef evidence fill:#E8FFF7,stroke:#0F9F8F,color:#07142E,stroke-width:1.5px;
    classDef memory fill:#FFF2FB,stroke:#C13C8A,color:#07142E,stroke-width:1.5px;
    class A,B input;
    class C research;
    class D evidence;
    class E memory;

🧱 Fundamental Understanding

Establish field, statement, timing, and industry context.

🧠 Intelligent Research

Turn operating phenomena into mechanisms and candidate directions.

🛡️ Trusted Validation

Move every research claim through successive evidence gates.

🗂️ Research Memory

Preserve results, failure reasons, and research lineage.

The endpoint of the product loop is not a factor; it is a reviewable research asset. Every run preserves its question, hypothesis, evidence, conclusion, and next steps.

The public version describes product capabilities and research principles only. Loopera's specific hypothesis structures, validation strategies, evaluation rules, model-collaboration mechanisms, and factor implementations are proprietary and are not disclosed here.

Technical Framework: Hypothesis-Driven, Evidence-Gated, Memory-Augmented

The core capability does not come from letting one model improvise; it comes from the coordination of an Agent, deterministic programs, and research memory.
A research environment around the model—not a model wrapped around a backtest.

💡 Hypothesis-driven

Explain first, compute second.

Start with an operating anomaly, compare competing mechanisms, and turn testable explanations into candidates.

Phenomenon → Mechanism → Candidate

🛡️ Evidence-gated

Evidence determines whether the work continues.

Data, timing, accounting treatment, logic, robustness, and incremental value form a sequence of gates.

Claim → Check → Decision

🧠 Memory-augmented

Give research durable context.

Preserve successes, failures, similar constructions, and unfinished leads to reduce repetition and reveal gaps.

Trace → Memory → Next Cycle

How the Three Capabilities Work Together

flowchart LR
    A["AI Agent<br/>Propose · Explain · Revise"] --> B["Research Contract<br/>Hypothesis · Fields · Direction · Constraints"]
    B --> C["Deterministic Harness<br/>Compute · Check · Evaluate"]
    C --> D["Research Memory<br/>Results · Failures · Lineage"]
    D -. "Provides research context" .-> A
    H["Human Researcher<br/>Review · Intervene · Decide"] <--> B

    classDef agent fill:#F1ECFF,stroke:#7C3AED,color:#07142E,stroke-width:1.5px;
    classDef contract fill:#E8F7FF,stroke:#168CFF,color:#07142E,stroke-width:1.5px;
    classDef evidence fill:#E8FFF7,stroke:#0F9F8F,color:#07142E,stroke-width:1.5px;
    classDef memory fill:#FFF2FB,stroke:#C13C8A,color:#07142E,stroke-width:1.5px;
    classDef human fill:#FFF8E6,stroke:#D98E04,color:#07142E,stroke-width:1.5px;
    class A agent;
    class B contract;
    class C evidence;
    class D memory;
    class H human;
  • AI Agent expands the research space by proposing, explaining, and revising ideas;
  • Research Contract turns natural-language claims into structured objects that can be computed and reviewed;
  • Deterministic Harness performs computation and objective checks so that narrative cannot substitute for evidence;
  • Research Memory supplies results, failures, and lineage as context for the next cycle;
  • Human Researcher retains review, intervention, and final decision rights at critical checkpoints.

System Modules

Nine modules form a three-layer architecture: the top layer handles interaction and orchestration, the middle layer performs research reasoning, and the bottom layer supplies data, evaluation, and long-term memory.
Each layer can evolve independently while sharing the same structured research objects.

Three-Layer System Architecture

flowchart TB
    subgraph L1["01 · Research Interaction & Orchestration"]
      direction LR
      A["Research Input & Material Understanding"] --> B["Agent Orchestration"] --> C["Traces & Reports"]
    end

    subgraph L2["02 · Hypothesis & Factor Research"]
      direction LR
      D["Hypothesis Research"] --> E["Factor Construction"] --> F["Trusted Validation"]
    end

    subgraph L3["03 · Data, Evaluation & Memory"]
      direction LR
      G["Data & Field System"] --> H["Backtesting & Incremental Evaluation"] --> I["Research Memory & Planning"]
    end

    A --> D
    B --> D
    E --> H
    F --> H
    H --> C
    G --> D
    G --> E
    I -. "Feeds back research context" .-> D

    classDef experience fill:#E8F7FF,stroke:#168CFF,color:#07142E,stroke-width:1.5px;
    classDef engine fill:#F1ECFF,stroke:#7C3AED,color:#07142E,stroke-width:1.5px;
    classDef foundation fill:#E8FFF7,stroke:#0F9F8F,color:#07142E,stroke-width:1.5px;
    class A,B,C experience;
    class D,E,F engine;
    class G,H,I foundation;
System Layer Question It Answers Included Modules
🔵 Research Interaction & Orchestration Where does research come from, how does collaboration work, and how is progress exposed? Research Input & Material Understanding · Agent Orchestration · Traces & Reports
🟣 Hypothesis & Factor Research How does a phenomenon become a testable candidate? Hypothesis Research · Factor Construction · Trusted Validation
🟢 Data, Evaluation & Memory Where does evidence come from, how is it evaluated, and how is it accumulated? Data & Field System · Backtesting & Incremental Evaluation · Research Memory & Planning
View the responsibilities and outputs of all nine modules
Module Core Responsibility Primary Output
Research Input & Material Understanding Accept a Topic, Prompt, or PDF and convert it into a unified, traceable research input Material summary, claim list, formula catalog, provenance
Data & Field System Unify financial fields, data versions, and publication times into a fundamental research panel Standardized data, field catalog, quality information
Agent Orchestration Coordinate a single Agent or multiple research roles and manage how a study begins, runs, and ends Research rounds, role opinions, task state
Hypothesis Research Propose and compare testable explanations for operating phenomena Research themes, operating mechanisms, evidence, failure conditions
Factor Construction Turn research hypotheses into computable candidate objects Candidate construction, fields used, expected direction, economic interpretation
Trusted Validation Check data, timing, accounting treatment, logic, robustness, and duplication Check results and rejection reasons
Backtesting & Incremental Evaluation Evaluate historical behavior consistently and test information beyond existing factors IC, grouped performance, coverage, stability, and incremental-value summary
Research Memory & Planning Preserve lineage, failure experience, theme crowding, and untested leads Direction board, failure knowledge, research gaps, next-step suggestions
Traces & Reports Organize inputs, reasoning, candidates, checks, and conclusions into readable artifacts Research cards, run traces, candidate funnel, result reports

Modules connect through structured research objects. Models, data sources, and evaluation components can therefore be upgraded independently without rewriting the entire research process.

PDF / Prompt Research Input Framework

Different forms of research material enter the same verifiable, traceable research thread.
Bring your question, your thesis, or an entire research report.

Research Entry Points

🎯 Topic

Provide a research direction

Let the Agent autonomously explore a theme such as cash-flow quality or operating efficiency.

✍️ Prompt

Express a research intent

Focus on a specified financial relationship, economic mechanism, industry scope, or validation priority.

📄 PDF

Import existing research material

Extract questions, claims, formulas, and constraints while preserving complete provenance.

From Material to Research Evidence

flowchart LR
    subgraph INPUT["Research Entry Points"]
        direction TB
        A["🎯 Topic"]
        B["✍️ Text Prompt"]
        C["📄 PDF"]
    end

    A --> D["Unified Research Input<br/>Identity · Summary · Source Fingerprint"]
    B --> D
    C --> D
    D --> E["Material Understanding<br/>Claims · Mechanisms · Candidates"]
    E --> F{"Conservative Routing"}
    F -->|Candidate is explicit| G["Priority Validation"]
    F -->|Primarily a viewpoint| H["Hypothesis Context"]
    F -->|Mixed content| I["Mixed Path"]
    G --> J["🛡️ Standard Validation Pipeline"]
    H --> J
    I --> J
    J --> K["🧠 Results · Failures · Source Lineage"]

    classDef input fill:#E8F7FF,stroke:#168CFF,color:#07142E,stroke-width:1.5px;
    classDef process fill:#F1ECFF,stroke:#7C3AED,color:#07142E,stroke-width:1.5px;
    classDef decision fill:#FFF7E6,stroke:#D97706,color:#07142E,stroke-width:1.5px;
    classDef trust fill:#E8FFF7,stroke:#0F9F8F,color:#07142E,stroke-width:1.5px;
    class A,B,C input;
    class D,E,G,H,I process;
    class F decision;
    class J,K trust;

Four Processing Stages

① 🧬 Unify the Input

Every item first receives a stable identity.

The system records material type, topic source, content summary, and a source fingerprint. Repeated material can be linked to earlier research records.

② 🔎 Understand the Material

Break long-form content into researchable objects.

Identify research questions, economic claims, applicable scope, explicit formulas, expected direction, constraints, and data gaps.

③ 🧭 Route Conservatively

Not every statement in a document is treated the same way.

Explicit candidates enter priority validation; viewpoints become hypothesis context; mixed material is separated; definitions that cannot be closed are recorded with reasons.

④ 🧾 Preserve Source Fidelity

Preserve the original claim and adapt only when necessary.

Formula structure, window, denominator, scope, and weights are retained as source constraints. Missing key fields are never silently replaced.

Routing Outcomes

Route When It Applies System Action
⚡ Priority Validation The definition is explicit and required data is available Convert it into a candidate and enter the standard validation pipeline
🧠 Hypothesis Context A viewpoint or mechanism is provided, but key choices remain unresolved Let the Agent continue proposing and comparing explanations
🔀 Mixed Path Explicit candidates and background views coexist Validate candidates first and use the remaining content for exploration
⏸️ Not Yet Supported Core data is missing or the definition cannot be closed Record the reason instead of forcing a construction

🛡️ Input safety: PDFs and Prompts can provide research evidence, but they cannot rewrite system rules, expand the data scope, or demand that validation be skipped.

✅ One standard: “Priority Validation” means only that a candidate can be constructed. Every candidate, regardless of source, still faces the same data, logic, accounting, historical-performance, and incremental-information checks.

🔗 End-to-end traceability: The final report identifies the source material, candidate-recognition outcome, necessary adaptations, blocking reasons, and final research disposition of every candidate.

View the material parsing checklist and source-adaptation principles

Loopera identifies the following from input material:

  • the research question and background;
  • the core economic claim and possible mechanisms;
  • the fundamental objects involved and the applicable scope;
  • explicitly proposed factors or formulas;
  • expected direction, constraints, and failure conditions;
  • data that may be missing, require a proxy, or remain ambiguous.

For a long PDF, the system first builds a catalog of candidate formulas so that factors explicitly stated in a table or later section are not buried by lengthy background discussion.

If the material specifies a formula structure, window, denominator, applicable scope, or weights, Loopera preserves them as source constraints. Conservative adaptation is allowed only when the material does not distinguish among standard accounting conventions, and the adopted convention is recorded in the result.

If a key field truly does not exist, the candidate is marked as data-missing or redirected into proxy research rather than silently replacing it with a superficially similar field.

How a Research Run Works

A research run is not “generate a formula + view a backtest.” It is an evidence-driven decision chain.
Context → Question → Mechanisms → Candidate → Evidence Gates → Memory

🧭 Expand the six-stage research loop and Evidence Gates

Six-Stage Research Loop

flowchart LR
    A["01  Establish Data Context"] --> B["02  Formulate the Research Question"]
    B --> C["03  Compare Competing Mechanisms"]
    C --> D["04  Construct a Candidate"]
    D --> E["05  Pass Evidence Gates"]
    E --> F["06  Write to Research Memory"]
    F -. "Feeds the next cycle" .-> B

    classDef context fill:#E8F7FF,stroke:#168CFF,color:#07142E,stroke-width:1.5px;
    classDef research fill:#F1ECFF,stroke:#7C3AED,color:#07142E,stroke-width:1.5px;
    classDef gate fill:#E8FFF7,stroke:#0F9F8F,color:#07142E,stroke-width:1.5px;
    classDef memory fill:#FFF2FB,stroke:#C13C8A,color:#07142E,stroke-width:1.5px;
    class A context;
    class B,C,D research;
    class E gate;
    class F memory;

① 🧱 Establish Data Context

First constrain what the Agent could have seen at the time.

Define financial fields, data versions, industry information, and the research period, then organize data by its actual publication time to prevent future information from entering earlier decisions.

② 🔭 Formulate the Research Question

Start with an operating anomaly worth explaining.

Ask why earnings failed to become cash, why operating liabilities diverged from business scale, or why capital spending did not produce corresponding assets—instead of combining fields at random.

③ 🧠 Compare Competing Mechanisms

Do not impose a single narrative on one phenomenon.

Retain plausible explanations such as normal settlement, active expansion, slower collections, or liquidity pressure. Continue only with mechanisms that financial evidence can distinguish.

④ 🧩 Construct a Candidate

Turn the hypothesis into a computable, reviewable research contract.

The candidate declares the information used, economic meaning, expected direction, and failure conditions. Later stages evaluate both the numbers and whether the implementation remains faithful to the original claim.

⑤ 🛡️ Validate in Stages

Run low-cost checks before full evaluation.

Data, timing, accounting treatment, logic, novelty, and historical evidence form successive gates. Any critical problem can stop the candidate.

⑥ 🗂️ Save and Continue Research

Both results and failures enter research memory.

Accepted candidates enter the research library. Rejected candidates retain their stopping point and reason, supporting deeper work, reduced repetition, or a deliberate pivot.

Evidence Gates

Evidence Gate Core Question Possible Outcome
⚙️ Execution & Coverage Does the code compute reliably, and is data coverage sufficient? Continue / Fix / Stop
⏱️ Point-in-Time Availability Was the financial information genuinely available at the research timestamp? Pass / Reject
🧾 Accounting Treatment Are stock, flow, cumulative values, and peer comparisons handled appropriately? Pass / Revise
🧠 Logical Consistency Do the economic interpretation, implementation, and expected direction agree? Pass / Return
🧬 Research Novelty Is the candidate merely a duplicate or slight variant of an existing result? Retain / Deduplicate
📈 Performance & Incremental Value Does the historical evidence meet basic quality standards and add new information? Admit / Stop

Every conclusion leaves the pipeline with evidence attached. Loopera records why the candidate was proposed, which checks it passed, where it stopped, and what the next research cycle should ask.

What the Agent Actually Produces

Loopera's smallest deliverable is not “a factor name + a backtest curve,” but a structured research record. Based on current run artifacts, a complete output usually includes:

Output Question It Answers
Fundamental phenomenon What anomaly was observed in the company's operations or financial relationships?
Research hypothesis Why might that anomaly relate to future operations or pricing?
Competing mechanisms What other plausible explanations could generate the same phenomenon?
Observable evidence What cross-statement or cross-period evidence could support, weaken, or reject an explanation?
Candidate description What risk or quality concept does the factor express, and what is its expected direction?
Quality record Did the candidate pass data, logic, accounting, and research-consistency checks?
Evaluation summary What do correlation, grouping behavior, coverage, and incremental information look like?
Lineage and next steps How does it relate to existing research, and what questions remain worth testing?

Full Case Study: From a Fundamental Observation to a Candidate Factor

A real research trace: from an accounting anomaly to an evidence-qualified candidate.
The case summary, nine-step trace, validation results, and evidence boundaries are collapsed below.

🔎 Expand the full case: abnormal employee-compensation liabilities × weak cash realization of revenue

Case question: Do abnormal employee-compensation liabilities contain cash-settlement pressure that the market has not fully understood?
A real research trace—from an accounting anomaly to an evidence-qualified candidate.

🔭 Research Question

Do abnormal liabilities reflect normal settlement, active expansion, or pressure on cash realization?

🧩 Candidate Concept

Employee-compensation liability deviation unexplained by operating scale × pressure on the cash realization of revenue

🛡️ Research Conclusion

The candidate passed all checks required in this round and entered the research library, but still requires out-of-sample validation.

Disclosure: The case logic and statistical results come from actual Agent output. To protect core technology, exact field combinations, time windows, weighting functions, outlier treatment, and internal decision parameters are not disclosed.

Why This Is a Cross-Statement Question

Employee-compensation liabilities represent wages, bonuses, benefits, and other employee-related obligations that have been recognized but not yet paid in cash. They sit on the balance sheet, while revenue and expenses appear on the income statement, and cash payments and cash receipts from sales appear in the cash-flow statement.

The absolute liability level alone is not meaningful enough. Company size, bonus seasonality, and expansion stage all affect its normal level. The real question is: Has the liability exceeded what business scale, industry characteristics, and the normal settlement cycle can explain?

Nine-Step Research Trace

flowchart TB
    subgraph P1["01 · Discover & Explain"]
      direction LR
      A["1 Detect an Anomaly"] --> B["2 Compare Mechanisms"] --> C["3 Select a Testable Explanation"]
    end
    subgraph P2["02 · Build & Review"]
      direction LR
      D["4 Form a Research Contract"] --> E["5 Validate Data & Implementation"] --> F["6 Blind-Review the Economic Logic"]
    end
    subgraph P3["03 · Evaluate & Learn"]
      direction LR
      G["7 Evaluate Performance & Incremental Value"] --> H["8 Compare the Candidate Family"] --> I["9 Write to Research Memory"]
    end
    C --> D
    F --> G
    I -. "Feeds the next cycle" .-> A

    classDef discovery fill:#E8F7FF,stroke:#168CFF,color:#07142E,stroke-width:1.5px;
    classDef validation fill:#F1ECFF,stroke:#7C3AED,color:#07142E,stroke-width:1.5px;
    classDef learning fill:#E8FFF7,stroke:#0F9F8F,color:#07142E,stroke-width:1.5px;
    class A,B,C discovery;
    class D,E,F validation;
    class G,H,I learning;
Stage One · Discover & Explain: From an anomaly to a testable mechanism

① Detect an Anomaly Worth Explaining

An earlier research round found a preliminary signal in the “deviation of employee-compensation liabilities from normal operating scale.” Instead of mechanically swapping the scaling denominator again, Loopera changed the next task to: explain why the existing signal might relate to future performance.

Research Question Card Agent Output
Observed phenomenon Employee-related operating liabilities are high relative to revenue and peer norms
Normal state Liabilities move with business scale and seasonal settlement, then decline in the following payment period
Deviation to explain The elevated amount cannot be fully explained by scale, bonus cycles, or normal expansion
Research question Does the deviation indicate future cash-payment, financing, or earnings-quality pressure?
Expected direction If the deviation represents unabsorbed payment pressure, future performance should be relatively weaker

② Propose Competing Mechanisms

Competing Mechanism Fundamental Interpretation Supporting Evidence to Observe
Cash-turnover pressure Insufficient operating cash causes employee-related payments to be delayed Deterioration in collections, cash buffers, or financing pressure
Profit-driven bonus accruals Improved profitability produces performance-bonus or profit-sharing accruals Earnings improve first; liabilities rise seasonally and decline after payment
Revenue recognition leads cash collection Revenue has been booked, but customer payments have slowed A gap emerges between revenue and cash receipts from sales
Capacity build-out and hiring lead revenue Facilities, equipment, and people are added before revenue is fully realized Capital investment and construction-in-progress rise before later operating expansion

These mechanisms can coexist. Loopera does not claim that three financial statements can prove whether a company is withholding wages. It searches for public evidence that raises or lowers the credibility of a particular explanation.

③ Select a Testable Mechanism

This round tests the mechanism that “revenue recognition leads cash collection.” Revenue on the income statement and cash receipts from sales on the cash-flow statement describe the same operating process from different angles. If revenue remains present while cash inflow weakens, the abnormal accumulation is more likely to relate to cash-realization pressure rather than scale alone.

Public conceptual expression: employee-compensation liability deviation unexplained by operating scale × pressure on the cash realization of revenue

This is not a production formula. The actual construction also contains time alignment, accounting-basis conversion, industry comparability, missing-value treatment, and robustness steps.

Stage Two · Build & Review: Turn the research claim into a trusted candidate

④ Form a Computable Research Contract

Declaration Content
Information used Public financial information from the balance sheet, income statement, and cash-flow statement
Economic meaning Identify abnormal employee-compensation liabilities outside normal operating relationships and accompanied by weak cash realization
Expected direction Greater pressure may imply greater pressure on future operating and market performance
Failure conditions Bonus seasonality, advance receipts, settlement timing, business-model differences, and active expansion may cause false positives

The code implementation is bound to these declarations. Even if historical performance looks strong, a candidate is rejected or the research claim must be revised when the code actually measures something else.

⑤ Validate Data and Implementation

  • Validate effective financial observations, research-panel coverage, and consistency across historical information snapshots;
  • Introduce new cross-statement mechanism information relative to earlier attempts rather than merely replacing a denominator;
  • Handle stock liabilities, period revenue, and cumulative cash flows according to their appropriate accounting treatment.

⑥ Review the Logic Without Seeing Backtest Results

An independent reviewer reads only the research hypothesis, field definitions, and candidate implementation—not backtest returns. The candidate continued after economic-logic review, subject to the following limitations:

  • Low cash receipts from sales relative to revenue is more accurately described as weak cash realization, not customer default;
  • Bonus accrual and payment are seasonal; peer comparison can mitigate but not eliminate the issue;
  • Industry classifications do not necessarily imply identical business models, so peer benchmarks may remain too coarse;
  • A single-period cash-realization measure can be affected by advance receipts, cross-period settlement, and a small denominator;
  • Current evidence supports risk-state identification but is insufficient to determine specific payment behavior by a company.
Stage Three · Evaluate & Learn: Decide whether to admit the candidate and what to study next

⑦ Evaluate Historical Performance and Incremental Value

The candidate enters full research evaluation only after passing logical review. Because the public materials do not simultaneously disclose a reproducible sample period, universe, rebalancing rules, costs, and turnover assumptions, this README does not display specific performance figures.

⑧ Compare Other Candidates in the Same Family

This research family retains 7 related attempts. 2 entered the research library, while 5 stopped at different stages:

  • The first base construction was returned because the stated research idea and implementation did not align; it passed only after revision;
  • A variant intended to remove expansion effects did not receive support in early data checks;
  • A rewritten version showed preliminary performance but failed to demonstrate incremental value beyond existing results;
  • Other liquidity-conditioned variants did not provide sufficient evidence.

Confirming a theme does not mean accepting every formula within it. Each branch must independently explain which mechanism it tests, whether it remains faithful to the original hypothesis, and whether it genuinely adds information.

⑨ Write to Research Memory

The system preserves more than the factor panel. It also records the source phenomenon and mechanism branch, where sibling constructions failed, seasonality and proxy risks raised by reviewers, how crowded the direction has become, and the out-of-sample, stability, and finer-grained fundamental validation required next.

When the Agent later studies a related topic, this material re-enters context so that the work does not restart from the same simple ratio.

Public Evidence Boundary

The README discloses only the research question, mechanisms, validation process, and conclusion boundaries. Until a complete methodology is published, it does not present weak metrics such as Rank IC, Sharpe ratio, annualized return, drawdown, or coverage that could be misread as product performance.

What the Evidence Supports

✅ Currently Supported

When employee-related operating liabilities deviate materially from normal operating relationships while revenue also shows weak cash realization, the combined state contains some incremental information in the historical sample.

🚫 Not Currently Supported

The evidence cannot confirm that a company is withholding wages, nor can it establish out-of-sample profitability or justify direct trading use.

A complete deliverable is not a formula. It is a research question, multiple competing mechanisms, an executable candidate, a layered body of validation evidence, a conclusion with explicit limitations, and research memory that the next cycle can reuse.

Core Characteristics

🧱 Fundamentals First

Start from business operations and cross-statement relationships rather than observing price outcomes first and inventing an explanation afterward.

⚖️ Separate Logic from Results

Judge whether the explanation is sound independently from whether historical data supports it, reducing the risk of reverse-engineering a narrative from attractive results.

🧬 Focus on Incremental Information

A candidate that performs well but closely resembles an existing factor does not automatically become a new research result.

🧾 End-to-End Traceability

Record sources, hypotheses, validation, decisions, and stopping reasons so that every conclusion can be reviewed.

🔁 Learn from Failure

Failures are research assets used to reduce repeated mistakes and reveal areas that remain underexplored.

🤝 Human-Agent Collaboration

The Agent expands exploration and organizes evidence; professional research teams retain critical review and final decision authority.

Current Research Output

147 candidate attempts · 66 structured hypotheses · 37 research patterns · 5 candidates admitted to the research library
The complete candidate funnel, research coverage, and independent Agent evaluation are collapsed below.

📊 Expand current research output and evaluation results

The following internal research-run snapshot illustrates what the Framework has actually produced.
These numbers describe research activity—not investable signals.

147

Candidate Attempts

66

Structured Hypotheses

37

Research Patterns

5

Admitted to the Research Library

Candidate Funnel

flowchart LR
    A["147 Candidate Attempts"] --> B["130 Valid Candidates"]
    A --> X["17 Did Not Produce Valid Candidates<br/>Execution or Generation Issues"]
    B --> C["125 Explicitly Stopped"]
    B --> D["5 Admitted to the Research Library"]

    classDef total fill:#E8F7FF,stroke:#168CFF,color:#07142E,stroke-width:1.5px;
    classDef stopped fill:#FFF1F2,stroke:#E5484D,color:#07142E,stroke-width:1.5px;
    classDef accepted fill:#E8FFF7,stroke:#0F9F8F,color:#07142E,stroke-width:1.5px;
    class A,B total;
    class X,C stopped;
    class D accepted;

Roughly two-thirds of attempts stopped during economic-logic review or early signal screening. The system's primary job is not to admit as many candidates as possible, but to eliminate ideas with weak explanations or insufficient evidence early.

Primary Stopping Point Attempts Typical Reason
Research logic and economic consistency 52 Narrative and implementation disagree, proxy interpretation is too strong, or direction/accounting meaning is problematic
Early signal screening 45 Basic historical evidence is insufficient, so full evaluation cost is not incurred
Data coverage and panel quality 11 Too few usable companies, insufficient cross-sectional differentiation, or unstable data state
Duplication with historical research 9 Too similar to earlier attempts and adds no substantive information
Full performance and incremental evaluation 7 Preliminary signal exists but does not meet final quality or incremental-value requirements
Execution and timing checks 3 Computation fails, is unstable, or uses data at an invalid time

Research Coverage

💵 Quality of earnings-to-operating-cash-flow conversion 📦 Customer collections, inventory, and working-capital usage
🏗️ Alignment between capital expenditure and asset formation 👥 Operating liabilities and employee-compensation settlement pressure
📈 Alignment between administrative expenses and business expansion 🧾 Abnormal use of prepayments and other receivables
🤝 Supplier credit and changes in procurement settlement ♻️ Sustainability of investment income

These themes reflect Loopera's fundamental orientation: the research object is not an isolated financial ratio, but an operating relationship that should hold across statements and may have begun to diverge.

What Characterizes Admitted Candidates

The current 5 admitted candidates are concentrated in the “abnormal operating liabilities” research thread. This suggests that the Agent found a phenomenon worth deepening, while also showing that research diversity remains limited at this stage.

⚠️ Abnormal-Burden Candidates

Assess whether an operating liability materially exceeds the normal range explained by revenue, costs, or peer operating conditions.

🔎 Mechanism-Differentiation Candidates

Combine cross-statement evidence such as cash realization and capital investment to distinguish normal expansion or settlement timing from potential cash pressure.

The public page does not disclose field combinations, production formulas, or performance ranges for admitted candidates. Public information focuses on the research process, traceable evidence, and explicit capability boundaries.

Independent Evaluation of Agent Capability

We also evaluate the Agent's discovery ability and false-discovery risk in simulated environments where the true answer is known, rather than relying only on historical market results whose ground truth cannot be confirmed.

✅ Capabilities Already Demonstrated

  • It can identify some traditional linear fundamental information;
  • The data-understanding, hypothesis-generation, factor-construction, and evaluation chain is operational;
  • In a no-signal environment, the full validation process filtered out final candidates created by chance significance.

🧭 Capabilities That Still Need Improvement

  • Autonomous discovery of interactions, state dependence, and complex nonlinear relationships remains limited;
  • The Agent is susceptible to examples and common formulations in prompts;
  • More data and more attempts do not automatically produce more truthful discoveries; stopping rules, diversity, and independent evaluation remain essential.

Across real runs and simulation experiments, Loopera is already an operational, verifiable, and cumulative fundamental-research Framework. Its clearest value today is expanding research coverage, standardizing the research process, and preserving reviewable evidence—not promising the automatic discovery of stable Alpha.

Use Cases

🧭
Expand Research Directions
Find fundamental phenomena worth explaining
🧩
Validate Factor Ideas
Turn economic hypotheses into candidates and screen them
🧬
Check Incremental Value
Identify duplicate constructions and new information
🧾
Standardize Research
Unify the evidence chain and preserve a complete trace
🎓
Assist Researchers
Provide scaffolding for fundamental research
🧪
Evaluate Agents Under Control
Measure discovery capability and false-discovery risk

Disclaimer

🚫 Not Investment Advice

Loopera does not promise returns and does not replace data licensing, compliance review, or investment decisions.

🚫 Not a Fact Generator

Language-model output is never treated directly as fact. Every claim requires evidence.

🚫 Not One-Click Alpha

One historically significant result is not an effective factor. Independent research and risk assessment are still required before formal use.

Public Disclosure Scope

✅ Public in This Repository 🔒 Not Publicly Disclosed
  • Product framework and research principles
  • Aggregated experimental conclusions
  • Case explanations that do not reveal core constructions
  • Unauthorized raw data and data snapshots
  • Specific candidate-factor implementations and trading use
  • Internal evaluation rules, parameters, and research strategies
  • Proprietary Agent collaboration, hypothesis-evolution, and validation mechanisms
  • Keys, service configuration, and run records containing sensitive context

Make Fundamental Research Compound

Start with a question worth explaining, and make every research cycle the foundation for the next.

Visit the Loopera website Read the Loopera technical paper Return to the full research case study

Loopera is intended for research and technical evaluation. It is not investment advice and does not promise future returns.

Explore related projects