Log decisions so you can disagree with them later

Starter inspired by reachjalil/jevlogs. This is not a JevSkills monitoring product. Privacy: log only synthetic or consented data; never store raw secrets or personal mailboxes.

Read source

What you'll make

Persist decision traces so a human can override and relabel them.

A local log format and a simple viewer. Not the future JevSkills monitoring product.

Jev decides

Produces the typed answer being logged.

Your code acts

Your app writes the log, redacts secrets, and records overrides.

Agent prompt

Give your agent a useful brief.

Key-safe by design

Codex prompt

You are helping a developer prototype a Jev-powered application.

Goal: Add an opt-in decision log with redaction and human override fields.

Product truth:
- Jev (TypeSafe System One) returns typed decisions and calibrated probabilities. It does not write emails, generate UI copy, play games by emitting pixels, or call Zapier.
- Your job is to write application code. Jev only answers questions whose possible answers are defined in advance.
- Use the official JS SDK documented at https://github.com/typesafe-ai/typesafe-sdk-js. Read the current README before inventing method names.
- Keep API keys in server-only environment variables. Never put TYPESAFE_API_KEY in client code, screenshots, git, or logs.
- Ship a working mock adapter first. Live TypeSafe calls are optional and must be clearly labeled.

Required behavior:
1. Inspect the current project and only change what is needed.
2. Define a small typed Choice or Score schema. Include an explicit uncertain / human-review path.
3. Implement mock mode with fixtures that include ordinary, ambiguous, and conflicting examples.
4. Add a server-only adapter that calls TypeSafe only when TYPESAFE_API_KEY is present.
5. Application code must validate the typed response and decide the action. Failed provider calls must not trigger side effects.
6. Do not send, delete, archive, or mutate real user accounts in this first version.
7. Add tests for the schema and mock path. Report what was run and what remains untested.

Official source to read: https://github.com/typesafe-ai/typesafe-sdk-js

Include a fixture log file.

When finished, write a short Verification section distinguishing mock results from any live API call.

Copies instructions into your clipboard. It does not run or install anything.

Setup and guardrails

Start small. Keep the boundary clear.

Prerequisites

Any of the other kits producing decisions

Setup steps

Define fields: timestamp, schema version, state digest, answer, confidence, override, outcome.
Hash or drop raw PII.
Show a table of disagreements.

Mock mode

Log mock decisions from fixtures.

Live mode

Same schema for live calls, with provider latency if you actually measure it.