# Service Checklist

### Gaby as a standalone app summary Checklist

The following table defines the initial architecture checklist for the API server / Model tuning behind Gaby's available services as the final product.

<details>

<summary>Gaby Application Services</summary>

| Action                                                                           | Description                                                                                 | Multi-agent network? Which platform?         | Gaby Feedback loop? i.e. whether this collected data is used in Gaby’s reward based learning system | Gaby ML models required? How many?                                                                                                         | Data (e.g. Insight) Cache required? i.e. Whether the fortnightly insights are cached in a database. | LLM Prompt Stack Required? How many?    | Gaby Temporal Memory required? (Temporal - in the last 2-4 weeks) | Gaby Long Term Memory required? |
| -------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------- | -------------------------------------------- | --------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------- | --------------------------------------- | ----------------------------------------------------------------- | ------------------------------- |
| Data Quality Summary / Sprint Dashboard                                          | Multi-agent Connection + Retrieve Data fields metrics and score (based on custom benchmark) | Yes, dependent database                      | No                                                                                                  | No                                                                                                                                         | Yes                                                                                                 | Yes, 3                                  | Yes                                                               | Yes                             |
| Software Team Summary / Sprint Dashboard e.g. Software Developer team, Data team | e.g. Team Members Work Progression per sprint                                               | Yes, Jira, Slack.                            | No                                                                                                  | No                                                                                                                                         | No                                                                                                  | Yes, 3                                  | Yes                                                               | Yes                             |
| Finance Reporting & Accounting                                                   | Company’s Ingoing and outgoing                                                              | Maybe                                        | No                                                                                                  | No                                                                                                                                         | Yes                                                                                                 | Yes                                     | Yes                                                               | Yes                             |
| Engagement & Behavior                                                            | --                                                                                          | No                                           | Yes                                                                                                 | Yes, 2 → human behavior mimicing, human inferencing,                                                                                       | Yes                                                                                                 | Yes, minimum 5 and 1 for backup \[Base] | No                                                                | Yes                             |
| Entire Company Tech Stack Projects / Database                                    | Company’s general monitoring                                                                | Yes, Jira, Slack, Github, Notion, Confluence | Yes                                                                                                 | Yes, 2 → Recommendation system built on Temporal memory for faster data retrieval specific to the company, Entity graph of company’s users | Yes                                                                                                 | No                                      | Yes                                                               | Yes                             |
| End of Week Documentation for employee / teams                                   | Recommendation system that is used to store                                                 | Yes, Typeform, Notion, Confluence etc.       | No                                                                                                  | Yes, 1 → Recommendation System                                                                                                             | Yes                                                                                                 | Yes, \~5                                | Yes                                                               | Yes                             |

</details>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://whoamimi.gitbook.io/blog/projects/readme-1/backend-api/service-checklist.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.