{
  "id": 6170416,
  "title": "A coding agent can request a discount. Who gets to approve it?",
  "url": "https://urgent.news/2026/09/07/a-coding-agent-can-request-a-discount-who-gets-to-approve-it",
  "topic": "ai",
  "section": "AI",
  "published": "2026-09-07T20:53:52.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/dpelleri/a-coding-agent-can-request-a-discount-who-gets-to-approve-it-3h07"
  },
  "original_language": "en",
  "account": "When a synthetic customer requests 30 seats on an Enterprise Plan, they ask for a 25% discount. The existing policy permits automatic approval for requests up to 10%. For requests greater than 10%, but up to 50%, a user decision is required before approval. To test this, a demo using the open-source Accordo framework is set up. The customer's request is submitted, and the system freezes a commercial snapshot, placing it in the \"pending_approval\" state. An HTTP 403 response is returned, indicating human approval is required. If a simulated user approves the request, the quote is marked as approved, with one user decision audit and a completed trace. The submission remains unchanged, and the original snapshot and business audit entry are not added. The refusal and approval records can be inspected, showing distinct traces for each outcome. The local database remains intact and can be replayed with a new target directory. This process does not require any authentication or explicit authorization from a person. Future implementation will need verified identity and explicit authorization configuration. The source code is available for review and adaptation, keeping the refusal checks intact. Accordo vendors source into the project, allowing for review and adaptation of the rules while maintaining the distinction between refusal and approval. The full walkthrough includes a client brief and recorded execution. Three teams with a real quoting or approval process are sought for a bounded pilot, provided they have a relevant process and rule to follow. Confidential information is omitted.",
  "summary": "An approval rule becomes useful when you can test what happens on both sides of it: the forbidden action is refused, and the permitted decision leaves evidence. A happy-path demo alone cannot show that distinction. Here is a runnable example using Accordo, the open-source framework coding agents use to build custom CRMs. A synthetic customer wants 30 seats of an Enterprise Plan and requests 25%…",
  "key_points": [
    "Requests over 10% discount require user decision for approval",
    "System freezes request in pendingapproval state with HTTP 403",
    "Future implementation needs verified identity and explicit authorization"
  ],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}