Public case study
TaiYi Lingjing / 太一·灵境
A proposed AI-native scientific discovery environment connecting evidence, biological state, simulation and experiment design.
Status Concept and research direction. Engineering implementation has not started — there is no repository, prototype or validation result.
What it is
TaiYi Lingjing is a proposed AI-native scientific discovery environment: a planned loop that starts from a biological question and ends with a ranked, evidence-backed experiment plan.
It is intended to be organised around five subsystems — Bio, Discovery, Experiment, Evidence, Human — with agents meant to coordinate the hand-offs between them.
Why it matters
The bottleneck in discovery is usually not generating hypotheses but judging which one is worth paying to test, and whether the evidence behind that judgement can be traced.
This is a research direction, not a delivered capability.
Current public status
Concept · Not Started.
Implementation has not started. There is no repository, no prototype, no deployment and no validation result.
What is publicly available
Nothing to open today, and no repository to verify. This page is deliberately the only public artefact.
Notes
No statement on this page should be read as an implementation status. The concept exists in writing only.
Implementation status
A written research concept. Engineering implementation has not started.
What exists today, and how you would check it. Nothing below is a rendered mockup of something that does not exist.
- Public code
- None — nothing published
| Component | State | Note |
|---|---|---|
| Research framing | Designed | The problem statement, scope and motivation are written down. Nothing beyond text exists. |
| Proposed architecture | Designed | A five-subsystem decomposition — Bio, Discovery, Experiment, Evidence, Human — described on this page as an intended design. No code can be cross-checked against it. |
| Discovery loop | Designed | The loop — hypothesis, retrieval, simulation, experiment proposal, evidence audit — is specified as an operating model, not implemented as a pipeline. |
| Engineering implementation | Planned | Not started. The first milestone is named on this page and nothing precedes it. |
| Prototype | Planned | None. No partial prototype, no unreleased prototype, nothing to show or withhold. |
| Validation | Planned | No validation has run because there is nothing to validate. What would have to be true is written down instead. |
| Public repository | Not public | None. No code link is shown anywhere on this site. |
How to read these states 3
- Designed Specified — architecture, contracts and scope exist in writing.
- Planned Identified for future work. Nothing to inspect yet.
- Not public Reported to exist, but no public artifact can be checked.
How to read this page
This is a research concept with a written brief, not a system you can inspect. Everything below describes intent. Where an artifact would normally be cited, none exists — and none is implied.
Source Site editorial standard.