Implementation-first
Every public claim should point toward code, docs, diagrams, workflows, or delivery assets.
About
Neunuc is a platform thesis, a build system, and a business surface.
It is being developed as a modular orchestration platform centered on the nuc runtime. The goal is to connect infrastructure, knowledge, AI, workflows, shared services, and user-facing capabilities into one coherent execution model.
Principles
The platform is strongest when the primitives stay small.
Operation
The central unit of work.
Artifact
A document, codebase, diagram, dataset, output, or evidence object.
Resource
A compute, storage, credential, model, API, or human capacity.
Module
A replaceable implementation unit with a stable contract.
Context
The evidence, memory, scope, constraints, and state around an operation.
Workflow
An ordered or conditional chain of operations.
Agent
An automated executor that performs bounded work.
Policy
Rules for validation, permissions, safety, compliance, and review.
Knowledge
Structured claims, relationships, citations, and reusable understanding.
Connector
A bridge to external systems, repos, files, APIs, or services.
Capability
A packaged service outcome built from primitives.
Interface
A user, machine, document, or agent-facing surface.
Build philosophy
Less pitch deck. More deployable structure.
Composable by default
Capabilities should assemble from reusable objects instead of becoming disconnected one-off apps.
Readable outside the room
Internal architecture must translate into buyer-facing outcomes without losing technical integrity.