What is DEKREL?
A result-driven AI workflow that moves from guided clarification into execution, review, and revisions instead of stopping at a one-turn answer.
Questions people ask before they trust the flow.
Usage, ownership, safety, revisions, and mobile scope are explained here before they turn into surprises.
Does a higher plan change the safety baseline?
No. Every plan keeps the same safety baseline. Higher plans mean deeper review, larger tasks, and wider support scope.
How do external accounts, domains, or email get handled?
Ownership stays with the user or workspace. The product can prepare drafts, explain the next step, and guide a safe action, but account-linked actions require confirmation.
What happens before an external account action moves forward?
The public contract is explain -> verify -> preview -> approve -> record -> revoke. That keeps external writes, publishing, account-linked actions, and billing-affecting steps understandable before they proceed.
Can I revoke access or stop a queued approval?
The interface should make approval boundaries understandable and give users a clear way to remove access, stop queued actions, or review what was approved.
Is one exact ownership verification method fixed for launch?
Not yet. The locked principle is ownership or authority verification before sensitive external actions. The exact launch method can vary by account type and implementation support.
How is usage explained?
Public guidance uses a task-level usage abstraction. Internal accounting stays hidden, and exact included usage numbers are finalized later.
Can I keep refining the result?
Yes. Results are meant to enter a revision loop with queueing, compare, restore, and request-level iteration.
Will design work ask for approval over and over?
Design-sensitive work should ask for one early direction check when it matters, then move detailed improvements into the result and revision loop.
Is this a mobile app?
The default promise is mobile-usable web. Installable PWA is conditional, and app-store delivery is a separate scope.