Skip to main content

Context Curation

Private preview

Context Curation is currently in private preview and may not be enabled for your organization. Contact your Promethium representative for access.

What is Context Curation?​

The 360° Context Hub is only as good as the context in it. Context Curation is how that context grows from your source material: Mantra's context curator reads what you give it and proposes new or updated business context, grounded in what it read.

Nothing the curator proposes is applied automatically. Every proposal pauses for human review, and context changes only when a reviewer accepts them. See Reviewing Proposals.

What the curator proposes​

  • Business rules — definitions of terms and metrics, aggregation and filtering conventions, and disambiguations (for example, which date field "fiscal year" refers to)
  • Table descriptions — what a table contains and represents, its grain, etc.
  • Column descriptions — what a column means, its units, and how to interpret it
  • Relationships — how two tables join, and on which keys

Every proposal carries its evidence: why the curator is confident, the level of confidence, and the evidence it draws from. When a proposal would change context that already exists, it is presented against the current version, either as an update or as a conflict.

Uploading a document​

From the Context Hub, open Upload Documents:

  1. Choose a document — PDF, DOCX, Markdown, or plain text, up to 25MB.
  2. Describe how the content should be interpreted: what the document contains and what the curator should take from it (for example, "Quarterly revenue definitions and the metrics finance reports on"). The description is required — it steers the curator's focus.
  3. Upload. The curator reads the document and drafts its proposals; anything it proposes appears in Context Review.
note

Uploading documents requires a role with document upload access. If you don't see the option, ask your administrator.

Tracking a document's progress​

Your uploaded documents are listed with a status that follows the work:

StatusMeaning
Processing stagesThe document is being received, parsed, and indexed
CuratingThe curator is reading the document and drafting proposals
In reviewA batch of proposals is waiting on a reviewer — the status links straight to it
ProcessedThe run is complete and nothing is awaiting review
FailedThe document couldn't be processed; the reason is shown with the status

Review threads​

Each curation run is a conversation — a review thread — between the curator and its reviewers:

  1. The curator proposes everything it found as one batch of proposals.
  2. Reviewers decide on each proposal. If everything is accepted, the context is applied, to the relevant domain or system-wide, and the thread closes.
  3. If any proposal gets feedback instead, nothing is applied yet. The curator takes the feedback and revises: the next batch in the thread adjusts accordingly — proposals are revised where the feedback applies, kept where it doesn't, and dropped where rejected. Rejected proposals are not re-proposed in the thread.
  4. The revised batch returns for review in the same thread, and the cycle repeats until the reviewer accepts the batch or nothing remains to propose.

In the review queue, a thread reads New when a batch is awaiting a review, Awaiting response while the curator is processing feedback, and Done when the thread has concluded.