CereX Change Approval Guard

Inspiration

Manufacturing master-data approvals often happen in a ticket, but the approver still has to spot a missing supplier identifier, a weak justification, or sensitive bank-detail changes. A convincing summary is not enough: reviewers need a traceable evidence gate before making their own decision.

What it does

CereX Change Approval Guard adds a read-only Forge Jira issue panel to supplier-change tickets. One click retrieves the current Jira issue through the signed-in user's Jira permissions and checks whether the evidence required for human review is present.

The panel returns HOLD_FOR_REVIEW with explicit risk codes (missing BP ID, weak justification, absent evidence reference, sensitive bank change without a second reviewer, or a closed issue) or READY_FOR_HUMAN_REVIEW. Importantly, ready never means approved: humans must inspect the original evidence. There are zero Jira, SAP, bank, or supplier-data writes.

How we built it

The Codegeist-specific app uses Atlassian Forge, a native Jira issue panel and resolver, authenticated Jira REST reads, and a deterministic, reviewable supplier-change policy. The Forge manifest also defines a Rovo agent/action, but a real Rovo invocation has not yet been independently demonstrated and is not claimed as completed.

Existing CereX computer-use work predates this contest; the purpose-built Forge change-approval module was started on November 6, 2026. The new app is deployed to Forge production and development and installed on a separate Jira Cloud developer tenant. No corporate or real supplier master data were used.

What works today

Official Forge app ID: 6bc75079-c499-48fe-8288-7f593bea5a6c
33/33 local automated policy and contract tests passed, including unauthorized Jira access and a regression for ADF hard-break formatting.
The actual Forge panel on synthetic Jira issue CLSD-6 returned READY_FOR_HUMAN_REVIEW for complete metadata after correcting an ADF parser defect.
Forge lint reported no issues; both production and development deployments and Jira test-site installations are verified.
A signed, shareable Jira installation URL and reproducible testing steps are provided in the submission.

Challenges and what we learned

A mocked Jira response does not prove the installed integration. Live testing revealed that Jira ADF hardBreak nodes were collapsing multiple fields into one line and incorrectly causing a hold. We fixed the parser, added regression coverage, redeployed, and verified the result in the real Jira panel. Another lesson: a reference to a document does not prove that document is authentic; the app deliberately preserves human review.

What's next

Verify the Rovo action end-to-end before claiming an agent feature, expand real-tenant negative-case testing, improve the judge installation flow, and add authenticated evidence integrity checks. Current scope is a functional, read-only Jira reviewer—not an autonomous approval system.

Live demo: https://youtu.be/Ka9nIMPryZ4

Source and reproducible judge guide: https://github.com/sahamgorengancuan-prog/cerex/tree/competition/codegeist-2026