Operational Infrastructure Platform

DNA OS

Build the coordination layer for workflows, business rules, documents, logistics, finance, AI, and operational execution — one governed system instead of disconnected scripts and dashboards.

What
A rules-governed coordination layer that runs workflows, documents, logistics, finance, and AI as one operational system.
Who
System architects, developers integrating operational workflows, and enterprise operators running real business execution.
Why
The system must govern itself — the same rules apply no matter who is operating it, even as the team changes.
How
Core → Gateway → Engines → Cognitive → Presenter → Services → Plugins → Registry → Browser
9
Layers
368
Modules
8/12
Domains Covered
5
Stage Connector Lifecycle

Platform Overview

What DNA OS is

A rules-governed coordination layer, not an application — every module, workflow, and integration in the business runs through the same Constitution and registry.

Purpose

DNA OS เป็น Self-Governing Operating System ที่ขยายได้ไม่จำกัด

Operating Principle

DNA OS เติบโตจากการขยายคลังกฎและ Workflow ไม่ใช่จากการฝึก AI

Structure

v2 — folder reorg (2026-07): renamed v2/v3/v4/v5/v6 version-numbered layers to purpose-named layers. No business logic changed, only physical location + layer naming.

Architecture

How the platform is layered

Every request moves through the same fixed sequence of layers — no layer calls another out of order, and every cross-layer import is declared in the dependency graph.

Modules

Registry health

Generated directly from the codebase on every build — not a static claim about coverage.

Total Modules

368

OK

282

Unused

44

Unregistered

34

Ecosystem

Connectors and external agents

Every external service goes through the same 5-stage connector lifecycle — no direct integrations, no shortcuts. AI agents are one class of worker in this ecosystem, not the center of it.

01
connect
02
register
03
test
04
enable
05
run
login oauth api_key token uri mcp webhook

AI Capability — Vendor-Agnostic Workers

Any agent that follows the Constitution and Execution Contract is DNA OS Compatible — AI is a worker in the system, not the runtime.

claude code · Anthropicgemini cli · Googlechatgpt · OpenAIcopilot · GitHubcursorwindsurfqwendeepseekkimigrokmistralllamacustom
อ่าน Registry
ปฏิบัติตาม Constitution
เขียน CHANGELOG
อัปเดต CURRENT_STATE
รับ Handoff
ผ่าน Validation

Live Sessions

claude-code-1783401743460idle
gemini-code-1783239590082unknown

Operational Domains

Business coverage

8 of 12 operational domains are fully codified today — shown honestly, including the gaps.

งานขาย / เสนอราคา

Covered

sales

6 modules

งานจัดซื้อ

Covered

purchase

2 modules

ลูกหนี้ / ติดตามหนี้

Covered

debt

8 modules

ภาษี / VAT / หัก ณ ที่จ่าย

Covered

tax

1 modules

ขนส่ง / จัดส่งวัสดุ

Covered

transport

5 modules

เอกสาร / ใบเสนอราคา / ใบแจ้งหนี้

Covered

document

3 modules

LINE / Email / แจ้งเตือน

Covered

communication

2 modules

คลังสินค้า / สต๊อกวัสดุ

Planned

inventory

0 modules

บุคลากร / คนขับรถ / ช่าง

Planned

hr

0 modules

ซ่อมบำรุง / เครื่องจักร

Partial

maintenance

0 modules

บัญชี / งบการเงิน

Planned

accounting

0 modules

ความสัมพันธ์ธุรกิจ / Business Timeline

Covered

relationship

3 modules

Developer

Build against the platform

สำหรับนักพัฒนา — Observer, API spec, Modules/Commands/Workflows/Constitution/Capabilities/Drivers, Examples, Playground

Documentation

Registry and architecture reference

The registry explorer and module documentation — architecture, rules, coverage, and connectors — generated directly from the codebase, not maintained separately.

Deployment

Operational status

Live governance check results for the currently deployed build.

8 module(s) need attention
282/368 modules OK — see the Documentation portal for the full registry explorer.