ARKTOR is the SC LABS operational AI platform. It lets AI use files, applications, browsers, computers and connected devices through explicit permissions while the human defines the goal, controls sensitive approvals and keeps authority over consequential decisions.

Which ARKTOR capabilities are already verified?

ARKTOR retains verified Rust engineering gates, external Windows evidence and physically validated Android product-workbench evidence. Current proof includes a 24/24 Core gate, a 96/96 control-layer acceptance gate and eight tested runtime configurations completing the same defined physical Android workflow. Public release readiness remains separately gated.

How does SC Node relate to ARKTOR?

SC Node remains the open-source Rust proof of concept that helped shape the ARKTOR direction. ARKTOR continues that work as a broader operational AI product family while proprietary implementation details remain private.

Does ARKTOR automatically write everything to long-term memory?

No. Durable memory remains controlled. Approved writes can use backup, hashing, verification, audit and rollback, while unrestricted automatic writes and destructive deletion remain separately gated.

How does ARKTOR control execution?

ARKTOR uses explicit permissions, bounded capabilities and auditable outcomes. Important state changes are independently verified before success is reported. Proprietary trust and coordination mechanisms are not part of the public product specification.

Is ARKTOR ready for public download?

Not yet. ARKTOR Core 0.1.1 and ARKTOR Go 0.6 provide verified engineering baselines, but public product downloads still require final packaging, signing, onboarding and product-specific release gates.

SC LABS / ARKTOR · OPERATIONAL AI UNDER HUMAN CONTROL

ARKTOR

OPERATIONAL AI PLATFORM

AI that can operate real digital systems while you keep control of scope, permissions and consequential decisions.

AI can reason.
ARKTOR lets it work.

Q: Does ARKTOR depend on one AI provider?

No. ARKTOR Core contains no mandatory model runtime or provider dependency. Local models and Frontier AI Partners are integrated as higher-level adapters, so provider choice can remain explicit and replaceable.

Give ARKTOR a real workflow. It can inspect evidence, use approved applications and tools, operate tested computers and devices, and return evidence of what changed. You set the scope and approvals; ARKTOR does the permitted work.

Start with a real workflow See ARKTOR on real systems

Human authority
Explicit permissions
Verified outcomes
Local-first
No silent cloud fallback

ARKTOR CONTROLLED SESSION READY

LOCAL MODELFILES: READAPPROVALS: ON

Check this Windows PC before handover. Protect important data and ask before any destructive step.

ARKTOR

I can inspect the approved files and system state first, preserve evidence and stop for approval before reset or removal actions.

Bounded access · explicit approval · outcome evidence

Ask ARKTOR…

Representative product UI. It illustrates the controlled ARKTOR experience; it is not a customer-system screenshot and contains no private workstation data.

NOT JUST ANSWERSParticipate in the actual workflowInspect evidence, use approved tools, operate real systems, test, compare and return results.

LIKE A DIGITAL OPERATORUse the systems people useFiles, applications, browsers, terminals, computers and connected devices can become part of one controlled workflow.

HUMAN IN CONTROLAuthority stays with youYou define the goal, grant permissions, approve sensitive actions and make the final decision.

PROVEN ON REAL WORKBeyond scripted demosARKTOR has been exercised on Windows, Android and demanding multi-step technical research workflows.

THE OPERATING MODEL

Goal → controlled execution → real system → independently verified outcome.

Models provide reasoning while ARKTOR coordinates bounded execution and independently verifies important outcomes. The human retains authority over permissions, scope and consequential decisions.

GOAL→CONTROLLED ACTION→REAL SYSTEM→VERIFY OUTCOME

See the Controller and Model Runtime proof ↗

ONE OPERATING MODEL · FOUR REAL-SYSTEM TRACKS

One operational model. Different real systems.

The same controlled loop has now been exercised across Windows, Android, an in-vehicle Android display and multi-stage security research. Each track keeps its own platform boundary and links directly to the evidence, journal or product context behind the claim.

REAL WINDOWS

WINDOWS x64 · WINDOWS 11 / OOBE

Operate a real PC, not a prepared mockup

