What a user can ask Studio to do
Import a complete compatible source project, repository ZIP, application project, or authorized package; discover dependencies and missing interfaces; propose real repairs; convert eligible functions into typed DataChips; connect them as Circuits and Genomes; choose local or enrolled remote resources; test equivalence to the original system; and export evidence, source and a qualified build. This is the roadmap; the present local adapter does not autonomously complete arbitrary entire applications.
Nine-stage operator workflow
- Preserve the original input as a hash-pinned, read-only reference.
- Identify permitted source types, licences and sensitive files.
- Map architecture, dependency graph, supported ABI, and expected application behavior.
- Run initial independent tests and record reproducible defects.
- Ask NIKI to generate or repair missing components, using compiler feedback.
- Decompose eligible source into typed reusable DataChips without pretending arbitrary binaries were recovered.
- Build connected Circuits and Genome versions; reject sockets with incompatible types.
- Apply hardware-specific resource plans and compare the original against reconstructed outputs with fixed test oracles.
- Publish only packages that have passed target-device, security, consent and ownership validation.
Gaming, AI and complex applications
For games, eligible component groups include rendering, physics, input, audio, networking, assets and gameplay AI. GPU-specific features, frame latency and actual graphics hardware remain constraints. For large AI systems, quantization, activation checkpointing, batching, partial loading and GPU-qualified offload are possible strategies; no 8 GB device becomes a 24 GB device through software. A program without editable source may be profiled and wrapped only to the extent that its format and rights allow.
Verified current local state
The adaptive system importer passed 7/7 scoped tests; the broader native adaptive Studio integration passed 40/40. Direct-drag and snap visual editor checks passed 28/28 in an earlier focused suite, although nonfatal Tk theme-change shutdown messages appeared. A newly packaged Windows Studio build completed in the local build log; subsequent premium glass jigsaw/direct graph local acceptance passed 19/19 scoped tests. In parallel, HuntAR has been used as an actual imported-source repair case. A browser-level candidate passed 13/13 scoped UI checks against 12/13 for the original; missing assets, real iOS AR and independent Council review remain outstanding. Full real-world arbitrary-source reconstruction, live 25-member Council repair and source-to-EXE equivalence across arbitrary languages are not yet established.
Operator acceptance checklist
Keep original source unmodified; provide meaningful test cases; confirm an executable generated DataChip actually performs its claimed behavior; inspect rights and network permissions; compare output hashes or semantic oracles; test on real target devices; and retain both rejection reasons and successful evidence. Do not claim completion from a screenshot, passing UI element check or a single toy BYTE circuit.
Sources, qualification and related records
Existing Studio system guide · Operator manual · DataChips & Circuits.
Figures refer to scoped local Windows engineering logs as at 25 October 2026. A passed test count does not equate to measured customer deployment. Proprietary source, keys, model credentials, sensitive identity and private account information are not published.