Same evaluator
The scalar used during play and the decomposed receipt share one evaluation kernel. A disagreement is a software defect, not a difference of interpretation.
A chess engine that shows its work.
Luxifare examines decisions across your recent games, proves every surviving finding with your own positions, and refuses to invent a pattern when the evidence does not hold.
Private preview · no account before value · every claim remains replayable
Keep every piece. Stay winning.
+7.75Give the rook. Break the king.
+13.82Material + piece squares+5.14
King safety+0.26
Weak squares+0.10
Pawn structure−0.12
The rook is the key. Taking it drags the bishop off e2. Then Nf3+ forks king and queen, and the attack ends in mate. The measured future is +6.07 better than the obvious check.
One decision, opened
Nf3+ keeps every piece and stays winning. Rxd3+ gives a rook for one pawn, pulls the bishop off e2, and turns the next knight check into a king-and-queen fork. Luxifare searched both moves to the same depth, then opened the difference concept by concept. Click either move to compare the futures.
Scroll the game continuation to watch the idea unfold.
Black to move
Nf3+ keeps every piece and stays comfortably ahead. Luxifare found that Rxd3+ can give up the entire rook, pull the bishop off e2, and make the king and queen collapse together.
Put the rook where it can be taken
The rook takes one pawn and checks. White has only two legal replies: Kc1 or Bxd3.The bishop accepts the rook
Five points disappear for one pawn. The bishop is pulled off e2, exactly where it was holding the position together.Fork the king and queen with check
The knight lands on f3 with tempo. The king must move while the queen on e1 is under attack.The king steps into the mating net
White answers the check, but cannot save the queen and keep the king safe at the same time.Take the queen
The rook is still gone. Luxifare has converted the sacrifice into White's queen and an exposed king.White blocks one route
The rook tries to cover the second rank. It cannot stop the knight from closing every escape square.Finish with mate
The knight returns to d4. Every flight square is covered. The sacrifice ends in checkmate.The rook really stays gone. Its job is to drag the bishop off e2 so Nf3+ arrives with tempo against both king and queen. In the recorded game, Luxifare took the queen and finished with Nd4#.
Why the rook can disappear
Named concepts 539cp+exact comparison remainder 68cp=decision margin 607cp
The mating continuation was played by Luxifare in a recorded engine game. The comparison was freshly re-run with the current champion. Both lines reached depth 8 under the same 250,000-node and 1,500ms caps. Both scores are exact completed search results. Stockfish 17.1 also ranks Rxd3+ first at depth 22.
Under every searched line
At each evaluated position, one kernel measures 32 named concepts: material and piece squares, king safety, mobility, threats, pawn structure, outposts, weak squares and more. The fast path collapses them into one score for search. The trace path reads the same computation back out by name.
Hover a concept. The board shows the squares it judges.
The 32 displayed integer contributions plus 4cp of per-term rounding equal the evaluation. No hidden strategic term. This is the engine's actual arithmetic.
The scalar used during play and the decomposed receipt share one evaluation kernel. A disagreement is a software defect, not a difference of interpretation.
Luxifare does not call the position after a move “the reason.” It follows the searched line to its resolved leaf, then compares that future with alternatives.
Sometimes one concept dominates. Sometimes several small advantages decide the move together. Luxifare reports the difference instead of inventing a tidy story.
The safety boundary
Luxifare is the chess engine. It searches, scores, compares and qualifies its own evidence in deterministic code. Lux is the conversational character. She may turn a typed receipt into a fluent coaching sentence, but she cannot add a reason that is absent from the receipt or influence the move.
The improvement machine
Losses become evidence, not vibes. Repeated failure clusters nominate a bounded experiment. Candidates run behind shadow gates, then play external validation matches. Most ideas die. Only measured gains can become the next engine.
Find recurring suites, phases and concept failures.
Change an approved parameter family, not arbitrary live code.
Ask where a shortcut would have cut, then verify what it missed.
Stockfish-first matches reject candidates that merely looked active.
Ship a measured gain, or store the failure so it is not rediscovered.
An LLM may suggest a typed, bounded experiment. It cannot execute arbitrary evaluator code, edit the live search loop, or overrule the validation harness. The test has veto power. The model does not.
The public record
Luxifare played 511 games in public under its own account, unattended, against whoever challenged it. The archive includes the wins, losses, ugly positions and rating drawdowns. It sits around 2400 Lichess rapid. Not world champion strength, and strong enough that its reasons have to survive real tactics.
The bot is paused while the work moves to analysis, so it will not answer a challenge today. Read the games move by move.
What exists, what opens next
The engine capabilities demonstrated above are real. The public product is not open yet. This ledger keeps engine-complete, product-complete and planned work separate.
Private preview
We are opening in small, consenting cohorts while we verify the evidence, usefulness, and safety of every step. Leave your email and we will send your invitation when Luxifare is ready. No account is needed before value.
Invite-only · one invitation when ready · no account before value