Jev reference
Transport, consent, limits and troubleshooting for report analysis.
Start with the setup guide. This page covers the controls behind it.
What it classifies
One request asks four questions about a report:
| Question | Classification |
|---|---|
| Did the work finish? | Completed, partial, blocked or unknown |
| How much friction occurred? | None, minor, substantial, blocked or unknown |
| What probably caused it? | Access, tooling, complexity, requirements, documentation or unknown |
| What could help? | Tooling, instructions, refactoring, tests or no action |
Jev supplies categories and probabilities. Your agent supplies concrete suggestions. PhaseDrift can record reports and proposals without Jev.
Managed and BYO
| Managed analysis | Your TypeSafe key | |
|---|---|---|
| Provider credential | Kept on PhaseDrift's backend | Your project's .env.local |
| Report path | Your machine → PhaseDrift gateway → TypeSafe | Your machine → TypeSafe |
| Allowance | Shared by your billing account | Your local policy and provider account |
| Inference billing | Included with PhaseDrift | Your TypeSafe account |
Both require explicit cloud-analysis consent. Connecting a subscription or opening a report does not grant that consent. Commercial builds require a valid product license even when you choose BYO or disable cloud analysis. Install the signed local release before connecting your subscription.
Limits
Managed defaults are 10,000 dispatch attempts and 10 million input tokens per UTC calendar month, 1,000 attempts per UTC day and three machine activations. Whichever limit is reached first applies. All projects and machines on the billing account share the allowance. The calendar-month reset is separate from your invoice date.
BYO starts with a local policy of ten requests per UTC day. Inspect policy and jobs without making a provider call:
phasedrift learning analysis policy
phasedrift learning analysis jobs
phasedrift learning analysis accountThe account command applies to managed access. Matching redacted reports reuse an account-scoped result. Managed outages and exhausted allowances keep local jobs queued with backoff. An uncertain provider dispatch is not blindly retried.
Explicit connection and consent
The dashboard is the easiest setup path. The CLI accepts private credentials on stdin, keeping them out of command arguments and shell history:
phasedrift learning analysis activate --stdinEnter one JSON object with gateway and licenseKey, then EOF. This activates a machine without authorizing report uploads.
To select managed analysis and consent to future reports:
phasedrift learning analysis connection --stdin <<'JSON'
{"mode":"managed","consentVersion":"cloud-analysis/v1","includeHistory":false}
JSONKeep includeHistory false unless you intend to submit reports already saved in this project. A raw policy change does not substitute for fresh consent. phasedrift init --host <host> --analysis requires a connected credential and records analysis consent; plain setup does not. Replace <host> with the same host selected during project setup.
Troubleshooting
| Situation | Next step |
|---|---|
| No credential connected | Connect your subscription or load your BYO key |
| Credential connected, analysis off | Inspect the payload and enable your chosen transport |
| Allowance exhausted or service unavailable | Keep working; eligible managed jobs stay queued |
| All machine slots occupied | Release an unused machine or explicitly replace a lost device |
| Uncertain dispatch | Inspect its recorded state; do not blindly resubmit it |
| Saved result expired at the gateway | Retain the local classification; do not assume a replay will recreate it |
Releasing a managed machine also pauses managed access for its other projects. Consent remains project-specific. There is no automatic fallback between managed and BYO.
What leaves your machine
Only bounded report prose and the classification recipe are submitted. PhaseDrift does not add code files, repository identity, raw transcripts, tool arguments, screenshots or diagnostic traces. Reports can still contain private information.
Common credentials, email addresses, URLs, local paths and fenced code are removed before dispatch. Inspect the payload preview: pattern-based redaction does not guarantee anonymity. Managed analysis pins its model recipe; BYO uses the configured TypeSafe model.
The gateway retains classifications for 30 days, plus usage, opaque fingerprints and account/device identifiers. It does not persist report prose. Saved classifications remain on your machine. Cloud-analysis consent is separate from any future optional diagnostics program.