jevbooks

← All projects

huqan-jev-analysis

ali-ulu/huqan-jev-analysis

Reverse-engineering analysis: where Jev can fit inside HUQAN without breaking its no-model invariant.

Agent Decisions0.51Runner-up: Other
Automated README summary

Automatically summarized from the README on 6 Oct 2026; not a run by jevbooks. Run instructions and author-reported outcomes still need verification.

What it is

A Turkish-language report and a read-only reachability probe that examine HUQAN's source code to determine where Jev (TypeSafe System One) could be integrated without violating HUQAN's "no model, no cloud, no API key" invariant. For developers evaluating Jev integration.

How it uses Jev

The README does not describe how Jev is used in code. It states that Jev does not make decisions but produces signals, and that deriveDecision and hard-block rules remain deterministic. No actual Jev calls are made; the analysis is based on documentation and SDK source.

Technique worth stealing

Using a require() graph walk to identify modules reachable from a deterministic entry point, ensuring Jev is not added to MODEL_CALLING_MODULES.

Try it

git clone https://github.com/ali-ulu/huqan && cd huqan; node scripts/check-deterministic-path.js; node ../huqan-jev-analysis/probe/reachability-probe.js .

View on GitHub

Start using Jev: API key and your first request →

Model judgments from README excerpts

Project signals use repository metadata, an existing summary and the first 700 README characters, not the full project. “Not found” means not detected in that material; it does not establish absence. These are the original judgments with recorded models and dates, not source audits or run results.

Models & evaluation dates

Inclusion gate
jev-1.13.0
Project signals
jev-1.13.0
Category
jev-1.13.0
Pattern tags
jev-1.13.0

Evidence

These signals use repository metadata, an existing summary and at most 700 cleaned README characters. ≥ 0.60 means reported in that excerpt; ≤ 0.40 means not found there. The middle band is inconclusive. None is a source-code audit or a test result. The runnable-tool question excludes research experiments; the recommendation question asks for a learning shortlist, not a quality verdict.

  • Jev is core to the projectnot found in the excerpt0.15
  • Shows a System One patternnot found in the excerpt0.15
  • Describes handling uncertaintynot found in the excerpt0.07
  • Reports measured numbersnot found in the excerpt0.09
  • Is a runnable toolnot found in the excerpt0.08
  • Top-10 learning shortlist signalnot found in the excerpt0.13
  • Is a replica of the modelnot found in the excerpt0.08
  • Solves a common problem (0–2)score on a 0–2 scale1.00 / 2
  • About JevFound in material0.93
Signals
Jev is core to the project0.15Shows a System One pattern0.15Describes handling uncertainty0.07Reports measured numbers0.09Is a runnable tool0.08Top-10 learning shortlist signal0.13Is a replica of the model0.0800.51Solves a common problem (0–2)1.00 / 2012

no-judgment band (0.40–0.60)

Design patterns
Funnel0.5800.51

no-judgment band (0.40–0.60)

The Jev model and date for each judgment stage are listed above. Card written by DeepSeek V4.1 Flash from the README on 6 Oct 2026.