Troubleshooting & FAQ
Common questions and fixes for specifying, approving, and grounding your work.
Short answers to the things people hit most often. See the Glossary for any unfamiliar term.
Why is "Route for E-Signature" unavailable — my spec won't lock?#
A spec can only be locked once it has no open critical gaps. Check the readiness view: any gap marked critical is a genuine decision the agent needs from you — answer it in the chat and the agent resolves it. Config gaps (defaulted, "confirm at build") don't block. When no critical gaps remain and the agent reports the spec complete, the option appears. See Gaps and decision points.
I can't sign my own specification#
In a team workspace, separation of duties applies by default — the person who authored the spec can't sign it, so a different Authorized Approver must. In a personal workspace you sign your own work. An org admin can switch a team workspace to self-serve approval in workspace settings. See Who can sign.
The agent isn't using the document I want it to reference#
Attach the document to the spec's knowledge base, not just the chat — text pasted into the conversation isn't indexed for grounding.
PDF, Word, Excel, CSV, JSON, Markdown, and plain text — plus a Git repository as reference material. Once indexing finishes, the agent reads the document, cites it by name, and turns the relevant details into real requirements.
My account is stuck on "pending"#
Amira is in closed beta — a new sign-up waits for an operator to approve your organization.
The pending screen advances itself the moment approval lands — you don't have to reload the page.
Can I keep changing a spec after routing it for signature?#
Routing locks the spec's content into an immutable version, so it can't be edited in place (approving a moving target would defeat the signature). If you need further changes, revise the spec — that produces a new version to be signed.