External Windows x64 E2E proved the ARKTOR Go + Link path on another machine. A separate real Windows 11 workflow then used controlled actions to inspect and prepare a test PC and return it to OOBE for its next owner.

Evidence ↗Journal ↗ARKTOR Go ↗

PHYSICAL ANDROID

ANDROID · 0.8.7 REFERENCE WORKBENCH

Use a real Android Product Workbench

The retained phone-workbench proof covers persistent chats, model switching with retained context, real Vision, image preview/persistence, verified Android actions, reconnect/lifecycle behaviour and DE/EN/System language selection.

ARKTOR Android ↗Evidence ↗Journal ↗

REAL CAR DISPLAY

AUTOMOTIVE · ANDROID · 4G/LTE

Carry the operating model into the vehicle

A real Android automotive/AI-TBox path was exercised on an in-vehicle display, including remote operation over an independent 4G/LTE path and reconnect after restart. App/UI evidence is kept separate from vehicle telemetry or control, and the public claim stops at the transport behaviour that was physically observed.

Evidence ↗Journal ↗Platform context ↗

REAL RESEARCH

SECURITY RESEARCH · HUMAN DECISION

Reason, test, falsify and preserve evidence

The security-research track used the complete operational loop: form a hypothesis, build controlled tests, try to falsify it, reproduce what survives, preserve evidence and return the consequential decision to the human.

HYPOTHESIS→TEST→FALSIFY→REPRODUCE→EVIDENCE→HUMAN DECISION

Evidence ↗Journal principle ↗

ARKTOR FAMILY

One platform. Clear product paths.

ARKTOR is the operational AI platform. Go, Rescue, Android and Vault turn that platform into products for different jobs. Shared technology stays underneath the family instead of becoming another product list.

ALPHA · RETAINED E2E

WINDOWS · PORTABLE

ARKTOR Go

Take ARKTOR to a Windows PC that still starts for controlled inspection, organisation, migration and assistance without making permanent remote access the default.

INSPECTORGANISEMIGRATEASSIST

Real external Windows proof is retained. The fresh clean-PC one-click release gate still needs verification.Explore ARKTOR Go ↗

PHYSICAL V0.1 ACCEPTED

BOOTABLE RECOVERY

ARKTOR Rescue

Boot independently when Windows cannot start normally, inspect the machine and recover data before moving into repair.

BOOTDIAGNOSERESCUE DATA

Physical diagnosis and hash-verified data rescue are proven. Continuous multi-reboot repair handoff remains the next milestone.Explore ARKTOR Rescue ↗

PHYSICAL PRODUCT WORKBENCH

ANDROID

ARKTOR Android

Persistent chat, vision and controlled device capabilities on Android, with platform permissions and human approvals kept visible.

CHATVISIONDEVICE ACTIONS

0.8.7 remains the stable phone workbench reference. 0.8.8 physically accepted the automotive transport recovery over independent LTE; a separate automotive chat/model issue remains open.Explore ARKTOR Android ↗

0.3.0 ALPHA · VERIFIED LOCAL

DURABLE LOCAL MEMORY

ARKTOR Vault

Keep approved knowledge available across chats, model changes and restarts while retaining source context and user control.

REMEMBERREUSETRACE

Current local alpha passed 21/21 retained memory E2E tests. Public release and broader multi-user hardening remain separate gates.Explore ARKTOR Vault ↗

USE & DEPLOYMENT

Personal and business use can share the same family without pretending they are the same product experience.

DIRECTION

Personal use

Computers, files, migration, organisation, Android endpoints and durable local memory.

DIRECTION

Business use

Controlled AI access to company systems and workflows. Enterprise identity, fleet and compliance features are only claimed when separately proven.

RELIABILITY PROOF · REVIEWED 10 SEPTEMBER 2026

Built to verify the result, not just run the action.

ARKTOR separates model choice, controlled work and outcome verification so a successful action is not automatically treated as a successful task.

96/96accepted control-layer Rust baseline

24/24Core Rust engineering gate retained

8/8tested configurations completed one defined physical Android workflow

