Blackmore Technology Group · public GitHub activity
NEWS
The Blackmore Technology GitHub footprint ledger.
A factual record of public releases, ENTITY fixes, public repository work, upstream fixes, forks, contribution activity and ENTITY-ingested evidence. This is not a marketing blog: GitHub and ENTITY evidence are the source of status.
History model: current repository, release and pull-request state is refreshed from GitHub on every sync. Public activity already observed by the automated ledger is retained from the first NEWS sync forward so older events do not disappear when GitHub's recent-events window rolls forward.
Chronological engineering activity
What changed across the Blackmore GitHub footprint.
Filter the ledger without changing the underlying source record.
Loading GitHub activity…
Releases
Published releases across the public Blackmore repository footprint.
Release records come from GitHub release state, not editorial announcements. Historical releases that GitHub exposes remain source-linked here.
Loading release records…
External engineering
Fixes and contributions outside Blackmore-owned repositories.
These entries track BTG-authored upstream pull requests separately from ENTITY ingestion, upstream merge state and economic settlement.
Loading upstream contribution state…
ENTITY evidence
External work that has been recorded through ENTITY.
An ENTITY evidence record means lineage/evidence state was recorded. It does not automatically mean payment, ownership transfer, independent certification or upstream acceptance unless the record explicitly says so.
Loading ENTITY evidence…
Complete public repository footprint
Owned repositories and forks.
Every public repository returned for the Blackmore Technology GitHub account is listed here. Forks show their upstream parent when GitHub provides it.
Loading repository inventory…
Status discipline: public GitHub activity is not automatically ENTITY evidence; ENTITY evidence is not automatically external validation; upstream merge is not payment; a fork does not imply ownership of upstream code; repository custody does not override upstream licensing.