delaunay 0.8.1

D-dimensional Delaunay triangulations and convex hulls in Rust, with exact predicates, deterministic degeneracy handling, explicit topology validation, and bistellar flips for finite point sets.
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82

# Code Organization Guide

This file is the required-reading architecture hub for the repository. It is
intentionally short: read it first, then follow the focused architecture links
only for the surface you are changing.

## Architecture Documents

The architecture directory is indexed in
[`architecture/README.md`](architecture/README.md). For common changes, use the
focused ownership map below.

| Need | Read |
|-----|-----|
| Repository tree, packaging shape, and top-level directories | [`architecture/project_structure.md`](architecture/project_structure.md) |
| `src/` module ownership, layer boundaries, and public namespace policy | [`architecture/module_map.md`](architecture/module_map.md) |
| Focused prelude taxonomy and import guidance | [`architecture/prelude_reference.md`](architecture/prelude_reference.md) |
| In-file Rust module layout and section-order conventions | [`architecture/module_patterns.md`](architecture/module_patterns.md) |

Development guidance is indexed in [`dev/README.md`](dev/README.md), with
commands in [`dev/commands.md`](dev/commands.md). Do not copy command matrices
into architecture docs; link to the command guide instead.

## Required Orientation

- `src/core/` is the internal TDS and algorithm layer. Public low-level access
  is exposed through curated root modules such as `delaunay::tds`,
  `delaunay::collections`, `delaunay::algorithms`, and `delaunay::query`, not
  through a broad public `delaunay::core` module.
- `src/core/tds/` owns the proof-bearing Levels 1–2 `Tds`, its private
  canonical storage, and every checked storage transition. Higher layers do
  not receive raw field access; this boundary is independent of where those
  higher-level modules live in the source tree.
- `src/triangulation/` owns the Levels 3–4 `Triangulation` model and all
  operations whose contracts require no Level 5 Delaunay proof, including
  queries, flips, and Pachner moves. It consumes checked TDS transitions and
  owns the Level 3 topology and Level 4 realization conditions.
- `src/delaunay/` owns the Level 5 refinement and Delaunay-facing
  construction, insertion, deletion, validation, repair, serialization, and
  forwarding query APIs.
- `src/geometry/` owns points, coordinate ranges, kernels, predicates,
  geometric quality measures, convex hull support, and coordinate conversion
  utilities.
- `src/io/` owns downstream-facing export data models for notebooks,
  visualization, analysis, and interchange. It does not own TDS hydration.
- `src/topology/` owns topology metadata/models, topology-space helpers,
  spherical coordinate backends, Euler characteristic helpers, manifold
  validation, ridge queries, and PL-manifold reasoning.
- `src/lib.rs` wires public modules, root re-exports, focused preludes, and the
  crate-level documentation map.
- `docs/dev/README.md` indexes the operational rules for agents. Keep
  architecture orientation here and detailed workflow/tooling instructions
  under `docs/dev/`.

## Layering Rules

- Proof-owner dependencies should stay
  `core::tds <- triangulation <- delaunay`; lower proof layers must not depend
  on higher proof owners.
- `edge.rs` and `facet.rs` stay in `src/core/` because they are direct TDS
  traversal primitives. Ridge query/view types belong in `src/topology/`
  because ridge shape and link semantics depend on dimension and topology.
- Generic Level 4 realization validation belongs in
  `src/triangulation/realization.rs`;
  implemented Level 5 Geometric Predicate APIs for Delaunay belong in
  `src/delaunay/validation.rs`, with TDS-level Delaunay-property scan helpers
  under `src/delaunay/`; Levels 1–2 validation belongs with `core::tds`, while
  Level 3 topology validation belongs with `Triangulation` and the topology
  helpers it consumes.
- Focused preludes should stay narrow and workflow-specific. Use
  `delaunay::prelude::pachner::*` for ordinary local move workflows. The public
  primitive bistellar API remains available to expert callers through a direct
  `delaunay::flips` import, but is intentionally excluded from preludes.

## Maintenance Notes

- When files move, update the focused architecture document that owns that
  surface rather than growing this hub.
- When command names, validation recipes, or tool policy change, start from
  [`dev/README.md`](dev/README.md), then update the focused owner it identifies,
  usually [`dev/commands.md`](dev/commands.md), not this file.
- Keep this hub small enough to load as part of every agent session.