Who this manual is for
System owners, researchers, institutional evaluators and authorized nontechnical operators. 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 — Read a DataChip record
Identify the capability, its owner, version, permitted inputs, output meaning, test scope and restrictions. Do not use a chip solely on the strength of its title.
02 — Understand a Circuit
Trace each step in the published overview and note dependencies, points where decisions are made, data classifications and any human approvals.
03 — Review a Genome revision
Compare version IDs, substituted components, tests required after the change, rights effects and whether release qualification was renewed.
04 — Run a permitted composition
Only within an authorized product release, select a qualified configuration, confirm the permitted data scope, review diagnostics and retain the run reference.
05 — Handle a failed run
Stop reuse of the affected result when validity is uncertain. Preserve the version, error category, bounded test evidence and any permitted diagnostic record for review.
06 — Assess a commercial claim
Ask whether the right offered is software utility, transferable IP or a separately authorized investment. Examine what precisely is licensed and what is withheld.
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.
Select a chip
Check purpose, inputs, outputs, units, supported environment, owner and test status.
Review Circuit
Follow connections in order and flag unconnected inputs or unexpected effects.
Check Genome version
Record precise component versions, dependencies, rights and the last validated test set.
Run bounded test
Use permitted data, compare actual against expected results, inspect failure and timing conditions.
Retain or reject
Promote only when the appropriate test and authorization thresholds have been met.
Handle revisions
Freeze prior state, capture change reason and rerun affected tests before reusing it.
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
- Describe an individual chip’s intended inputs and outputs
- Identify the authorized origin, version and dependencies
- Verify the chip under stated test cases
- Connect compatible chips under a defined Circuit
- Test end-to-end behaviour, failures and permissions
- Freeze the qualified Circuit Genome and record change/retest decisions
Problem and recovery guide
| What you notice | What to do |
|---|---|
| Type mismatch | Stop until contract and conversion are reviewed. |
| Missing dependency | Do not silently substitute an untested component. |
| Unexpected result | Retain inputs and sanitized failure trace within permitted storage; return to last qualified version. |
| Unclear licensing | Refuse commercial use pending source-rights review. |
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
- Signed or recorded owner/lineage statement
- Versioned input-output contract and supported environment
- Unit/integration/regression tests including negative cases
- Qualification and admitted-runtime boundaries
- Reproducible build identity without revealing private source
- Rights Passport and commercial contract when applicable
Corporate system information → Engineering evidence and limitations → Publications → ENTITY (the separately published open component) →
AI Creation Council and FarmNode research — audited update
The council can produce candidate methods for potential DataChips or Circuits only after bounded independent evaluation. Passing 65,536 predetermined test cases is not automatic Genome admission; rights, interoperability, safety, domain fit and owner-signed ENTITY grants remain separate.
Read the complete AI Council research guide → · Public operator manual → · Printable evidence report →