Two work credits
One credit covers one written diagnostic with source evidence, a bounded patch direction, and acceptance criteria.
Romeo Apps
One public repository. Two written diagnostics or one bounded diagnostic-to-proof package over 30 days.
Four pilot clients. Prepaid once. No calls, auto-renewal, production access, secrets, emergency support, or unlimited backlog.
The 30-day unit
Use the desk when a public repository has recurring support questions, unclear bugs, or review work that keeps slipping. Choose two diagnostics or spend both credits on one deeper proof package.
Included for 30 days
One credit covers one written diagnostic with source evidence, a bounded patch direction, and acceptance criteria.
Use both credits for up to four active engineering hours on a focused test, benchmark, fixture, script, document, GIF, or small proof PR.
Scope decision in one business day, first finding within 36 business hours, and final delivery within three or five business days.
The pilot expires after 30 days. A later recurring plan requires explicit written opt-in after delivery.
Settled public proof
Public captures became mapped fields, CRC evidence, a clean build, repository tests, and 57/57 known-capture replays.
USD 55 paid diagnosticPlayback capacity decisionA broad stability request became a source-backed diagnosis, safe benchmark protocol, and explicit capacity limits.
USD 200 paid deliveryPolicy, benchmark, and docsA public task became reproducible code, held-out evaluation, a representative GIF, documentation, and fully green checks.
Operating rhythm
Send the public repository, current issue queue, and the outcome that matters this month. Romeo Apps accepts only work it can validate.
Each complete brief starts a 36-business-hour first-finding clock. Proof work begins only after evidence supports a bounded path.
Receive a written outcome report: what moved, what stopped, what remains, and whether another month is worth buying.
Boundaries
The pilot is deliberately narrow. It is not a retainer for unlimited implementation, third-party merge guarantees, production incidents, or private access.
Four pilot clients
Send the repository, two or three candidate issues, the result you need, and how often the problem class recurs. If the scope passes the acceptance gate, Romeo Apps creates one dedicated payment route. Work starts only after verified payment.