# ARKTOR

> ARKTOR is the public SC LABS controlled-AI product family, now grounded in a verified minimal Rust foundation.

Canonical page: https://sclabs.uk/arktor/
Machine-readable verified facts: https://sclabs.uk/arktor/product-facts.json
Parent organisation: https://sclabs.uk/
Status: Product Family Alpha · Core, Go, Link and Node engineering paths verified
Last verified: 2026-08-18

## What ARKTOR is
ARKTOR separates a small deterministic execution core from optional intelligence and product layers. ARKTOR Core owns bounded file, process and system primitives, a typed JSON contract and signed sidecar execution. Memory, models, browser automation, Windows UI and orchestration remain modular.

## Verified foundation
- ARKTOR Core 0.1.1 isolated Rust foundation
- 24/24 Core tests PASS
- Independent red-team hardening: a reproducible Windows executable-resolution boundary issue was fixed in Core 0.1.1 and retained as a regression gate
- Rust formatting PASS
- Clippy with warnings denied PASS
- Optimized release build PASS
- Standalone empty-folder smoke PASS
- Bounded file, process and system primitives
- Transport-neutral JSON request/response contract
- SHA-256 and Ed25519 signed-sidecar contract
- No mandatory HTTP, MCP, Python, Node, browser, Windows UI or model runtime in Core

## Why ARKTOR Node exists
SC Node remains the historical public open-source proof of the earlier controlled Rust runtime direction. ARKTOR Node is the second-generation slim runtime built after those lessons, not a rename. Its hot path is Model -> Permission Gate -> Native Tool -> Audited Result -> Model. Workspace file tools, explicit write/process grants and lightweight audit stay in the MVP; memory/RAG, browser automation, Windows UI, multi-agent orchestration, MCP hosting, Link/Relay and provider routing stay outside it.

## Product paths
- ARKTOR Go 0.6: live-tested portable Windows x64 access core
- ARKTOR Node 0.1.0-alpha.1: 14/14 Rust tests PASS, strict Clippy PASS, optimized release build PASS; live Node execution evidence verified through Link
- ARKTOR Node benchmark reference: 100 measured pairs, median provider-path delta 14,700 ns on the reference Windows workstation
- Portable v1 decision: explicit user start, no permanent service by default, outbound-only target connectivity and no AI-provider secret stored on the endpoint
- ARKTOR Business: planned controlled daily-work product path
- ARKTOR Private: planned dedicated private-infrastructure product path
- ARKTOR Vault: local context and controlled durable-memory module
- ARKTOR Link: external Windows x64 E2E verified through the native owner path; owner-bound full-control, system.info, file list/read and process.run PASS
- Relay and Rescue remain separate modular streams

## Internal engineering proof
The internal AURON environment proved autonomous orchestration through 1,550/1,550 deterministic checks, 10/10 unattended soak runs and 33/33 project-routing regression checks. Operational review later removed autonomous orchestration from the primary production path; it continues as separate R&D rather than a production dependency.

## Not yet complete
General public ARKTOR downloads, production Windows code signing/public one-click onboarding, release soak, signed-module distribution and the public Business/Private product experiences remain release work.

## Naming
AURON remains the internal SC LABS engineering and orchestration environment and Engineering Journal author. ARKTOR is the public product family.