Pygplates Fiction Worldbuilder

2. Select API depth:

• Prefer ReconstructModel and TopologicalModel for repeated time queries.
• Use one-shot functions (reconstruct, resolve_topologies, partition_into_plates) for batch utilities.

3. Preserve data invariants:

• Ensure reconstructable features have geometry, reconstructionPlateId, and valid time when needed.
• Keep rotations and feature times in the same temporal frame (Ma before present).
• Treat topology-driven reconstruction as point-based unless you explicitly build a mesh/sampling strategy.

4. Build user-facing defaults:

• Default anchor plate from model unless user requests otherwise.
• Default topological time_increment=1 Myr for stability.
• Expose named plates in UI and map to internal plate IDs.
• Keep advanced deformation parameters hidden behind an "expert" panel.

5. Validate behavior:

• Verify a known point/path reconstructs correctly at multiple times.
• Check features outside plate coverage and report fallback behavior.
• Confirm exports load in GPlates when interoperability is required.

Product Guardrails

• Use reverse_reconstruct only when you intentionally rewrite stored geometries in-place.
• Reuse RotationModel/ReconstructModel/TopologicalModel instances across time loops for performance.
• When partitioning with overlapping polygons, set deterministic sorting and document chosen policy.
• Explain left/right plate semantics whenever editing subduction or transform boundaries.

Output Requirements

• Provide explicit assumptions about time range, anchor plate, and model coverage.
• Surface API-level caveats that affect user-facing correctness.
• Prefer minimal reproducible examples over abstract guidance.