[TO-DO] determine a "possible" schema and implement persistent chain

[Sing-Li]

Experiment with Llama3.2-vision and/or Llama3.3-vision to determine the elements that can be (somewhat) reliably detected on a variety of receipts.

Based on the above define a "schema" (in JSON?) that represents a receipt. Make it a superset of what can be detected (not every element needs to be reliably detected).

Implement, on top of App Engine's persistence service, the ability to persist a collection of such schemas. Make the mechanism flexible for all possible applications by using linked chain or doubly linked chain (or even 3D linking mechanism).

[KrishnaShuk]

"Make the mechanism flexible for all possible applications by using linked chain or doubly linked chain (or even 3D linking mechanism)." -- can you elaborate more?

[Sing-Li]

Sure. But first, please investigate into what "our persistent mechanism" is. Try some persistent code yourself in an app.

Then if you still have this question, please come back and elaborate on your question.

[KrishnaShuk]

Okay. Checking persistent storage docs.

[4shb0rne]

since this is one of core thing of this project, should we answer it here or is this just as a [To Do] for us to find out and write it later as part of the proposal ?

[Sing-Li]

Looking for actual implementation. Welcoming PRs.

The thing to realize that a single "chaining" implementation does not reduce what you can have in your proposals, in fact it should increase the possibilities.

For example, we can have a "chain by date" PR here; while your proposal can cover "chain by date" as well as "chain by category" and "chain by ....".

Another axis is ... can the management of these chains be done by a clever prompt instead of fragile complex code?