Design philosophy
Understand human confirmation and review
Distinguish questions, tool permissions, proposed edits and content delivery review.
Updated
During a task, DraPub may ask for missing information or confirmation of an action. Read the card to understand which response is needed.
| Request | What to decide |
|---|---|
| Question | Missing evidence, preferences or scope |
| Operation permission | Tool to run and object affected |
| Proposed edit | What changes and whether to preserve the current version |
| Delivery review | Whether text, media, platform and account are ready |
Permission applies to that request. A new target, edit or version needs a decision based on its current state. An expired confirmation is not current authorization.
Open the original conversation when it needs you. If the scope is unclear, clarify or decline rather than relying only on a reassuring chat statement.
Actions follow their actual permission and review rules. Manually saving a note, adopting a text revision, allowing a tool and handing work to an extension do not all use the same controls.
The extension adds a confirmation before saving a platform draft. See Review changes and the Extension guide.
Q: Does approving a tool call also approve publishing?
**A: ** Read the specific object and action on the card. Tool permission, adopting text, and delivery review have separate scopes; approving one does not cover the others.
Q: What if I cannot tell what an approval will affect?
**A: ** Clarify your requirements or reject the request and ask for the affected object and action scope. Assess the new valid request once the details are clear.