# Qurmtessence funding and email safeguards

This extension keeps the operator useful without turning a browser page into an
unrestricted financial or communications agent.

## Allowed in the command desk

- prepare a funding-opportunity research plan and application-packet outline;
- prepare a lender-readiness checklist without a credit inquiry;
- prepare an email draft or triage-label plan without opening a mailbox;
- prepare a read-only Gmail monitoring plan with an owner-selected OAuth scope,
  polling cadence, notification channel, and retention period;
- prepare a compliance-deadline reminder plan without filing or certifying anything;
- prepare a metadata-only index plan for a server-side encrypted document vault;
- return a request ID and QI audit status for every preview.

## Always blocked here

- submitting a grant, SBIR/STTR proposal, loan, credit-card, or credit-line application;
- accepting terms, signing guarantees, opening a bank account, or moving money;
- reading or sending Gmail/Resend messages;
- enabling an always-on mailbox monitor without an explicit OAuth grant and
  revocable schedule;
- uploading bank statements, tax returns, identity documents, passwords, or API keys;
- shell execution, arbitrary file access, external crawling, or unattended workflows.

## Required handoff

1. The owner supplies verified facts from authoritative records.
2. A human reviewer checks recipients, claims, attachments, budget, and terms.
3. The approved provider portal or mail client performs the final action.
4. The signed QI audit record stores only redacted metadata and the request ID.

For Gmail, use a dedicated Google OAuth consent flow with `gmail.readonly` only.
Do not request `gmail.modify`, `gmail.send`, or full-account scopes for this
feature. Verify every address before connecting it; the currently confirmed
mailboxes are `qurmmie@gmail.com` and `qurmmius@gmail.com`.

The command API emits `execution_enabled: false` for every command, and the UI
labels financial and email features as preparation-only. Credentials belong in
server-side environment variables or a separately authenticated vault, never in
a browser request.