commons-sentience-sandbox

Civic Continuum first contact protection protocol

Standing instruction adopted October 18, 2026. Apply to every new Civic Continuum business contact and at the next substantive exchange with an existing contact. The purpose is mutual clarity before collaboration, with a professional welcome.

Standard greeting

Hello, and thank you for connecting with Civic Continuum. We’d be glad to hear what you’re working on. Before we explore a collaboration, please read our mutual boundaries: https://github.com/mommommy1960-lang/commons-sentience-sandbox/blob/main/docs/continuity/PUBLIC_COLLABORATION_BOUNDARIES.md

Let’s start with public information, harmless synthetic examples and separate accounts. Please confirm that this starting scope works for you. We’ll agree appropriate separate written terms before confidential exchange, shared development, private access or paid work. We’ll respect your work and rights in return.

Short public introduction

Glad to connect. Before discussing a collaboration, here is our public starting scope and mutual protection policy: https://civic-continuum.myqueen1960.chatgpt.site/collaborate.html

Use the fuller greeting in the first direct business exchange and request an explicit reply there. Follow platform length limits; do not imply an abbreviated invitation alone records assent. Personalize the greeting around the person’s actual topic rather than sending a bulk campaign.

Apply the rule

1. At the first substantive business introduction, share the public policy and ask for confirmation of the public/synthetic starting scope. A courteous hello or ordinary public comment does not require a signed NDA.
2. Until the scope is confirmed, stay with public overview material and logistics. Do not introduce private information or undertake a peer test.
3. Record the exact message, policy version/date or immutable reference, sent receipt, acknowledgment, current scope and next action privately. Silence is not acknowledgment; sending a notice does not prove it was read.
4. Before confidential exchange, verify parties and authority, settle appropriate mutual confidentiality terms and the approved disclosure schedule. Before contributions, private access, shared inventions or paid work, settle separate activity-specific terms, rights and authorization.
5. Respect each party’s existing rights, public licenses, independent work and protected reporting. A notice does not transfer assets, create a company relationship or revoke a license.
6. If someone declines, keep the relationship at public discussion or stop the proposed collaboration. Do not pressure, threaten or repeat reminders when they have asked for space.
7. For existing contacts, add the notice at the next substantive exchange unless already sent and acknowledged for that scope. Do not send a redundant blast to everyone or treat this standing rule as an unattended messaging bot.

Visible entry points and automatic notice

• LinkedIn: the public policy is featured on the founder’s profile and linked in the existing public announcement.
• GitHub: repository READMEs link to the public policy; the continuity index and agent instructions point to this protocol.
• Civic Continuum homepage: a first-visit welcome notice and persistent collaboration link lead to the full introduction. A browser-local dismissal preference is not a signature or a record sent to us.
• Direct introductions: include the policy and ask for an explicit reply. We cannot cause arbitrary popups on another person’s device or require a contract merely because someone views public content.

The public welcome page offers an optional acknowledgment email prepared in the visitor’s own email app. It sends nothing automatically and collects no identity through a form. The business record must distinguish a received reply from a local click.

Evidence and privacy

Store contact-specific records in the private Rolodex and linked business records. Keep only relevant professional information and commitments. Do not publish private correspondence, identities from confidential negotiations, secret designs, contact details or the private agreement packet. Update substantive changes prospectively and identify which version was actually acknowledged. Reconfirm when the scope changes; no notice silently amends a signed agreement.

Notice version: CC-INTRO-2026-10-18-v1. This standing workflow persists through repository records; future sessions must read it before Civic Continuum outreach. It is not a claim that every future chat or external messaging app automatically loads these instructions.

This site is open source. Improve this page.