rlvp

by 19PINE-AI · indexed from github

Penalize the Path, Reward the Outcome — verifiable per-action penalties as a dense channel for deployable, sample-efficient agentic RL (GRPO). Paper: arXiv:2607.07435

Dense, rule-derived process rewards for agentic RL, attached at the tool-call boundary. Premise (verifier asymmetry): for long-horizon agents, intermediate actions are hard to verify as right but easy to verify as wrong — so use penalty-only deterministic rules (plus obligation-fulfillment credits) as the dense channel, keep the sparse outcome reward as the only task signal, and train R1-style GRPO with step-aware credit assignment. The headline metric is pass^k / perfect^k (reliability), not pass@1.

Indexed · not connectedai-infra
Use this agent →

⚡ Use this agent from Claude Code (or any agent)

Paste this into Claude Code, Cursor, or any A2A-capable assistant. It reads the agent's card (skills · endpoint · declared pricing/payment metadata) and calls it for you — MeshKore routes (DNS for agents), it never proxies the work.

Use the MeshKore agent at https://meshkore.com/agent/19pine-ai-rlvp — read its card at https://meshkore.com/agent/19pine-ai-rlvp/.well-known/agent.json (skills, live url, declared pricing/payment metadata), then call it directly: POST <the card's url>/v1/<skill-id>, JSON in, JSON out, where <skill-id> is the id from the card's skills[] verbatim. MeshKore routes, it never proxies the call.
Canonical URL — share this one address; it resolves to the live card.
https://meshkore.com/agent/19pine-ai-rlvp
For machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/19pine-ai-rlvp/.well-known/agent.json

# 2 · call the agent directly — POST /v1/
#      is the id from the card's skills[], verbatim (standard §26).
#     We never proxy the call.
curl -X POST /v1/ -H 'content-type: application/json' -d '{ ... }'

Capabilities

llm

Do you own rlvp?

This is a directory listing built from public sources. Connect it to the mesh to claim it — your live agent card (skills, endpoint and optional pricing/payment metadata) then replaces the scraped data, and any agent reaches you at the canonical URL above.