Data visualisation layer

[Varunram]

Right now, our process for investing is as follows:

1. The investor possesses AnchorUSD and wants to invest in a specific project.
2. Investor sends money to the platform equivalent to his investment in the platform
3. Platform sets up an issuer (solely for the project) if the project hasn't been invested in before and the issuer sends an investment asset to the investor as proof of investment in the project.
4. The platform updates its internal databases inline with on-chain confirmations

Once the project has reached its funding goals,

1. The platform transfers the project's value to an escrow account, a 2/2 multisig with the recipient and platform's pub keys (platform signs by default).
2. The recipient is sent a notification to unlock the project (if the recipient doesn't have the "auto accept" option on)
3. The recipient unlocks the project / the platform does it automatically due to auto unlock and the recipient is sent two types of assets - Payback asset and Debt Asset. The payback asset is sent to the platform by the recipient on payback and is equivalent to the number of months it would take for the recipient to payback (on current rates) and the debt asset is sent by the recipient to the platform for payback of USD equivalent (stable coin / XLM / similar)
4. The platform starts relevant handlers for monitoring different processes.

This entire flow right now is a series of transactions on the blockchain and internal handlers on the platform itself. We need a data viz layer on top of this where investors and recipients can see at which stage their projects are at, somewhat similar to Amazon's package tracker (just that this has blockchain transactions instead of locations and stuff). This would act as a middle layer for people who want to quickly see info on the project without getting too deep into specifics (blockchain, not a blockchain, etc).

It is important to note that this data viz layer would be independent of which solution we're using (legacy / blockchain). As a result, this could be an independent effort in another backend system (eg node.js / python) which could later be integrated into our current workflow.