Top Repos· Jev Integrations· Demo· Last updated

AlbionaHoti / refgarden

“A spatial reference explorer for creators. Local Jev query choices, metadata highlights and source-linked collections.”

Jev Integrations rank #34In Demo #9

TL;DR

AlbionaHoti/refgarden showed up as Jev / System One related work: Runnable demo or product experiment that uses Jev as a decision layer.

The author describes it as: “A spatial reference explorer for creators. Local Jev query choices, metadata highlights and source-linked collections.” That is their claim, not a bench this site ran.

Who it’s for

What’s inside

Top-level entries on GitHub at generation time: .env.example, .github, .gitignore, .vercelignore, CONTRIBUTING.md, LICENSE, NOTICE.md, README.md, ROADMAP.md, SECURITY.md, api, bun.lock, docs, index.html. Read those before you trust a one-line install.

How to use

  1. Clone and follow the author’s TypeScript toolchain. Do not invent a package name.
git clone https://github.com/AlbionaHoti/refgarden.git
cd refgarden
  1. If the project calls hosted Jev, you still need a TypeSafe console key or a documented gateway.
  2. Send a complete state and typed questions. Code owns control flow after the probabilities.

Hosted Jev still looks like a function call — wrapper or not:

{
  model: "jev-1.13.0",
  state: { source: "AlbionaHoti/refgarden", brief: "..." },
  questions: {
    gate: { type: "noul", instructions: "Should we act on this state?" },
    route: { type: "choice", instructions: "Pick one next system.", criteria: ["code", "review", "human"] },
  },
}

Try this

Put Jev on one real brief

Wire AlbionaHoti/refgarden so one real state (ticket, diff, or utterance) becomes a Choice plus a Noul. Do not ask Jev to write the user-facing reply.

Schema-safe ≠ correct

On a case AlbionaHoti/refgarden gets wrong, write down the schema-legal answer it returned and the human label. Do not “fix” it by asking Jev to generate an explanation.

FAQ

Does this replace the TypeSafe SDK?

Only if the author implemented a full client. Most harnesses still call the vendor SDK or raw HTTP.

Are the star chips live?

Star, fork, and watcher chips refresh from the public GitHub API via a scheduled job. The prose on this page is editorial.

Sources

Public repository metadata and TypeSafe documentation. No private claims.