How jev-ai/jev-api works
This tree is a static Next.js site snapshot, not the Jev decision service implementation. The README describes a typed-decision API and Playground workflow; sampled browser bundles also expose an AI generation studio with model forms, task status, history, and results. Paths below identify the available page and compiled chunks, so internal wiring beyond the documented workflow is intentionally limited.
Main entry points: 13cc3e46dbf9f9d4.js Generation studio · be70605be73fce34.js Decision Playground · README.md Typed results · index.html Jev website
Components 15
Decision workflow
- Decision Playground
_next/static/chunks/be70605be73fce34.js - Shared state
README.md - Typed questions
README.md - Decision API
- Typed results
README.md - Application logic
README.md
Generation studio
- Generation studio
_next/static/chunks/13cc3e46dbf9f9d4.js - Model form
_next/static/chunks/13cc3e46dbf9f9d4.js - Generation endpoint
- Task tracking
_next/static/chunks/13cc3e46dbf9f9d4.js - Generated media
_next/static/chunks/13cc3e46dbf9f9d4.js - Auth and credits
_next/static/chunks/be70605be73fce34.js - Generation history
_next/static/chunks/be70605be73fce34.js
Site interface
- Jev website
index.html
Other components
- Developer / user
Connections 14
- Developer / user → Jev website: uses
- Developer / user → Decision Playground: defines
- Decision Playground → Shared state: provides
- Decision Playground → Typed questions: defines
- Decision Playground → Decision API: submits
- Decision API → Typed results: returns
- Typed results → Application logic: informs
- Developer / user → Generation studio: opens
- Generation studio → Model form: configures
- Generation studio → Auth and credits: checks access
- Generation studio → Generation endpoint: submits
- Generation studio → Task tracking: tracks
- Generation studio → Generation history: loads
- Task tracking → Generated media: displays