Skip to content
Menu

harness-investigations

AI

HEY verified shipping evidence from the project’s own public sources; ownership of this page is not claimed yet.

A repository for collecting LLM agent challenges, hypotheses / methods, and experimental results. For science!

What HEY knows

Building
Dormant: no ship for 72 daysDerivedDormant: 0 meaningful events in 30 days; latest ship on 2026-07-28. Details Source

Build Momentum 0How it is measured

Latest ship
Code changes, week of 2026-07-27 – 2026-08-02 · · Code activity

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

Latest change
Fact7 days ago: Code changes, week of 2026-09-28 – 2026-10-04. Evidence Source
FollowCreate alertTerminal previewView latest ship
ShareShare on X

Follow puts harness-investigations on your private watchlist and at the top of “Since you were last here” when you come back. Then pick what HEY should notify you about. Following needs an account; browsing never does.

Without an account:RSS
Email me harness-investigations’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.

Token market · context
No token tracked
Not yet known
Unknown3 gaps: Official docs (no source), API description (no source), Official site changes (no source). No official website on record.

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

Compare with…What Terminal access adds →
What HEY checked — why it says this
Dormant.
DORMANT by the activity rule: 0 meaningful events in the last 30 days, the newest 2026-07-28.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsship:f9ffc15a-6d5f-4f43-b7c6-f565c0b0b47eWhat HEY derivedThe activity rule under hbm-v25 gives 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.
Source1 registered source, 0 of them context only.ReadWhat HEY derivedVERIFIED_BUILDER (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
LinksGitHubSources

Latest ship

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

Code activitySource linked

2 active days in shcv/harness-investigations.

What changed, in the repository’s own words:

This week HEY looked inside 1 of 2 commits to see what changed: 1 changed code. One code change is enough for the week to count, so HEY stopped there. 4 automated commits (bot accounts or a repeating scripted message) not counted.

Record ship:f9ffc15a… · 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.

Build timeline

  1. Code changes, week of 2026-09-28 – 2026-10-04 · 10 commits

    Code activitySource linked

    38 active days in shcv/harness-investigations.

    Automated commits only — not counted as building. 12 automated commits (bot accounts or a repeating scripted message) not counted.

    View evidence

  2. Code changes, week of 2026-09-21 – 2026-09-27 · 8 commits

    Code activitySource linked

    34 active days in shcv/harness-investigations.

    Automated commits only — not counted as building. 8 automated commits (bot accounts or a repeating scripted message) not counted.

    View evidence

  3. Code changes, week of 2026-09-14 – 2026-09-20 · at least 10 commits

    Code activitySource linked

    31 active days in shcv/harness-investigations.

    Automated commits only — not counted as building. 10 automated commits (bot accounts or a repeating scripted message) not counted.

    View evidence

  4. Code changes, week of 2026-09-07 – 2026-09-13

    Code activitySource linked

    26 active days in shcv/harness-investigations.

    Automated commits only — not counted as building. 32 automated commits (bot accounts or a repeating scripted message) not counted.

    View evidence

  5. Code changes, week of 2026-08-24 – 2026-08-30

    Code activitySource linked

    23 active days in shcv/harness-investigations.

    Automated commits only — not counted as building. 1 automated commit (bot accounts or a repeating scripted message) not counted.

    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 harness-investigations? Sign in with GitHub to submit a research note. Notes are reviewed before they appear here.

Research coverage

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

7 of 10 applicable dimensions measuredShow each dimension

Identity

  • IdentityMeasuredRead 1mo ago.

Building

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

Official site

  • Official docsNo sourceNo official website on record.
  • API descriptionNo sourceNo official website on record.
  • Official site changesNo sourceNo official website on record.

Code and packages

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