Activity
Stars and mentions · Last 30 days, Oct 6 – Nov 4
Top repositories
iii-hq’s repositories ranked by pull request authors, as on trending.
Contributes to
Repositories outside iii-hq’s account where iii-hq opened or reviewed pull requests in the past 365 days.
Who noticed iii-hq
Everyone who starred or forked iii-hq’s repositories since the archive began in 2011.
Notable accounts
Ordered by the stars their own repositories have received.
Biggest fans
Accounts that starred the most of these repositories.
Breakout weeks
Each repository’s best week of new stars, with the release published around it.
Achievements
Awards earned by the repositories iii-hq owns. Select an award to embed its badge.
No awards yet
Repositories earn awards by reaching the top three in a completed trending day or week.
A repository earns an award for finishing first, second or third in a completed trending day or week, ranked by new stars, new forks or pull request authors. Awards follow a repository through renames and transfers and count toward its current owner. Weeks run Monday to Sunday, UTC.
Mentions
@RyanEls4 Not really. Yesterday I got deep in weeds and hand rolled this iii#2393 It would have taken longer to PRD and engineer a harness around Opus as it had some tricky lifetime/trait changes. I’ve also stopped my Claude subs. as I don’t need it for the upcoming weeks
iii puts observability on the same surface as composition. Workers register with an engine, join a live catalog, and the same system exposes traces, logs, queues, and state in one console. The point is the shared runtime surface. #SystemsLiteracy #Observability