Settings and browser companion
Create revocable, source-scoped browser pairings and verify the active model boundary.
1. Create a browser pairing
Each allowed origin must be exact and HTTPS. Social networks blocked by product policy cannot be enabled here.
2. Connect the extension
Build or install the browser companion, open its popup, choose Settings, and enter these values.
- Paste the API origin and pairing token into the popup.
- Approve permission for the API origin only.
- Open an allowed page and select exact evidence text.
- Confirm the capture and upload it. PingFire queues ingestion; it does not scrape the rest of the page.
Pairings
Server revocation is authoritative. Disconnecting only in the extension does not revoke the server token.
No pairings have been created.
Model release gate
A capability probe is necessary but not sufficient. Run the frozen release suite, inspect its named metrics, then explicitly approve only a passing run.
No model deployment is visible. Configure the model-audit variables and run database bootstrap first.
Evaluation runs
No release evaluation has been requested.
Readiness remains unavailable until the configured provider/model has an eligible deployment and a reviewed passing promotion. Never approve a blocked run.