A customer cancels a subscription renewal and unexpectedly loses access to time they already paid for. Trajectory turns that friction into a decision the people responsible for the experience can make without writing code. A guided GitHub issue captures what happened and the desired result. The installed Trajectory GitHub App presents clear outcomes: keep paid access, end it immediately, or propose a prorated refund. Selecting an outcome prepares a corresponding code and configuration change in a reviewable branch and pull request. Changing the decision creates a separate outcome and invalidates the earlier intent confirmation. A Vultr-hosted Go worker uses Vultr Serverless Inference to generate a bounded access-function candidate. A disposable, isolated container runs independent boundary tests; repository-defined assertions and a comparison against the proposed PR tree check the selected change. GitHub Checks connect the issue, choice, patch, test results and evidence for review. A separate containment demonstration tests that a host canary is inaccessible from the sandbox. The demo uses an illustrative customer and a fixed example proposing $18 for 18 unused days. It does not execute a refund or change a real customer account. Verification covers the stated test cases; intent review remains a human step before merge.
Category tags: