Description
Sum one supplied inventory record under an explicit system boundary.
A farm or garden budget depends on a common area, quantity, observation period, and system boundary. Recovery, exclusions, overlap, and allocation change how a share is calculated. Supplied accounting or geometry terms remain separate from measured crop performance and verified environmental outcomes.
Sum one supplied inventory record under an explicit system boundary.
When to use this tool
Use Farm Life Cycle Boundary One Input when you need a clearly bounded area, material, resource, energy, or allocation term for supplied garden or farm records.
How to use the tool and how it works
- Enter inputId, includedIds, upstream, onFarm, downstream, includeUpstream, includeDownstream. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read included, contribution. Inspect included before interpreting the associated values.
Test inputId membership in includedIds. Return contribution as zero when absent, otherwise onFarm plus upstream and downstream only under their respective inclusion flags.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| inputId | Input Id | Required. Text; maximum UTF-16 length 8192. |
| includedIds | Included Ids | Required. Array of text; maximum UTF-16 length 8192; maximum items 256. |
| upstream | Upstream | Required. Finite number. |
| onFarm | On Farm | Required. Finite number. |
| downstream | Downstream | Required. Finite number. |
| includeUpstream | Include Upstream | Required. Boolean. |
| includeDownstream | Include Downstream | Required. Boolean. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| included | Included | Required. Boolean. |
| contribution | One term under the stated formula, not necessarily a complete statistic. | Required. Finite number. |
{
"input": {
"inputId": "fuel",
"includedIds": [
"fuel"
],
"upstream": 20,
"onFarm": 50,
"downstream": 10,
"includeUpstream": true,
"includeDownstream": false
},
"output": {
"included": true,
"contribution": 70
}
}Limitations and assumptions
- Quantities can be signed and require one common impact unit. Boundaries are caller choices; this is one inventory term, not a complete life-cycle assessment or environmental claim verification.
- The field tables state structural bounds; the mechanics also specify cross-field constraints. Malformed inputs and unsupported domains cause errors. A successful false flag, empty branch value, or zero placeholder has the meaning stated above and is distinct from an input error.
- Numeric calculations use binary floating point unless exact decimal-integer arithmetic is explicitly stated. No hidden measurement tolerance or decimal rounding is added; nonfinite or out-of-contract results are rejected. Signed zero is exported as zero.
Alternative or Complementary methods
Verify the system boundary, units, and source records before combining this term into a resource or environmental report. Physical design and crop-performance questions require appropriate measurements and a broader model.
References
Similar or alternative tools
- Farm Energy Boundary Term
Sum supplied energy ledger terms under explicit boundaries and signed flow conventions.
- Emission Boundary Exclusion Token
Sum supplied signed emission quantities under explicit category exclusions without choosing an accounting standard.