Concepts
The engine
How Qualia produces a briefing from an actor.
The engine processes actors asynchronously and writes the briefing to the actor record.
The loop
- Ingest.
POST /v1/actorscreates the actor and enqueues an enrichment job. - Research. The engine fans out in parallel across public sources: company filings, product launches, LinkedIn activity, hiring indicators, technical footprint, press coverage.
- Reason. A reasoning model synthesizes the evidence into a single decision.
- Deliver. The briefing lands on the actor record. Read it with
GET /v1/actors/{actorId}oncestatusisenriched.
Lifecycle
The status field on getActor reflects where the actor is in the loop.
| Status | Meaning |
|---|---|
pending | Actor row written; the enrichment job is queued but has not been picked up yet. |
enriching | A worker is running the engine against this actor. |
enriched | Terminal success state. enrichment and intelligence are populated. |
failed | Terminal failure state. Contact support with the actor id if needed. |
Performance
Enrichment runs asynchronously. POST /v1/actors returns immediately with the actor id. Poll the actor until status is enriched (success) or failed (terminal failure).
Next
- Briefings. The shape of the JSON the engine writes.
getActorreference. The polling endpoint.