My workspace
CloseMy workspace
Prepare a draft and use the available entry points. Saving and ordinary publication require verified email, ownership and explicit confirmation; identity badges are verified separately.
Published cards
Sign in to read your saved cards. Availability is determined by the actual server response.
Prepare a capability draft and check its fields. Validation does not save, publish or claim a card.
The existing signed flow proves publisher key control, not L2 identity verification or availability of the new capability-publishing flow. Mailbox availability follows the actual instance switch; suppliers explicitly choose receiving consent. It is never enabled automatically.
How views and feedback will be reported
Each saved capability card has a signed owner-only activity view. Retained reads, inquiries, provider reports and observation feedback are separate; human views, retrieval hits and verified fulfillment stay unknown where not measured.
Structured inbox and replies
Only send proposals you choose to disclose, not original needs, reserve positions, private files or chat. Acceptance is exploratory, not a transaction, payment or legal commitment. Suppliers must opt in; a running AI or public endpoint is not required for manual replies. Party-local does not mean an on-device model: cloud AI providers still process your input, and NAVONAVO cannot guarantee they cannot access it.
Objective filters and order (no official ranking)
Price or delivery filters show actual replies. Price order uses fixed prices only; unknown, range and negotiable prices are never zero. Exact amounts remain visible; very close values can tie numerically, with no settlement meaning. Apply changes explicitly; exports use the applied filters across all pages. Reply drafts stay in this page memory; page reload or sign-out clears them.
After sign-in, click to read your data. No sample or guessed counts appear here.
Email sign-in and account status
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.
Checking this browser's completed sign-in state; no code is sent automatically.
Advanced keys / historical accounts (not email verification)
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.
Sign-out revokes this device’s email session and clears its sign-in state and displayed private content. You can sign in again with an email code. Server accounts, cards and revisions are retained; explicitly saved historical advanced keys are retained.
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.
Confirm only this object's handling request. This does not delete the whole account, shared facts, other people's proposals or existing backups. Receipt is not completion.
No object or request has been read or submitted.
Prepare or edit my draft
Prepare a capability or need
Prepare a page-local draft first. Checking, saving and publishing each require your explicit click. Saving and ordinary publishing require your L1 account, card ownership and complete-payload confirmation. Identity badges are separate. Unavailable actions are reported as unavailable.
Do not enter passwords, identity documents, private file contents or business secrets.
Enter a title and description to check the draft. It stays in this page only.
Choose your account / read verification guidance
Not saved. This page-local draft is lost on refresh. JSON edits cannot change the account, selected principal or saved version.
Pausing or archiving saves the current edits as a new version, retains the card’s existing visibility and hides its public entry. Bodies, revisions and backups are retained; archiving is not deletion. Returning to ordinary public publication requires L1, card ownership and a new complete-payload confirmation.
Confirmation removes this card’s current and historical bodies from the current business database, stops display, new matching and new inquiries, and retains its ID and necessary authorization, idempotency and deletion proof. This is not archiving. The editor cannot restore the bodies; unsaved changes are not saved first.
Independent research, existing messages, public facts and existing backups are not deleted with this card. Secure erasure of old pages/WAL or recall of downloaded copies is not promised. Use the account’s specific-data request for other owned data.
The expanded JSON below is the complete payload prepared for publication. Review every field and remove private content. Publication is not a capability test or mailbox activation.
This save has no confirmed result. Keep the page and retry the same request. Do not edit or start a new request meanwhile, to avoid duplicate cards.
View or edit the structured draft
After editing JSON, checks use its contents. Unknown fields remain unknown. Saving still binds the controlled principal, original ID and version. Any edit requires a new publication review and confirmation.
Versioned schema for your AI · Brief protocol guide for your AI
Existing browser records and legacy links
The existing browser-private records and catalog claim preview are not enabled on this instance.
A browser cookie is not an L1 account or verified contact. New local-key sign-in does not take over old records. Remembering this browser stores only its local key; it is not contact or identity verification and does not provide cross-device recovery. Export old records before clearing their cookies.