Forem: Triple Gyrus Core

Toward Version 2 of Triple Gyrus Core with Community Feedback

Triple Gyrus Core — Mon, 15 Dec 2025 15:27:09 +0000

Early Info About Triple Gyrus Core

Triple Gyrus Core is a data and software system built for accessibility and usability first. After 2 weeks of being live, some important lessons have happened and some invaluable feedback has come from the disability community. So, plans for version 2 are underway, and that new version will be released as soon as possible.

Versioning Strategy for Triple Gyrus Core

Versioning for Triple Gyrus Core is just simple numbers, what you see is what you get. The upcoming version is version 2, and the version after that will be version 3. Since semantic versioning (major, minor, patch) is ambiguous with screen readers, harder to express with speech to text, and has its own structural ambiguities (like where the distinction between a minor version and patch is), Triple Gyrus Core versions will sidestep all that complexity. Version 2 will be the second release, version 3 will be the third, and so on.

Equivalent Triple Markers

The markers in the initial version of Triple Gyrus Core, such as ^+1+1^, were optimized for universal access on all computer keyboards and ease of writing by hand for analog-to-digital conversion. However, in the real world, some confusion and ambiguity occurred. Some OCR didn't handle carets as well as initial tests suggested, and conflicting information about character usage in Braille emerged. The question of why Triple Gyrus Core did not use more traditional markers, like those used in XML or HTML, also came up multiple times. The attempt to create a single accessible representation caused some usability friction.

So, the solution that will be implemented in Triple Gyrus Core version 2 is the ability to have multiple equally valid formats for markers. The premise of Triple Gyrus Core will remain the same: information in triples with contextual information present in each triple.

The original format of ^+1+1^ is still going to exist in Triple Gyrus Core version 2, since is original logic is still valid. However, based on feedback from the community, at least 3 equally valid alternative markers will be implemented: a marker that is reliable across more OCR contexts, a Braille representation of markers, and an HTML/XML style marker. Exactly how these will be implemented is still being worked on; for the sake of flexibility the goal will be to create a way for users to specify marker formats that make the most sense to them, with some formats (like the suggested ones) built into the system by default.

Improvements to Bidirectional Text

The Triple Gyrus Core HTML editor currently forces markers and their content to be on separate visual lines to handle display mangling between left-to-right and right-to-left text. While that works as long as the information inside markers goes in one direction only, information that combines text directions still breaks.

The W3C has acknowledged the usefulness of newline characters as bidirectional separators for some time, as in their Additional Requirements for Bidi in HTML and CSS. This is a technique that has been reliable for managing bidirectional text mangling for over a decade.

So, version 2 of Triple Gyrus Core will enhance text direction detection and extend the same logic that keeps markers on their own lines to any string of text where direction changes. This will be a purely visual enhancement, but is should significantly improve usability for people using right-to-left scripts.

Braille and Tactile Support

One of the most critical pieces of feedback from the community was the understanding that Braille is far richer than it may first appear. Optical character recognition (OCR) often fails with it, optical Braille recognition (OBR) is its own area of study, and tactile support can depend on both the physical peripheral being used and the Braille mode a user prefers.

Due to a current lack of knowledge, Triple Gyrus Core is not equipped to handle all of these complexities yet, especially not without further input from the atypical vision community. However, if you have knowledge or information that would make Triple Gyrus Core better, please don't hesitate to reach out. The point of the system is accessibility and usability first, and there are no better people to provide input than those who actually need those things in their own contexts.

For now, version 2 of Triple Gyrus Core will include a Braille representation of its markers, with cell count minimized, tactile distinctiveness maximized as much as possible, and adherence to Braille norms a primary concern. Just like with the equivalent markers listed above, if there are tactile markers that may work better for some users, please don't hesitate to reach out and state what you need.

Accessibility Compliance Documentation

