Two work credits
One credit covers one written diagnostic with source evidence, a bounded patch direction, and acceptance criteria.
Romeo Apps
OSS Proof Desk.
This 14-day validation experiment is closed. The smaller one-off public-repository diagnostic remains available.
The window ended 29 July 2026 without meeting the qualified recurring-demand threshold. The pilot application is no longer available.
- 14 live days
- Threshold not met
- Pilot closed
- One-off retained
Validation outcome
The recurring claim did not earn the right to continue.
The pilot required qualified applications and credible recurring demand. The validation threshold was not met, so Romeo Apps closed the pilot, removed its application path, and kept the lower-commitment one-off diagnostic.
What was tested
A bounded support unit, tested without pretending demand.
Or one proof package
Use both credits for up to four active engineering hours on a focused test, benchmark, fixture, script, document, GIF, or small proof PR.
Written service levels
Scope decision in one business day, first finding within 36 business hours, and final delivery within three or five business days.
Ended automatically
The offer closed after its validation window. It will return only after new buyer evidence supports a different test.
RomeoApps-owned proof system
The desk keeps scope, evidence, and completion separate.
One target is pinned to exact source, observed behavior, missing evidence, a smallest useful experiment, and a factual stop line.
Happy paths, malformed inputs, concurrency, lifecycle, and unchanged-base checks are mapped to the claim they prove or disprove.
Final bytes, commands, outputs, known limits, rollback, and buyer-visible readback are recorded without publishing customer work.
The retained method
Choose. Diagnose. Prove. Close.
Choose
Send the public repository, current issue queue, and the outcome that matters this month. Romeo Apps accepts only work it can validate.
Spend the credits
Each complete brief starts a 36-business-hour first-finding clock. Proof work begins only after evidence supports a bounded path.
Close one unit
Receive a written outcome report: what moved, what stopped, what remains, and whether a separately scoped next unit is worthwhile.
Boundaries
No hidden support debt.
The pilot is deliberately narrow. It is not a retainer for unlimited implementation, third-party merge guarantees, production incidents, or private access.
- No calls or on-call coverage
- No secrets or production access
- No private repository work
- No guaranteed merge or release
- No hardware claim without evidence
- No prohibited assisted submission
Active service
Start with one public issue.
The one-off diagnostic keeps the same written scope discipline without asking a buyer to prepay for recurring capacity that has not been validated.