Public repositories

Locked

Use the Monolythium GitHub organization and each repository’s release page as the current public inventory. This page intentionally does not promise a repository count, unpublished roadmap, or production release that cannot be verified from a public artifact.

Independently reviewable surfaces

• chain-registry records public chain identity and network metadata. Confirm the exact revision before integrating.
• mono-core-sdk is the public client surface documented in the SDK reference. Package versions and source revisions remain the authority for supported methods.
• Public documentation records product and network boundaries, but it is not implementation source.
• Local lyth_mcp Stele profile is published as a v0.1.0 GitHub prerelease with three read/status tools: stele_connection_status, stele_search_services, and stele_agent_wallet_status. The release includes a tarball, checksums, an SPDX SBOM, and cosign bundles.
• Hosted Stele MCP is a separate live keyless OAuth surface. Its authenticated tools/list response is authoritative for the runtime inventory.

Repository presence alone does not prove that an artifact is released, deployed, audited, or compatible with the current registered development-network profile.

Unpublished core

mono-core is internal and unpublished. External reviewers cannot currently perform line-by-line source review, reproduce the node from public source, or fork the running implementation. Public RPC observations and registry data can verify limited network behavior, but they do not close that source-availability gap.

No public page should expose private repository paths, internal review material, Foundation operator procedures, infrastructure topology, credentials, or incident playbooks.

Safe verification

For a public artifact, record:

1. the repository and immutable revision;
2. the release or package version, if one exists;
3. checksums and provenance supplied with that release;
4. the binding license file; and
5. observed compatibility with the value-less, resettable development testnet.

Absence of any item is a diligence gap, not permission to infer it from a roadmap statement. See License and IP posture and Diligence.