Odel
GeniusFlow Evidence

GeniusFlow Evidence

@kaydeep0AstroUpdated 3 days ago

Re-check pinned sources, package and cite. Live Federation MCP. No account.

Server endpointStreamable HTTPNo authProbed

This is the third-party server itself — Odel doesn't run it. Hitting this URL directly talks straight to the upstream server with no auth or proxying. Connect through Odel to front it with managed auth.

GeniusFlow

Evidence is the product. Federation and MCP are the interfaces. RWA / CIRCLE is the proving ground. Research is the laboratory.

Pinned claims about real-world entities. Live source re-check. Fail-closed packages. Public MCP.

USE NOW      Evidence API + MCP     this README
RESEARCH     labeled experiments    not a product feature
ROADMAP      registry / reliance / settlement    future

Try Federation · Connect MCP · CIRCLE example · What this does not claim


Use GeniusFlow

Evidence-backed claims that can be independently re-checked.

No account. Live origin:

https://geniusflow-federation.vercel.app
Do thisCall
Open an entity cardGET /api/dossier?entity=CIRCLE
Re-check a pinned stringPOST /api/verify
Admit or withholdPOST /api/package
CitePOST /api/cite with {kind, id, claim}
MCPPOST /api/mcp — registry io.github.Kaydeep0/geniusflow-federation

SLA: best-effort Vercel hobby. No promised uptime.

A missing circulating figure stays UNKNOWN. That is product behavior, not an empty cell to fill in.


How it works

Entity → Claim → Grounding → Verify → Package → Cite
  1. Entity — a specimen card (CIRCLE is the public proving ground).
  2. Claim — a published sentence on that card.
  3. Groundingsource_url + expected substring, taken from the claim. Do not invent expected.
  4. Verify — another machine re-fetches the source and reports whether the substring is still there.
  5. Package — admit or withhold. Invented attestations are withheld.
  6. Cite — a cite packet over a published claim object.

Literal string re-check. Not semantic fact-checking. Not “the world is true.”

Pages (kaydeep0.github.io/eigenstate-research) and Federation are different surfaces. Snapshot identities can differ. Do not treat them as one synchronized view.


CIRCLE example

# 1. Entity card
curl -sS "https://geniusflow-federation.vercel.app/api/dossier?entity=CIRCLE"

# 2. Take grounding from claims[0] — do not invent expected
# 3. Verify, package, cite: see examples/

Copy/paste scripts (curl + python3, no clone of the private engine):

Machine index: llms.txt · OpenAPI: openapi.json


Connect MCP

Remote. No private filesystem path.

{
  "mcpServers": {
    "geniusflow-federation": {
      "url": "https://geniusflow-federation.vercel.app/api/mcp"
    }
  }
}

Official registry: io.github.Kaydeep0/geniusflow-federation

Tools (live tools/list): gf_status gf_dossier gf_report_feed gf_cite gf_verify gf_package gf_darshan gf_return_wire gf_openapi

gf_darshan and gf_return_wire are experimental adapters. Core evidence tools are gf_dossier / gf_verify / gf_package / gf_cite / gf_status.


Research

Experiments testing whether maintained state helps independent AI observers recover position and, separately, allocate future attention.

These are labeled experiments. They are not the product on the first screen.

ExperimentPublic status
H_CHATGPT_POSITION R1Task-specific: maintained multi-artifact package C recovered position better than thinner packages A/B (n=15). Not a memory product. Not a general information-advantage proof.
H_CHATGPT_POSITION A1Frozen. 0/25 observers. Waiting on ChatGPT upload apparatus. Not run.
Phase 8Apparatus reachable; prospective experiment not yet started. T0 none. Not a live world-tracking feature. Not an experimental result.

Roadmap

Explicitly future. Not current product claims.

  • RWA registry as something others rely on
  • Shared reliance
  • Settlement

CIRCLE is inspectable today. That does not make a complete RWA registry.


What this does not claim

  • Persistent AI memory product
  • Better than RAG / Graphiti / Mem0 / Letta
  • Complete RWA registry
  • Settlement or reliance
  • Real-time world model
  • Proven information advantage
  • Synchronized websites (Pages and Federation snapshot ids can differ)
  • Production SLA
  • $500T+ tokenized-market figure

Public surfaces

The runtime engine repository is private.

Also on this site

Human research Pages (secondary; not the Evidence API):