Documentation
Read what we ship.
The canonical RockyGuard documentation, available as PDF for offline reading and for circulating internally to your security or procurement team.
RockyGuard gives you two ways to enforce a licence: a simple status branch you add in a few lines, or load-bearing binding, where a real feature’s data is sealed under a key the licence carries so a tampered licence just yields the wrong key. The docs below cover both.
Need the integration walkthrough first? Read the Quick Start rendered on this site.
AI Integration Guide
For your AIA tool-agnostic recipe written for AI coding assistants (Claude, ChatGPT, Cursor, Copilot, Gemini, Cody, ...). Ships at the root of every customer zip. Tell your AI: "Read AI_INTEGRATION_GUIDE.md and integrate RockyGuard into this project." Deterministic steps -- locate main(), add the CMake block, embed the public key, insert the verification call, gate features by license -- with copy-pastable snippets for both node-locked and floating tiers. Rendered HTML for human reading; the raw markdown is also available at /AI_INTEGRATION_GUIDE.md for AI agents that fetch by URL.
HTML · rendered on this site
Customer Documentation
Start hereThe full integration manual: package contents, vendor license, Quick Start, library integration (static + shared linking on both Windows and Linux), end-user license management, floating licensing, hardware fingerprinting, CLI tools reference, license file format, anti-tampering features, troubleshooting.
PDF · ~500 KB
Customer API Reference
Public C++17 API surface: namespace and headers, diagnostic output, enums and types (LicenseStatus, LicenseType, SignatureAlgorithm, LicenseResult), License struct, LicenseVerifier class, HardwareFingerprint class, FloatingLicenseClient class (Premium), CLI tools reference, integration examples.
PDF · ~390 KB
Phase 4.1 Customer Onboarding Report
TransparencyCold-read passes against the shipped customer zip in isolated environments, by evaluators given no prior knowledge of the product. The v1.3.0 cycle added a fresh-agent Stage 1 read that surfaced 38 findings, 9 of them HIGH, in documentation that had already passed four review rounds. Every finding, every fix, and the four deliberately not fixed are listed with reasons. Ships publicly so a fresh evaluator can read what a prior fresh evaluator hit before they start their own evaluation.
PDF · ~440 KB
Future Roadmap
TransparencyThe complete backlog of customer-driven changes deferred to v1.3 and v1.4+. Every item names where it was first surfaced (Phase 4.1 gap, Phase 5 audit finding, Phase 6.1 reviewer comment, etc.) so a future reviewer can read the original finding in context. The list of proposals REJECTED from a doc-structure review is also included so future restructuring does not re-litigate decisions already made.
PDF · ~360 KB
HTML rendering of these documents (with deep-linkable section anchors and full-text search) is on the website v1.1 roadmap. PDFs are the source of truth at v1.0 launch.