RCF Protocol

Questions & Insights — RCF Protocol

by

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:

  • Legal teams love the audit trail. Developers love the CLI. Almost no overlap between these two use cases in the same company.

  • The hardest part wasn't cryptography — it was explaining why this isn't "just another license."

  • Premium feature ($19/one project) funds development, but 80% of users never pay. The free tier is intentionally complete for individual developers.

What I need help with:

  • Adoption: How do we get AI training pipelines to parse these markers?

  • Standardization: Is there a path to IETF/SPDX, or does RCF stay proprietary?

  • Jurisdiction: Has anyone tested "AI training restriction" clauses in court?

Drop insights if you've thought about this space. Especially interested in ML engineers' perspective — would you implement marker detection in your data pipeline?

37 views

Add a comment

Replies

Be the first to comment