What would make you trust obligations extracted from an executed contract?

[wassimbensalem]

We are building Aakd, a self-hostable workspace for turning executed agreements into reviewed, source-linked obligations. We want to pressure-test the trust model before broadening the product.

If you work with contracts, legal ops, procurement, delivery, or security, I would value your answer to any of these:

1. When an amendment, renewal, or related agreement arrives, what must a system show before you would trust a proposed change to obligations, owners, or dates?
2. What is the minimum evidence you need to rely on a contract-derived task: source citation, review history, approval, audit trail, or something else?
3. If self-hosting matters to you, where does the operational burden outweigh the privacy and control benefit?

Please keep examples general and do not share contract text, personal data, credentials, or other confidential information. If you prefer a structured route, use the workflow-feedback issue template: https://github.com/aaked-app/aakd/issues/new?template=workflow_feedback.md

We will turn concrete feedback into public, reviewable issues instead of claiming the workflow is solved.