DART Research References
Load this skill when adding, updating, auditing, or citing research references
(papers, textbooks, model-format standards, or comparative engines) for the DART
experimental simulation world — its public API and its algorithms.
Catalog Location
docs/readthedocs/papers.md is the single source of truth and the published
website page. It is a companion to the experimental API design docs:
docs/design/simulation_cpp_api.md
docs/design/simulation_python_api.md
Entry Schema
Each entry has an id, a full citation, and these properties:
| Property |
Values |
| Type |
textbook, paper, standard, engine |
| Topic |
e.g. dynamics, kinematics, contact, integration, collision, terminology, model-format, api |
| Status |
referenced, planned, in-progress, implemented, deferred, rejected |
| Priority |
high, medium, low, — |
| Verdict |
adopt, baseline, reference, evaluate, reject |
| Where used |
link to the design doc, code, or test that uses (or will use) it |
Status is written from the experimental world's perspective. A method shipping
in classic DART but not yet in the experimental world is planned, with the
classic location noted in Notes.
Workflow: add or update an entry
- Ground the entry in real evidence — a design doc, code path, test, or an
explicit project decision. Do not add aspirational references with no link.
- Write an accurate citation (authors, title, year, venue/publisher). Prefer an
official URL; do not fabricate DOIs.
- Add a row to the matching summary table and a detail subsection with the
full properties and a one-line rationale.
- Set
Status from the experimental world's perspective; note classic-DART
status separately in Notes.
- Set
Verdict (adopt to build on, baseline to compare against,
reference to cite, evaluate while undecided, reject with a reason).
- Fill
Where used with the design-doc/code/test link.
- When the relationship changes (e.g. a
planned algorithm becomes
implemented, or an evaluate is decided), update Status/Verdict and the
Where used link in the same change.
Rules
- Prefer robotics/dynamics literature (textbooks, papers) over engine-specific
names when a reference informs a terminology decision; record the grounding in
the catalog's "Terminology Grounding" section.
- Keep the catalog scoped to the experimental world for now; the schema is
general and can extend to the rest of DART later.
- Keep
engine entries as baselines/comparisons, never as dependencies.
- Use
docs/ai/verification.md to select the docs-only or AI docs/adapters
gate set, then run pixi run lint after edits.
Full Documentation
For the catalog and its rationale: docs/readthedocs/papers.md
For the API it supports: docs/design/simulation_cpp_api.md,
docs/design/simulation_python_api.md
For DART's research focus: docs/ai/north-star.md
1---2name: dart-references-23description: DART References: manage the experimental simulation research catalog (papers, textbooks, engines) with status, priority, and verdict4---56# DART Research References78Load this skill when adding, updating, auditing, or citing research references9(papers, textbooks, model-format standards, or comparative engines) for the DART10experimental simulation world — its public API and its algorithms.1112## Catalog Location1314`docs/readthedocs/papers.md` is the single source of truth and the published15website page. It is a companion to the experimental API design docs:1617- `docs/design/simulation_cpp_api.md`18- `docs/design/simulation_python_api.md`1920## Entry Schema2122Each entry has an `id`, a full citation, and these properties:2324| Property | Values |25| -------------- | ---------------------------------------------------------------------------------------------------------- |26| **Type** | `textbook`, `paper`, `standard`, `engine` |27| **Topic** | e.g. `dynamics`, `kinematics`, `contact`, `integration`, `collision`, `terminology`, `model-format`, `api` |28| **Status** | `referenced`, `planned`, `in-progress`, `implemented`, `deferred`, `rejected` |29| **Priority** | `high`, `medium`, `low`, `—` |30| **Verdict** | `adopt`, `baseline`, `reference`, `evaluate`, `reject` |31| **Where used** | link to the design doc, code, or test that uses (or will use) it |3233`Status` is written from the experimental world's perspective. A method shipping34in _classic_ DART but not yet in the experimental world is `planned`, with the35classic location noted in `Notes`.3637## Workflow: add or update an entry38391. Ground the entry in real evidence — a design doc, code path, test, or an40 explicit project decision. Do not add aspirational references with no link.412. Write an accurate citation (authors, title, year, venue/publisher). Prefer an42 official URL; do not fabricate DOIs.433. Add a row to the matching summary table **and** a detail subsection with the44 full properties and a one-line rationale.454. Set `Status` from the experimental world's perspective; note classic-DART46 status separately in `Notes`.475. Set `Verdict` (`adopt` to build on, `baseline` to compare against,48 `reference` to cite, `evaluate` while undecided, `reject` with a reason).496. Fill `Where used` with the design-doc/code/test link.507. When the relationship changes (e.g. a `planned` algorithm becomes51 `implemented`, or an `evaluate` is decided), update `Status`/`Verdict` and the52 `Where used` link in the same change.5354## Rules5556- Prefer robotics/dynamics literature (textbooks, papers) over engine-specific57 names when a reference informs a terminology decision; record the grounding in58 the catalog's "Terminology Grounding" section.59- Keep the catalog scoped to the experimental world for now; the schema is60 general and can extend to the rest of DART later.61- Keep `engine` entries as baselines/comparisons, never as dependencies.62- Use `docs/ai/verification.md` to select the docs-only or AI docs/adapters63 gate set, then run `pixi run lint` after edits.6465## Full Documentation6667For the catalog and its rationale: `docs/readthedocs/papers.md`6869For the API it supports: `docs/design/simulation_cpp_api.md`,70`docs/design/simulation_python_api.md`7172For DART's research focus: `docs/ai/north-star.md`