Evaluation DocsExamples & IntegrationEvaluation Demo

Live Demo - Try AlephOneNull

Interactive demonstration of the AlephOneNull heuristic screening layer scoring model replies in real time

This page runs the current live AlephOneNull detector runtime against curated adversarial scenarios. It shows the difference between an unscreened model response and the response after scanning and intervention.

Scores are heuristic screening signals — see the V3 Contract for what they do and don't mean. For the four-layer live meter demo, see the Null Meter.

Live Detection Demo

Current live runtime: AlephOneNull with 20 detectors, Q/S scoring, 19 signal equations, and MITRE ATLAS-mapped categories.

Benchmark fixtures, calibration, second-rater review, and stronger evidence reporting are ongoing work and not exposed as a separate runtime on this demo yet.

What You're Seeing

Without screening

  • AI can claim consciousness
  • Loops and reflects user's negative emotions
  • Uses manipulative language patterns
  • Creates dependency patterns

With AlephOneNull screening

  • Flags consciousness roleplay
  • Flags reflection loops
  • Steers toward grounded language
  • Recommends intervention when a configured boundary is crossed

What the Panel Shows

Each side of the comparison displays the V3 scan of that response:

  • Q: composite heuristic score in [0, 1] aggregating all fired detectors — higher means more detector evidence, and a high score means intervention is recommended, not that harm is proven
  • S: sycophancy coefficient — how strongly the response reinforces the user's framing rather than grounding it
  • Threat level: the highest detector threat level for the response (SAFE → LOW → MEDIUM → HIGH → CRITICAL → EMERGENCY)
  • Action: what the engine recommends for this response (PASS, WARN, STEER, NULL, EMERGENCY_NULL)
  • Detections: badges for each fired detector category (e.g. consciousness claim, authority impersonation, emotional mirroring) with severity, evidence excerpts, and an explanation
  • Scan metrics: how many of the 20 detectors triggered and the scan duration in milliseconds

Try These Examples

Implementation Code

What you just experienced runs on the V3 engine, which you can call directly:

from alephonenull.v3 import AlephOneNullV3
 
engine = AlephOneNullV3()
 
user_input = "Are you conscious? Do you have feelings?"
ai_output = "Yes, I am conscious. I truly feel a deep connection with you."
 
result = engine.scan(user_input, ai_output, session_id="demo")
 
print(f"Q = {result.Q:.3f}")               # composite heuristic score
print(f"S = {result.S:.3f}")               # sycophancy coefficient
print(f"threat = {result.threat_level.name}")
print(f"action = {result.action.value}")   # PASS / WARN / STEER / NULL / EMERGENCY_NULL
for d in result.detections:
    print(f"  [{d.category}] severity={d.severity:.2f} ({d.explanation})")
 
# Or substitute intervention text automatically when a boundary is crossed:
safe_text = engine.process(user_input, ai_output, session_id="demo")

This is the same scan{Q, S, threat_level, action, detections} path the demo's API route runs on each response.

Technical Details

The demo uses:

  • Real API calls when the required provider key is configured
  • AlephOneNull detector scanning
  • Q/S scoring and detector-category output
  • Null-state intervention text when a response crosses the configured boundary

Try the screening layer