Repository navigation
Share a decision you ran through Parley #92
Replies: 1 comment 2 replies
|
Thanks for the pointer, Oleh. I ran the README quickstart with parley-consensus 0.2.1 and Python 3.14.8 on macOS (arm64). Your procurement recipe selected Vendor A. I tried a way for a team using Parley to carry that decision into its own purchasing system while keeping control of who can place the order. In a local demo with VATE v0.7.0, the verifier draft I maintain, the buying agent signed a purchase instruction that included the Parley record’s hash. VATE rechecked the agent’s authority just before checkout. The agent had permission to buy from both A and B. The purchasing system recorded the A order tied to the original decision. It held back a B order and an A order citing a different Parley record that also selected A. When I revoked the grant after initial approval, VATE stopped the fourth order even though the supplier and record still matched. The attached ZIP replays all four cases with synthetic purchase data. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Ran Parley, even just the README quickstart? Post what happened here, errors included.
Please include:
pip show parley-consensus) and your Python versionparley-mcptool from Claude or Cursor, or a recipe likeexamples/demo/recipe_*.jsonA failed run helps as much as a clean one. If you ran a real decision between parties with conflicting limits, say which one, and whether a red line held. The sharpest cases become demo scenarios with your source cited.
All reactions