THE SERVICE CATALOG

Four focused tools.
One controlled engine.

Small input contracts, bounded work and explicit results. Available through the same engine over HTTP and MCP.

01 / Decide

Evaluate evidence against up to eight related questions: boolean probabilities, finite choices or rubric scores. Useful for classification and a narrow first pass over known facts.

POST /v1/decide
MCP: sysone_decide

The caller supplies the evidence and the possible answers. The engine validates the model output. Missing probability stays unknown; the caller decides what confidence is acceptable and whether to escalate.

02 / Logs

Use jevlogs to triage up to 16 log records. Confidently routine events can avoid expensive analysis. Protected errors and uncertainty remain eligible for inspection.

POST /v1/logs
MCP: sysone_logs

This is an analysis filter, not a log archive. Retain every original record in your own logging system. Never discard an event solely because a model considered it routine.

03 / Tree

Use jev-tree to select from your taxonomy. The engine bounds recursive model calls and cancellation around the library. Ambiguous paths return an escalation signal.

POST /v1/tree
MCP: sysone_tree

Good for routing to a known category or narrowing an existing hierarchy. A selected identifier never grants access or authorizes an action.

04 / Dialogue

A small decision service for authored narrative. The application supplies the current context, eligible recorded cues, completed lines and timing. The engine can recommend one cue, silence or a deterministic fallback.

POST /v1/dialogue
MCP: sysone_dialogue

The Infinite Parable pattern

The first reference integration uses optional advice over prerecorded narrator reactions. Deterministic filtering handles repetition and spacing before a model call. A context identifier lets the application reject advice that arrives after the player or scene has moved on.

The game's narration director owns playback and continuation. The engine does not generate a new script, synthesize speech, change geometry, grant progress or override the player.

Silence is a valid result. A fast response is only useful when it respects the scene and the authority of the application.

Shared controls

All four services use scoped consumer credentials, daily admission limits, bounded concurrency, cancellation, exact per-connection caching and durable usage receipts. Start with the setup guide and inspect the service schemas in Studio.