Onboarding an organisation

Development status: Planned — Planned experience, not instructions. This preview lists the decisions an organisation would expect to make before adopting Cubane and the responsibilities that would remain its own. Every capability behind these decisions is planned or being explored, and none is available. The page contains no service terms, prices, contracts or legal assurances, and nothing is publicly available for live use.

Before you read: Future developer experience: what a supported release would add.

What would an organisation need to decide and prepare before adopting Cubane? This page sets out, as a concept-level checklist, five decisions an organisation would make — a starting profile, custody, approval authority, cost estimation and a visibility policy — each with the question behind it, the status of the underlying capability and a link to where it is explained. It ends with the responsibilities that would stay with the organisation.

Planned experience, not instructions. This is a planning aid, not an onboarding procedure. No onboarding is available today.

Choosing a starting profile

Status of this section: Being explored — no profile is defined.

• What is intended. Opinionated starting profiles are being explored to help teams choose confidentiality and performance settings for common use cases; see Use-case profiles.
• The question. What kind of workload is the organisation planning, and how much confidentiality does that workload need?
• Not described. Profile names and settings are not described.

Deciding custody

Status of this section: Being explored — custody choices do not exist in the experimental implementation.

• What is intended. The design is being explored to let an organisation choose how the signing keys behind its funds are held, for example by one party or by a group of parties; see Custody options for organisations.
• The question. Who, in or around the organisation, would hold signing keys?
• Not described. This documentation does not describe custody services or providers, and it does not describe Cubane holding organisations’ keys.

Setting approval authority

Status of this section: Being explored — nothing enforces approval by several parties.

• What is intended. Approving a sensitive action could require several authorised approvers, separate from the key used for day-to-day signing; see Approving actions: authority and multi-party approval.
• The question. Which actions need more than one approver, and who would those approvers be?
• In practice. How such arrangements would fit an organisation’s work is illustrated on Organisation workflows with shared approval and custody choices.

Estimating costs

Status of this section: Planned — the design is being explored; estimates are not available.

• What is intended. The planned developer experience would allow a customer to request a price estimate before submitting work; the design is being explored and is not available. See Fees and cost estimates.
• The question. How would the organisation budget for its intended workload?
• Not given. No prices, rates or estimates are given, and no fees are charged anywhere today.

Setting a visibility policy

Status of this section: Being explored — no access-controlled data exists in the experimental prototype.

• What is intended. Data owners are intended to decide who can see which data, including time-limited access for auditors; see Visibility controls and selective disclosure.
• The question. Who inside and outside the organisation should see which data, and for how long?
• What remains visible. Some protocol metadata remains observable even with confidential execution; see What remains observable.

Each of these five decisions would be the organisation’s own, made separately. Answering the questions now — even provisionally — is useful preparation, because the questions do not depend on details that are still unsettled.

The organisation’s own responsibilities

Whatever the platform eventually provides, an organisation would remain responsible for:

• Its obligations. Assessing its own legal and regulatory obligations; see Compliance position and data-protection intent.
• People and roles. Managing its approvers, key holders and internal roles, and changes to them over time.
• Its data. Classifying its data and deciding what it is prepared to submit.
• Governance changes. Following governance changes that could affect it; see Governance, compliance and assurance.
• Monitoring and incidents. Planning its own monitoring and incident response.

Assumptions, trust and limitations

• Each decision depends on capabilities that are planned or being explored, and the decisions themselves may change as designs settle.
• This page is a planning aid. A release would define the supported options for each decision.
• Statements on this page describe intent; none is an offer, a commitment or a term of service.

Not yet available, and how this page will grow

Once released, onboarding guidance would be expected to walk through these decisions with the supported options documented for each. When that guidance exists, it is intended to replace this preview at the same address, and the change would be recorded in the Documentation change log. Further technical reference is not yet available.

What this page does not claim

This page does not claim:

• any service terms, prices, contracts or support levels;
• any legal or regulatory assurance;
• any integration design;
• that any onboarding is available today.

Anything not stated here as available should be treated as unavailable.

Related pages

• Organisation workflows with shared approval and custody choices — the application pattern behind several of these decisions.
• Use-case profiles — starting profiles.
• Custody options for organisations — the custody choice.
• Approving actions: authority and multi-party approval — approval authority.
• Fees and cost estimates — cost estimation.
• Visibility controls and selective disclosure — the visibility policy.
• Compliance position and data-protection intent — what is and is not claimed about compliance.

Glossary

• Use-case profile
• Custody
• Signing key
• Multi-party approval
• Approval authority
• Cost estimate
• Visibility
• Time-limited access

References

No approved public references yet.