Core concepts

Colabra becomes easier to use once the object model is clear. Most actions in the product are just different ways of moving between these objects.

Concept	What it is
Workspace	Your team boundary. Owns members, settings, integrations, automation defaults, and reusable configuration.
Project	A single deal. It contains the evidence, findings, entities, tasks, requests, reports, and saved views for that transaction.
File	A piece of evidence. Files are uploaded or synced, then processed into extracted data, entity links, and findings.
Entity	A company, person, facility, or jurisdiction discovered in the evidence and linked into the org-structure and risk model.
Perimeter	The in-scope boundary of the transaction. It lets the team distinguish the entities that matter to the deal from background entities discovered in documents.
Finding	A risk item generated from extracted evidence and evaluated against your diligence guardrails.
Task	A work item used to review, resolve, or follow up on diligence work.
Request	A follow-up ask tied to a task, sent to sell-side or advisers, and tracked through response and resolution.
Report	A written output created manually or generated from a built-in report type.
View	A saved filtered lens over projects, files, entities, or tasks.

How the objects fit together

The basic shape of the product is:

1. A workspace contains many projects.
2. A project contains many files.
3. Files produce entities and findings.
4. Findings and gaps turn into tasks and requests.
5. The team uses views to monitor those objects and reports to publish conclusions.