Skip to content
HEY Research Lab
Menu

noren

AI Agents

Is this your project? Claim it →

An operating layer that agents can be held to. Signed grants, hash-chained audit, isolated code execution, x402 payments on Robinhood Chain.

What HEY knows

Development

Shipped this weekShipping: 2 counted ships in 30 days; latest ship yesterday. Evidence Source

Build Momentum 38How it is measured

Latest: Mizuki escrow f1af3600fbd6ce79381c1a11f5a8b2013d35e19f

Token

No token tracked
FollowCreate alertTerminal preview
Get updates

Get updates

Follow puts noren on your private watchlist; its changes then lead “Since you were last here” when you come back. Following needs an account; browsing never does.

Sign in to follow noren

No account? Email me noren’s changes

No account and no password. HEY stores the address and what you asked for, sends one confirmation, and nothing else until you confirm. Every email has a one-click unsubscribe that deletes the address.

Or read its RSS feed.

View latest ship
Share
More detail
Not yet known
Unknown3 gaps: Official docs (not tied to the project yet), API description (not enough yet), Official site changes (not enough yet). HEY found a docs link on its website and holds it as context: nothing yet ties it to the project.
Compare with…The same summary, with every line’s evidence: snapshot API
What HEY checked — why it says this
Shipping.
“Shipping” by the activity rule: 2 counted ships in the last 30 days, the newest 2026-10-29.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsMizuki escrow f1af3600fbd6ce79381c1a11f5a8b2013d35e19fCode changes this week (since Mon 26 Oct) · 1 commitWhat HEY derivedHEY’s activity rule reads the counted events as “Shipping”.Not concludedIt says what HEY can read of the building, not how good the project is, who is behind it, or what its token will do. Quiet or unknown is not "abandoned".
Verified Builder.
The quality gate found verified building evidence from the project's own sources.
Source3 registered sources, 0 of them context only.ReadRecordsMizuki escrow f1af3600fbd6ce79381c1a11f5a8b2013d35e19fCode changes this week (since Mon 26 Oct) · 1 commitsource:c645f2c5-d4ba-4efb-9e8b-20bf42d1e321+1 moreWhat HEY derivedThe quality gate’s stored decision: “Verified Builder”.Not concludedA verified builder is one whose shipping HEY confirmed from public evidence. It does not say who runs the project — that is the ownership claim, a separate check.
Research coverage: HEY can answer 7 of the 10 research questions that apply.
7 of 10 applicable dimensions measured.

Identity

  • IdentityMeasuredRead 2h ago.

Building

  • Building activityMeasuredRead 55m ago.
  • RepositoriesMeasured
  • ReleasesMeasuredRead 8h ago.
  • TimelineMeasured

Official site

  • Official docsNot tied to the project yetHEY found a docs link on its website and holds it as context: nothing yet ties it to the project.
  • API descriptionNot enough yetHEY has not read its website’s published files yet.
  • Official site changesNot enough yetHEY has no first reading of its website to compare against yet.

Code and packages

  • Repository detailsMeasuredRead 1h ago.
  • Published packagesMeasuredRead 1h ago.

Not applicable here: Package advisories, Contract creation, Contract activity, Verified source, Contract interface, Current market, Market history, Supply distribution, Locks, Market checks, Protocol economics.

A count of what HEY has read, never a score: projects are not compared or ordered by it. Unknown is never zero. The same states: coverage API.

Market figures are context only and never change activity status. Methodology
LinksWebsite (opens in a new tab)GitHub (opens in a new tab)X (opens in a new tab)Sources

Latest ship

Checked

Mizuki escrow f1af3600fbd6ce79381c1a11f5a8b2013d35e19f

GitHub releaseSource-backed

Why it matters: The first release HEY has recorded for this project.

Hosted SBPFv2 escrow build evidence for protected-main commit f1af3600fbd6ce79381c1a11f5a8b2013d35e19f.

Record ship:9523e7a4… · HEY counts it as building; it does not judge the release’s quality.

Release, read from the team’s GitHub · no deployment linked
What it names
The team’s release names it: “Mizuki escrow f1af3600fbd6ce79381c1a11f5a8b2013d35e19f” (mizuki-escrow-f1af3600fbd6ce79381c1a11f5a8b2013d35e19f).
Stage
A release is code the team published; HEY has not observed it deployed unless a link below says so.
Reported by
Read from the team’s GitHub. Reported in the team’s own source. No independent record HEY holds corroborates it.
Release and deployment
Not established: the text HEY holds names none of the project’s contracts. Timing alone never links a release to a deployment.
Activity
No contract is tied to this change, so no product activity is attributed to it. Product usage is read on its own.
When
The source dates it 2026-10-29 18:22 UTC; HEY first knew on 2026-10-30.
Not known
  • HEY does not hold the commit the release was cut from.
  • HEY has not observed a deployment of this change.
  • Not established: the text HEY holds names none of the project’s contracts. Timing alone never links a release to a deployment.

Evidence: ship record

A ship says what was shipped and where HEY read it. It is not a judgement of quality, of the team, or of what the token will do.

View evidence ↗ (opens in a new tab)Post this ship on X

Shared change · Published

noren was published on HEY with its sources recorded.

Builder status: Shipping.

Observed by HEY on 2026-10-30Source: HEY’s research record

Evidence receipt

Builder activity

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: 11 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.

  1. Code changes this week (since Mon 26 Oct) · 1 commit

    Code activitySource-backed

    What changed, in the repository’s own words:

    1 active day in norenagent/noren.

    How HEY read this week

    This week HEY looked inside 1 commit to see what changed: 1 changed code.

    View evidence: Code changes this week (since Mon 26 Oct) · 1 commit (opens in a new tab)

Other changes on HEY’s record

4 changes on HEY’s record for noren: 1 release · 1 new Verified Builder or owner proof · 1 new project on HEY · 1 week of code pushed.

All 4 changes for noren →

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)

Questions HEY can answer about noren — as of 30 Oct

Show the answers
Is noren still being built?
DerivedShipping: 2 counted ships in 30 days; latest ship yesterday. Evidence
What did noren ship last?
FactMizuki escrow f1af3600fbd6ce79381c1a11f5a8b2013d35e19f — GitHub release, yesterday. Evidence
What does HEY not know about noren?
Unknown3 gaps: Official docs (not tied to the project yet), API description (not enough yet), Official site changes (not enough yet). HEY found a docs link on its website and holds it as context: nothing yet ties it to the project.

Sources

3 places HEY reads for noren