Documentation
Use the application to explore synthetic life sciences workflows, then follow the route that matches what you want to build or understand. The Markdown files here are the current documentation source. The ordinary build also serves selected articles at /docs/; the same source can build at the root of the independent foundation site. Documentation implementation names the manifest, profiles and source-derived GraphQL reference.
Start and try
- Getting started: local example, a sample walkthrough, Node API and one focused test.
- Fixture provenance: synthetic records, supplied findings and scenario-policy boundaries.
- Database choices: supported PostgreSQL and bundled examples, with retained MySQL compatibility, plus optional graph/RDF/object-store extensions.
- Local PostgreSQL clone: start, stop, backup, restore and reset an isolated persistent example.
- PostgreSQL: server configuration, explicit schema/seed ownership, bounded transactions and recovery.
- Deployment: ordinary Node serving, isolated PostgreSQL, bundled examples and the Figma Make adapter.
Change and extend
| Reader task | Source route | Related contract |
|---|---|---|
| Add a scene or preserve edits across responsive views | Application | Mobile, workspace layout, loading |
| Add a read or inspect persisted data | Server | GraphQL, catalog, visitor workspaces |
| Change permissions or a shared record shape | Shared contracts | Permission scenarios, input boundaries |
| Choose a useful test or investigate a failure | Tests | Automation, selective checks |
| Deliver, maintain dependencies or recover setup | Runbooks | Node deployment, publication scan, database recovery |
Understand an interaction
Specimens, Source records, comparisons, release records, Map and QC, Artifacts, Cohort rules and Profile name their accepted effects and recovery. The workspace assessment connects these families without treating every visible control as an external operation.
Theme, Plate layout, compact records and presentation styles describe composition and paint. Shareable navigation records bounded URLs, Back/Forward and Source draft continuity. Guided exploration explains the optional walkthrough's control handback. Research documents preserve the source and reasoning behind a decision; their dated observations stay distinct from a check of a new revision.
Source and publication
Edit an owning Markdown document rather than generated output. The ordinary build generates /llms.txt and /llms-full.txt from the population in the content manifest: root Markdown, LICENSE, docs/, guidelines/, .agents/skills/, admitted articles and the generated schema reference. That public bundle includes development guidance; it grants no runtime authority. Nearby READMEs under source directories remain repository reading routes, linked from this index. Attributions and the license retain their own roles.
Human and AI-assisted contributors can use the local methods in AGENTS.md. Required operating guidance lives in this clone; public research references supply additional context.
Return to the repository