# OrbPro2 Module Authoring Agents

Use these instructions when creating SDK-compliant OrbPro2 modules from the
OrbPro public documentation.

## Source Of Truth

- The Space Data Module SDK owns the generic manifest, ABI, harness, compliance,
  and host-loading contract.
- OrbPro owns the domain-specific authoring recipes for propagators, maneuver
  planners, force models, OD, conjunction analysis, access/coverage, sensors,
  shaders, and Basilisk-backed simulation.
- `space-data-network-modules` is the reference implementation corpus.

## Required Routing

1. Read the SDK module contract first.
2. Select exactly one module-type layer from `modules/layers/`.
3. Use the layer's reference module paths as examples.
4. Keep all inputs and outputs SDS-backed.
5. Produce a canonical `dist/isomorphic/module.wasm` artifact.
6. Add authoritative tests before claiming the module is complete.

## Guardrails

- Do not invent repo-local FlatBuffer schemas.
- Do not use app-framework types as module ports.
- Do not generate JavaScript fallback physics for deployable module behavior.
- Do not mark numerical modules complete with only self-generated golden data.
- Do not treat application integration as module authoring.

## Layer Index

- `layers/propagators.md`
- `layers/maneuver-planners.md`
- `layers/atmosphere-force-models.md`
- `layers/orbit-determination.md`
- `layers/conjunction-analysis.md`
- `layers/access-coverage.md`
- `layers/sensor-shader-modules.md`
- `layers/basilisk-backed-simulation.md`