Follow puts manda on your private watchlist; its changes then lead “Since you were last here” when you come back. Following needs an account; browsing never does.
“Active” by the activity rule's longer window: 2 counted ships in the last 45 days (the rule needs at least 2); the newest, 2026-09-26, is more than 30 days old.
This week HEY looked inside 1 of 13 commits to see what changed: 1 changed code. One code change is enough for the week to count, so HEY stopped there.
Record ship:4f7dbaf6… · HEY counts it as building; it does not judge the release’s quality.
Bars: meaningful, source-backed ships per week (count). Weeks run Monday to Sunday, UTC, labelled by their Monday. Commits are aggregated, a code week counted once. Hatched: 4 weeks before HEY began reading this project’s sources — not yet read, not zero.
Build timeline
A code week counts as building when a commit HEY looked inside changed code; one is enough, so HEY stops there.
Code changes, week of 2026-10-05 – 2026-10-11 · 1 commit
Code activity · Source-backed
1 active day in nifemi0/manda.
Documentation or maintenance only — not counted as building. This week HEY looked inside 1 commit to see what changed: 1 documentation or maintenance only.
97-second Manda product walkthrough with a real authenticated Arbitrum Sepolia agent payment, confirmed onchain receipt, and an over-limit request blocked before submission. This is testnet evidence; see SUBMISSION.md and submission/evidence in the source repository.
This week HEY looked inside 2 of 14 commits to see what changed: 1 changed code, 1 documentation or maintenance only. One code change is enough for the week to count, so HEY stopped there.
The full change record holds 3 more, of kinds this list leaves out — new locks, unlock reminders and HEY’s own research bookkeeping among them. Full record (JSON)
https://github.com/Nifemi0/bot-chain-crash-labContext onlyContext only because HEY found this repository by its owner alone and nothing the project controls ties it to the project; it counts once a moderator accepts it, or once the project’s verified owner adds it and a GitHub claim names it, it names the token’s contract, it carries a Robinhood Chain dedication HEY matched to this project, or its homepage is the project’s own site (one the owner did not type in).
HEY keeps these on record as context. None counts toward the activity status or Build Momentum; each says why.
Code activityCode changes, week of 2026-10-26 – 2026-11-012026-10-26Recorded, not counted: it was read from a source HEY holds only as context, and that source says why under Sources.
Code activityCode changes, week of 2026-10-19 – 2026-10-252026-10-25Recorded, not counted: it was read from a source HEY holds only as context, and that source says why under Sources.
Questions HEY can answer about manda — as of 5 Nov
Show the answers
Is manda still being built?
DerivedActive: 0 counted ships in 30 days; latest ship 40 days ago.Evidence →
What did manda ship last?
FactCode changes, week of 2026-09-21 – 2026-09-27 · 13 commits — Code activity, 40 days ago.Evidence →
What does HEY not know about manda?
Unknown2 gaps: Official docs (no source), API description (no source). HEY read its website and found no link to docs.