State-driven open extension ecosystem powered by Coly.
AI should sleep — wake it only when needed.
NicCent is a reactive, state-driven extension ecosystem built on top of the Coly language and runtime.
It replaces traditional Agent / MCP / Workflow paradigms with a shared-state architecture based on ColyVar.
Instead of tool calls or linear pipelines, everything in NicCent is driven by state changes in a distributed network of extensions.
NicCent is composed of four fundamental components:
A programming language designed for state-driven computation.
👉 Official site: https://coly.spwaiter.top/
The central runtime responsible for:
- Managing ColyVar (shared state)
- Coordinating extensions
- Broadcasting state changes
- Maintaining system consistency
ColyVar is the core abstraction of NicCent.
Everything is a state:
- system metrics
- AI outputs
- extension results
- scheduled events
Extensions react to changes in ColyVar instead of direct calls.
PAW is the AI extension runtime of NicCent.
It provides:
- AI-powered extensions
- Multi-model support (via external adapters)
- Reactive execution based on state changes
Supported models are NOT hardcoded — they are provided by extensions.
Examples:
- OpenAI
- DeepSeek
- Claude
- Qwen
- Gemini
- Local LLMs (Ollama, etc.)
Scheduler is an independent process responsible for:
- Time-based triggers
- System event scheduling
- Updating ColyVar states
No polling. No busy waiting.
Everything is event-driven.
NicCent is built as a network of extensions, not a hierarchy.
Example extensions:
- PAW (AI runtime)
- DiskGuard (storage monitoring)
- MemoryOcean (memory analytics)
- ThermalSense (hardware state tracking)
- Scheduler (event engine)
Extensions communicate through ColyVar state changes, not direct calls.
Instead of:
- tool calls
- agent chains
- workflows
NicCent uses:
State Change → Reaction → State Update → Network Propagation
Everything is reactive.
NicCent is NOT:
- ❌ An agent framework
- ❌ An MCP implementation
- ❌ A workflow automation system
It is a reactive distributed runtime ecosystem.
| Paradigm | Model |
|---|---|
| MCP | Tool calling |
| Agent | Continuous reasoning loop |
| Workflow | Sequential execution |
| NicCent | State-driven reactive network |
NicCent is not a tree — it is a network graph.
PAW
↗ ↑ ↖
DiskGuard ColyServer MemoryOcean
↘ ↓ ↙
ThermalSense
↓
Scheduler
All nodes interact via shared state (ColyVar).
- AI should sleep when idle
- No unnecessary computation
- No centralized control flow
- Everything is reactive
- Everything is state
- NicCent Core: Open Source
- PAW: Open Source
- Extensions: Open or Closed (developer choice)
- MCP Adapter Layer
- Extension Marketplace
- Distributed ColyServer
- Cross-platform runtime support
- Cloud synchronization layer (optional)
(to be defined in implementation phase)
Planned:
- install Coly runtime
- run ColyServer
- register PAW extension
- start Scheduler process
"AI is not something that runs continuously.
It is something that should sleep until the world changes."
NicCent is built around this idea.
- Coly Language: https://coly.spwaiter.top/
- PAW Extension System (part of NicCent)
- Scheduler Runtime (part of NicCent)
TBD (Recommended: Apache-2.0 or MIT)