Support

This support path covers Mandate Companion and Receipted Memory.

Before contacting support

Do not send secrets. Keep these out of issues, emails, chats, screenshots, and shared exports:

• Vault passphrases.
• Recovery sheet codes or QR data.
• OpenAI, Anthropic, Claude, ChatGPT, or other provider API keys.
• Unredacted page snapshots, prompts, memory field values, receipts, or exports unless you have intentionally reviewed and redacted them.

What support can help with

• Installing the Web Store build or loading an unpacked developer build.
• Understanding permissions, local storage, recovery sheets, and export contents.
• Interpreting Mandate Companion verifier output such as `VALID`, `INVALID`, `outside_scope`, and `gap`.
• Interpreting Receipted Memory receipt verification and chain checks.
• Finding offline verifier artifacts in `docs/VERIFIER_DISTRIBUTION.md` and known limitations in `docs/COVERAGE_GAPS.md`.
• Reproducing UI problems with redacted screenshots and exact browser/version information.

What support cannot do

• Recover a lost vault, passphrase, recovery sheet, local signing key, provider API key, ledger, or browser profile.
• Undo a prompt, field value, or browser action after you send it to a provider or website.
• Provide legal, compliance, investment, financial, tax, medical, or security advice.
• Verify an export that you do not provide or reconstruct evidence that was never stored locally.

Support request template

Use this template after removing secrets and personal data:

```text

Extension: Mandate Companion / Receipted Memory

Version:

Browser and version: Chrome / Edge

Install type: Web Store / unpacked developer build

Operating system:

What you expected:

What happened:

Steps to reproduce with non-sensitive demo data:

Verifier output or error text, if relevant:

Screenshots attached? Confirm they contain no secrets: yes/no

Exports attached? Confirm they are redacted and intentionally shared: yes/no

```

Quick self-checks

Mandate Companion

1. Confirm the active mandate target matches the current origin.

2. Confirm the mandate is not expired or revoked and the action/rate caps are not exhausted.

3. Confirm the action verb is one the executor supports.

4. If using BYO provider mode, confirm provider choice, model name, API key, and provider account status.

5. If using the local demo, use `http://localhost:8791/agent-demo.html` and a local-demo mandate.

Receipted Memory

1. Confirm the vault is unlocked in the same browser profile where the fields were created.

2. Confirm the field was selected before clicking **Prepare signed prompt**.

3. Confirm the page is `https://claude.ai/` or `https://chatgpt.com/` and the composer is visible.

4. Confirm you manually sent the prepared prompt only after reviewing it.

5. For verification, use the public key that matches the receipt log or compliance ZIP.

Store listing support URL

For Web Store submission, point the support URL to the repository issue tracker, project support page, or a hosted copy of this file. The public page must repeat the no-secrets rule above.