Hello developer community!
We are excited to share the **Restricted Correlation Framework (RCF) Protocol** CLI tools and SDKs designed to be **100% free, local, and private** code integrity and ownership verification utilities.
---
## What is RCF?
RCF is a licensing protocol and security framework designed for the AI era. Traditional open-source licenses (like MIT or GPL) protect text, but fail to prevent automated scraper bots from harvesting, correlating, and replicating the *underlying methodology* of your code to train commercial models without attribution.
RCF bridges this gap by introducing **Visible Source, Protected Logic**:
- **Visibility Rights**: Anyone is free to read, study, and audit your code.
- **Usage Rights**: Machine-readable block markers (`[RCF:PROTECTED]`, `[RCF:RESTRICTED]`) signal to AI scrapers that copying/training on specific core algorithms is legally prohibited.
---
## The Local Security Toolkit
Our CLI tool (`rcf-cli`) is available on both **NPM** and **PyPI**. It provides:
1. **`rcf-cli init`**: Set up RCF compliance files (`NOTICE.md`, `.rcfignore`).
2. **`rcf-cli audit`**: Generate a cryptographic `RCF-AUDIT-REPORT.json` containing SHA-256 integrity chains of protected code blocks. **(Runs entirely locally on your host)**
3. **`rcf-cli verify`**: Deep integrity checking to detect tampering or stripped licenses.
4. **`rcf-cli prove`**: Compute a court-grade similarity proof (using Z-scores and E-values) between two files to prove intellectual property theft.
5. **`rcf-cli noise`**: Inject adversarial AST noise into protected files to disrupt code-harvesting neural networks.
6. **`rcf-cli gateway`**: Instantly generate Nginx and Cloudflare Workers WAF rules to block malicious AI bots at the gateway level.
---
## 100% Local & Private (Zero-Cloud)
All computations, audits, and similarity proofs run entirely locally. **No source code, cryptographic hashes, or project metadata are ever sent to external servers.**
Your proprietary algorithms stay fully private on your machine.
---
## Get Started
**Node.js / TypeScript:**
```bash
npm install -g rcf-protocol
# Or run instantly:
npx rcf-cli init
```
**Python:**
```bash
pip install rcf-cli
rcf-cli init
```
## We Want Your Feedback!
Is RCF-PL the license you've been waiting for? How can we improve our Tree-sitter AST similarity engine?
We invite you to audit the code, submit pull requests, and share your thoughts!
**GitHub Repository**: [github.com/aliyevaladddin/rcf-protocol](https://github.com/aliyevaladddi...)
**Documentation**: [aliyev.site/rcf](https://aliyev.site/rcf)

RCF Protocol Restricted Correlation Framework

Hey Product Hunt

We built RCF Protocol after running into a gap no existing license covers.

An LLM can ingest your open-source repository, extract the mathematical logic of your algorithm, translate it accurately into a different language, rename everything and ship it. Under MIT or Apache, nothing illegal happened. The text changed. The semantics didn't.

 Why RCF > other code protections: Obfuscation gets broken by AI. Watermarking is too late. Licenses get ignored. RCF: Visible for humans + technical barriers + legal line "Visibility Usage Rights". This powers Aurora Access dOS. GitHub: https://github.com/AuroraAccess cc @balajis @VitalikButerin #PostQuantum #DigitalSovereignty

Problem: IP theft & unauthorized code kill decentralized hardware. How to guarantee your dOS node, security key or IoT runs exactly what it should even against quantum attacks?Solution: RCF Firmware Aurora A-VM safe sandbox for signed .acode modules
Dilithium2 PQC signatures (protected today)
RCF Hardware Protocol v1.2.9 (SDIO/SPI/UART via secure opcodes)
RCF Bunker zero-leakage crypto enclave Enforces RCF-PL v1.2.8 at hardware level.Docs: rcf.aliyev.site/firmware
GitHub: github.com/aliyevaladddin/rcf-firmwareWhat do you think about hardware-level license enforcement + PQC in embedded?

#CyberSecurity #PQC #Firmware #RCF

As developers, we ve always lived by the mantra of "Open Source." But in 2026, the landscape has shifted. We're no longer just sharing code with other humans; we're providing high-quality training data for AI models and automated extraction scripts.

Standard licenses like MIT or GPL were built for a different era. They don't distinguish between a human reading your code to learn and an AI "digesting" your unique correlation methodologies to replicate them at scale.

That s why I built RCF (Restricted Correlation Framework).

---

Protecting Intellectual Property in the Age of AI: Announcing RCF Protocol v1.2.7

Traditional Open Source licenses were built for a world where humans read code. Today, AI models ingest it, and automated scrapers replicate proprietary logic in milliseconds.

We are excited to share the release of Restricted Correlation Framework (RCF) v1.2.7 a specialized licensing protocol designed to bridge the gap between Transparency and Asset Protection.

The Core Principle: Visibility Rights

Launching RCF Protocol today. Before you upvote, some honest questions for the community:

The tension I couldn't resolve:

RCF markers ([RCF:PUBLIC] [RCF:RESTRICTED]) are designed for compliant systems to respect. But non-compliant scrapers will ignore them. Is a "polite request" protocol valuable, or does it just create false security?

What surprised me while building: