The operating contract
in plain sight.

First-release boundary

The limited-preview scope is a tenant-wide SharePoint Framework (SPFx) package with a Copilot Component, a page web part and a list command, backed by SharePoint lists you own. It starts with a ticket that is already in your queue. The signed-in operator uses their existing SharePoint permissions to read the evidence and edit a proposal whose lines are marked observed or inferred. After approval, the package applies one exact change with the ticket’s version check. A fresh SharePoint readback records whether the ticket now reads as approved. Approvals happen in the Copilot card or from the tickets list's command bar; the first release does not deliver approvals through Teams or Agent 365.

Data boundary

Tickets, proposals, approvals, decisions and run records remain in your SharePoint lists; nothing is sent to Celest. Microsoft 365 Copilot reads the queue the component shows it and proposes one exact change as tool arguments, under your Microsoft agreements. Celest holds no SharePoint credential, no copy of a ticket and no service in the path. The privacy notice lists what setup creates in your tenant and how to remove it.

The loop

Two cards carry every ticket, wherever the operator meets them: in Microsoft 365 Copilot or from the tickets list’s command bar; a SharePoint page shows the queue and the setup card.

1. 01
   Queue

   The tickets awaiting triage, with the reason each one stalled; the routing vocabulary your desk uses goes to Copilot with the queue.

2. 02
   Proposal

   One exact change, field by field, before and after, with evidence marked observed or inferred, what is still missing, a rationale and a confidence. Every field is editable.

3. 03
   Approval

   A person approves or denies in the card. Nothing is applied until then.

4. 04
   One update

   The package writes the approved fields with the ticket’s version check; a ticket someone changed meanwhile is refused, not overwritten.

5. 05
   Readback

   The package reads the ticket back and records verified, stale, diverged, indeterminate or failed on the run row, with who decided and when.

Receipt contract

Every decision, approved or denied, becomes a row in the Celest Triage Runs list: the ticket, the proposal as shown, the change as approved, who decided and when, the write’s result and the readback. A denial changes nothing on the ticket. The card shows the same receipt the moment it exists: verified, stale, diverged, indeterminate or failed, and what the ticket now reads.

Statuses and receipts

New · In Progress · Resolved

Statuses your list carries on its own; an approved proposal replaces whichever one the ticket had with Triaged.

Awaiting triage

A status a ticket may carry; the queue lists every ticket with an exception reason and confidence, whatever its status.

Triaged

A person approved a proposal and the write was read back.

Receipt: verified

The readback matches the approved change.

Receipt: stale

The ticket changed before the write; nothing was applied.

Receipt: diverged

The write went through but the readback differs; the run row records what it read.

Receipt: failed

SharePoint rejected the write for a reason other than its version; nothing was applied and nothing is retried.

Receipt: indeterminate

The readback could not be completed, or the receipt itself could not be written; the card says so and the operator checks the ticket.

Product limits

• No mail, autonomous or drafted-and-sent: the reply to the requester stays a draft.
• No closing tickets.
• No creating tickets during triage; the only tickets the package creates are the eight fictional samples you can add from the setup card.
• No changes an operator did not approve, and no “while you are there” changes.
• No approvals delivered through Teams or Agent 365 in the first release.
• No Celest service, key or data path: it runs in your tenant only.

Pricing and availability

Free during the preview. The Microsoft marketplace listing is prepared for SPFx 1.24 general availability; until then the package installs from your own tenant app catalog, and nothing is charged for the preview. Pricing for a later release is not announced.