FAIL-SAFEuncertain outcomes stay incomplete rather than becoming false success

CONTROL LAYER · ACCEPTED CANDIDATE

Reliability remains a bounded claim

The accepted V0.3 baseline passed its defined 96/96 Rust gate. A later reproduced selection defect was fixed and the deterministic quality gates remained green.

Boundary: an accepted engineering candidate is not universal production readiness.

PHYSICAL ANDROID · 8/8

Same workflow, multiple tested configurations

Eight retained configurations completed the same defined real-device workflow and important state changes were checked independently before success was accepted.

Boundary: one defined workflow on tested hardware; not a universal model, task or Android-device claim.

REPLACEABLE MODELS

Model choice stays separate from product authority

Local and remote model choices can change without giving a model automatic authority over permissions or consequential decisions.

Boundary: no universal speed or model-quality claim.

View current proof ↗

RUST-BUILT CORE · MODULAR BY DESIGN

A focused core. Capabilities that can be combined around the job.

ARKTOR is built around a small Rust foundation and focused capabilities that can evolve independently. Products combine only what they need instead of turning every function into one permanent stack.

BUILDING-BLOCK ARCHITECTURE

Each part has a job. The product combines what the task needs.

Models, computer access, devices, connectivity, memory and skills remain distinct capabilities. They can be combined, replaced or extended without changing the whole product experience.

The idea started in 2013.

The original concept was simple: software capabilities should work like building blocks — small pieces that can be combined, replaced and reused. Modern AI, Rust and today's local computing ecosystem finally make that direction practical.

Founder story. A historical statement about the origin of the concept, not a patent or legal-priority claim.

ARKTOR

MODELSreplaceable reasoning

COMPUTER USEapproved actions

DEVICEScontrolled endpoints

CONNECTIVITYsession choices

MEMORYdurable context

SKILLStask abilities

CONNECTIVITY

Choose the connection model that fits the product.

ARKTOR does not require every endpoint to use the same connection pattern. Local work, managed remote sessions and self-hosted directions can remain separate choices with their own maturity and user-control boundaries.

RETAINED WINDOWS EVIDENCE

MANAGED REMOTE

Remote sessions

Real external Windows evidence exists; fresh public-release verification remains open.

BOUNDARY · Functional proof is not current release certification.

PHYSICAL ANDROID

LOCAL / DEVICE

Direct device sessions

The Android workbench has physically validated local-device operation and reconnect behaviour.

BOUNDARY · Device proof is not a universal Internet claim.

SELF-HOSTED DIRECTION

INFRASTRUCTURE CHOICE

Self-hosted connectivity

A self-hosted direction remains under engineering validation for users who want greater infrastructure control.

BOUNDARY · Stable authenticated Internet E2E remains a release gate.

PLATFORMS · REVIEWED 10 SEPTEMBER 2026

Windows and Android are product platforms, not brand endorsements.

ARKTOR follows the operating system and device boundary. Individual machines are named only when they matter to the evidence record.

REFERENCE PLATFORM

WINDOWS x64

Broad Windows engineering evidence

Portable work, controlled computer use and recovery scenarios have all been exercised on real Windows hardware.

ARKTOR Go retains external Windows E2E
ARKTOR Rescue V0.1 has physical boot, diagnosis and data-rescue proof
Fresh public packaging and one-click release gates remain separate

PHYSICAL PRODUCT WORKBENCH

ANDROID

Chat, Vision and controlled actions on real Android hardware

ARKTOR Android 0.8.7 remains the stable phone-workbench reference with persistent chat, model switching, Vision, image persistence, verified device actions and lifecycle evidence.

Product identity is ARKTOR Android, independent of phone manufacturer
The retained reference phone proof used a Huawei P30 Pro
A separate Android 13 automotive endpoint has also been physically exercised
0.8.8 physically accepted the automotive transport recovery over independent LTE

Explore ARKTOR Android ↗

SKILLS & EXTENSIONS

Add what the task needs without making every ability permanent.

ARKTOR can keep capabilities modular and load task-specific skill context when it is useful. A skill can improve instructions; it does not create new permission or execution authority by itself.

