THE LONG HOWL / BUILDING IN PUBLIC
WORK LEAVES
A TRACE.
Alpha Husky didn't appear overnight. Follow the actual record: code merged in public, dated notes preserved, and milestones you can investigate yourself.
NO FABRICATED STREAKSSOURCES BEFORE CLAIMSCODE ≠ LIVE VERIFICATION
01 / THE BIGGER PICTURE
Consistency beyond the PRs.
The public developer profile tells a much bigger story than a list of merged pull requests. These figures were observed in the founder's GitHub contribution calendars on 4 November 2026.
Account-wide GitHub contributions may include commits, pull requests, reviews, issues and private activity, depending on GitHub settings. They are not an independently audited Alpha Husky-only count, and cannot be added to the PR or devlog totals below. Both numbers are dated screenshots, not continuously refreshed data.
02 / PROJECT CODE ACTIVITY
The commits behind the years.
This is the Alpha Husky project-only Git record, reconstructed from all five accessible repositories. Every square represents real Git activity attributed to the founder, not just merged PRs. No invented activity, no artificial streak.
Loading audited commit history…
Full development history
No main-branch authored commitPublic activityPublic + private / private only
Select an active day for public commit receipts.
Historical snapshot through . Public commits are globally deduplicated by SHA; private activity is represented only by daily counts. This measures founder-authored commits reachable from each repository's main branch, using UTC author dates; it is not an all-branch or local/VPS activity audit. Some additional work may not be represented. GitHub profile contributions above are a different measure and must not be added to these totals.
03 / THE PUBLIC SOURCE RECORD
Public PRs and devlogs.
This is a selective evidence index, not a complete history of daily work. It only counts merged PRs in two public repositories and dated notes in the preserved archive. Ordinary commits and private backend work are not counted here.
Loading source-backed activity…
Selective public evidence timeline
Merged PRArchived noteBothNone documented
Select a documented day to inspect its sources.
This calendar is a historical snapshot, not a live GitHub counter. Merges may include automation or collaborative contributions. Archived notes are contemporaneous reports, not independent proof of each claimed feature. No daily work or author attribution is inferred from these signals.
04 / HOW THE GAME EVOLVED
Not just green squares.
Follow the project from preserved early accounts to later public code history. We are not presenting invented before/after screenshots; visual comparisons require authentic, dated captures.
Visual evidence archive
Eight original Telegram WebApp screenshots supplied by the founder. The capture dates are unverified; these are comparisons of interface states, not a dated release timeline.
05 / MILESTONES WITH RECEIPTS
Show the source.
Milestones are labelled by what the evidence actually proves. A historical devlog isn't a production test; a merged PR isn't a player-session test.
06 / HOW TO READ THIS
Evidence, not a performance.
The secondary selective calendar above counts merged pull requests across the public game repository and official website repository. It does not count all commits, private backend work, unmerged branches, design sessions or code authored by a particular person. The archive series counts dated entries in the preserved Build History, not the individual tasks within them. Missing days are unknown, not idle.
Evidence snapshot: . Future entries require a new reproducible source audit. See the review-gated Build Log for curated public updates. The separate GitHub profile figures are account-wide snapshots provided by the founder, not repository-specific totals. No telemetry, wallet data or private tester information is published here.