Organization-level GitHub configuration for General Liquidity.
profile/README.mdrenders on the organization profile page.scripts/update-profile-readme.mjsregenerates the repository tables (stars, issues, pull requests) between therepositories:startandrepositories:endmarkers. Repository descriptions live in that script..github/workflows/update-readme.ymlruns the generator daily, on demand, and whenever the generator changes.assets/holds the profile banners.
banner.png and banner-dark.png are generated, not drawn. They come from
scripts/make-lockups.ts in the website repository, which sets the wordmark in the same
General Sans file the site serves, so a banner cannot drift from the site header. Copy them
across after regenerating rather than editing them here.
The profile serves them through a <picture> element so GitHub shows the dark cut to
readers in dark mode. gl-header.png is the previous banner, kept only until nothing
references it.
Group order on the profile is priority, not history, and is a deliberate statement. The machine economy API comes first because it is what the company is for. Capital markets follows as one table holding Gordon, SharpeBench and SharpeArena: public and maintained, but no longer the focus.
For the profile to render, this repository must be created on GitHub as
general-liquidity/.github (the special organization configuration repository).
To add or move a repository on the profile, edit the GROUPS array in
scripts/update-profile-readme.mjs and run it locally with a token, or let the workflow
refresh it:
GITHUB_TOKEN=<token> node scripts/update-profile-readme.mjs