Latest verified engineering — 25 October 2026
Studio's October 25 expansion includes native project inspection, source preservation, typed reconstruction and hardware-aware optimization. Adaptive native Studio local QA passed 40/40 and a Windows build completed; complete autonomous arbitrary-project reconstruction and independent 25-member Council review remain unqualified.
Current engineering record · Studio ingestion · Adaptive computing · Contribution and use economy
Purpose
BTG Studio is the visual and programmable construction environment. A person describes the system they want. Studio identifies available DataChips and typed Circuit interfaces; NIKI proposes genuine missing capabilities; FarmNode executes permitted tests; a Council is intended to challenge and verify output; ADAM and BTDU keep reproducible versions, while ENTITY controls who is allowed to use or publish each part.
A visual puzzle piece alone is not a functional invention. A complete system requires runnable components, correct interfaces, input/output tests, resource boundaries, persistence, packaging and user documentation.
Five-product integration
ENTITY: authenticate subject and device; verify scoped account and owner grants. Bridge: request permitted real data and permitted destinations, without transferring unrelated private information. Bit Trade Global: resolve and validate the instrument or licence, with rights different for U-class, A-class and I-class instruments. FarmNode Host: execute only allowed compatible workloads and return signed evidence. Studio: assemble, test, repair and package verified functional systems.
Intended construction workflow
1. The owner specifies measurable requirements and constraints in Studio. 2. Typed capabilities are discovered, and exact missing pieces are listed. 3. NIKI proposes candidate code, circuits, tests and tools. 4. The Council challenges the proposal with independent model responses when real models are connected. 5. Only approved code runs in a restricted evaluator and on qualified FarmNodes. 6. Working versions and failures are stored in a reproducible Genome; a reviewer approves promotion. 7. The finished application or system is built, installed and tested on its intended device, rather than represented by a mockup.
What is demonstrated
At the 24 October audit, the existing Composer integration passed 6/6 tests, puzzle visual checks 9/9, constructor/compiler 21/21 and original FarmNode regression 22/22. A Windows BTG Studio executable has been installed. A subsequent Studio–Bridge–Exchange–FarmNode local rights integration suite was repaired and independently rerun, passing 8/8 tests. That validates only the scoped local research integration; purchased rights, unified production authorization and complete automatic system construction remain unqualified. Genuine independent Council quorum, complete autonomous construction and production identity remain unfinished.
Safety and rights
Do not run untrusted generated code outside a sandbox. Do not accept output because a model is confident or a UI looks finished. Never expose private source, passwords or user data to unauthorised model providers. A commercial instrument does not override ENTITY, data consent, device or scope restrictions.