Latest verified engineering — 25 October 2026
An owner contract governs computing participation, a separate service licence governs system use, and investment securities remain a distinct family. Actual production and realized economics—not an invented share price—determine value. Local Exchange backend 262/262 passed; no real settlement is proven.
Current engineering record · Studio ingestion · Adaptive computing · Contribution and use economy
Who this manual is for
Prospective rights holders, issuers, commercial customers, institutions and eligible investors. Readers should first understand the product scope and respect the fact that roles, contracts, source permissions and approvals cannot be created by a mere software screen.
Before starting
- Use only an official, current and authorized release.
- Identify which organization or account is responsible for the action.
- Review the permissions, data classification, allowed scope and supporting rights.
- Verify current product availability and the limits of published evidence.
- Do not disclose passwords, access tokens, financial details, sensitive source records or confidential algorithms.
01 — Explore an asset
Open the public instrument or asset directory. Read the asset description, version, provenance, evidence scope, restrictions and risk disclosures. Distinguish technical information from a legal offer before making a decision.
02 — Understand an instrument
Identify whether the record is U, A or I. Check the named grantor or issuer, exactly which rights would be received, geographic and time restrictions, and whether the record is a proposed, approved or active offering.
03 — Evaluate a proposed investment
Read issuer identity, legal offering documents, share or debt terms, eligibility criteria, loss risk, transfer restrictions and sources of potential revenue. Seek independent professional advice where appropriate. Do not send funds through an unverified channel.
04 — Review market information
Identify the currency and whether a price is modelled, quoted, indicative or executed. Compare best bid and ask only where a genuinely authorized market makes them available. Check fees and timestamps.
05 — Review holdings or transaction history
After authorized deployment, log in through the official account, examine instrument identifier, quantity, status and transaction records. Compare the legal entitlement and third-party settlement evidence rather than treating a screen balance as definitive.
06 — Report an issue
Preserve the instrument name, timestamp, description, permitted screenshot and transaction reference. Contact official BTG support. Do not publish private account information, secret credentials or confidential asset data in a public report.
Understanding statuses and results
Proposed: a design or candidate, not an accepted product or offering. Qualified: supported by named evidence within a stated test scope. Authorized: a competent rights holder, organization or regulator has given the particular approval required. Completed: the independently defined outcome has actually occurred, including any external settlement or delivery where applicable.
Common questions
Does the public document grant access?
No. Publishing a description or a manual does not give readers access to private software, underlying data or investments.
Does a test pass establish production readiness?
No. Tests must be interpreted by version and scope; actual production readiness requires the applicable operational, legal and security qualifications.
Who decides data or investment rights?
The legally competent rights holder, issuer, contracting parties and applicable authorities—not a software identifier or automation alone.
Support and issue records
Record the date, relevant public identifier, product version if known, symptom or question, steps observed and the minimum permitted evidence. Report through BTG’s official contact page. Avoid attaching unrelated confidential or personal records.
Detailed workflow and decision record
This is a task and review manual for a planned or specifically authorized deployment. Screen names, buttons, account permissions and automatic outcomes must be checked against the actual tested product version; where the UI has not been verified, instructions are deliberately expressed as actions, not invented clicks.
Examine candidate
Open the asset record and distinguish the data asset from its issuer and any proposed instrument. Note its evidence date and restrictions.
Classify the thing offered
Ask whether the buyer gets use, a transferred right, or a legal financial security. If it is a share, identify the issuer and actual authorized terms.
Check investment information
Look for financial statements, class rights, dilution, material risks, jurisdiction, offering exemption, minimum commitment, custody and the legal decision-maker.
Read market status
Distinguish an indicative example from a legally admitted offer, executable order, matched trade and reconciled settlement.
Check proof
Compare issuer documents, signed entitlements, financial confirmations and ledger records; a ledger entry alone is never conclusive.
Report discrepancy
Record instrument identifier, display timestamp and non-sensitive evidence. Contact the official BTG contact route; do not transmit credentials.
Before operating — acceptance checklist
- Identify the actual operating version and service owner.
- Confirm your role and explicit authority for this data, research or financial action.
- Read the purpose, risks, permitted scope and available evidence before taking action.
- Know which support and incident-reporting channel applies and how to stop safely.
- Make no release, resale, rights-transfer or investment decision on a proposed record alone.
Expected workflow
- Identify the technical asset and version
- Establish actual rights holder and lawful issuer
- Classify U-use, A-transferable right or I-investment security
- Publish instrument terms, limitations, evidence and risks
- Admit trading only under the correct legal authority
- Record contractual effects, reconciled payments and relevant investor entitlements
Problem and recovery guide
| What you notice | What to do |
|---|---|
| Candidate shown as investable | Stop. Demand actual issuer authority, a legally available offering, complete disclosures and permitted distribution mechanism. |
| Wallet or ledger disagrees with statements | Do not assume a financial settlement. Reconcile the actual securities register, custodian and bank records. |
| Price appears without executions | Treat it as an indication, not a verified traded market price. |
| Rights status disputed | Suspend consideration until owner, licence and third-party encumbrance records have been independently reviewed. |
What the operator should record
- Date, timezone, role and intended action.
- Public object identifier and version, never a secret or private credential.
- The authority, permission or review reference in appropriately protected storage.
- Expected outcome versus observed result, including negative and failed cases.
- Whether action is proposed, internally qualified, externally authorized or actually completed.
- Escalation destination and final decision, if any.
What this manual does not promise
Not every capability described here is available to a public account or installed in a consumer application. Real operation depends on qualified builds, actual provider permissions, formally delegated roles and sometimes legal authorization. Do not infer an available menu, released feature, verified rights entitlement or active securities market from a conceptual workflow.
Documents to request before relying on a result
- Issued legal contract and scope of rights
- Issuer incorporation and beneficial ownership evidence
- Professional securities classification and venue analysis
- Authenticated actual corporate financials and capitalization
- Verified investor eligibility and custody arrangements
- Fiat payment, ledger and security-register reconciliation