Details

Flows are prebuilt or commonly generated flows. What you may have thought of as an "app" in the past is a "Flow" in Colibri due to the fact that we do not build the aplication but rather just choose the flow. In this doc we are not discussing the flow feature as that is part of the library, rather we are focued on the internal flows we will prebuild in order to proide users and our internal team with some core capabilities.

Task Chat Branch API

note

These details are only updated with each release, for more acurate updates and keeping track of progress, see the task in GitHub.

---

Feature Details

Team

Owner	Lead
Mendy	Sergey

Status

Doc Status	Product Status	Last Update	Version	Release	Phase
In Progress	Up Next	04.03.2024	0.01	Internal	Alpha

---

Description

Reminders

Links & Resources

Research

Research

note

the research listed here is spesifict to the Chat feature, for research related to the general Colibri development see the Research document.

Technical

---

Question - Answer -

Conclusion -

Sources

• [test]

---

Business

User Details

User Stories

Persona One

Update Coming Soon

Flows

Personas

Libraries

Libraries

Below is a list of libraries that will be utilized in order to deliver the best Action Flow and UX Flow to the user.

• Actions

  Each Action is one function, could be thought an endpoint or directly built into colibri, published by Colibri or third party.

• Stacks

  Stacks are a compelation of actions, while actions are custome built by the user or generated by Colibri, the Stacks Library will store commenly used or "Templated" Stacks. These can be used directly, edited to custome usecaes and even used to train Colibri.

• Components

  The Component library is what enables Colibri to generate the UX Flow, it can also be used by third party devs to create Apps, as well as to create drag and drop usecaes.

• Assets

  The Assets Libarary enables our marketplace, allowing colibri to plan and maintain assets, this is difirent from asset managment apps, while one might use an app to manage thier own assets, the library allows those apps to search and utilize assets that the user needs, apps can also add assets to the library, physical or digital.

• Goods & services

  Goods work similar to assets but spesifictly for goods and servies being sold, retail, holsale, b2c, b2b, etc.

• Apps

  All the apps avalible to Colibri, the app is a file detailing each screen, what component and actions to use from ther respective library.

Features

Features

Below is a list of features that will be utilized in order to deliver the best account features and functionalities. The details bellow are not comprehensive feature details but rather, describe how the features will be utilized within the account, for further details, please see the individual feature documentation.

• Access

  If the account type is not "indiviual" the account will not have an auth method and thefore will reqesre access. This will be a sub-collection within the account document that will hold the account, group, etc IDs of anyone who has access to this account.

Data

On the document we want to keep all the important data, the first fetch and fast to access, all secondary data should be stored on a subcollection and fetch sepratly (if this is cost sfective)

User Accounts should be a top level collection, each account will generate a new document within the "Accounts" collection.

Endpoint

- Endpoints
- - endpoint 1
- - - type 
- - - apiName
- - - apiUrl
- - - pricing
- - - docsUrl
- - - use case
- - - exclusive (true, false)
- - - open (true, false) is it for apps only or open to Colibri

Endpoint