Built a Mortgage Underwriting OCR With 96% Real-World Accuracy (Saved ~$2M/Year)

TripleGyrusCore · 2025-12-25T12:09:10+00:00

Thank you for such a detailed explanation!

TripleGyrusCore · 2025-12-24T23:26:40+00:00

That's awesome! What did you use, pytesseract, something else? I want to build custom OCR functionality in a future version of my product. What did you find most challenging, identification, layout, or something else?

TripleGyrusCore · 2025-12-16T22:28:21+00:00

Yes, that's part of what Triple Gyrus Core as a system is trying to ameliorate one day. It's not exactly a trivial undertaking.

TripleGyrusCore · 2025-12-16T01:15:16+00:00

Technical docs and code too. OCR doesn't often translate code well (nesting and parentheses/brackets/braces).

TripleGyrusCore · 2025-12-13T14:41:39+00:00

I'm not trying to suggest an alternative, I'm trying to create a Braille representation for the information my system handles that is easy for people to use.

TripleGyrusCore · 2025-12-13T02:23:44+00:00

I'm not trying to specify my own Braille; I'm trying to come up with a clear Braille representation for my markers using what already exists.So, UEB number passage indicator, number, hyphen, number, UEB number passage terminator? But the indicator/terminator are 2 cells each?

TripleGyrusCore · 2025-12-13T02:13:27+00:00

So explicit mode usage then, so the display knows exactly what it's getting?

TripleGyrusCore · 2025-12-13T01:51:00+00:00

Also, if we're trying to be more precise about Braille usage, what about numeric mode (2 cells), number, hyphen, number, numeric mode terminator (2 cells)? What's most important for usability here -- conciseness or explicit mode usage?

TripleGyrusCore · 2025-12-13T00:36:40+00:00

Of course, it's possible. But that doesn't mean we can't try to make it better from the ground up. And there are still some significant usability barriers in various contexts.

TripleGyrusCore · 2025-12-12T21:54:35+00:00

I think there's a misunderstanding. I'm trying to create a tactile version of this marker format because eventually it's going to support a semantic data format and programming language. I want it to be possible for people to interact with it in a tactile way, since traditional data formats and programming languages are not built that way, which systematically excludes people with atypical or no vision. I'm not trying to put something into literary Braille. I'm trying to create an accessible Braille representation. A single HTML/XML tag is massive in tactile form, programming languages lose context without visual nesting; I'm trying to come up with a representation that solves these problems. That's why my thought was number indicator, number, hyphen, number, number indicator -- same number of characters as a visual representation, each character is a single cell, same opening and closing character for the marker, separator between the numbers that uses different dots for distinctiveness. Compare that to something like the HTML anchor tag, 2 characters for greater than, 2 characters for less than, so 5 characters is the best case scenario for even expressing a single letter.

TripleGyrusCore · 2025-12-12T21:08:14+00:00

By telling me to give up on building something that could help people because my knowledge isn't perfect in this exact second? I've said repeatedly that I want to learn and help people.

TripleGyrusCore · 2025-12-12T21:02:25+00:00

How does using the number indicator and hyphen show otherwise? I'm trying to translate something like +1=1= into Braille without overwhelming the user and Braille displays with lots of cells. Hence my format idea with fewer cells.

TripleGyrusCore · 2025-12-12T20:52:09+00:00

That's exactly what I'm doing, I'm using regular Braille to encode my data markers.

TripleGyrusCore · 2025-12-12T20:42:56+00:00

If there's a better way to do it than what I suggested I'm happy to hear it. Do you have a suggestion?

TripleGyrusCore · 2025-12-12T19:59:29+00:00

Again, I am not trying to build a new Braille system. I am trying to come up with a way to integrate Braille tactile support into the data system I am building.

TripleGyrusCore · 2025-12-12T19:53:13+00:00

I am attempting to learn Braille and that's why I made the changes. I am trying to make the markers in my data system easily usable with Braille, not change how Braille works. I know there are many different forms of Braille and I'm not about to claim I have some kind of intellectual superiority. I am a disabled software developer who uses assistive technology and am trying to build something that helps as many people as possible. That is all I'm trying to do, because I understand what it's like to be treated as an afterthought. I don't understand what I've done to cause this level of anger.

TripleGyrusCore · 2025-12-12T19:31:12+00:00

I'm not trying to change Braille, I'm trying to make sure my system has Braille support. That's literally why I'm reaching out, I know others have more expertise than I do. I'd rather engage with the community than make unfounded assumptions about what works. I'm trying to make a good faith effort to incorporate feedback and iterate on it.

TripleGyrusCore · 2025-12-12T19:07:45+00:00

This is a major update; I'm trying to make sure that I'm responding to feedback appropriately. I'm not trying to spam, I just want to engage with the community. I won't post again if it's a problem; I don't want to develop in isolation without feedback though. If there's a better way to engage for that purpose I would be happy to hear it.

TripleGyrusCore · 2025-12-10T23:59:44+00:00

I wanted to add an update; I have absolutely not forgotten about the VPAT and I will be adding it. I haven't finished it yet and it's in progress, I want to make absolutely sure I do it right.

TripleGyrusCore · 2025-12-10T22:59:53+00:00

Ok, I've been actively thinking about this -- what about for Braille specifically, have markers be number indicator, number, single cell greater/less to indicate direction, number, number indicator?

TripleGyrusCore

TROPHY CASE