Carry Forward Ledger
Carry Forward Ledger
A ledger for claims that cross a company boundary. Each claim is re-examined when it is received, not passed along on trust. Available as three separate tools: Automotive, Aerospace, and Software (SBOM).
See the editions- Supplier
- Claim ARe-evaluated on receipt
- Integrator
- Claim BRe-evaluated on receipt
- Customer
A violation in Claim A is inherited by Claim B, and by every claim after it.
- Allow
- Restrict
- Escalate
- Block
What it does
A claim is a statement one organization makes to another about an artifact, such as a part, a software component, or a vulnerability. The ledger governs what happens to that claim after it changes hands.
Re-evaluates every claim
A claim records who issued it, who received it, what it says about which artifact, and the evidence behind it. The ledger checks it against the rules of its edition and returns Allow, Restrict, Escalate, or Block, listing the conditions that produced the result. The verdict is recomputed whenever the claim’s inputs change.
Carries violations downstream
Each claim can point to the claims it was built on. When a claim upstream violates the rules, every claim that follows inherits that violation, however many hops away.
Does not take trust on faith
A claim can declare a high level of trust, such as vendor-verified or approved by an authority. If the receiving organization hasn’t recorded how the claim maps to its own artifact, the ledger lowers it to the self-attested level.
Keeps the history
Every claim keeps its lifecycle history. If someone overrides a verdict, the override is recorded next to the computed verdict instead of replacing it, and a chain viewer follows any claim back through the claims behind it.
Works with the files you have
Import claims from JSON or CSV files and export a ledger as JSON or CSV. Each edition runs as a single file in your browser, and nothing you enter is sent to Governed Intelligence or anyone else.
Three editions, three tools
Each edition is its own tool, with the trust levels, severity scale, and artifact details of its industry. Buy the one you work in, or more than one if you work across industries.
Trust levels shown in brass need a recorded mapping on the receiving side, or the claim is lowered to the first level.
Automotive
For OEMs and Tier-N suppliers passing claims about parts and components up and down the supply chain.
- Trust levels, lowest to highest
- Self-Attested
- EGA-Informed
- GI-Verified
- Severity scale
- Low, Medium, High, Critical
- Artifact details it records
- Model year, platform, supplier tier, component, IMDS ID, purchase-order line item, ASN reference
- Changes that require re-evaluation
- Engineering content changed; manufacturing process changed; regulatory basis changed
- Conditions it watches for
- Known dependency drift; an invalidated assumption; an ownership change since the build
Aerospace
For parts traceability, where a claim about a part or its approval has to hold up as the part moves between organizations.
- Trust levels, lowest to highest
- Self-Certified
- DER/ODA-Approved
- FAA/EASA-Issued
- Criticality scale
- Non-Critical, Critical, Flight Safety Critical
- Artifact details it records
- Part number, serial number, form reference, program, component stage, quality-system reference
- Changes that require re-evaluation
- Design change; manufacturing process change; airworthiness directive applicability; means of compliance changed
- Conditions it watches for
- A life-limited part; an airworthiness directive issued; a known quality escape
Software (SBOM)
For software bills of materials and vulnerabilities, where a claim about a component has to be re-examined by each organization that builds on it.
- Trust levels, lowest to highest
- Self-Attested
- Vendor-Verified
- Reproducibly-Built (SLSA L3+)
- Vulnerability severity
- None, Low, Medium, High, Critical
- Artifact details it records
- Package URL, artifact hash, supplier name, build system, SBOM format
- Changes that require re-evaluation
- Build environment changed; dependency tree changed; licensing terms changed; upstream maintainer changed
- Conditions it watches for
- Known upstream abandonment; a license change; known dependency drift
Pricing
Each edition is sold on its own, plus annual maintenance. The Carry Forward Ledger is sold separately from the seven Governance Protocols, with its own checkout.
Automotive
Due now
$2,997
- CFL Automotive
- $2,997
- Annual maintenance
- $600 per year
Aerospace
Due now
$2,997
- CFL Aerospace
- $2,997
- Annual maintenance
- $600 per year
Software (SBOM)
Due now
$2,997
- CFL SBOM
- $2,997
- Annual maintenance
- $600 per year
Prices are in US dollars. The amount due now and the annual maintenance fee are shown separately.
Also looking for the seven Governance Protocols? See the Protocols and their pricing.
