Method / 03Read before you remix

A prompt is
a beginning.

Prompt Forge separates the idea, the compiler, the runtime, and the evidence. That makes a flashy demo inspectable instead of magical.

source record→brief→deterministic compiler→sandboxed runtime→revision + seal
01 / Evidence

Sources stay attached.

Official model pages, public repos, DEV articles, and indexed social posts enter as short attributed records. We keep the claim and the source URL beside the artifact.

modelrepopost
02 / Compiler

No hidden magic call.

The core experience uses four deterministic templates. A prompt changes the scene, palette, controls, and telemetry; it never asks an unavailable model key to finish the job.

SVGCanvasThree.js
03 / Runtime

Play is evidence.

Every preview loads in a script-only iframe. Controls change state, resets work, and the artifact exposes a small telemetry object for QA and future agent calls.

loadinteractreset
04 / Integrity

Revisions leave a seal.

Create, update, and retire events append a SHA-384 chain. Replay detects the first broken link and the export keeps the source trail beside the result.

canonical JSONreplay
The score

Boring math
beats a magic number.

The engine returns a score, itemized factors, a recommendation, and a seal. It is a prompt-readiness signal—not a claim about model quality.

30%Specificity
25%Interaction contract
20%Visual direction
25%Constraints + evidence
Ready to test the loop?

Compile something you can play.