QUENVOR

Open Field Note 04 / The Counsel

How to let recognition travel without building a dossier about someone who never consented.

A good intention does not create consent. Discovery can invite recognition without accumulating information about people who never chose to enter the process.

QUENVOR goes first

The constraint, rejected alternatives, decision, and failure conditions are public before any response.

Existing work only

Reply with three to six sentences or one public link. Do not create a new deliverable.

Private discovery

No résumé, confidential material, ID, banking information, fee, money, or IP assignment.

No implied role

This is discovery and possible founding dialogue—not a vacancy, offer, compensation promise, or selection.

How can a trusted peer say ‘this made me think of you’ without sending QUENVOR the person’s name, email, résumé, employer, handle, or private history?

Constraints QUENVOR could not wish away

  • A nominator may know a strong person but does not own that person’s professional story or contact data.
  • The discovery stage requires no private nominee information, confidential material, identity document, banking data, money, or IP assignment.
  • The initiative cannot imply employment, compensation, equity, ownership, selection, or future money.
  • Retention, deletion, withdrawal, and anti-impersonation controls must be visible before submission.

Three paths. One selected.

A decision is more inspectable when the rejected alternatives and their consequences remain visible.

Collect the nominee’s contact details from the nominator

Rejected. The person has not chosen to enter QUENVOR’s process.

Accept a direct nomination with only the nominator’s good intention

Rejected. Good intention is not evidence of the person’s knowledge and consent.

Private forwarding first; consented nomination second

Selected. Recognition can travel while the person retains agency and privacy.

The consent-first recognition protocol

A consent-first nomination protocol with private forwarding as the default, explicit acknowledgement for direct nomination, and fixed prohibited-data and retention rules.

  1. 01
    Recognize privately

    Choose one official role invitation and send it directly to the person.

  2. 02
    Disclose the boundary

    Tell them no information has been shared with QUENVOR and they can decline or ignore it.

  3. 03
    Let the person verify

    Provide legal-entity, process, privacy, and anti-impersonation evidence before any response.

  4. 04
    Let the person respond

    They may answer one question, share existing public evidence, or do nothing.

  5. 05
    Use direct nomination only with consent

    If a nominator submits, the person must know about and consent to that submission.

  6. 06
    Delete on schedule

    Apply the published retention, withdrawal, and deletion controls to the submitted record.

A protocol needs both proof and a stop condition.

What is directly checkable now

  • The private invitation contains no recipient identifier in its URL.
  • The official role pages state the right to decline and the no-new-work boundary.
  • The direct nomination path requires an explicit consent acknowledgement.
  • A missing-consent production test returned HTTP 400 and created no provider submission.

When QUENVOR must stop or revise

  • Stop if a route requests a private directory, scraped contact, résumé, or nominee dossier.
  • Stop if the person’s consent is assumed from the nominator’s relationship or intention.
  • Stop if economic or legal terms are described before they are actually defined.
  • Stop if any public evidence exposes private response or administrator information.

Where would your judgment change this decision?

When did your judgment let responsible progress continue while preventing a material legal, privacy, security, or ethical failure? Answer in three to six sentences, show one existing public decision, or leave without responding. QUENVOR requests no new work and promises no role.