FAQ: BOLD Carbon and BOLD Recycling

This FAQ brings together questions about BOLD Carbon (CH₄) and BOLD Recycling. It covers material eligibility, MassID validation, and transport and weighing records, including a Waste Transport Manifest (MTR, Manifesto de Transporte de Resíduos) with multiple materials.

The answers describe application version 1.0.0; they do not confirm which revision is deployed.

How do I check whether a material is accepted?

Check the material against the application you will use, not just the MTR or its stated destination:

1. Read the Carbon eligibility criteria or Recycling eligibility criteria, then the corresponding Carbon integration guide or Recycling integration guide.
2. Choose a supported document type and subtype from Waste Classification. Do not relabel an unsupported material as a supported organic subtype.
3. For Brazil, check the supported waste-code table, documented under Carbon and used by the shared regional classification processor in both current applications. The local code, its description, and the subtype's CDM mapping must agree; being in the official IBAMA list is not enough.

A manifest can list both eligible and ineligible materials. Assess each line independently. A material missing from the supported table does not pass the current regional classification rule, even if its transport or treatment is documented. The code table and methodology criteria are maintained in their canonical pages rather than repeated here.

Which validation rules do Carbon and Recycling share?

Both applications configure the same MassID qualification, regional classification, uniqueness, manifest, and weighing processors. Recycling does not automatically accept every material merely because it is recycled.

Their conflict checks target GasID for Carbon and RecycledID for Recycling, plus related credit documents and passed or in-progress audits for the same methodology. Carbon also configures emission calculation. These checks concern related certificates, credits, and audits; they are not a manifest-wide allocation or double-counting guarantee.

Can two MassIDs reference the same MTR?

The shared rules do not make the MTR number a unique key across MassIDs. More than one MassID can reference the same manifest, but that alone does not establish eligibility or prevent duplicate accounting.

Each MassID has one type, one subtype, and its own mass in kilograms. Represent a separately identified material with its corresponding classification and supported mass; do not assign the full mixed load to each material. A zero-quantity or excluded manifest line is not a positive mass eligible for these rules.

The current qualification rule in both applications accepts only type: Organic, supported organic subtypes, and a positive currentValue in kg. The broader material classes accepted by the API do not establish eligibility under these applications. In Brazil, the regional classification rule also checks the local code and description against its supported table and the MassID subtype's CDM mapping. A listed material or a composting destination does not by itself satisfy those checks.

Does a different IBAMA code guarantee a distinct MassID?

No. A material description, a local waste code, the MassID type, and its subtype are different fields. See Waste Classification.

The integrator's credentials select the test or production environment. Duplicate checks apply within that environment; changing credentials for the same environment does not make matching MassIDs distinct.

The duplicate query compares:

• category, type, subtype, and currentValue;
• waste generator and recycler participant IDs;
• pickup and drop-off address IDs and timestamps;
• the pickup vehicle plate, ignoring case, spaces, and hyphens.

It searches both current and legacy document formats. More than one non-cancelled matching document fails the rule; cancelled matches do not cause that failure. The query does not include the MTR number, local waste code, local description, or a manifest line sequence. Different supported subtypes produce different duplicate queries; different local codes with the same subtype and the other matching fields can still collide. Changing a weight or timestamp merely to avoid a match would not substantiate a separate mass.

This is a comparison of document and movement fields, not a universal check that every MTR or physical load has been used only once. Participant IDs and address IDs scope the comparison; it is not keyed only by a participant, facility name, or document number. measurementUnit is not in the duplicate query, although qualification requires kg.

How do I identify different waste materials on the same MTR?

Keep the official MTR number as the document number. In the supporting records, associate each material with its classification, supported mass, and corresponding manifest entry. A line sequence, for example, can help organize those records; it is not a substitute for the official MTR number.

Use the local waste code and description consistently with the material's classification and the manifest. These fields help identify the material, but neither the local code nor the MTR number is a MassID duplicate key.

Does the system check the mass of each MTR line?

The attachment check can flag inconsistencies between the manifest and weighing evidence. It does not establish a complete line-by-line reconciliation: it neither allocates a mixed load among MassIDs nor reconciles their combined masses against the MTR. Passing the check is not proof that each item was validated or that different MassIDs refer to different manifest entries.

For each material, report only the mass supported by the evidence and keep the link between its manifest entry and weighing records. Check all MassIDs associated with the shipment against the actual load so that the same mass is not counted more than once. If a scale ticket covers a mixed load, retain it together with the evidence supporting each material's mass.

Should I recalculate gross weight or tare for each material?

Use the weighing records captured during the operation and the mass supported for each material by the available documentation. A shared truck weighing records the combined load. If the ticket has 1,000 kg gross and 200 kg tare, and the materials weigh 300 kg and 500 kg, the ticket establishes 800 kg for the load. Repeating its full net weight in both MassIDs would count the load twice.

The current weighing processor evaluates events within one MassID. Where gross weight, tare, container quantity, and event value are available, its calculation is:

net event value = gross weight − (tare × container quantity)

The tolerance is 0.1 kg. There is no implemented formula here for distributing a shared truck gross weight or tare between materials or for checking the sum across MassIDs.

Preserve the original ticket and the material-level evidence. If only a combined weighing is available, confirm the supported submission representation with the Network Integrator before sending derived gross/tare values. The inspected rules do not establish a supported allocation procedure.

Where can I inspect the rule implementation?

You can inspect the rules in the public methodology-rules repository. The code published there does not by itself confirm which revision is deployed in your environment.