DIKWP+BUG Architecture for Purpose-Aware Cognitive Computing

Purpose-aware AI systems are increasingly deployed in safety-critical, multi-agent, and human-facing environments, where they must transform heterogeneous data into timely, explainable, and goal-aligned decisions under uncertainty. Existing architectures often couple perception, reasoning, communication, and security only at the pipeline level. This creates a research gap in unified semantic transformation, purpose-oriented judgment, bounded imperfection handling, and semantic self-protection. To address this gap, this paper proposes a DIKWP+BUG semantic–cognitive reference architecture for artificial-consciousness-oriented computing, without claiming definitive artificial consciousness. The architecture represents cognition through the Data–Information–Knowledge–Wisdom–Purpose (DIKWP) model and uses BUG theory to model bounded approximation, incomplete evidence, and confidence miscalibration in cross-dimensional reasoning. The model is mapped to an Artificial Consciousness Processing Unit (ACPU) reference substrate, an Artificial Consciousness Operating System (ACOS), a DIKWP semantic communication subsystem, and a concept–semantic fused security subsystem. The components are implemented through runtime emulation and evaluated in smart-city governance, autonomous-driving, and medical-triage simulations. Compared with selected baselines, the prototype increased cognitive throughput from $4.5\mathrm{k}$ to $7.8\mathrm{k}$ logged events, reduced perception–action latency from $340\mathrm{ms}$ to $120\mathrm{ms}$, reduced CPU utilization from $95\%$ to $68\%$, lowered smart-city congestion duration by $30\%$, improved emergency response time by approximately $40\%$, achieved 0 collisions versus approximately $2/10$ baseline IoV runs, and improved medical-triage accuracy from $85\%$ to $92\%$. These online-runtime results provide initial feasibility evidence under controlled simulation conditions; they do not include offline model-preparation costs and therefore should not be interpreted as end-to-end lifecycle speedups. Matched-compute ablation, statistical benchmarking, hardware prototyping, and real-world validation remain future work.