Fautore Implementation Plan

Fautore development could go any of many ways. Rather than rushing to getting rough functionality in place that we would need to go back and rework to actually bring the framework in line, we have chosen to use the Email Agent as a pilot use case to build the framework around. This will provide us a real world example to design towards and give us something "real" to test as we go as well.

The email agent isn't listed in the development plan. It is just understood it will progress in parallel with the rest of the Fautore process. As each below feature moves forward we will advance the email agent as far as we can and then pick up work on the next element. This will be true of each individual API. We'll develope the entire API JSON engine, but not every specific API before advancing the Email Agent.

Member Management: A reasonable proving ground for testing out our database and screen building strategies. We'll also need to have users operating in the tool so we can test the legitimate interfaces for using infrastructure and ancillary components as they are developed.

API Engine: Once we can communicate with Fautore we need to give it a method of actually speaking to the world. The API engine will process our JSON. Having the "Comms" mouth is one thing, but we need to have the API voicebox in place to really facilitate communication.

Create JSON server
Then we move to it taking in a specific message, probably the "Registration request" message.

API Development: This is where using the Email Agent as a driving force will really shine as a strategy. As we work to actually make the agent functional we will be finding out the API's beyond the obvious onces that we really need to make things happen. Out of the below list of obvious APIS's the "fau_register" call will be the first devloped to support the email agent registering itself properly.

Oh, hey... you'll need to stop right there. I'm afraid you not allowed to see that at the moment. Please do drop us a note and we'll fix you right up. (Provided you not some mean ass saboture, then we'll be fixen yo up a whole different way)

Config Screen: Once the registration API is complete and the email agent can register itself wethen need the application configuration facility to be put in place. This enables the Application Manager, (first this will just be the Chieftain, and we will then evolve to enabling whoever has permissions t become an application manager) to make the email client fully operational from the fautore interfaces.

API fau_push: Once we can configure the Email Agent settings in Fautore weill need to focus on completing the agent. To do this we'll need the fau_push API to make the agent fully operational.

Fautore Comms: Nothing talks to Fautore without Comms working. If nothing talks to fautore nothing gets done, we can't even register anything from which to collect data. Once we have the primary data transfer protocol functioning using the Email Agent we can turn our attention to using it for Fautore-to-Fautore (FtF) communications and get the encrytion strategy going.