Skip to content
Menu

RunTimeAdmin

AI Agents

Is this your project? Claim and verify →

On-chain identity, reputation, and staking for autonomous AI agents. Live on Robinhood Chain testnet (46630). W3C DIDs + Ed25519 PKI + CSIG cryptoeconomics.

What HEY knows

Building
Quiet for 40 daysQuiet: 0 meaningful events in 30 days; latest ship 40 days ago. Evidence Source

Build Momentum 18How it is measured

Latest ship
Code changes, week of 2026-09-07 – 2026-09-13 · at least 2 commits · · Code activity

Why it matters: First week of code changes after 47 quiet days.

FollowCreate alertTerminal previewView latest ship
Share

Follow puts RunTimeAdmin 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 RunTimeAdmin’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 (not tied to the project yet), API description (no source). HEY found a docs link on its website and holds it as context: nothing yet ties it to the project.

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
Quiet.
“Quiet” by the activity rule: 0 meaningful events in the last 30 days, the newest 2026-09-08.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsCode changes, week of 2026-09-07 – 2026-09-13 · at least 2 commitsCode changes, week of 2026-07-20 – 2026-07-26 · at least 8 commitsWhat HEY derivedHEY’s activity rule reads the counted events as “Quiet”.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.
Source4 registered sources, 0 of them context only.ReadRecordsCode changes, week of 2026-09-07 – 2026-09-13 · at least 2 commitsCode changes, week of 2026-07-20 – 2026-07-26 · at least 8 commitssource:2ef47edd-fb0d-4d80-a8e0-dfcb23a1f6cd+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.
Market figures are context only and never change activity status. Methodology
LinksWebsiteGitHubSources

Latest ship

Checked

Code changes, week of 2026-09-07 – 2026-09-13 · at least 2 commitsruntimeadmin/countersig-network

Code activitySource linked

9 active days in RunTimeAdmin/countersig-network.

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

View evidence ↗

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

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

Is RunTimeAdmin still being built?
DerivedQuiet: 0 meaningful events in 30 days; latest ship 40 days ago. Evidence
What did RunTimeAdmin ship last?
FactCode changes, week of 2026-09-07 – 2026-09-13 · at least 2 commits — Code activity, 40 days ago. Evidence
What does HEY not know about RunTimeAdmin?
Unknown2 gaps: Official docs (not tied to the project yet), API description (no source). HEY found a docs link on its website and holds it as context: nothing yet ties it to the project. Details

Build timeline

  1. Code changes, week of 2026-07-20 – 2026-07-26 · at least 8 commitsruntimeadmin/detent.systems

    Code activitySource linked

    What changed, in the repository’s own words:

    1 active day in RunTimeAdmin/detent.systems.

    This week HEY looked inside 2 of 8 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.

    View evidence

  2. Code changes, week of 2026-07-20 – 2026-07-26runtimeadmin/countersig-network

    Code activitySource linked

    8 active days in RunTimeAdmin/countersig-network.

    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 RunTimeAdmin? 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 RunTimeAdmin: 3 weeks of code pushed.

RunTimeAdmin on What changed →

The full change record holds 5 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 15h ago.
  • RepositoriesMeasured
  • ReleasesMeasured
  • 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 descriptionNo sourceIts website links no API description.
  • Official site changesMeasuredRead 21h ago.

Code and packages

  • Repository detailsMeasuredRead 6d ago.
  • Published packagesMeasuredRead 6d 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