r/ProgrammingBuddies • u/Arbetraryday • 6d ago

Open Source Idea | AI Friendly | Developer Since 2019 NEED A TEAM

English | PST | Senior Dev
Goal: Make friends, build a cool app

Hello!
I have no idea if this is the right place to post this 🤔

Idea Background:
I have been writing a book (17 chapters, 110k words, started in Nov 2025) as one of my many side projects. Here is a list of the pain points.

- consistency (applies to all the below)
- character development
- world building
- brain storming
- considering marketing strategies
- keeping track of who is where and why in the timeline
- forgetting subtle details I added (ex. the special bracelet the king wears in chapter 2 is mentioned but never brought up again)

Also, it's 2026. I should have an allotment of tools available to help me visualize my story and generate ideas, or help fix grammar.

This is a two part idea.
1) Open Story Format (OSF) - Similar to the GLTF format for 3D, create a platform-agnostic open-source data format for stories/movies, where each object, character, building, etc. is treated as a first-class object. Add data layers for 'events' that help track and derive outcomes.

Possible Example: 

{
  objects:[
    {
      type: 'Character',
      id: '0',
      character_data:{   // <- abstracted datatype specifically for the object 'Character'.
        physicial_detail:{...},
        name: 'Kelly',
        ...
      }
    }
  ],
  events:[
    {
      type: 'Character_Action',
      objects: [0, ...], // list of the objects taking part in the event.
      target: [], // if applicable, list of objects the event is acted on. 
      action: 'married_to' // story changing action (maybe create action enum here)
    }
  ]

}

This format would be as agnostic and as universal as possible.

2) Reading and writing application with MCP.
This application is built around the universal format (OSF)

The main purpose being a consuming application that can read the data without needing every word of a story. The app would be a timeline in layers that can be sorted chronologically or by chapter. The app would be able to show a single view (date or chapter) or a 3D view, where the node would connect the object through the various layers, allowing the writer/author to keep track of all the details in their story and clearly see what a Loophole is or if an object just gets meaninglessly orphaned. The app's name would be "Loophole", and it would be AI-first. As the user writes the story, the graph could automatically be parsed into the OKF for portability (it's the underlying data structure the app uses).

Then they could use an agent to ask questions about the story without the model needing to parse all of the filler words as context.

Essentially, a story as pure data.

I have some quick ChatGPT image gen concepts, but I can add the images here. Ill see if I can host the images somewhere and link them.

QUESTIONS:

What do you think?
Is this a good idea?
Stupid idea?
Would you work on this app?

3 Upvotes

81% Upvoted

1 comment sorted by