Member Site Directory: All Authority Domains in the Technology Services Network

The Technology Services Network operated through computerscienceauthority.com comprises 7 authority domains, each covering a distinct vertical within professional technology services. This directory documents the scope, subject matter, and structural role of each member domain, and describes how the network's coverage maps across infrastructure, data intelligence, and software development disciplines. Researchers, procurement officers, and technology professionals navigating specialized service sectors use this directory to identify which domain governs a given technical area and how the domains interrelate.

• Definition and scope
• Core mechanics or structure
• Causal relationships or drivers
• Classification boundaries
• Tradeoffs and tensions
• Common misconceptions
• Checklist or steps
• Reference table or matrix
• References

Definition and scope

A technology authority network is a structured cluster of reference-grade domains, each assigned a non-overlapping subject scope within a broader technical discipline. The computerscienceauthority.com hub anchors 7 member sites spanning artificial intelligence, cloud infrastructure, data science, database systems, distributed systems, operating systems, and software engineering — disciplines that collectively represent the core of the ACM Computing Classification System (ACM CCS 2012), the authoritative taxonomy maintained by the Association for Computing Machinery.

Each member domain functions as an independent reference authority for its vertical, providing practitioner-grade documentation of service landscapes, qualification standards, regulatory frameworks, and technical classifications. The network is structured so that no two domains share a primary subject boundary: artificial intelligence methods do not overlap with cloud infrastructure operations, and database systems administration is formally separated from data science methodology. This non-overlap rule mirrors the partitioning logic used in the IEEE Computer Society's technical committee structure, which segments computing into discrete bodies of knowledge (IEEE Computer Society Technical Committees).

The full member directory provides the canonical listing of all active domains with their assigned scopes and coverage maps.

Core mechanics or structure

The network operates as a hub-and-spoke reference architecture. The hub — computerscienceauthority.com — maintains cross-domain coverage for topics that span multiple verticals, including foundational cross-domain technology concepts such as concurrency, fault tolerance, and cryptographic primitives. Each spoke domain is responsible for depth coverage within its assigned vertical.

Artificial Intelligence Systems

Artificial Intelligence Systems Authority covers the professional and technical landscape of AI system design, model development, deployment pipelines, and governance frameworks. This domain is the primary reference for practitioners working across machine learning infrastructure, neural architecture selection, and emerging AI regulatory compliance requirements under frameworks such as the NIST AI Risk Management Framework (NIST AI RMF 1.0).

Cloud Computing

Cloud Computing Authority documents the cloud services sector across the three canonical delivery models — Infrastructure as a Service (IaaS), Platform as a Service (PaaS), and Software as a Service (SaaS) — as defined by NIST Special Publication 800-145 (NIST SP 800-145). The domain covers provider landscape analysis, service procurement standards, shared responsibility frameworks, and the FedRAMP authorization process for cloud services used by US federal agencies.

Data Science

Data Science Authority addresses the professional service sector built around statistical modeling, predictive analytics, and data pipeline engineering. This domain defines qualification standards, methodology frameworks including the Cross-Industry Standard Process for Data Mining (CRISP-DM), and the boundary between data science and adjacent disciplines such as business intelligence and machine learning operations.

Database Systems

Database Systems Authority covers the full spectrum of database technology — relational, NoSQL, NewSQL, and time-series systems — along with database administration as a professional discipline, licensing categories, and the ANSI/ISO SQL standard (ISO/IEC 9075) that governs query language conformance. This domain is the reference for procurement teams evaluating database platforms and for professionals holding credentials such as the Oracle Database Administrator Certified Professional or Microsoft Certified: Azure Database Administrator Associate.

Distributed Systems

Distributed Systems Authority documents the engineering and operational service landscape for systems spanning multiple networked nodes — including consensus protocols, fault-tolerant architectures, and the CAP theorem tradeoffs first formalized by Eric Brewer in 2000. The domain covers distributed middleware, service mesh frameworks, and the professional roles responsible for operating large-scale distributed infrastructure.

