Carbon package workflow
This is the producer-side entry point for FEMIC’s forest carbon lane. It connects the static package, the public fertilization response, the HWP assumptions, the GCBM bridge, and the WS4 consumer path. The detailed pages remain the authority; this page is the map.
Start here
If you are |
Read |
Why |
|---|---|---|
An analyst building a study |
This page, then Carbon Package Export |
Build and validate the package that WS4 consumes. |
A developer or reviewer |
Forest Carbon Domain and CBM Package Contract, then this page |
The schema, join key, crosswalk, and engine boundary. |
A researcher or policy analyst |
Harvested wood product lifecycle, Fertilization Response and Emissions Audit, and GCBM walltowall Export |
The assumptions, the emissions accounts, and the bridge boundary. |
An LLM agent |
This page, |
The stable source map before changing the carbon lane. |
Data flow
public instance bundle + checkpoint
|
v
FEMIC carbon export-package
(static classifiers, inventory, yield, crosswalks, boundaries)
|
v
femic carbon validate
|
v
WS4 package loader -> SIT compiler -> libcbm -> carbon accounts
|
+-> HWP lifecycle (public config)
+-> optimizer block ledger
+-> system targets
FEMIC export gcbm is a separate walltowall bridge; it is not a WS4 runtime dependency.
What belongs where
Surface |
Owner |
What it means |
|---|---|---|
Static package |
FEMIC |
Species/eco/disturbance crosswalks, initial inventory, merchantable yield, boundaries, provenance, and hashes. |
Schedule and events |
WS4 |
The annual treatment chain, block area, and the exact event offsets. |
Engine |
WS4 |
libcbm behind the driver protocol; a replaceable engine, not a package field. |
HWP assumptions |
FEMIC publishes; WS4 applies |
Public half-life, split, utilization, and displacement config in
|
GCBM project and results |
FEMIC exports; WS4 reads |
A separate spatially explicit bridge and tabular reader, not a parity oracle. |
Stable page map
Question |
Page |
|---|---|
What is the package schema and join contract? |
|
How do I export and validate a package? |
|
What are the public fertilization response and emissions factors? |
|
How are HWP products, decay, displacement, and EOL emissions counted? |
|
How do I prepare a GCBM walltowall project? |
|
How does WS4 consume the package and optimize carbon? |
|
How do I run a carbon study end to end? |
Production evidence
The production package ids and validation status for TSA08, TSA16, TSA40, and TSA41 are
recorded in the producer note notes/reports/p120-multi-boundary.md and the
WS4 consumer report.
The key producer facts are:
all four packages validate against the public CBM defaults hash
4bd722d8825abeda3c9cf77247bbd4903824259e2fcc046d9a335336c8842155;each package carries multiple eco boundaries where the TSA straddles them, with per-row inventory shares for the WS4 split;
the TSA08/16/40/41 compiled-matrix and full-landscape schedules are WS4 evidence, not a FEMIC carbon-engine claim; and
GCBM bridge runs check format and readiness only. They do not establish numerical equality with libcbm.
Boundaries
FEMIC does not run a carbon engine for every WS4 schedule.
FEMIC does not own the WS4 treatment transition or the optimizer ledger.
The HWP config is a public scenario input, not a calibrated parameter estimate.
GCBM is not a runtime dependency and is not a parity target.
CBM4 is unreleased; the package/SIT boundary is the migration seam.