Skip to content

What is public vs private

Keystone's public implementation repositories, documentation, evaluation framework, and published ledger are publicly inspectable. Runtime Validity is also public as a separate bounded research implementation. Deployment configuration and internal infrastructure detail remain private. This page states exactly where that line sits.

What is public

The following are publicly available and inspectable:

  • Platform documentation: this site: architecture, the substrate model, extension design, capabilities, design heritage, and evaluation summaries.
  • The evaluation framework: keystone-verify. Inspect the profile system, the assertion vocabulary, and the judge engine. GitHub →
  • The published evaluation ledger: keystone-ledger holds the artifacts behind every published baseline, with results and metadata. GitHub →
  • The conversational extension: keystone-engage. Governed conversational agent source. GitHub →
  • The retrieval extension: keystone-counsel. Authorization-first retrieval source, including the client-isolation enforcement. GitHub →
  • The governed RAG reference implementation: keystone-gov. Query-time RBAC, fail-closed gating, and audit trail source. GitHub →
  • Runtime Validity (Track A): runtime-validity, a bounded public research implementation within Governed Execution, Keystone's broader runtime-governance research program. Results from Track A are evidence about a narrow mechanism, not validation of the broader platform. GitHub →
  • The platform demo: the employer-facing platform narrative at getkeystone.ai/platform/.

What is private

The following remain private:

  • keystone-demo deployment configuration: Docker Compose, Caddy, initdb migrations, and corpus management. This is a separate private repository.
  • Internal infrastructure details: node identifiers, network topology, addressing, and deployment-specific configuration.
  • Internal evaluation artifacts that have not yet been published to the ledger.
  • Operational and security details: authentication configuration, secrets management, and monitoring specifics.

Why it is private

What remains private is deployment-specific: infrastructure identifiers, operational configuration, and internal artifacts that are not yet part of the published evaluation ledger. The architecture, the evaluation methodology, and the extension source are public because they are the substance of the work. What stays private is operational detail that would not help a technical reviewer and could complicate deployment security if disclosed.

Contact: arnaldosepulveda.com · LinkedIn