Vector and Memnox were not just patch ingestion
The external-contribution campaign uses real software work outside BTG as evidence-bearing economic events. The important object is not simply “a patch stored in ENTITY”; it is the durable lineage connecting a real problem, contributor, exact change-set, independent review, CI, upstream acceptance, rights context, governed evidence state and any later commercial consequence.
What the campaign proves today
Vector #26501 / PR #26504
Externally originated problem, BTG-authored fix, review/CI evidence and upstream merge were captured into ENTITY as UPSTREAM_ACCEPTED_RECORDED. The contribution is pro bono, with realized cash of USD 0 and no payment settlement claimed.
Memnox #46 / PR #86
Externally originated policy-validation problem, exact BTG changes, maintainer review, requested follow-up, green CI/security and upstream merge were captured into ENTITY as UPSTREAM_ACCEPTED_RECORDED. It is also pro bono with realized cash of USD 0.
Why this is economic lineage
ENTITY’s economic architecture is designed so a contribution does not need an existing bounty or price before its technical history can become economically useful. The accepted event can remain permanently linked to the contributor and evidence; later commercial terms can reference that same history rather than recreating or rewriting it.
| External contribution fact | ENTITY economic meaning |
|---|---|
| Issue / problem | Externally attributable source event and subject of work. |
| Contributor / organization | Persistent actor whose role can be bound to authority, provenance and participation terms. |
| Exact change-set / commit | Evidence-bound contribution object suitable for lineage and reconstruction. |
| Tests / review / CI | Independent or external evidence about the contribution; not ownership or payment. |
| Upstream merge / acceptance | Measurable external consequence proving the work was adopted by the upstream project. |
| Licence / rights context | Controls what may legally/economically be done; ENTITY provenance does not override it. |
| Contribution class / cash state | PRO_BONO, contingent, funded or settled state is represented separately from technical acceptance. |
| Later contract / instrument / usage | Can reference the accepted lineage if valid terms are established. |
| Payment evidence | Moves economic state only when the required settlement evidence exists. |
The larger market fabric around that lineage
The same ENTITY runtime contains the exchange and recovery machinery for venues, rights-based instruments, balances, listings, disclosures, orders/order books, trades, clearing, entitlements, usage, surveillance, RFQs/quotes/acceptances, cancellations, revenue rules, authorized settlement verifiers and payment attestations. Those capabilities are the economic infrastructure into which a contribution lineage may later participate.
Contribution as an instrument class
The Exchange Protocol explicitly supports a CONTRIBUTION instrument class alongside spot licences, subscriptions, compute-to-data, procurement and secondary licences. That means accepted contribution histories can become a first-class input to economic workflows when an issuer with valid authority creates the relevant instrument and terms.
Causal economic graph
ENTITY’s causal-economic graph requires evidence on causal edges and does not equate correlation with causation. Economic observations are explicitly not accounting fair value, and protocol records do not determine legal entitlement by themselves.