Operating Systems

Operating Systems Authority provides reference coverage of operating system architecture, kernel variants, scheduling algorithms, and the professional service ecosystem surrounding OS deployment, hardening, and administration. The domain maps directly to the infrastructure and systems vertical and cross-references the NIST National Vulnerability Database (NVD) for OS-level security classifications.

Software Engineering

Software Engineering Authority covers software development as a professional and regulatory discipline, including the IEEE Standard for Software Engineering Body of Knowledge (SWEBOK v4, IEEE SWEBOK), software lifecycle models, quality assurance frameworks, and the credentialing landscape for software engineers including IEEE Certified Software Development Professional (CSDP) certification.

The how the domains relate reference page maps dependency and overlap relationships across all 7 member domains.

Causal relationships or drivers

The network's 7-domain structure reflects the partitioning of computer science as a professional discipline, not an arbitrary editorial grouping. The ACM and IEEE jointly published the 2013 Computer Science Curricula (CS2013), identifying 18 knowledge areas in undergraduate CS education — the Technology Services Network's domain boundaries map to 7 of those areas where professional service markets have formed distinct procurement and credentialing ecosystems.

Three structural forces drive the need for domain-level specialization at this depth:

Regulatory divergence. AI systems face governance requirements under the NIST AI RMF and emerging EU AI Act alignment efforts, while cloud platforms face FedRAMP and StateRAMP authorization processes, and database systems face HIPAA technical safeguard requirements under 45 CFR Part 164 (HHS HIPAA Security Rule). A single generalist domain cannot adequately address these divergent regulatory landscapes.

Credentialing fragmentation. The technology credentialing market includes over 300 active vendor-neutral and vendor-specific certifications across the 7 domains covered by this network, according to the IT certification tracking maintained by CompTIA (CompTIA IT Industry Outlook). Domain-specific reference authorities allow credential seekers and hiring organizations to navigate this landscape without conflating unrelated qualification pathways.

Service procurement complexity. Enterprise technology procurement across the data and intelligence vertical and software development vertical requires evaluation criteria specific to each domain — database RFPs invoke different technical standards than AI model deployment contracts or cloud service agreements.

The network coverage map visualizes how these causal drivers map to specific domain assignments.

Classification boundaries

The network applies three primary classification axes to determine which domain governs a given technical topic:

1. Layer of the computing stack — Operating systems and distributed systems occupy infrastructure layers; database and data science domains occupy data layers; AI systems and software engineering span application and model layers.
2. Professional role alignment — Each domain corresponds to at least one recognized professional role category in the US Bureau of Labor Statistics Standard Occupational Classification system (BLS SOC 2018), specifically under SOC 15-0000 (Computer and Mathematical Occupations).
3. Standards body jurisdiction — Topics governed by ISO/IEC JTC 1/SC 32 (data management) map to the database domain; topics under ISO/IEC JTC 1/SC 42 (artificial intelligence) map to the AI domain; topics under ISO/IEC JTC 1/SC 7 (software engineering) map to the software engineering domain (ISO/IEC JTC 1).

The network editorial standards document defines how boundary disputes between domains are resolved and which topics receive coverage at the hub level.

Tradeoffs and tensions

Several structural tensions shape how the network's 7 domains are bounded and maintained.

Depth versus completeness. A domain assigned a narrow scope — such as operating systems — achieves greater depth on kernel architecture and scheduling than a broader domain could, but risks leaving cross-cutting topics (e.g., containerization, which involves OS primitives, distributed systems orchestration, and cloud deployment) without a clear primary home. The network resolves this by assigning containerization to the how-it-works hub-level coverage, with contributing treatment from both the operating systems and distributed systems domains.

Stability versus emergence. Software engineering and AI systems represent opposite ends of the stability spectrum: SWEBOK v4 codifies practices accumulated over 5 decades, while AI systems governance frameworks — including the NIST AI RMF, published in January 2023 — are revised on compressed timescales. Domain coverage must balance stable reference content with timely updates to regulatory and standards developments.

