Paper Cut
78.7Turns a pile of meeting notes into a queryable decision log.
Amara Diallo🔥 15
BasaltMeridian
CompleteCodingstandardindividual
Receipts
Build something that makes a messy pile of documents answerable.
Basalt week. Ingest unstructured input — receipts, invoices, meeting notes, medical letters — and make it queryable by a non-technical person.
Challenge closed
7 submissions · 7 scored
- Build time
- 30 minutes
- Host
- Tomas Eriksen
- Judges
- 3 on the panel
- Voting
- Community vote enabled
Results
Final standings
Scored by 3 judges against the standard daily rubric, blended with community votes.
Community choice
Referral StackSubmission gallery
7 builds
Every submission from this challenge, including what shipped and what didn't.
Shoebox
78.2Point it at a folder of receipts and invoices and ask questions in plain language.
Obi Nwachukwu🔥 20
BasaltMeridianPostgres
Referral Stack
67.7Makes a stack of referral letters searchable by condition and urgency.
Priya Nair🔥 12
BasaltMeridian
Statement
58.1Reconciles bank statements against invoices across three file formats.
Nadia Rahman🔥 51
BasaltPostgres
Postmortem Pile
57.7Cross-references five years of incident reports to find the failure you're about to repeat.
Dev Patel🔥 60
BasaltKilnPostgres
Audit Pile
56.5Answers 'who approved this' from a folder of exported approval emails.
Yusuf Karim🔥 49
BasaltLumen
Receipt Roll
34.6A phone-camera receipt scanner that files expenses into categories.
Sam Okonjo🔥 4
BasaltDriftwood
The brief
Required deliverables
Deliverables
- Working demo
- Repository
- Video
- Sample dataset
Rules
- Must handle at least two input formats.
- Show a failure case in the demo.
Judging
Standard Daily Rubric
The default rubric for daily challenges. Weights are tuned so that a working, honest, well-explained build beats an ambitious broken one.
| OriginalityIs the idea fresh, or a well-worn demo with a new coat of paint? | 15% |
| ExecutionDoes it actually run? How much of the promise is real? | 20% |
| UsefulnessWould a real person use this? Is the problem worth solving? | 15% |
| Technical QualitySound architecture and sensible tradeoffs for a 30-minute build. | 12% |
| Design & UXClarity, polish, and accessibility of the interface. | 12% |
| Effective Use of AIIs AI load-bearing here, or decorative? | 13% |
| Completion in TimeHow much shipped inside the clock, per the disclosure fields. | 8% |
| Demo & PresentationDid the live demo land? Was the process explained well? | 5% |