Skip to content

Cognita

Is this your project? Claim it →

What HEY knows

Development

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) · 2 commits

Token

No token tracked
FollowCreate alertTerminal preview
Get updates

Get updates

Follow puts Cognita 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 Cognita

No account? Email me Cognita’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
Unknown2 gaps: Official docs (no source), API description (no source). HEY read its website and found no link to docs.
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-29.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsCode changes this week (since Mon 26 Oct) · 2 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.
Source3 registered sources, 0 of them context only.ReadRecordsCode changes this week (since Mon 26 Oct) · 2 commitssource:462af0eb-9af8-4733-999e-acc8b1120699source:f9bcc7ea-e4e9-42e2-940b-13ee37ee2156What 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 8 of the 10 research questions that apply.
8 of 10 applicable dimensions measured.

Identity

  • IdentityMeasuredRead 6h ago.

Building

  • Building activityMeasuredRead 1h ago.
  • RepositoriesMeasured
  • ReleasesMeasured
  • 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 4h ago.

Code and packages

  • Repository detailsMeasuredRead 5h ago.
  • Published packagesMeasuredRead 5h 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 account @wageholdx not found, checked 2026-10-30.Sources

Latest ship

Checked

Code changes this week (since Mon 26 Oct) · 2 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:

2 active days in cognita-robinhood-chain/cognita.

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.

Record ship:c5bc10a7… · 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
1 of 1 commit 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-29; HEY first knew on 2026-10-30.
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.

Shared change · Verified Builder

Cognita is now a verified builder: HEY verified its builder sources.

1 meaningful development event was recorded in the last 30 days. Builder status: Shipping.

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

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.

What changed

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

All 3 changes for Cognita →

Questions HEY can answer about Cognita — as of 30 Oct

Show the answers
Is Cognita still being built?
DerivedShipping: 1 counted ship in 30 days; latest ship yesterday. Evidence
What did Cognita ship last?
FactCode changes this week (since Mon 26 Oct) · 2 commits — Code activity, yesterday. Evidence
What does HEY not know about Cognita?
Unknown2 gaps: Official docs (no source), API description (no source). HEY read its website and found no link to docs.

Sources

3 places HEY reads for Cognita