Problem and contributor
The outside issue and BTG contributor remain attributable instead of being reduced to an anonymous code artifact.
The accepted contribution ledger records real events outside BTG through exact contributor/change-set provenance, review, CI, upstream merge, licence context and economic state. Vector and Memnox are accepted examples. AWS #934 / PR #935 is an active contribution that remains below acceptance while maintainer-controlled gates are incomplete. These states are intentionally not collapsed.
The outside issue and BTG contributor remain attributable instead of being reduced to an anonymous code artifact.
Commits, tests, reviews, CI/security and accepted upstream state provide evidence that a specific contribution was independently adopted.
A contribution can be pro bono, contingent, funded or settled. Upstream merge does not automatically become a payment or monetary valuation.
ENTITY's exchange/recovery layers implement the state required for venues, rights-based instruments, balances, listings, disclosures, order books, call auctions, RFQs/quotes/acceptances, trades, clearing, entitlements, usage, surveillance, cancellations, revenue rules/rule sets, trade-revenue bindings, authorized settlement verifiers and payment attestations.
CONTRIBUTION is an implemented Exchange Protocol instrument class. If valid rights and terms exist, a contribution history can later be referenced by a rights instrument, contract, service or participation policy.
Later commercial terms bind to the accepted lineage; they do not retroactively turn an open-source merge into proprietary ownership or pretend a payment existed before settlement evidence.
The cards below are rendered from machine-readable ENTITY contribution evidence and current upstream state. Both accepted cases are pro bono and correctly report zero realized cash/no payment settlement.
Loading the machine-readable contribution ledger…
The BTG pull request remains open. The reviewer-requested correction restored execution/ARN-scoped synthetic-root IDs and added a two-provider collision regression requiring unique (traceId, spanId) identities while retaining the shared trace ID.
The contribution is not represented as UPSTREAM_ACCEPTED_RECORDED. Maintainer-controlled Build and OTel Conformance workflows remain action_required, so acceptance and settlement remain unclaimed.
contributions.json is reserved for published ENTITY evidence records. Adding an active PR there as accepted evidence would blur the distinction this site is designed to preserve.| State | What it means |
|---|---|
PREPARED / VALIDATED_DIFF / COMMIT_PUSH / UPSTREAM_PR | Engineering/provenance stages before upstream acceptance. |
UPSTREAM_ACCEPTED_RECORDED | Upstream acceptance/merge has been captured into ENTITY evidence. |
| Instrument/listing/order/trade | Separate market states only when a valid instrument and market workflow actually exist. |
| Clearing/obligation | Economic amount and counterparties can be established without claiming external payment. |
Payment attestation / SETTLED | Separate verifier/evidence state required before settlement is claimed. |
Economic attribution is evidence-bound and acyclic. A market observation is not automatically accounting fair value, and protocol records do not determine legal entitlement by themselves.