Skip to content

[codex] docs: add OpenCoven IP protection records - #1

Merged
BunsDev merged 1 commit into
mainfrom
codex/ip-protection-record-20260704
Jul 4, 2026
Merged

[codex] docs: add OpenCoven IP protection records#1
BunsDev merged 1 commit into
mainfrom
codex/ip-protection-record-20260704

Conversation

@BunsDev

@BunsDev BunsDev commented Jul 4, 2026

Copy link
Copy Markdown
Member

Summary

Adds the OpenCoven root IP protection and disclosure documents:

  • PATENTS: patent non-assertion pledge and prior-art notice
  • PROVENANCE.md: origin and publication record
  • CONTRIBUTING.md: DCO and patent contribution terms, merged with any existing repo guidance
  • SECURITY.md: responsible disclosure policy, merged with any existing repo guidance

Validation

  • Only root documentation files changed: PATENTS, PROVENANCE.md, CONTRIBUTING.md, SECURITY.md
  • Internal-only source notes were not copied
  • git diff --check passed locally

@BunsDev
BunsDev force-pushed the codex/ip-protection-record-20260704 branch from d3e321f to 9244b23 Compare July 4, 2026 14:22
@BunsDev
BunsDev marked this pull request as ready for review July 4, 2026 14:52
Copilot AI review requested due to automatic review settings July 4, 2026 14:52
@BunsDev
BunsDev merged commit a701c12 into main Jul 4, 2026
1 check passed
@BunsDev
BunsDev deleted the codex/ip-protection-record-20260704 branch July 4, 2026 14:54

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Adds IP protection and disclosure documentation (PATENTS/provenance/contribution/security policies) at the repository root, intended to establish origin records and reporting processes.

Changes:

  • Added PATENTS with a patent non-assertion pledge and prior-art notice.
  • Added PROVENANCE.md describing architectural origin and publication record.
  • Added CONTRIBUTING.md (DCO + patent contribution terms) and SECURITY.md (responsible disclosure policy).

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 6 comments.

File Description
SECURITY.md Introduces a security vulnerability reporting policy and scope definition.
PROVENANCE.md Adds a provenance/origin record and prior-art style references.
PATENTS Adds a patent non-assertion pledge and prior-art notice table.
CONTRIBUTING.md Adds DCO sign-off instructions and patent non-assertion contribution terms.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread SECURITY.md
Comment on lines +7 to +13
If you discover a security vulnerability in OpenCoven, please report it responsibly.

**Do not open a public GitHub issue for security vulnerabilities.**

Contact the maintainers directly:
- Discord: https://discord.gg/OpenCoven (DM @BunsDev)
- Or open a GitHub Security Advisory on the repository
Comment thread CONTRIBUTING.md
Comment on lines +1 to +8
# Contributing to OpenCoven

Thank you for your interest in contributing. OpenCoven is MIT licensed and community-driven. We want contributing to be easy, open, and safe for everyone.

## Developer Certificate of Origin (DCO)

OpenCoven uses the **Developer Certificate of Origin (DCO) v1.1** for all contributions. This is a lightweight mechanism — not a CLA — that asks you to certify that you have the right to submit what you're submitting.

Comment thread PATENTS
Comment on lines +5 to +6
OpenCoven is MIT licensed. The maintainers of this project have not filed and do not intend to file patents on the architectural patterns, protocols, or mechanisms described in this repository.

Comment thread PROVENANCE.md
Comment on lines +1 to +18
# PROVENANCE.md — OpenCoven Origin Record

> This document exists to establish the clear, timestamped origin of the architectural ideas that define OpenCoven. It is a public record, not a legal claim. It is maintained so that future readers — contributors, users, researchers, patent examiners — can verify where these ideas came from and when.

---

## Origin

**OpenCoven** was created by **Valentina Alexander** (`@BunsDev`) and first published publicly on **April 27, 2026** under the MIT License.

- GitHub organization: https://github.com/OpenCoven
- Website: https://OpenCoven.ai
- Discord: https://discord.gg/OpenCoven
- X / Twitter: https://x.com/OpenCvn
- License: MIT (https://opensource.org/licenses/MIT)
- Repository creation date: **2026-04-27** (verifiable via GitHub API: `https://api.github.com/repos/OpenCoven/coven`)

This repository has no fork parent. It is an original work with no upstream source repository.
Comment thread PROVENANCE.md
Comment on lines +24 to +34
### 1. The Familiar Identity Model
**First appeared:** `coven-cli/src/familiar_identity.rs`, commit history from 2026-04-27

A named, role-scoped agent persona — a "familiar" — resolved from a configuration manifest (`familiars.toml`) and attached to a session via a CLI flag or runtime config. Each familiar has an `id`, `display_name`, and `role`. The familiar model is the foundational identity primitive for multi-agent systems in OpenCoven.

This concept was original to this repository. It has been independently acknowledged as prior art by third parties in their own published documentation.

### 2. The Agent Spawn Harness
**First appeared:** `pty_runner.rs:307` (`spawn_piped_with_observer`), commit history from 2026-04-27

A structured dispatch pattern for launching configured agent/harness processes. The pattern validates a harness allowlist, canonicalizes working directory, checks session state, then dispatches to one of a defined set of low-level spawn primitives. This is the root pattern from which single-chokepoint process execution architectures in agent systems derive.
Comment thread PATENTS
- The agent spawn harness: a structured dispatch pattern that validates and routes process execution through a defined set of primitives
- The multi-agent orchestration substrate: composable, purpose-scoped agents ("familiars") coordinating through structured routing with shared session context
- The session memory and continuity substrate (OpenTrust): durable, portable agent memory and session state with provenance tracking
- The graded approval tier model: auto → familiar-review → human-review → human-required escalation for agent actions affecting protected resources
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants