Membership Criteria: How Authority Sites Join This Network

The seven member sites within the Computer Science Authority network are not aggregated by category alone — each occupies a defined domain within computer science based on subject boundaries, coverage depth, professional relevance, and editorial standards. This page documents the criteria that govern membership, how the qualification process operates, what scenarios trigger inclusion or exclusion, and where the structural boundaries lie between adjacent domains. The framework applies to all seven current members and provides the reference basis for evaluating any future additions.

Definition and scope

Network membership designates a site as a primary reference authority for a bounded subject within computer science. The National Institute of Standards and Technology (NIST) and the Association for Computing Machinery (ACM) both publish formal taxonomies of computing disciplines — NIST through its Computer Security Resource Center and the ACM through its Computing Classification System (CCS) — and the network's domain structure maps to those recognized discipline boundaries rather than to commercial or promotional categories.

Membership is subject-bounded, not audience-bounded. A site qualifies by demonstrating authoritative coverage of a discrete computer science subdiscipline, not by targeting a particular profession or skill level. The Computer Science Authority hub maintains subject-boundary documentation to prevent overlap between members and to ensure that adjacent domains are covered without duplication.

Three classification tiers determine how a domain fits within the network:

1. Core infrastructure domains — operating systems, database systems, distributed systems, and cloud computing, each of which underpins the computational stack.
2. Applied intelligence domains — artificial intelligence systems and data science, which operate at the analytical and decisional layer above the infrastructure.
3. Engineering practice domains — software engineering, which spans the professional methodology layer governing how systems are designed, built, and maintained.

The seven current members span all three tiers. Coverage of the Infrastructure and Systems Vertical and the Data and Intelligence Vertical is distributed across members without subject overlap.

How it works

Membership qualification follows a structured evaluation sequence. The process is not application-driven in the consumer sense; it reflects an editorial determination made against published standards.

1. Subject boundary verification — The proposed domain is mapped against the ACM Computing Classification System to confirm it represents a recognized, non-redundant subdiscipline. Boundaries must be documentable and stable, not provisional or trend-dependent.

2. Coverage depth assessment — The site must demonstrate reference-grade coverage: factual specificity, named source attribution, and treatment of professional, regulatory, and technical dimensions within its scope. The Network Editorial Standards page defines the applicable content requirements in full.

3. Cross-domain conflict review — The proposed domain is reviewed against all existing member domains for overlap. If two candidate domains share more than 40 percent of their subject matter as defined by NIST or ACM taxonomy, only one qualifies. The How the Domains Relate page documents current adjacency decisions.

4. Vertical assignment — Qualified members are assigned to a vertical: Infrastructure and Systems, Data and Intelligence, or Software Development. The Software Development Vertical contains members whose primary scope is engineering practice rather than underlying computational architecture.

5. Ongoing editorial compliance — Membership is conditional on continued adherence to network editorial standards, including source attribution density, factual accuracy, and absence of promotional content.

Common scenarios

Artificial intelligence systems represent the clearest example of applied intelligence membership. The Artificial Intelligence Systems Authority covers AI system architecture, model governance, and deployment frameworks — including compliance touchpoints under the NIST AI Risk Management Framework (AI RMF 1.0) — making it the network's primary reference for AI practitioners and researchers evaluating implementation and risk contexts.

Cloud computing qualifies as a core infrastructure domain because cloud platforms constitute a recognized architectural layer with distinct standards bodies, service models (IaaS, PaaS, SaaS), and regulatory frameworks. The Cloud Computing Authority covers cloud architecture, deployment models, and the regulatory and contractual landscape governing cloud service procurement in enterprise and government contexts.

Data science occupies the analytical layer above raw data infrastructure, addressing statistical methodology, machine learning pipelines, and data product development. The Data Science Authority provides reference coverage for this domain, including the professional qualification landscape and the tooling standards recognized by bodies such as the IEEE.

Database systems qualify separately from data science because the subject covers storage architecture, query optimization, transaction models, and database administration — not analytical methodology. The Database Systems Authority covers relational and non-relational database systems, indexing structures, and the ANSI/ISO SQL standards that govern query language compliance.

Distributed systems address the architectural challenges of coordinating computation across multiple nodes — consistency models, consensus protocols, and fault tolerance — distinct from cloud deployment. The Distributed System Authority covers these theoretical and applied dimensions, including CAP theorem tradeoffs and the engineering standards that govern distributed application design.

Operating systems form the foundational infrastructure layer. The Operating Systems Authority covers kernel architecture, process scheduling, memory management, and the POSIX standards maintained by the IEEE, providing reference coverage for systems engineers and OS-level developers.

Software engineering qualifies under the engineering practice tier, covering the discipline of software design, development methodology, and systems lifecycle management. The Software Engineering Authority addresses professional frameworks including IEEE 12207 (Software Life Cycle Processes) and ISO/IEC 25010 quality models, serving practitioners across the Software Development Vertical.

Decision boundaries

The network applies four boundary rules to resolve ambiguous membership cases.

Subdiscipline vs. full discipline — A site covering only one methodology within a larger field does not qualify as a domain authority. A site covering agile methodology alone does not qualify; a site covering software engineering as a field does.

Stability vs. trend — Domains must reflect stable, recognized subdisciplines. A subject defined primarily by a single vendor product, a short-term technology cycle, or an emerging category without formal standards body recognition does not meet the boundary test. The Network Glossary documents the definitional sources used to make stability determinations.

Overlap resolution — When two valid disciplines share significant subject matter, the narrower domain is subordinated to the broader unless the narrower domain has independent standards body recognition. Database systems and data science share data modeling concepts, but both carry independent ACM classification nodes, justifying separate membership.

Geographic scope — All current members operate at national scope within the United States. Members referencing state-level licensing or regulatory variation must do so within a nationally scoped framework. The Network Coverage Map documents scope assignments for all members.

Researchers and professionals evaluating the network's subject coverage against a specific technology question can consult the Member Directory for domain-level summaries and cross-references across all 7 members. For discipline adjacency questions spanning multiple members, the Cross-Domain Technology Concepts page documents recognized intersections and how coverage responsibility is allocated between members.

References

• National Institute of Standards and Technology (NIST)
• NIST AI Risk Management Framework (AI RMF 1.0)
• ACM Computing Classification System (CCS)
• NIST Computer Security Resource Center
• IEEE Standards Association
• IEEE 12207 — Software Life Cycle Processes
• ISO/IEC 25010 — Systems and Software Quality Models
• ANSI/ISO SQL Standards