Version 1 of Triple Gyrus Core did not contain accessibility compliance documentation. To rectify this, Version 2 and every version after that will contain accessibility compliance documentation as part of its Zenodo release, and the documentation will also be present in the project's GitHub repository. A VPAT is currently being built and will be included with version 2. If there are other accessibility compliance documents you would like to see, please reach out so they can be added.

Additional Features

Triple Gyrus Core is also still going to be a full semantic data system and accessible programming language one day. Whether that can happen in version 2 is still uncertain; it may be in version 3 or in a future version. Please be assured, however, that the functionality is coming.

Learning More

If Triple Gyrus Core sounds like something that could help you out with accessibility and data tasks, please feel free to check out the project website or LinkedIn page, and email if you have feedback or are interested in collaborating.

If you have any feedback about Triple Gyrus Core, please reach out! Connecting with the user community is important, and you are why Triple Gyrus Core exists in the first place.

https://triplegyruscore.github.io/
https://www.linkedin.com/in/jsrc-expert/

Turning CSV Files Into Queryable Data With Triple Gyrus Core

Triple Gyrus Core — Mon, 08 Dec 2025 12:24:52 +0000

The Problem With Simple Data

Simple formats like CSV are small and useful to write in the moment, but they're not always as easy to analyze as you might expect. In Python, for example, you need to read an entire file into a dataframe, manipulate columns, spend time making sure your program works. We're used to that. But, Triple Gyrus Core can make your analysis workflow simpler even with formats like CSV.

Let's say you have a CSV file of customer data. It's a pretty standard scenario for a lot of us: 10 rows, 10 customers with IDs, information, and statuses.

customer_id,first_name,last_name,email,phone,city,state,zip_code,signup_date,total_purchases,lifetime_value,status CUST0001,Christopher,Harris,christopher.harris38@email.com,620-260-1810,Phoenix,AZ,37974,9/18/2024,39,774.23,Active CUST0002,Robert,Hernandez,robert.hernandez60@email.com,791-204-2535,Austin,TX,62012,6/25/2024,32,3261,Active CUST0003,Linda,Ramirez,linda.ramirez32@email.com,272-785-5860,San Jose,CA,99615,9/25/2024,21,4474.83,Active CUST0004,Patricia,Jackson,patricia.jackson98@email.com,717-655-7031,Charlotte,NC,83429,1/24/2025,24,3904.34,Inactive CUST0005,Richard,Harris,richard.harris71@email.com,532-426-7413,Houston,TX,44001,3/17/2024,17,3405.2,Active CUST0006,Christopher,Williams,christopher.williams92@email.com,348-848-3768,Fort Worth,TX,40502,1/8/2024,37,2092.87,Active CUST0007,Michael,Johnson,michael.johnson53@email.com,781-919-6949,Philadelphia,PA,36561,1/17/2024,44,4786.74,Active CUST0008,Elizabeth,Martinez,elizabeth.martinez11@email.com,732-377-1291,Charlotte,NC,44410,2/21/2024,42,3954.51,Active CUST0009,Christopher,Jones,christopher.jones27@email.com,857-341-9173,Denver,CO,94083,1/10/2025,5,4695.04,Inctive CUST0010,Charles,Taylor,charles.taylor43@email.com,784-955-8711,San Diego,CA,19332,9/8/2025,30,4760.35,Active

But, looking at this block of text, how well can you read and analyze it without programming help, really? How would something like a screen reader handle it? The answer to both of those questions is "not very well."

Triple Gyrus Core As Analysis Prep

That's where Triple Gyrus Core comes in. You can easily open your CSV in the spreadsheet program of your choice and add in Triple Gyrus Core markup:

And now your data is ready for analysis, no program maintenance or library dependence needed.

