Community · E2 · artifact verified

Call Jev from Flutter apps

A Flutter plugin that brings typed Jev calls to Dart apps: question builders for Noul and Choice with option-count validation, the systemone wire protocol on the native endpoint, and a Python-side test harness for the plugin's bridge.

01 · Role in the system

What Jev does here

The plugin gives Flutter's Dart layer first-class Jev questions: helpers construct Noul questions with optional true/false criteria and Choice questions with two-or-more options (builder raises on an invalid option count), and the plugin posts to api.typesafe.ai's systemone wire protocol by default, with the base URL overridable. Answers flow back into typed Dart structures for the app to threshold, so mobile code consumes calibrated probabilities instead of parsed prose. The repo is organized as a federated plugin with a documented example app, and the bridge side carries a Python test harness plus CLI, catalog and chunking modules for exercising the client end to end.

Typed questions as a Dart dependency

This plugin's contribution is making Jev questions a first-class Dart type. Builders construct Noul questions with optional criteria and Choice questions with two or more options, raising on an invalid option count at construction time — so a misdeclared question fails in the compiler-adjacent layer, not in production traffic. Answers return as typed structures the app can threshold, with no prose parsing anywhere in app code.

The wire side defaults to the systemone protocol against the native endpoint with an overridable base URL, and a Python-side harness exercises the bridge end to end. The federated-plugin layout with a documented example app is the shape the Flutter ecosystem expects, which lowers the cost of evaluating the pattern.

A record about plumbing, honest about its age

The limitations are unusually candid for a package record: the plugin was created days before capture, has no published package yet, and its iOS and Android integration paths are untested by anyone outside the author. The API surface may still change — the record says to expect it.

Its value to the index is as infrastructure evidence: the mobile cluster contains control loops and use-case apps, and this record shows the client-side plumbing they would share. Any mobile Jev integration inherits its question-builder validation and typed-answer consumption as a starting point.

02 · Control boundary

Where Jev sits

Jev as a typed-decision dependency for mobile: question builders validate Noul and Choice shapes at construction, calls go over the systemone wire protocol with a default native endpoint, and Dart consumes typed answers - no text parsing in app code.

Code owns the loop, permissions, thresholds, validation, and side effects. Jev owns only the bounded judgments described above.

03 · Known limits

What this evidence does not prove

  • Brand-new plugin (created 2026-09-28, 0 stars); API surface may still change.
  • Flutter/Dart client with a Python test harness; no published package yet.
  • iOS and Android integration paths are untested by anyone outside the author.

04 · Attribution

Public sources

This is a Community record: the project was published by a third-party community author.

  • pkcoulon ↗Community · github · public · checked 2026-09-30