Formless is a PoC designed to streamline the client onboarding process, eliminating the need for extensive form filling. This solution leverages user prompts, a fine-tuned OpenAI model, and a Rails application to create client objects and manage user requests related to recently onboarded clients. formless.onrender.com

Users initiate the client onboarding process by providing a simple text prompt:

"Please add a new client called Jane Doe, born 19-02-1989, British, national number is DE3131212, female, 07772772727, their email is [email protected]"

On receiving the user prompt, the fine-tuned AI model springs into action, generating a structured response. In the example provided above, let's say we're onboarding a client named Jane Doe. The AI response is structured as a hash with predefined keys:

• first_name
• middle_name
• last_name
• date_of_birth
• email
• nationality
• national_number
• phone_number
• gender

These keys are populated with data extracted from the original user prompt, forming the AI's response. The values are formatted in the Rails application, date_of_birth becomes DD/MM/YYYY, nationality becomes GBR, using ISO 3166-1 alpha-3.

Once the client data is processed and saved, users can inquire about it using natural language queries such as:

• "What is the name of the last client I created?"
• "How many clients do I have?"

For security and privacy reasons, the AI does not have direct access to the database. Instead, it responds with variable placeholders within the text response it generates, for example:

"Let me check for you. You currently have [GET_CLIENTS_COUNT] clients."

The Rails application interprets these queries and populates the placeholders with real data from the database. Various validation steps are in place throughout this process to ensure data accuracy and security.

• OpenAiRateLimitable: This middleware helps limit and manage OpenAI requests, preventing rate limits from being exceeded. It fetches user session information through Warden and keeps track of the number of user requests made within the last hour.

• Rails Caching: I highly recommend caching and I think it is not used enough in Production environments. I am using caching to store the latest repo release details from the GitHub API (see an example in application_helper.rb). This is to avoid making unnecessary requests to the API with Octokit. The cache is cleared every 24 hours.

A default fake user is assigned to the session, simplifying the application's use. It's important to note that this approach is recommended for the proof of concept phase.

The Formless application relies on several Ruby gems to enhance its functionality:

• Ruby-openai: This gem serves as a client for the OpenAI fine-tuned model.
• Kaminari: It provides straightforward pagination capabilities.
• Rspec: Extensive testing is ensured using RSpec.
• Factorybot-rails: This gem facilitates testing by providing factories for generating test data.
• Sidekiq: Asynchronous workload handling is managed efficiently with Sidekiq.
• Octokit: It enables fetching the latest repository release tags from GitHub.
• Devise: This gem handles user sessions and authentication.

Test-Driven Development is an integral part of the development process. RSpec is used to ensure test coverage across various components, including controller and service object requests, concerns, and additional API/v1 endpoints.

In addition to the standalone application, there are also some api/v1 endpoints where all user prompts can be requested and the api schema documentation can also be retrieved.

Formless is hosted on formless.onrender.com and makes use of the following addons:

• sidekiq-worker: Manages background jobs.
• sidekiq-redis: Supports Sidekiq for asynchronous task processing.
• PostgreSQL 15: The application's database is powered by PostgreSQL 15.

Please note; as part of the deployment process, the formless database is cleaned and re-seeded periodically.

Please refer to this README for an in-depth understanding of Formless and its technical underpinnings.