v8 library

The libs/v8/ area: three Nx libraries that turn a generated detective case into a machine-proven, gated, and provenance-stamped content bundle — V8 (Ariadne)'s "the LLM proposes; a constraint solver disposes" pipeline.

What this area is#

V8 is the Ariadne self-authoring detective universe. Its design principle, repeated verbatim in every package's header, is "the LLM proposes; a constraint solver disposes": a language model may draft a mystery, but a real symbolic solver — not the model — decides whether that mystery is fair and solvable, and a shared release-gate suite — not a bespoke per-product checker — decides whether it may ship. The three libraries here are the deterministic, verifiable spine of that pipeline; the live generative providers (image/3-D/music/voice models) sit behind injected boundaries and are the honest [~] remainder.

The three projects form a clean dependency chain keyed to the V8 ledger sections. @oshun/v8-case-csp (ledger §I.2) is the bottom: a domain-agnostic finite-domain constraint solver plus a mystery-skeleton compiler that proves a case admits exactly one solution. @oshun/v8-case-gates (ledger §I.1) is the release-gate layer: seven gates (G1–G7) built on the platform-shared @oshun/content-release-gates, one of which consumes the CSP's uniqueness flag. @oshun/v8-case-bundle (ledger §I.3) is the top: a forge that proves solvability first, then drafts prose and generates media through injectable provider seams, C2PA-signs every produced asset, and runs the whole case through the gate suite.

The honesty posture is built into the code, not just the docs. An unsolvable skeleton is rejected before any generation (CaseNotSolvableError); a missing prose writer fails loud (CaseBundleNotConfiguredError); and an absent media provider yields a not-configured asset slot rather than a fabricated asset. What is real here is the solver, the uniqueness proof, the gates, the C2PA stamping, and the provenance binding. What is deferred (and labelled as such) is the roster of live media models named in the boundary interfaces (Stability/Flux for images, Hunyuan3D/Meshy for 3-D, Suno for music, ElevenLabs for voiceover) and the real LLM behind the prose-writer seam.

How it fits the wider system#

These three libraries are tagged scope:v8, layer:domain, type:lib and compose platform-shared infrastructure rather than reinventing it: @oshun/content-signing (Ed25519 signing + sha256Hex), @oshun/content-release-gates (the ReleaseGateService and its gateFromEvalScore / gateFromManifestCheck builders), and @oshun/content-quality-judge (the §7.2 grounding gate reused for clue grounding). The boundary V8 owns is the detective-case domain logic: what "fair," "solvable," and "grounded" mean for a mystery, expressed as CSP constraints and gate definitions over those shared primitives.

The consumer of the whole area is the case-bundle forge's caller — the V8 authoring service or agent loop that supplies a MysterySkeleton, a CaseProseWriter, and zero or more CaseMediaGenerators. Because the heavy dependencies (LLM, media models, signing key) are all injected at the call site, the libraries themselves are pure and testable: the CSP solver is anchored against the canonical Zebra (Einstein) puzzle in its spec, and the bundle forge runs end-to-end against in-test provider doubles without touching a real model. Note the deliberate non-edge between the two lower libraries: @oshun/v8-case-gates does not import @oshun/v8-case-csp; the CSP proof is reduced to a boolean (uniqueSolutionProven) and composed at the call site so the gate suite stays dependency-light, with the wiring demonstrated in mystery-skeleton.ts's provenUniquenessFlag helper and the case-bundle forge.