Foundational System Documentation
Foundational Whitepapers
These documents define ARMI’s public-interest mandate, ethical boundaries, and system architecture across education, justice, and digital immunity.
Reference Library
Whitepapers & System Documents
This library serves as the technical and structural reference collection for the public digital infrastructure framework. The documents published here describe how the architecture is built, how its systems are composed, and how its components interact at an engineering and operational level. They are written as working system definitions rather than as conceptual or policy statements.
The materials in this section focus on implementation-facing detail: system architecture, interface contracts, execution layers, integration boundaries, deployment models, and operational constraints. Together, they form the technical substrate that makes the framework concrete, reviewable, and implementable in real environments.
This collection is intended for engineers, system architects, auditors, and institutional technical teams who need to understand not only what the framework is meant to do, but how it is structured to behave in long-lived, real-world deployments.
The documents here are versioned, citable, and designed to evolve over time. Many will remain under review as the architecture is refined and tested across different institutional contexts. Inclusion in this library does not imply finality; it indicates technical maturity sufficient for examination, implementation, and formal review.
Conceptual, architectural intent, and governance framing documents are maintained separately in the Research section. This library is reserved strictly for concrete system descriptions, specifications, and technical structures that make the framework operable in practice.
Technical Reference
Core Technical Volumes
These documents form the primary, cross-cutting technical reference set for the public digital infrastructure. They define overall system structure, architectural composition, and integration logic at the highest technical level.
Unlike domain-specific or subsystem papers, the volumes listed here describe the shared foundations of the architecture itself. They are intended to be read as the root technical definitions that all other system specifications build upon.
Full Technical Specification
Comprehensive technical definition of the complete system architecture and components.
Software Architecture
Logical and internal software structure of the implementation stack.
Architecture & Integration
Cross-layer structural composition and system integration patterns.
Figures & Diagrams
Canonical reference diagrams used across the technical specification set.
System Documentation
System & Architecture Whitepapers
The sections below contain the technical definition documents for the individual systems and major architectural layers of the infrastructure. Each group focuses on the internal structure, interfaces, integration patterns, and implementation constraints of a specific subsystem or execution layer.
Unlike the Core Technical Volumes, which define the shared foundations of the architecture as a whole, the documents organized here describe how those foundations are applied, specialized, and realized in concrete systems.
These papers are written as implementation-facing references. They are intended to support engineering, system integration, auditing, and long-term technical maintenance across institutional deployments.
Documents may appear in review form as the architecture evolves. Their identifiers and references remain stable and are intended to be used directly in real technical work.
Framework (Technical)
These documents define the technical framework of the infrastructure: how its major layers connect, how interfaces are structured, and how integration is performed across systems. This section does not contain institutional, governance, or conceptual framing documents.
Public Digital Infrastructure Design Guide
Technical design guidance for long-lived, institutionally deployed infrastructure.
DIPA Ecosystem Overview
Technical ecosystem structure and system-layer relationships.
ICI Technical Definition
Technical definition of the Intelligent Civic Interface and its system role.
Architecture & Core Structure (Technical)
The core technical architecture of the system is defined in the Core Technical Volumes listed above. Those documents describe the overall structure, software composition, integration boundaries, and cross-layer relationships of the platform as a whole.
The sections that follow do not repeat that material. Instead, they describe how this shared architecture is applied, specialized, and realized within specific systems, execution layers, and institutional domains.
Interpretation, Boundary & Immunity (Technical)
These documents define the concrete implementation of the interpretation, boundary, and continuity layers. They focus on internal structure, technical composition, and system behavior rather than institutional or conceptual framing.
NIIS Architecture
Internal structure and composition of the digital immunity layer.
NISS Blueprint
Blueprint-level specification of containment and continuity mechanisms.
CII Interface Specification
Formal interface definition for the constitutional boundary layer.
Education (Technical)
These documents define the technical implementation of the education systems, including system architecture, internal component structure, and specialized control mechanisms for institutional and child-centered learning environments.
IM System Architecture
Architecture and internal component structure of the institutional learning system.
KIM MVP Prototype
Technical prototype and implementation structure of the child-centered system.
Guardian Switch Specification
Technical specification of the intervention and containment mechanism.
Justice (Technical)
These documents define the technical implementation of the justice systems, including functional scope, system boundaries, internal coordination, and integration of continuity and integrity mechanisms within the justice access infrastructure.
JARS Scope & Functional Boundaries
Formal definition of scope, limits, and responsibilities of the JARS system.
Justice & Integrity Network System (JINS)
Technical definition of the inter-institutional justice coordination network.
Justice Desk (JD) — MVP
Implementation structure and functional layout of the Justice Desk system.
Rights Desk (RD) — MVP
Technical structure and feature scope of the Rights Desk system.
Digital Immunity for Justice
Integration of continuity and integrity mechanisms within justice systems.
Core Platform & Infrastructure
These documents define the shared technical substrate used across all domains, including core data structures, interface contracts, operational topology, and system-level flow and segmentation. They are not specific to any single sector and apply to the platform as a whole.
Database Schema
Canonical data structures shared across systems.
API Design
Public and internal interface definitions for system integration.
Security Zone Architecture
Operational segmentation and isolation model for deployments.
System Dataflow
End-to-end data movement and processing flow across the platform.
Execution & Continuity (Technical)
These documents define the concrete implementation of the execution and runtime layers of the infrastructure. They focus on deterministic behavior, kernel structure, system composition, and the internal mechanics of machine-level and network-level execution.
NCS Kernel Specification
Kernel-level definition of deterministic network execution behavior.
NCS Technical Definition
Formal technical definition of network-level execution scope and limits.
NCS Architecture & Integration
Structural integration of network execution within the overall system.
MCS Technical Papers
Collected technical papers on machine-level execution internals.
Operational & Deployment Specifications
These documents define how the systems are deployed, operated, staged, and maintained in real institutional environments. They do not describe core architecture or execution internals. Instead, they specify operational structure, rollout strategy, administrative control, and resource planning required for long-lived, real-world deployments.
This section exists to separate system design from system operation. The documents listed here are used by deployment teams, institutional operators, and program planners rather than by core system engineers.
Administration & Operations
Operational administration, deployment, and management structure.
Budget & Cost Model
Cost structure and institutional planning model for deployments.
Pilot & MVP Estimation
Scope, staging, and resource estimation for pilot deployments.
School Deployment & Data Policy
Operational deployment constraints and institutional data handling structure.
JD Procedural Guidance Framework
Operational specification of procedural guidance flows and institutional constraints.
Closing Note
This library is intended to function as a living technical reference. The documents collected here describe systems and structures that are designed to evolve over time, under real institutional use, review, and operational pressure.
Some specifications will change, some will be split or merged, and others will be refined as deployments mature and new requirements emerge. Stability in this context does not mean immobility; it means that changes are made deliberately, traceably, and in ways that preserve long-term continuity.
These documents are not published as abstract proposals. They are written to be examined, implemented, audited, and maintained by technical teams working in real environments. Their purpose is to support durable public infrastructure, not short-lived experimentation.
Conceptual framing, institutional role definitions, and governance models are maintained separately in the Research section. This library remains focused on the concrete technical structures that make such frameworks operable in practice.