# Neon RiddleNode Intent-Matrix Report

## Plain-English Summary

The Neon RiddleNode lab can now answer several small mix-change questions in one public-target proof pass. The shared health/layout/playback gates ran once, then the matrix ran separate claim-candidate loops for bass, guitar, and chord "down a little" requests.

The useful catch is speed and boundary control: the proof system can batch reviewable candidates without waiting on a `lilarcade.com` or `riddledc.com` promotion, and without claiming any candidate sounds better.

## What Changed

- LilArcade PR #534 added `npm run proof:sequencer:riddlenode-intent-matrix`.
- The matrix reuses the already-published RiddleNode Neon lab target at `https://riddlenode.com/neon-lab/`.
- Shared RiddleNode gates run once before intent-specific loops.
- Each intent still produces its own human-review packet with objective receipts, guardrails, and the proof/taste boundary.

## Verification

Live RiddleNode intent matrix:

- status: `intent_matrix_ready_for_review`
- shared gates: `local_gate_ready`
- bass request: `bass -0.05`, supported `3`, rejected `0`
- guitar request: `guitar -0.02`, supported `3`, rejected `0`
- chord request: `chord -0.035`, supported `2`, rejected `1`
- deterministic findings: `0`
- review warnings: `0`

Local/package checks:

- `node --test scripts/__tests__/neonRatchetIntentMatrix.test.mjs scripts/__tests__/neonRatchetBatch.test.mjs`
- `npm run test:neon`
- `npm run proof:sequencer:riddlenode-intent-matrix`

GitHub checks:

- LilArcade PR #534 CI passed at head `a014e2a`.

## Proof Boundary

This proves that the Neon lab can batch bounded public-target claim-candidate loops and produce compact review packets. It does not prove subjective mix quality, the best musical candidate, or that any candidate should be applied without listening review.