Choose your path
Development status: Overview — This page only routes readers and makes no capability claims; every destination page carries its own status label, and every path passes through a page that states current availability. Cubane is under development, and nothing described in this documentation is publicly available for live use.
Before you read: nothing — this page is a starting point.
Pick the card below that matches your role and goal. Each card states the questions its path answers, gives one recommended reading order, says what you should be able to judge at the end and names the limits of what the documentation can answer today. Paths are reading orders, not tutorials: no step involves installing or running anything. You can leave a path at any point, and the Glossary and Topic index are always available for quick lookup.
Evaluating whether Cubane fits
For developers evaluating fit.
Questions this path answers: what Cubane is intended to do and for whom; what exists today and whether any of it can be used; which application patterns are intended and where their boundaries lie; which parts are simulated; and what would be needed before building, and when — to which the answer is that no dates are published.
Path:
- About the Cubane developer documentation
- Development status: what exists today and what does not
- What Cubane is designed to do
- Capability map
- What you could build: intended application patterns
- Processing sensitive data with verifiable results
- System model: how Cubane is intended to work for its users
- Transaction lifecycle: from submission to result
- Privacy and confidentiality: intent and current limits
- Known limitations of the experimental prototype
- Tools, SDKs and wallet availability
- Future developer experience: what a supported release would add
Outcome: a fit judgement you can explain to a colleague without overstating it.
Limits: there are no answers on performance, price, dates or compatibility; these are stated as unavailable.
Preparing an application, tool or wallet
For developers preparing future applications, tools or wallets.
Questions this path answers: how identity, keys, wallets and approvals relate; what happens to a transaction and to a long-running confidential job; how recorded state can be checked; how data, including confidential data, would be queried; which interfaces exist and where reference would appear; which failures to design for; and what setup and integration would feel like once a release exists.
Path, in stages:
- Concepts: System model: how Cubane is intended to work for its users; Identity, keys and access: concepts; Participant identity; Wallets and the experimental wallet prototype; Key lifecycle: creation, rotation and revocation; Approving actions: authority and multi-party approval.
- Lifecycles: Transaction lifecycle: from submission to result; Confidential jobs: tracking, cancelling and retrieving results; Agreement and finality status; Service levels and admission control; Lifecycle stages used in this documentation.
- Data: Data and state: how information is recorded and retrieved; Committed state and inclusion proofs; Application logic, execution and storage; Querying network data and browsing activity; Querying confidential data.
- Interfaces and failures: Interfaces and their status; What can go wrong: failure and error concepts.
- Future experience: Future developer experience: what a supported release would add; Getting started once a release exists; Local development environment; Submitting work and retrieving results; Integrating an application end to end; How illustrative examples work in this documentation; Versioning, compatibility and deprecation; Glossary.
Wallet and tool builders follow the same path, paying particular attention to the wallets, interfaces and versioning pages.
Outcome: conceptual design readiness — you can sketch an application against the documentation’s lifecycle stage terms and know what a supported release would add.
Limits: no method names, payloads, formats, error codes, package names or commands are given; previews are never instructions, and every example is a labelled illustrative local demo.
Researching intended properties and assumptions
For researchers.
Questions this path answers: which problem is addressed and which properties are intended; what is assumed of each party and what remains observable; what is simulated today; which questions are open; and how claims will be evaluated and what can be cited.
Path:
- Research: problems, properties and open questions
- Problem statement and intended properties
- What Cubane is designed to do
- Security model, trust and limitations
- Trust assumptions and responsibilities by participant
- Known limitations of the experimental prototype
- Threat model and misbehaviour defences
- Cryptographic foundations and trust roots
- What remains observable
- Confidential computation
- The research design notes, listed on the Research overview
- Assumptions and open questions
- Evaluation methodology and published results
- Public references
- Glossary
Outcome: an accurate picture of goals versus evidence, including the explicit absence of published results and approved references.
Limits: design constructions, proofs, parameters and internal mechanisms are not described; further technical reference is not yet available.
Planning adoption in an organisation
For organisations and enterprise integrators.
Questions this path answers: whether the intended platform fits sensitive workflows; who could see the organisation’s data and what stays observable; how keys would be held and actions approved; how costs would be estimated; how change would be governed; what is and is not claimed about compliance; and what onboarding would involve.
Path:
- What Cubane is designed to do
- What you could build: intended application patterns
- Organisation workflows with shared approval and custody choices
- Sharing selected results with auditors and partners
- Use-case profiles
- Visibility controls and selective disclosure
- What remains observable
- Keeping encrypted data available
- Custody options for organisations
- Approving actions: authority and multi-party approval
- Fees and cost estimates
- Governance, compliance and assurance
- Compliance position and data-protection intent
- Onboarding an organisation
- Development status: what exists today and what does not
Outcome: a decision list for a possible future adoption, and an accurate statement of what is not offered today.
Limits: no service terms, prices, or legal or regulatory assurances are given.
Preparing to operate infrastructure
For prospective operators.
Questions this path answers: what operating would involve; what exists today and whether anyone can prepare; what would be monitored, backed up and recovered; how upgrades and incidents would be handled; and whether staking, penalties and governed economic settings are intended.
Path:
- Operating a node: intended roles and what exists today
- Development status: what exists today and what does not
- Networks and environments
- Participants and roles
- Peer-to-peer networking
- Node monitoring and observability
- State persistence, snapshots and recovery
- Deployment, backup and recovery: what operators would plan for
- Emergency controls and protocol safeguards
- Time-delayed execution and staged upgrades
- Staking and validator participation
- Penalties for misbehaviour
- Treasury and governed economic settings
- Threat model and misbehaviour defences
Outcome: realistic expectations — the responsibilities to plan for and the items that are explicitly not yet specified, with no readiness checklist that could be mistaken for a real one.
Limits: no requirements, hardware, ports, commands or rewards are given, and no operator prerequisites can be listed until a release exists.
Assessing claims and evidence
For assurance readers: auditors, regulators and reviewers.
Questions this path answers: what is claimed, what is implemented and what evidence exists — to which the answer is that no audits or measurements are published.
Path:
- Known limitations of the experimental prototype
- Security assurance status and reporting problems
- Audit trails and tamper-evident logging
- Visibility controls and selective disclosure
- Compliance position and data-protection intent
- Governance, compliance and assurance
- Governance proposals and decisions
- Threat model and misbehaviour defences
- Evaluation methodology and published results
Outcome: a clear separation between intent, internal experimental work and published evidence.
Limits: no certification, audit result or legal assurance is offered.
Assumptions, trust and limitations
- Paths reflect the documentation as of this page’s date, and every destination keeps its own status label.
- Nothing on any path is available for live use, and no path involves installing or running software.
- A path is a suggested order, not a prerequisite chain; the “Before you read” note on each page gives its real prerequisites.
Not yet available, and how this page will grow
When releases exist, the application path would gain released getting-started material and versioned reference, and the operator path would gain published requirements. Paths will be revised when pages are added, renamed or retired, and each revision will be recorded in the Documentation change log. Paths link only to published pages, never to placeholders.
Related pages
- About the Cubane developer documentation — scope and the site-wide notice.
- Development status: what exists today and what does not — the status hub every path passes through.
- Capability map — every documented capability with its status label.
- Glossary — definitions for terms met on any path.
- Topic index — direct lookup by topic for readers not following a path.
Glossary
References
No approved public references yet.
