Capabilities / One Operating System
Six domains answer six procurement questions: who acts, how the system improves, how risk is controlled, where data and models run, how delivery becomes engineering, and how existing work entry points connect.
They share one runtime kernel. Channels do not create another customer truth, the CLI does not bypass permissions, the growth loop does not skip Release Gate, and topology does not change governance or audit semantics.
NexusClaw operating chain
one kernel · six domainsrecords and knowledge
identity sets authority
access, guardrails, approval
trace and tool evidence
outcome and ownership
turn corrections into rollback-ready assets
set data and model boundaries
make delivery an engineering workflow
return every entry to one runtime chain
01 / Operating Foundation
This layer answers who acts, what they may do, and how outcomes return to business.
Digital Workforce
Independent employees run with their service account and role; assistants inherit the real caller’s authority. Identity sets the authorization subject while the execution engine owns tools, approval, handoff, and write-back.
02 / Trust & Improvement
Enterprises need more than successful execution: they need refusal, accountable approval, and rollback.
Growth Loop
Execution signals become explicit candidates, then pass draft, simulation, evaluation, human approval, and Release Gate. Production behavior is not rewritten by uncontrolled self-modification.
Governance
Permission-aware context, L0–L4 guardrails, human approval, trace, tool calls, cost, and audit events form one control plane.
03 / Delivery & Access
Deployment, developer tools, and channel adapters deliver the system to customer boundaries without redefining permissions, audit, or customer truth.
Deployment
Managed SaaS, hybrid cloud plus customer AI PC, and private/single-host full stack have different resource and responsibility models while sharing one governance chain.
Developers
nexus CLI brings target resolution, source sync, Workforce training, machine output, and rollback to the terminal while preserving workspace isolation, permissions, audit, and Release Gate.
$nexus workspace current --target-org dev
one TargetContext resolved
$nexus source push --dry-run --json
phase: dry-run · remote unchanged
$nexus deployment rollback --history-id <id>
revision-ledger entry recorded
Integrations
WeCom, Feishu, DingTalk, Web Chat, API, phone, and Mobile H5 are access channels that return to one identity, routing, execution, audit, and attribution chain.
Evaluation map
Bring a real operating chain and start from an external entry or business record. Validate identity and access, controlled execution, human takeover, audit and attribution, governed improvement, and the selected deployment boundary. No number of features should hide a missing link.
This reflects the current platform scope. The growth loop is human-gated and is not an autonomous self-evolution promise. Resource figures apply only to their named topology. Channel, model, and Community-edition depth follow project and release contracts.
We will validate it with all six domains: who acts, how control works, what evidence remains, how improvement releases, where it runs, and where work enters.
