Technical Contracts
This section is FEMIC’s compact technical contract surface.
Use it when you need a fast answer about repo invariants, runtime prerequisites, path resolution, stage boundaries, canonical artifacts, or restart behavior.
This is intentionally not a separate agent-only documentation universe. The pages here live in the same Sphinx tree as the narrative Guides and API Reference, and they link back to those deeper pages instead of duplicating them wholesale.
How to use this section
Start here when you need the shortest source-of-truth answer for an operational seam.
Follow the linked Guides when you need the full runbook or interpretation detail.
Follow the linked API pages when the question is really about code ownership or callable behavior rather than workflow contract.
Contract Pages
- Patchworks Model Semantics
- Forest Carbon Domain and CBM Package Contract
- Repo and Runtime Invariants
- Instance and Data Roots
- Instance Extension Boundaries
- Stage Boundaries and Canonical Artifacts
- Recovery and External Runtime Boundaries
- Hydrology Domain Contract
- Hydrology Data Bundle Contract
- Hydrology Disturbance Ledger Contract
- Tier 0 Hydrology Screening Contract
- Flood-Frequency Response Contract
- Process-Model Adapter Contract
- Surrogate Model Contract
- Hydrology Response Bundle Contract
- Hydrology Validation And Closeout Contract
- LiDAR Source and Tile-Index Contract
- LiDAR Materialization Contract
- LiDAR Terrain Product Contract
- Terrain-Derived Stream Candidate Contract
- Native Canopy And Tree Product Contract
- LiDAR Product Bundle Contract
- LiDAR ground-bundle contract
- Inventory ALS Contract
- Climate Contract (
femic.climate.v1) - Climate Consumer
- Disturbance Contract (
femic.disturbance.v1) - EFI Model Card (
femic.efi.model.v1) - EFI Model Application (
femic.efi.coefficients.v1) - EFI Biomass Curve (
femic.efi.biomass_curve.v1) - Site-Index Reconciliation (
femic.site-index.reconciliation.v2)