Vendor neutrality versus practitioner utility. The membership criteria for network domains require vendor-neutral framing, consistent with IEEE and ACM publication standards. However, practitioners in database administration and cloud computing frequently require vendor-specific qualification information. The network addresses this by documenting vendor-specific credentials and platforms within a vendor-neutral classification framework.

Common misconceptions

Misconception: Data science and database systems cover the same subject matter.
These are structurally distinct domains. Database systems covers storage engine architecture, query optimization, ACID transaction models, and DBA professional practice. Data science covers statistical modeling, feature engineering, and analytical pipeline construction. The ACM SIGMOD and ACM SIGKDD technical communities — which correspond to these domains respectively — have non-overlapping conference tracks and publication venues.

Misconception: Cloud computing and distributed systems are redundant.
Cloud computing authority covers commercial cloud service procurement, provider evaluation, and deployment governance. Distributed systems authority covers the underlying architectural patterns — consensus algorithms, replication models, Byzantine fault tolerance — that cloud platforms implement but do not expose directly to service buyers. A procurement officer uses cloud computing authority; a systems architect designing a multi-region replication strategy uses distributed systems authority.

Misconception: The AI domain subsumes all data-related disciplines.
Artificial intelligence systems authority is scoped to AI model architecture, training infrastructure, deployment pipelines, and AI-specific governance. It does not govern data warehouse design, ETL pipeline administration, or relational schema normalization — those fall under database systems and data science authorities respectively, consistent with the ISO/IEC JTC 1 subcommittee partitioning described above.

Misconception: Software engineering and operating systems overlap on systems programming.
Systems programming languages and techniques are covered by software engineering authority from a methodology and toolchain perspective. Operating systems authority covers the runtime environment those programs execute within — kernel APIs, scheduling, memory management, and OS-level security. The network glossary provides canonical term definitions that resolve these boundary cases.

Checklist or steps

Domain selection protocol — for researchers and procurement teams identifying the correct member domain:

1. Identify the primary technical layer: infrastructure (OS, distributed systems, cloud), data (database, data science), or application (software engineering, AI systems).
2. Map the professional role category involved to a BLS SOC 15-0000 subcategory.
3. Identify the applicable standards body jurisdiction (ISO/IEC JTC 1 subcommittee, IEEE technical committee, or ACM SIG).
4. Cross-reference the topic against the network coverage map to confirm primary domain assignment.
5. If the topic spans 2 or more domains, consult cross-domain technology concepts for hub-level coverage.
6. For regulatory or compliance questions, identify the governing framework (NIST, FedRAMP, HIPAA, SOC 2 TSC) and match to the domain whose vertical the regulation primarily governs.
7. For credential or qualification questions, consult how to get help for technology services and the relevant domain's credentialing landscape section.
8. For definitional disputes or term clarification, consult the network glossary before selecting a domain.

The technology services frequently asked questions page addresses the 12 most common domain selection queries received by the network.

Reference table or matrix

The key dimensions and scopes of technology services page provides expanded coverage of how these dimensional axes interact across procurement and regulatory contexts.

The network index provides the master entry point for all hub and member domain content.

References

• ACM Computing Classification System (CCS 2012) — Association for Computing Machinery
• IEEE Computer Society Technical Committees — Institute of Electrical and Electronics Engineers
• NIST AI Risk Management Framework (AI RMF 1.0) — National Institute of Standards and Technology
• NIST SP 800-145: The NIST Definition of Cloud Computing — National Institute of Standards and Technology
• ISO/IEC 9075: SQL Standard — ISO/IEC Joint Technical Committee 1
• ISO/IEC JTC 1 Subcommittees — ISO/IEC Joint Technical Committee 1
• HIPAA Security Rule, 45 CFR Part 164 — US Department of Health and Human Services
• BLS Standard Occupational Classification 2018 — Computer and Mathematical Occupations (SOC 15-0000) — US Bureau of Labor Statistics
• [IEEE SWEBOK