A customer's view of what was promised
Cut as a family workflow: it stays a CommitOps feature. The CommitOps ledger exists; the shared page and delivery evidence per promise are not built.
Use case
A customer's view of what was promised: a workflow across CommitOps, RepoOps that starts from a person publishes the page, then it refreshes daily.
Who would use it
Customer teams and the customers they serve.
What value it provides
A shared page per customer with each promise, its state and what shipped, published only after a person approves it.
Why it matters to the user
One page replaces a thread of status emails, and the customer sees the same truth the team sees.
The problem
Customers ask when it will ship by email, and the answers drift between people.
Expected outcomes
- Status emails per account per month
- Promises shown with delivery evidence
Each run records its outcome as met, not met or not measured.
How it runs
Products and connections
| Product | Role in this workflow | Docs |
|---|---|---|
| CommitOps | List the customer's promises (list_assertions); Build the page | Reference · CommitOps docs |
| RepoOps | Attach delivery evidence per promise | Reference · RepoOps docs |
Outside the family: GitHub.
What a person approves
| Action | Default risk |
|---|---|
commitops.page.publish | high |
Action keys are from the PromptCompute catalog.
How to access it from an agent
No run to start. Cut as a family workflow: it stays a CommitOps feature.
Call the products yourself, step by step:
| Product | Endpoint | Tools |
|---|---|---|
| CommitOps | https://commitops.ai/api/mcp | whoami list_assertions get_assertion promised_not_started |
| RepoOps | https://mcp.repoops.ai/mcp | search_brain get_pre_edit_context propose_brain_entry get_incident_attribution |