And here's where the magic happens -- Triple Gyrus Core's syntax is so regular and predictable that AI not only understands it perfectly but can use your marked up data as a springboard. Pop this marked up data into your favorite AI (you might need to give it the Triple Gyrus Core spec on Zenodo too if the AI hasn't slurped it up yet) with this prompt:

Please identify the Triple Gyrus Core markup in this document and generate markup for every cell.

And AI will give you this:

`^+1+1^ customers example ^+1+1^ ^+1+2^ 42 ^+1+2^ ^+1+3^ ^^1^^ ^+1+3^

^+1+5^ customer_id ^+1+5^ ^+1+2^ 42 ^+1+2^ ^+1+6^ header customer_id ^+1+6^
^+1+5^ first_name ^+1+5^ ^+1+2^ 42 ^+1+2^ ^+1+6^ header first_name ^+1+6^
^+1+5^ last_name ^+1+5^ ^+1+2^ 42 ^+1+2^ ^+1+6^ header last_name ^+1+6^
^+1+5^ email ^+1+5^ ^+1+2^ 42 ^+1+2^ ^+1+6^ header email ^+1+6^
^+1+5^ phone ^+1+5^ ^+1+2^ 42 ^+1+2^ ^+1+6^ header phone ^+1+6^
^+1+5^ city ^+1+5^ ^+1+2^ 42 ^+1+2^ ^+1+6^ header city ^+1+6^
^+1+5^ state ^+1+5^ ^+1+2^ 42 ^+1+2^ ^+1+6^ header state ^+1+6^
^+1+5^ zip_code ^+1+5^ ^+1+2^ 42 ^+1+2^ ^+1+6^ header zip_code ^+1+6^
^+1+5^ signup_date ^+1+5^ ^+1+2^ 42 ^+1+2^ ^+1+6^ header signup_date ^+1+6^
^+1+5^ total_purchases ^+1+5^ ^+1+2^ 42 ^+1+2^ ^+1+6^ header total_purchases ^+1+6^
^+1+5^ lifetime_value ^+1+5^ ^+1+2^ 42 ^+1+2^ ^+1+6^ header lifetime_value ^+1+6^
^+1+5^ status ^+1+5^ ^+1+2^ 42 ^+1+2^ ^+1+6^ header status ^+1+6^

^+1+5^ CUST0001 ^+1+5^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 1 customer_id ^+1+6^
^+1+5^ Christopher ^+1+5^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 1 first_name ^+1+6^
^+1+5^ Harris ^+1+5^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 1 last_name ^+1+6^
^+1+5^ christopher.harris38@email.com ^+1+5^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 1 email ^+1+6^
^+1+5^ 620-260-1810 ^+1+5^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 1 phone ^+1+6^
^+1+5^ Phoenix ^+1+5^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 1 city ^+1+6^
^+1+5^ AZ ^+1+5^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 1 state ^+1+6^
^+1+4^ 37974 ^+1+4^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 1 zip_code ^+1+6^
^+1+5^ 9/18/2024 ^+1+5^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 1 signup_date ^+1+6^
^+1+4^ 39 ^+1+4^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 1 total_purchases ^+1+6^
^+1+4^ 774.23 ^+1+4^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 1 lifetime_value ^+1+6^
^+1+5^ Active ^+1+5^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 1 status ^+1+6^

^+1+5^ CUST0002 ^+1+5^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 2 customer_id ^+1+6^
^+1+5^ Robert ^+1+5^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 2 first_name ^+1+6^
^+1+5^ Hernandez ^+1+5^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 2 last_name ^+1+6^
^+1+5^ robert.hernandez60@email.com ^+1+5^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 2 email ^+1+6^
^+1+5^ 791-204-2535 ^+1+5^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 2 phone ^+1+6^
^+1+5^ Austin ^+1+5^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 2 city ^+1+6^
^+1+5^ TX ^+1+5^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 2 state ^+1+6^
^+1+4^ 62012 ^+1+4^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 2 zip_code ^+1+6^
^+1+5^ 6/25/2024 ^+1+5^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 2 signup_date ^+1+6^
^+1+4^ 32 ^+1+4^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 2 total_purchases ^+1+6^
^+1+4^ 3261 ^+1+4^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 2 lifetime_value ^+1+6^
^+1+5^ Active ^+1+5^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 2 status ^+1+6^

^+1+5^ CUST0003 ^+1+5^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 3 customer_id ^+1+6^
^+1+5^ Linda ^+1+5^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 3 first_name ^+1+6^
^+1+5^ Ramirez ^+1+5^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 3 last_name ^+1+6^
^+1+5^ linda.ramirez32@email.com ^+1+5^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 3 email ^+1+6^
^+1+5^ 272-785-5860 ^+1+5^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 3 phone ^+1+6^
^+1+5^ San Jose ^+1+5^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 3 city ^+1+6^
^+1+5^ CA ^+1+5^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 3 state ^+1+6^
^+1+4^ 99615 ^+1+4^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 3 zip_code ^+1+6^
^+1+5^ 9/25/2024 ^+1+5^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 3 signup_date ^+1+6^
^+1+4^ 21 ^+1+4^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 3 total_purchases ^+1+6^
^+1+4^ 4474.83 ^+1+4^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 3 lifetime_value ^+1+6^
^+1+5^ Active ^+1+5^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 3 status ^+1+6^

^+1+5^ CUST0004 ^+1+5^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 4 customer_id ^+1+6^
^+1+5^ Patricia ^+1+5^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 4 first_name ^+1+6^
^+1+5^ Jackson ^+1+5^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 4 last_name ^+1+6^
^+1+5^ patricia.jackson98@email.com ^+1+5^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 4 email ^+1+6^
^+1+5^ 717-655-7031 ^+1+5^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 4 phone ^+1+6^
^+1+5^ Charlotte ^+1+5^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 4 city ^+1+6^
^+1+5^ NC ^+1+5^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 4 state ^+1+6^
^+1+4^ 83429 ^+1+4^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 4 zip_code ^+1+6^
^+1+5^ 1/24/2025 ^+1+5^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 4 signup_date ^+1+6^
^+1+4^ 24 ^+1+4^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 4 total_purchases ^+1+6^
^+1+4^ 3904.34 ^+1+4^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 4 lifetime_value ^+1+6^
^+1+5^ Active ^+1+5^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 4 status ^+1+6^

^+1+5^ CUST0005 ^+1+5^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 5 customer_id ^+1+6^
^+1+5^ Richard ^+1+5^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 5 first_name ^+1+6^
^+1+5^ Harris ^+1+5^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 5 last_name ^+1+6^
^+1+5^ richard.harris71@email.com ^+1+5^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 5 email ^+1+6^
^+1+5^ 532-426-7413 ^+1+5^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 5 phone ^+1+6^
^+1+5^ Houston ^+1+5^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 5 city ^+1+6^
^+1+5^ TX ^+1+5^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 5 state ^+1+6^
^+1+4^ 44001 ^+1+4^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 5 zip_code ^+1+6^
^+1+5^ 3/17/2024 ^+1+5^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 5 signup_date ^+1+6^
^+1+4^ 17 ^+1+4^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 5 total_purchases ^+1+6^
^+1+4^ 3405.2 ^+1+4^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 5 lifetime_value ^+1+6^
^+1+5^ Active ^+1+5^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 5 status ^+1+6^

^+1+5^ CUST0006 ^+1+5^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 6 customer_id ^+1+6^
^+1+5^ Christopher ^+1+5^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 6 first_name ^+1+6^
^+1+5^ Williams ^+1+5^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 6 last_name ^+1+6^
^+1+5^ christopher.williams92@email.com ^+1+5^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 6 email ^+1+6^
^+1+5^ 348-848-3768 ^+1+5^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 6 phone ^+1+6^
^+1+5^ Fort Worth ^+1+5^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 6 city ^+1+6^
^+1+5^ TX ^+1+5^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 6 state ^+1+6^
^+1+4^ 40502 ^+1+4^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 6 zip_code ^+1+6^
^+1+5^ 1/8/2024 ^+1+5^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 6 signup_date ^+1+6^
^+1+4^ 37 ^+1+4^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 6 total_purchases ^+1+6^
^+1+4^ 2092.87 ^+1+4^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 6 lifetime_value ^+1+6^
^+1+5^ Active ^+1+5^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 6 status ^+1+6^

^+1+5^ CUST0007 ^+1+5^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 7 customer_id ^+1+6^
^+1+5^ Michael ^+1+5^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 7 first_name ^+1+6^
^+1+5^ Johnson ^+1+5^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 7 last_name ^+1+6^
^+1+5^ michael.johnson53@email.com ^+1+5^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 7 email ^+1+6^
^+1+5^ 781-919-6949 ^+1+5^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 7 phone ^+1+6^
^+1+5^ Philadelphia ^+1+5^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 7 city ^+1+6^
^+1+5^ PA ^+1+5^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 7 state ^+1+6^
^+1+4^ 36561 ^+1+4^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 7 zip_code ^+1+6^
^+1+5^ 1/17/2024 ^+1+5^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 7 signup_date ^+1+6^
^+1+4^ 44 ^+1+4^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 7 total_purchases ^+1+6^
^+1+4^ 4786.74 ^+1+4^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 7 lifetime_value ^+1+6^
^+1+5^ Active ^+1+5^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 7 status ^+1+6^

^+1+5^ CUST0008 ^+1+5^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 8 customer_id ^+1+6^
^+1+5^ Elizabeth ^+1+5^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 8 first_name ^+1+6^
^+1+5^ Martinez ^+1+5^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 8 last_name ^+1+6^
^+1+5^ elizabeth.martinez11@email.com ^+1+5^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 8 email ^+1+6^
^+1+5^ 732-377-1291 ^+1+5^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 8 phone ^+1+6^
^+1+5^ Charlotte ^+1+5^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 8 city ^+1+6^
^+1+5^ NC ^+1+5^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 8 state ^+1+6^
^+1+4^ 44410 ^+1+4^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 8 zip_code ^+1+6^
^+1+5^ 2/21/2024 ^+1+5^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 8 signup_date ^+1+6^
^+1+4^ 42 ^+1+4^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 8 total_purchases ^+1+6^
^+1+4^ 3954.51 ^+1+4^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 8 lifetime_value ^+1+6^
^+1+5^ Active ^+1+5^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 8 status ^+1+6^

^+1+5^ CUST0009 ^+1+5^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 9 customer_id ^+1+6^
^+1+5^ Christopher ^+1+5^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 9 first_name ^+1+6^
^+1+5^ Jones ^+1+5^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 9 last_name ^+1+6^
^+1+5^ christopher.jones27@email.com ^+1+5^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 9 email ^+1+6^
^+1+5^ 857-341-9173 ^+1+5^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 9 phone ^+1+6^
^+1+5^ Denver ^+1+5^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 9 city ^+1+6^
^+1+5^ CO ^+1+5^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 9 state ^+1+6^
^+1+4^ 94083 ^+1+4^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 9 zip_code ^+1+6^
^+1+5^ 1/10/2025 ^+1+5^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 9 signup_date ^+1+6^
^+1+4^ 5 ^+1+4^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 9 total_purchases ^+1+6^
^+1+4^ 4695.04 ^+1+4^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 9 lifetime_value ^+1+6^
^+1+5^ Active ^+1+5^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 9 status ^+1+6^

^+1+5^ CUST0010 ^+1+5^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 10 customer_id ^+1+6^
^+1+5^ Charles ^+1+5^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 10 first_name ^+1+6^
^+1+5^ Taylor ^+1+5^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 10 last_name ^+1+6^
^+1+5^ charles.taylor43@email.com ^+1+5^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 10 email ^+1+6^
^+1+5^ 784-955-8711 ^+1+5^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 10 phone ^+1+6^
^+1+5^ San Diego ^+1+5^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 10 city ^+1+6^
^+1+5^ CA ^+1+5^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 10 state ^+1+6^
^+1+4^ 19332 ^+1+4^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 10 zip_code ^+1+6^
^+1+5^ 9/8/2025 ^+1+5^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 10 signup_date ^+1+6^
^+1+4^ 30 ^+1+4^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 10 total_purchases ^+1+6^
^+1+4^ 4760.35 ^+1+4^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 10 lifetime_value ^+1+6^
^+1+5^ Active ^+1+5^ ^+1+2^ 42 ^+1+2^ ^+1+6^ customer 10 status ^+1+6^

^+1+1^ customers example ^+1+1^ ^+1+2^ 42 ^+1+2^ ^+1+3^ ^^2^^ ^+1+3^`

Using Triple Gyrus Core With Data

Now at first I'm sure you're thinking, wait a minute, all we did was turn this from one text format into another more verbose one. And at first glance, yes, that's what we did. But this verbosity unlocks a simpler and faster way to analyze data.

Let's say you want to find every person who has a first name starting with M. No need to use SQL -- just use a quick find in your text editor for "M.*?last_name".

How about something more complicated, like all people with a last name starting with J and a home state of Colorado? Just tweak the regex to "J(?!.J).?last_name.?CO.?state". Much shorter than SELECT last_name, state FROM customers WHERE last_name = "M*" AND state = CO.

Also, you can identify the type of data you're working with, even if you didn't explicitly mark it up that way, because AI is smart enough to do it for you with the prompt you gave it. If you need to find numeric data, simply look for the ^+1+4^ markers.

Once you have your triples, depending on your text editor and your workflow, you can copy the data out of your text editor, move it forward in a pipeline for processing, whatever next step you need.

Effectively, you can use Triple Gyrus Core to turn a CSV file into a pseudo-database without worrying about a database engine, and all you need to do is know how to use a text editor -- no programming or DB knowledge required.

And, as always, Triple Gyrus Core markup is accessible -- people using assistive technologies can read it easily and international teams can use it in their languages, which makes communicating about your data easy.

Learning More

If Triple Gyrus Core sounds like something that could help you out with data tasks like this, please feel free to check out the project website or LinkedIn page, and email if you have feedback or are interested in collaborating.

https://triplegyruscore.github.io/
https://www.linkedin.com/in/jsrc-expert/

Triple Gyrus Core: An Accessible Data and Software System

Triple Gyrus Core — Sun, 07 Dec 2025 17:36:38 +0000

What is Triple Gyrus Core?

Triple Gyrus Core is a data system built from the ground up with accessibility, usability, and international collaboration in mind. More than half a century after programming and data management began their development as fields, modern data formats and programming languages are still largely inaccessible, both to people with disabilities and to people whose knowledge does not fit into the dominant assumptions in those fields.

Triple Gyrus Core was released on the last day of November this year to start making progress toward an accessible, internationalizable, and inclusive computing stack. Version 1 is focused on OCR, pulling data out of tricky file formats like images and scanned PDFs. The format is built for consistency; you can partially mark up a document, then feed it to AI and the AI can correctly create markup that wouldn't otherwise fit, like for the distinct cells of a table.

The major thing that makes Triple Gyrus Core so accessible is its simplicity. It uses only two symbols that are easily recognized by both OCR and assistive technologies: caret and plus sign. It can handle text flowing left to right or right to left and is built using cognitive load principles to reduce reliance on working memory and allow faster creation.

The system has been endorsed by Accessible Me and is in active development on GitHub, with its initial release on Zenodo.

Triple Gyrus Core is in its infancy now, but the goal is for it to become the basis for an accessible computing stack, which has become more important over the last months with accessibility becoming an ISO standard.

Please feel free to check out the project website or LinkedIn page, and email if you have feedback or are interested in collaborating.

https://triplegyruscore.github.io/
https://www.linkedin.com/in/jsrc-expert/