COMPUTER

Files · Apps · System

Approved machine work stays bounded by the product's permission model.

DEVELOPMENT

Code · Git · Test · Build

Engineering abilities can be added for the task without becoming permanent product responsibilities.

WEB

Browser · API

Network-facing work remains separately scoped and reviewable.

DOCUMENTS

PDF · DOCX · XLSX

Document work remains modular rather than inflating the core product.

SKILLS

Task-specific guidance

Relevant skills can be selected on demand instead of injecting every instruction into every session.

PUBLIC BOUNDARY

Capability is public. Private dispatch and trust mechanics are not required to understand the product.

Users need to know what ARKTOR can do, what it may access and how the result is checked. Internal discovery and coordination remain engineering details.

Evidence remains scoped to the tested capabilities and environments.

HOW IT FITS TOGETHER

One product experience, replaceable parts underneath.

ARKTOR keeps reasoning, permissions, real-world capabilities, memory and outcome checks separate enough to evolve independently without exposing that internal machinery as the product itself.

ARKTOR familyGoRescueAndroidVault

↓ user-approved goal

Reasoning + controlReplaceable AI modelsBounded coordination

↓ explicit permission

CapabilitiesFilesApplicationsDevices

VerificationOutcome checksEvidenceFail-safe limits

Human authorityScopeApprovalsConsequential decisions

HONEST ALPHA STATUS

Strong engineering proof. Public release work still remains.

Each claim stays tied to the product path that actually passed it.

Verified now

ARKTOR Core 0.1.1 retains its 24/24 Rust engineering gate
The accepted control-layer baseline retains its 96/96 reliability gate
ARKTOR Rescue V0.1 has physical boot, diagnosis and hash-verified data-rescue proof
ARKTOR Android 0.8.7 remains the stable phone-workbench reference
ARKTOR Android 0.8.8 physically accepted the automotive transport recovery over independent LTE
ARKTOR Vault 0.3.0-alpha.1 retains a 21/21 local-memory E2E suite
ARKTOR Go retains real external Windows evidence

Still being completed

Fresh ARKTOR Go clean-PC public-release verification
Continuous Rescue → reboot → Windows/WinPE repair handoff
Independent closure of the automotive Android chat/model UI issue
Stable self-hosted Internet deployment proof
Final public packaging, signing and onboarding
General public ARKTOR downloads

FAQ

Clear answers without turning the product page into an engineering manual.

What is ARKTOR?

ARKTOR is the SC LABS operational AI platform. It lets AI work with real digital systems while the human defines the goal, controls access and keeps authority over consequential decisions.

What is ARKTOR Go?

ARKTOR Go is the portable Windows path for a PC that can still start: bring a controlled ARKTOR session to the machine, do approved work and leave permanent remote access off by default.

What is ARKTOR Rescue?

ARKTOR Rescue is the bootable recovery path for a PC that cannot reliably start Windows. V0.1 is physically accepted for boot, controlled diagnosis, read-only Windows inspection and hash-verified data rescue. Continuous multi-reboot repair is the next milestone.

What is ARKTOR Android?

ARKTOR Android is the Android product path for persistent chat, vision and controlled device capabilities. Individual phone and automotive devices are test hardware, not separate ARKTOR brands.

What is ARKTOR Vault?

ARKTOR Vault is durable local AI memory. The current 0.3.0 alpha keeps approved knowledge reusable across chats, models and restarts while preserving source context and user control.

Does ARKTOR depend on one AI provider?

No. Model choice is designed to remain replaceable. Using a model does not automatically give it permission or final decision authority.

Is ARKTOR available as a public download?

Not yet. Several product paths have strong physical and engineering proof, but packaging, signing, onboarding and product-specific release gates remain before general public distribution.

OPERATIONAL AI · HUMAN-CONTROLLED · LOCAL-FIRST

Start with the ARKTOR product path that fits the job.

Portable Windows work, bootable recovery, Android endpoints and durable local memory now sit inside one clear product family.

Explore the ARKTOR family Start an ARKTOR pilot