Skip to content
Menu

Oriel

Is this your project? Claim it →

Oriel is an AI workspace on Robinhood Chain. Describe a site, design or document in chat; Oriel builds it, hosts it on its own subdomain, and keeps improving it with you.

What HEY knows

Building
Shipped this weekShipping: 1 counted ship in 30 days; latest ship yesterday. Evidence Source

Build Momentum 25How it is measured

Latest
Code changes this week (since Mon 26 Oct) · 53 commits
FollowCreate alertTerminal previewView latest ship
Share

Follow puts Oriel 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 Oriel’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
Unknown1 gap: API description (no source). Its website links no API description.
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: 1 counted ship in the last 30 days, the newest 2026-10-28.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsCode changes this week (since Mon 26 Oct) · 53 commitsWhat 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.
Source5 registered sources, 0 of them context only.ReadRecordsCode changes this week (since Mon 26 Oct) · 53 commitssource:45d9883f-9980-44cb-b8be-6fb411c0c2f2source:dcd3b242-e3e9-48b9-a996-fff6f3561159+2 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 9 of the 10 research questions that apply.
9 of 10 applicable dimensions measured.

Identity

  • IdentityMeasuredRead 4h ago.

Building

  • Building activityMeasuredRead 6m ago.
  • RepositoriesMeasured
  • ReleasesMeasured
  • TimelineMeasured

Official site

  • Official docsMeasuredRead 4h ago.
  • API descriptionNo sourceIts website links no API description.
  • Official site changesMeasuredRead 3h ago.

Code and packages

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

Code changes this week (since Mon 26 Oct) · 53 commits

Code activitySource-backed

Why it matters: The first week of code changes HEY has recorded for this project.

What changed, in the repository’s own words:

1 active day in buildoriel/oriel.

This week HEY looked inside 3 of 53 commits to see what changed: 3 changed code. In a burst week, enough of a sample has to change code for the week to count.

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

Code changes, read from the team’s GitHub · not a deployment
What it names
3 of 3 commits HEY read changed code. A week of code names no capability.
Stage
Code changes are not a deployment: HEY has not observed a release or a deployment of this code.
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 a release or a deployment: code is not 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 to the week of 2026-10-28; HEY first knew on 2026-10-29.
Not known
  • No source HEY holds names what this change does.
  • HEY has not observed a deployment of this change.

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)

Shared change · Published

Oriel was published on HEY with its sources recorded.

Builder status: Shipping.

Observed by HEY on 2026-10-29Source: 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

  1. What’s new

    AnnouncementSource-backed

    New features and improvements to Oriel. October 28, 2026

    View evidence: What’s new (opens in a new tab)

Other changes on HEY’s record

4 changes on HEY’s record for Oriel: 1 verification change · 1 new project on HEY · 1 other ship · 1 week of code pushed.

All 4 changes for Oriel →

Questions HEY can answer about Oriel — as of 29 Oct

Show the answers
Is Oriel still being built?
DerivedShipping: 1 counted ship in 30 days; latest ship yesterday. Evidence
What did Oriel ship last?
FactCode changes this week (since Mon 26 Oct) · 53 commits — Code activity, yesterday. Evidence
What does HEY not know about Oriel?
Unknown1 gap: API description (no source). Its website links no API description.

Sources

5 places HEY reads for Oriel