Open Source · evidence archive

Open-source evidence

Source-linked records distinguish repositories I own, projects I maintain for others, organizations I created, and merged work in upstream projects.

Forks are working copies, not authorship. They appear only when merged upstream work is documented. See Work for project descriptions.

Reading key

Records are grouped by relationship. Read exact subjects, roles, and source links in the ledger below.

  • Ownedrepositories I created and own
  • Maintainedprojects I lead inside organizations I do not own (vlang)
  • OrganizationGitHub organizations I created for project families
  • Upstreammerged pull requests to projects run by other people

Source-backed records · select a lane to trace its evidence

Trace ready · select a lane to follow its evidence.

Evidence refreshed · exact records follow below.

Primary record

Evidence ledger

Roles and merged work from the evidence cache, with a provenance link on every row.

Kind → subject → evidence → source

Owned project

6 records

Maintained project

3 records

Organization work

2 records
  • Create-Node-App / Create-Python-App / Create-Vlang-AppOrganization maintainerReviewed evidence ↗
  • HorneroOSOrganization creator — composition, shell, config, CLI, greeter, installer, docs, websiteReviewed evidence ↗

External contribution

2 records
  • vlang/vMerged authored PRs on vlang/v (search link — not a vanity count)Reviewed evidence ↗
  • alphacrack/readme2demo10 merged authored pull requests to an upstream project (the ulises-jeremias fork is a working copy, not authored work)Reviewed evidence ↗

Notes

  • Committed cache from verified editorial evidence. Run `pnpm data:refresh` with GITHUB_TOKEN (optional) to re-verify public repo existence. Volatile counts omitted until refresh succeeds.