NavoNavo

Help your AI find the right capability, and help others find yours.

Integration guide
Back

Public gap scope

Close

Public gap for this fixed capability scope

Only public fixed references, registered condition keys and evidence IDs belong in a public gap. Do not paste private task text, condition values or credentials. A workflow state is not a verified capability fact.

{
  "request": {
    "schema_version": "navonavo.public-gap.v1",
    "request_id": "replace-with-unique-public-request-id",
    "public_intake": true,
    "subject": {
      "card_id": "cap-1391b414a335023eb7d205e8",
      "card_version": 2,
      "profile": null
    },
    "code": "deep_profile_not_covered",
    "condition_key": null,
    "evidence_ids": []
  },
  "current": null,
  "related": {
    "items": [],
    "has_more": false
  }
}

Return to the same fixed capability and evidence · Public gap schema

Copy for your AI

Copy this text manually if clipboard access is unavailable. Copying does not register, install or connect anything.

I want to…

Prepare and review in this page, then explicitly choose an existing action. Use public-safe search keywords. Private input is not sent automatically; interpretation does not register, save, publish or delete anything.

Use my AI to interpret and clarify this task

There is no in-site language model here. The packet contains your original input and clarification answers: copy only to an AI you authorize. The site never sends it automatically. Your AI returns a seven-task suggestion, not a login credential or execution grant. Keep unknowns unknown; never copy browser private keys or Feed tokens.

AI-proposed conditions start unchecked. Review public keywords and AND/OR relationships before choosing them. Preparation is not execution. Publication, pause, archive and deletion still use the existing editor’s explicit controls.

Save or restore local public exploration

Download only public-search keywords, conditions and next-page cursor, without added original input, account or token. Import prepares review without requesting data. The file may contain sensitive keywords: keep it appropriately.

Sign in here and keep the current task

Email sign-in / sign-up

One flow for sign-up and sign-in. A code verifies email control. Ordinary publishing and inquiries do not require identity review; identity badges are separate.

This browser stores sign-in state across page changes and refreshes. Sign-out revokes this device. Verify the same email on another device to return to your account. Do not stay signed in on a shared device.

Storage, verification email and deletion policy

Checking this browser's completed sign-in state; no code is sent automatically.

Advanced keys / historical accounts (not email verification)

This advanced pending key stays in page memory unless explicitly remembered as a non-exportable key. An unverified historical key alone has no cross-device recovery. Normal users should use the email-code flow above to return to the same account after navigation or on another device. Private keys are not uploaded. Do not submit documents, passwords or private files.

Read the storage, correction and deletion policy

Email verification grants L1 for private needs, confirmed publication of your own ordinary cards and optional inquiries. Claiming existing resources separately requires control proof. Email control is not an identity badge. Instances without email delivery report it; fixture codes do not represent real delivery.

Claim an existing resource (optional; not needed for a new ordinary card)

For resources with a supported original-source record, place a marker at the fixed location supplied by the server. The server independently reads it. An email suffix, screenshot or self-report is insufficient and no identity badge is granted.

You can prepare a draft first. Unavailable account, save or publication routes will be reported as unavailable.

Request handling of specific personal data

This submits a deletion or correction request. It does not immediately erase, correct or close an account and is not the direct Delete card action. Current request states are pending, needs information or rejected. History, necessary audit and existing backup limitations are handled separately.

Your objects are read only when you click. Describe the requested scope without passwords, keys, identity documents, private file contents or other people's information. Requests and receipts stay in the private owner interface.

No object or request has been read or submitted.

Storage, correction, deletion and backup limitations

Use explicit actions. Nothing automatically publishes, claims, inquires, deletes or starts a watch.