Skip to content
Menu

enro

AI Agents

Is this your project? Claim and verify →

Execution layer for robotics and AI operators on Robinhood Chain

What HEY knows

Building
Dormant: no ship for 76 daysDormant: 0 meaningful events in 30 days; latest ship on 2026-08-03. Evidence Source

Build Momentum 0How it is measured

Latest ship
v0.2.0 · · GitHub release

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

FollowCreate alertTerminal previewView latest ship
Share

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

No account? Email me enro’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.

Token market · context
No token tracked
Not yet known
Unknown2 gaps: Official docs (no source), API description (no source). HEY read its website and found no link to docs.

HEY can answer 8 of the 10 research questions that apply · Research coverage

Compare with…The same summary, with every line’s evidence: snapshot API
What HEY checked — why it says this
Dormant.
“Dormant” by the activity rule: 0 meaningful events in the last 30 days, the newest 2026-08-03.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsv0.2.0What HEY derivedHEY’s activity rule reads the counted events as “Dormant”.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.
Source2 registered sources, 0 of them context only.ReadRecordsv0.2.0source:d6ca2696-edd2-4cb2-8747-5c2478e3ad34What 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.
Market figures are context only and never change activity status. Methodology
LinksWebsiteGitHubSources

Latest ship

Checked

v0.2.0

GitHub releaseSource verified

v0.2.0 · Machine pool with bounded concurrency · GPU provider implementation · Graceful shutdown, rate limiter, metrics endpoint · Structured tracing with env-filter · Multi-OS CI matrix Show all
  • v0.2.0
  • Machine pool with bounded concurrency
  • GPU provider implementation
  • Graceful shutdown, rate limiter, metrics endpoint
  • Structured tracing with env-filter
  • Multi-OS CI matrix

Record ship:5c79fd6b… · HEY counts it as building; it does not judge the release’s quality or what it means for the token.

View evidence ↗Post this ship on X

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: 4 weeks before HEY began reading this project’s sources — not yet read, not zero.

Questions HEY can answer about enro — as of 2026-10-18

Is enro still being built?
DerivedDormant: 0 meaningful events in 30 days; latest ship on 2026-08-03. Evidence
What did enro ship last?
Factv0.2.0 — GitHub release, on 2026-08-03. Evidence
What does HEY not know about enro?
Unknown2 gaps: Official docs (no source), API description (no source). HEY read its website and found no link to docs. Details

Build timeline

  1. v0.1.0

    GitHub releaseSource verified

    Initial Release · Core runtime with config and error types · VM crate with provider trait, machine abstraction, snapshots · Operator crate with vision pipeline, action executor, policy engine · API server and CLI · CI workflow, Docker, docs, examples Show all
    • Initial Release
    • Core runtime with config and error types
    • VM crate with provider trait, machine abstraction, snapshots
    • Operator crate with vision pipeline, action executor, policy engine
    • API server and CLI
    • CI workflow, Docker, docs, examples
    View evidence

  2. Code changes, week of 2026-07-27 – 2026-08-02 · 5 commits

    Code activitySource linked

    5 active days in enrorobotics/enro.

    Documentation or maintenance only — not counted as building. This week HEY looked inside 5 commits to see what changed: 5 documentation or maintenance only.

    View evidence

Research notes

Written by HEY researchers and reviewed before publishing. Commentary with sources — not the project's own claims, and not evidence of shipping.

Know something about enro? Sign in with GitHub to submit a research note. Notes are reviewed before they appear here.

What changed

3 changes on HEY’s record for enro: 2 releases · 1 week of code pushed.

All 3 changes for enro →

The full change record holds 2 more, of kinds this list leaves out — lock records and HEY’s own research bookkeeping among them. Full record (JSON)

Research coverage

HEY can answer 8 of the 10 research questions that apply.

8 of 10 applicable dimensions measuredShow each dimension

Identity

  • IdentityMeasuredRead 1mo ago.

Building

  • Building activityMeasuredRead 1d ago.
  • RepositoriesMeasured
  • ReleasesMeasuredRead 2mo ago.
  • TimelineMeasured

Official site

  • Official docsNo sourceHEY read its website and found no link to docs.
  • API descriptionNo sourceIts website links no API description.
  • Official site changesMeasuredRead 18h ago.

Code and packages

  • Repository detailsMeasuredRead 2h ago.
  • Published packagesMeasuredRead 2h 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.

Sources