commons-sentience-sandbox

IP, security and marketing practices

Adopted October 18, 2026. Applies prospectively across Civic Continuum research, inventions, software, books, services, websites, supplier discussions and marketing. This is an operating workflow; it does not establish that every asset or account has completed review.

Before a release or disclosure

  1. Identify the asset, contributors, dated source evidence, exact revision and storage location in the private asset register. Do not assume company ownership from repository possession; record assignments, licenses and gaps.
  2. Classify information: public/licensed, internal, confidential candidate, or restricted personal/credential data. Keep secrets and private customer information out of public repositories, course tools, AI marketing inputs and demos.
  3. Check public disclosure history and proposed publication against patent/trade-secret strategy. A timestamp is evidence, not a patent filing; do not rely on a grace period without tailored review. Published information does not become secret through a later label.
  4. Preserve applicable open-source, third-party and contributor licenses. Separate our original expression from underlying ideas, methods and third-party work. No blanket “all rights reserved” override of existing licenses.
  5. Before protected exchange, verify parties and authority, minimum disclosure, appropriate mutual confidentiality terms and recipients. Before development or contributions, settle scope, background assets, rights in results, payment and exit terms.
  6. Check actual access, secrets handling, dependency risks, privacy and relevant behavior tests. Save evidence for what was checked; do not turn an unchecked item green.
  7. Obtain owner approval for the exact release/disclosure; record when, where and what was shared. Use verified registration records before claiming registered marks, patents, certification or partnership.

Ongoing records and response

Private inventory fields: asset ID; title/type; creator/contributors; current ownership evidence; repository/file and immutable revision; creation/evidence dates; prior disclosures; existing licenses; confidentiality classification; current access; relevant agreements; legal/registration status; renewal/deadline evidence; development cost; revenue evidence; protection cost quote; priority; next action and owner. Use the private invention disclosure template at the beginning of a project, not after publication. Do not put unpublished invention details in this public file. For a suspected infringement or security incident: preserve original evidence and timestamps privately, assess ownership/license/scope and actual impact, restrict exposed access where authorized, obtain appropriate expert review before accusations or takedowns, and record resolution. No automatic takedown or surveillance service is enabled by this document. Review these records at each release, new contributor, material scope change and actual renewal/deadline. Recurring automation is not claimed installed.

Apply marketing learning

Choose one specific outcome and audience, record a baseline, implement a bounded change, and compare actual results. First priorities are honest product descriptions, mobile usability, broken links, clear calls to action, consent-respecting feedback and accessible content. Use aggregated or synthetic data for AI assistance. Review generated claims, licenses and privacy before publication. Do not infer sensitive traits or upload customer records to unapproved tools. Metrics: qualified inquiries, completed public demos and failures, useful feedback, and verified paid conversions only when payment/delivery is actually live. Unmeasured values remain unknown, not zero or success. No paid ads, trials that become subscriptions, new analytics trackers or vendor purchases are authorized here.

Public notice versus technical implementation

Public notices and release workflows are implemented in the main repository and current Civic Continuum homepage. A visit, dismissal or silence is not a signature. Appropriate engagement terms remain necessary. The inaccessible original Maya Site and other product account/security audits remain separately tracked; this page does not certify them. Mutual boundaries · First-contact protocol · Public IP page

Basis

Owner-provided “Text” email and Verizon AI marketing worksheet informed these original operating instructions; copyrighted course materials are not republished.

This site is open source. Improve this page.