rederive

version 0.0.2, single-substrate (claude-cli, model claude-opus-4-7), single-target (typescript), local LAN only

Endpoints

GET /capabilities
service metadata, public key.

POST /derive
derive a signed materialization from a constraint set. Body: application/json with {"constraints": "<text>", "name": "<optional>"}, or multipart/form-data with a constraints file field, or text/* with the raw constraint source.

GET /materializations/<hash>
fetch a cached materialization by candidate-code hash or constraint-set hash.

Quick start

curl -X POST http://192.168.4.132:7474/derive \
  -H "content-type: application/json" \
  -d '{"constraints": "## C1\ntype: specification\nauthority: human-authored\nscope: m\nstatus: active\ndepends-on: []\n\nExport export const answer = 42; in TypeScript.\n"}'

Notes

Materializations are signed with the server's Ed25519 keypair (public key in /capabilities). Verify locally with verifySignedArtifact from the rederive engine.
Identical constraint sources return the same cached materialization (idempotent).
Constraint sets with @imports are not yet supported over HTTP; use the CLI.
Derivations are dominated by substrate latency; expect 3-15 seconds per call.