Availability and changes
Development status: Status and changes — Nothing described in this documentation is publicly available: there is no public network, endpoint or faucet and no publicly released SDK, command-line tool or wallet, and the experimental implementation and experimental tooling exist for internal development and testing only. No releases, versions or compatibility promises exist yet, no release plans or dates are published, and a public feedback channel has not yet been announced.
Before you read: Development status: what exists today and what does not.
This section holds the dated detail behind the status hub. Use this page to find the page that answers your question about availability, versioning, conventions, changes or feedback, and to see how availability statements are written.
The short answer
Nothing described in this documentation is publicly available for use. An experimental implementation exists for protocol development and integration work; it is an early prototype and is not a release. No releases, protocol versions, compatibility promises, release plans or dates are published.
The status hub, Development status: what exists today and what does not, summarises status for the whole documentation; this section gives the detail.
Pages in this section
- Networks and environments — there is no public network, endpoint, network identifier, faucet or distribution of test funds.
- Tools, SDKs and wallet availability — no SDK, command-line tool or wallet is publicly available; experimental tooling exists for internal testing only.
- Versioning, compatibility and deprecation — there are no releases or compatibility promises yet; the page explains how versions, deprecations and migrations would be documented.
- Documentation conventions: status labels, dates and reviews — what the site-wide notice, status labels, dates, review markers and claims boxes mean.
- Documentation change log — dated changes to this documentation, including status-label changes and superseded pages.
- Feedback on this documentation — how feedback would be accepted once a public channel is announced.
Which page answers your question
| If you are asking… | Read |
|---|---|
| “Can I connect to a network, or get test funds?” | Networks and environments |
| “Can I install an SDK, a command-line tool or a wallet?” | Tools, SDKs and wallet availability |
| “Which version does this describe, and will my integration keep working?” | Versioning, compatibility and deprecation |
| “How current is this page, and what does its label mean?” | Documentation conventions: status labels, dates and reviews |
| “What has changed?” | Documentation change log |
| “How do I report an error in the documentation?” | Feedback on this documentation — a public channel is pending and has not yet been announced |
| “How do I report a security problem?” | Security assurance status and reporting problems — a reporting route is pending and has not yet been announced |
How availability statements are written
- Dated. Each statement is true as of its page’s as-of date; check the date before relying on it.
- Absence first. Pages say plainly what does not exist, and anything not stated as available should be treated as unavailable.
- No predictions. No release dates, plans or phasing are published, and pages do not speculate about them.
- No internal detail. No internal environment names, identifiers, endpoints or tool names are given.
- Recorded. Every change to an availability statement is dated in the change log.
Assumptions, trust and limitations
Status pages describe the state of development as of their dates; they are not commitments, and experimental work is not a release. Statements about Cubane’s availability that do not come from this documentation are not confirmed by it.
Not yet available, and how this page will grow
When an environment, tool or release becomes available, the relevant page would list it with its date, version identity and support status; the status hub would summarise it, and the change log would record it. If a reviewed statement about release plans is approved, it would be published on the status hub and recorded in the change log.
Related pages
- Development status: what exists today and what does not — the status hub for the whole documentation.
- Networks and environments — network, endpoint and test-funds availability.
- Tools, SDKs and wallet availability — developer and operator tooling availability.
- Versioning, compatibility and deprecation — version and compatibility policy.
- Documentation conventions: status labels, dates and reviews — how to read labels, dates and review markers.
- Documentation change log — dated documentation changes.
- Feedback on this documentation — how documentation problems would be reported once a channel exists.
Glossary
References
No approved public references yet.
