Vault - v.0.1

Updated: 28th April 2025

Feature Context

This is a build out of vault inspired from our previous demos where we take an opinionated view on the ontology on behalf of the users to make the navigation experience of the documents much more delightful & faster.

Future states of Vault

In the future states of the vault we will have:

• More data: much more data e.g. more public data (8-Ks etc.), alternative data (podcasts youtube videos and more), private data (sellside reports etc.)
• More opinionated ontologies: each set of data can be sliced even further to provide a much better experience ahead of the user 'diving' into a given document e.g. sellside reports can be aggregated to have a 'Buy' 'Sell' tag to get the broker's view on the equity
• More liveliness: as new data enters the system the vault will update but importantly there can be constantly changing summaries to make it easier to get TLDRs on information ahead of diving in.

Note: This version is also helpful internally for us to test out the supabase/loveable integrations AND also check for any data incompleteness on an interface. None of this is dummy data, it's the data we currently have. As we add more data to the db, that vault will update. As we add more equities, that vault will automatically update.

Open questions:

• User journey to QA: How does the vault user journey connect to the user QA journey? There must be a link to 'ah I these documents' > I want this synthesised and/or find specific pieces of information
  • Thought: I can see a world where a lot is built around the vault (and starts naturally from the vault)
• Consultancy: if we go down the consultancy route, how will we structure it the way to position this? Building a functional software vs one where we can update as the user asks is very different (latter gives more lenience on time, former requires a lot more performance guarantees from the get go)

Vault - v.0.1

Link: Vault

Features

• Public Data + Wissen Ontology: the user can see a much more nicely sliced data that is more intuitive
• Document Viewer: When the user wants to see a PDF, it'll open into a "document viewer" mode
• Auto-updating Vault UI: as we add more data (equites or within equities) into supabase, this vault interface will update
• Content name search: You can search for the content name

To dos:

• UI clean-ups: vertical scrolling is odd in many places
• More data: as we add more data, the vault will be more fleshed out
• Supabsae Edge functions: need to study a bit more into the supabase edge functions to see if this is the way we can add more 'complex' actions from our APIs whilst releasing that to our frontend/db