Future developer experience: what a supported release would add
Development status: Overview — Planned experience, not instructions. The developer experience described in this section is planned; its pages preview intended experiences and cannot be followed today. An experimental developer-facing node interface and other experimental tooling exist for internal testing only. No SDK, command-line tool, wallet or public network is publicly available, and exact installation commands and released tooling are not yet available.
Before you read: Development status: what exists today and what does not.
What will developing on Cubane be like once a supported release exists, and what is missing today? This page describes the intended developer journey across this section’s previews, lists what a supported release would add before any preview could become a real guide, and states plainly what is missing today.
Planned experience, not instructions. Nothing in this section can be followed today. Exact installation commands and released tooling are not yet available.
What this section is
- Previews of a planned experience. Each page in this section previews part of the planned developer experience and is marked as a planned experience, not instructions.
- Conditional language. Previews use conditional language — “would”, “is intended to”, “once released” — and set no dates.
- Notices instead of commands. Where a command, interface detail or version would normally appear, a preview states that exact installation commands and released tooling are not yet available.
- Illustrations, not interfaces. Any example is an illustration, not a released interface; see How illustrative examples work in this documentation.
What exists today, and what does not
- No SDK, command-line tool, wallet or public network is publicly available; see Tools, SDKs and wallet availability and Networks and environments.
- An experimental developer-facing node interface exists for internal testing; the broader developer API design is being explored. See Interfaces and their status.
- Other experimental tooling exists for internal development only. It is not a release, and it is not a starting point for outside developers.
- Nothing in this section can be followed today.
The intended developer journey
Status of this section: Planned — every preview below describes a planned experience; none can be followed today.
Read in order, the previews follow a developer from a first result to a complete integration. The organisation-onboarding preview runs alongside them, covering the decisions an organisation would make for itself.
- Getting started once a release exists — Planned. Obtain tooling, configure an environment, confirm readiness and produce a first result.
- Local development environment — Planned. Build and debug against a local environment that would behave like the network, with debugging aids for confidential workloads.
- Submitting work and retrieving results — Planned. Submit confidential work and get results back through language SDKs; long-running work would be handled as confidential jobs that could be tracked, cancelled and refunded.
- Integrating an application end to end — Planned. See how identity, approvals, submission, result checking and monitoring would fit together in one application.
- Onboarding an organisation — Planned. The decisions an organisation would make before adopting, such as a starting profile, custody and approval arrangements, and who may see which data.
What a supported release would add
Before any preview could become a real guide, a supported release would need to add:
- A version identity — a released version identity, shown on every page that documents released behaviour.
- Supported interfaces with reference — supported interfaces, each with versioned technical reference.
- Tooling with installation instructions — tooling, such as SDKs, with installation instructions and supported versions.
- Exact commands — exact commands, configuration guidance and examples checked against the released interface.
- Supported environments — supported environments with their prerequisites, and a compatibility and deprecation policy applied to real versions; see Versioning, compatibility and deprecation.
Until these exist, the previews remain previews.
Preparing now
- Learn the concepts the previews rely on. Start with System model: how Cubane is intended to work for its users, Lifecycle stages used in this documentation, Identity, keys and access: concepts and Privacy and confidentiality: intent and current limits.
- Think through your data. Decide which data in an intended application is sensitive, and who should be entitled to its results. Those answers do not depend on details that are still unsettled.
- Follow status changes. Watch Tools, SDKs and wallet availability and the Documentation change log.
- Do not build ahead of a release. Do not build against internal experimental tooling, and do not treat illustrations as an interface.
Assumptions, trust and limitations
- Previews describe intentions that may change. They carry no dates and no promise that any preview becomes available in the form described.
- Planned tools are described by what they would do; no product or package names are used. A tool is available only if Tools, SDKs and wallet availability says so.
Not yet available, and how this page will grow
When a supported release exists, each preview is intended to become a real guide at the same address, so that links and bookmarks would stay valid; the change would be recorded in the Documentation change log. Exact installation commands and released tooling are not yet available.
What this page does not claim
This page does not claim:
- that any tooling, SDK, command-line tool, wallet, package or environment is available;
- any command, version, interface or supported platform;
- any release date or schedule;
- that any planned tool would be production-ready or compatible with other platforms’ tools.
Anything not stated here as available should be treated as unavailable.
Related pages
- Getting started once a release exists — the intended first-run sequence.
- Local development environment — the planned local environment.
- Submitting work and retrieving results — the planned SDK experience.
- Integrating an application end to end — how the concepts would fit together.
- Onboarding an organisation — decisions for organisations.
- Tools, SDKs and wallet availability — what is available today.
Glossary
References
No approved public references yet.
