Curated Taxonomy Alignment

This page records the manual alignment between an imported external taxonomy and Atlas-native graph nodes.

Alignment policy

1. Reuse existing Atlas nodes when the external concept already has a graph-native home. 2. Add a new Atlas node only when the concept is broad, clearly distinct, and connects cleanly to existing Atlas domains or specializations. 3. Do not mirror leaf technologies blindly. Frameworks, tools, services, providers, and databases should resolve to existing Atlas nodes or wait for manual curation.

Manual top-level mappings

• Backend -> `domain:backend`
• Frontend -> `domain:frontend`
• Fullstack -> `domain:fullstack`
• Mobile -> `domain:mobile`
• Embedded Systems -> `domain:embedded-systems`
• Systems Programming -> `domain:systems-programming`
• DevOps -> `domain:devops`
• MLOps -> `domain:ml-ops`
• Data Engineering -> `domain:data-engineering`
• Data Science -> `domain:data-science`
• ML/AI -> `domain:ml-ai`
• Networking -> `domain:networking`
• Cybersecurity -> `domain:cybersecurity`
• QA/Testing -> `domain:qa-testing`
• Blockchain -> `domain:blockchain`
• IoT -> `domain:iot`
• Game Development -> `specialization:game-development` within `domain:gaming`

Curated second-pass additions

The second pass keeps the manual policy but fills gaps where the external taxonomy exposed broad practice areas that Atlas did not yet model cleanly.

Added skill areas

• Testing: `skill-area:service-mocking`, `skill-area:acceptance-testing`, `skill-area:regression-testing`, `skill-area:smoke-testing`
• Frontend/web: `skill-area:frontend-routing`, `skill-area:form-management`
• Platform/application: `skill-area:authentication-authorization`, `skill-area:configuration-management`, `skill-area:data-validation-sanitization`, `skill-area:serialization-deserialization`, `skill-area:caching-strategies`, `skill-area:messaging-queuing`, `skill-area:search-indexing`, `skill-area:background-job-processing`, `skill-area:streaming-realtime-processing`, `skill-area:email-notification-delivery`
• UI/data quality: `skill-area:data-fetching-caching`, `skill-area:application-state-management`, `skill-area:animation-transitions`, `skill-area:data-visualization`, `skill-area:ui-styling`, `skill-area:component-testing`, `skill-area:cross-browser-testing`, `skill-area:frontend-performance-testing`, `skill-area:data-quality-testing`
• AI/ML: `skill-area:model-monitoring-drift-detection`, `skill-area:agent-planning-reasoning`, `skill-area:multi-agent-coordination`
• AI/ML additional: `skill-area:natural-language-processing`, `skill-area:model-serving-operations`
• Core engineering/security: `skill-area:encryption-decryption`, `skill-area:file-handling`, `skill-area:error-handling-exception-management`, `skill-area:performance-monitoring-profiling`, `skill-area:code-analysis-linting`, `skill-area:deployment-infrastructure-management`, `skill-area:concurrency-multithreading`, `skill-area:parsing-data-formats`, `skill-area:command-line-interface-tools`, `skill-area:backend-security`, `skill-area:task-scheduling-cron-jobs`, `skill-area:analytics-tracking`, `skill-area:data-preprocessing`, `skill-area:computer-vision`, `skill-area:model-validation-testing`
• Backend/platform additions: `skill-area:object-relational-mapping`, `skill-area:middleware-design`, `skill-area:api-clients-sdks`, `skill-area:database-drivers-connectors`, `skill-area:database-testing`
• Frontend additions: `skill-area:ui-component-libraries`, `skill-area:frontend-e2e-testing`, `skill-area:state-management-testing`
• Mobile additions: `skill-area:mobile-local-databases`, `skill-area:mobile-location-services`, `skill-area:mobile-sensor-integration`, `skill-area:mobile-ui-automation`, `skill-area:cross-platform-testing`, `skill-area:offline-mode-testing`, `skill-area:battery-consumption-testing`, `skill-area:memory-usage-testing`, `skill-area:mobile-security-testing`, `skill-area:network-condition-testing`, `skill-area:payment-integration`

Curated third-pass additions

The third pass extends the manual alignment with broad testing and analytical practice areas that were still missing from Atlas after the earlier curation.

• Cross-domain utilities: `skill-area:date-time-manipulation`, `skill-area:compression-archiving`
• QA/testing additions: `skill-area:functional-testing`, `skill-area:security-testing`, `skill-area:usability-testing`, `skill-area:compatibility-testing`, `skill-area:stress-testing`, `skill-area:sanity-testing`, `skill-area:ui-testing`, `skill-area:ab-testing-experimentation`
• Data and ML quality additions: `skill-area:training-data-testing`, `skill-area:bias-fairness-testing`, `skill-area:model-robustness-testing`, `skill-area:inference-performance-testing`, `skill-area:model-explainability-testing`, `skill-area:ml-pipeline-testing`
• Data science additions: `skill-area:data-analysis`, `skill-area:statistical-analysis`, `skill-area:geospatial-data-analysis`, `skill-area:statistical-testing`, `skill-area:data-pipeline-testing`, `skill-area:etl-testing`, `skill-area:reproducibility-testing`
• Alias additions for adjacent Atlas concepts: `term:retrieval-augmented-generation-setup`, `term:prompt-engineering-context-management`, `term:llm-fine-tuning-adaptation`, `term:inference-serving-optimization`, `term:llm-monitoring-logging`, `term:containerization-orchestration`, `term:secret-secure-config-management`, `term:observability-monitoring-logging-alerting`, `term:version-control-gitops`, `term:rate-limiting`, `term:dependency-injection`, `term:progressive-enhancement`, `term:feature-store-architecture`, and `term:drift-detection`

Curated fourth-pass additions

The fourth pass fills another Atlas-native slice centered on ML lifecycle, LLM quality, and mobile pattern aliases.

• ML and agent practice additions: `skill-area:feature-engineering-pipelines`, `skill-area:model-registry-management`, `skill-area:hyperparameter-tuning-experiment-management`, `skill-area:automated-retraining`, `skill-area:ml-governance-compliance`, `skill-area:ci-cd-ml-pipelines`, `skill-area:llm-summarization-qa`, `skill-area:hallucination-mitigation-fact-checking`, `skill-area:agent-simulation-testing`, `skill-area:agent-debugging-logging`, `skill-area:rlhf-systems`
• Mobile and rendering alias additions: `term:hydration`, `term:bloc-architecture`, `term:sqlite-database`, `term:encrypted-storage`, `term:cache-synchronization`, `term:biometric-authentication`, `term:deep-linking`, and `term:ui-automation-testing`
• ML, agent, and LLM pattern aliases: `term:transfer-learning`, `term:continual-learning`, `term:hyperparameter-tuning`, `term:model-registry-patterns`, `term:ci-cd-machine-learning`, `term:multi-agent-systems`, `term:memory-based-agents`, `term:tool-driven-agent`, `term:instruction-tuned-llms`, `term:chain-of-thought-prompting`, and `term:system-user-prompting-layers`

Added topics

• Architecture: `topic:clean-architecture`, `topic:onion-architecture`, `topic:microservices-architecture`, `topic:serverless-architecture`, `topic:backend-for-frontend`
• Reliability: `topic:retry-pattern`, `topic:timeout-pattern`
• Web app shape: `topic:single-page-application`, `topic:progressive-web-application`, `topic:static-site-generation`
• Service and integration: `topic:rest`, `topic:message-driven-architecture`, `topic:service-oriented-architecture`, `topic:publish-subscribe`, `topic:request-reply`, `topic:sidecar-pattern`
• Additional architecture/frontend: `topic:layered-architecture`, `topic:sharding`, `topic:bulkhead-pattern`, `topic:client-side-rendering`, `topic:incremental-static-regeneration`, `topic:code-splitting`, `topic:finite-state-machine`, `topic:micro-frontend-architecture`, `topic:jamstack-architecture`, `topic:offline-first`
• Security/data/frontend patterns: `topic:oauth-openid-connect`, `topic:api-key`, `topic:defense-in-depth`, `topic:zero-trust-architecture`, `topic:data-at-rest-encryption`, `topic:data-in-transit-encryption`, `topic:secure-token-pattern`, `topic:fallback-pattern`, `topic:compensating-transaction`, `topic:monolithic-architecture`, `topic:load-balancing`, `topic:auto-scaling`, `topic:partitioning`, `topic:throttling`, `topic:repository-pattern`, `topic:data-mapper`, `topic:unit-of-work`, `topic:database-per-service`, `topic:shared-database`, `topic:event-store`, `topic:mvc`, `topic:mvp`, `topic:mvvm`, `topic:component-based-architecture`, `topic:atomic-design`, `topic:context-api-pattern`, `topic:composition-pattern`, `topic:css-modules`, `topic:css-in-js`, `topic:utility-first-css`, `topic:lazy-loading`, `topic:service-workers`, `topic:dynamic-imports`, `topic:tree-shaking`, `topic:custom-hooks`
• Frontend pattern additions: `topic:isomorphic-universal-javascript`, `topic:flux-architecture`, `topic:redux-architecture`, `topic:container-presentational-pattern`, `topic:multi-page-application`, `topic:islands-architecture`, `topic:streaming-ssr`, `topic:compound-components`, `topic:higher-order-components`, `topic:render-props`, `topic:provider-pattern`, `topic:controlled-components`, `topic:uncontrolled-components`, `topic:smart-dumb-components`, `topic:component-composition`, `topic:slots-pattern`, `topic:styled-components-pattern`, `topic:bem`, `topic:oocss`, `topic:smacss`, `topic:atomic-css`, `topic:css-variables-pattern`, `topic:theming-pattern`, `topic:virtual-dom`, `topic:infinite-scrolling`, `topic:windowing-virtualization`, `topic:active-record`
• Additional frontend/perf/design patterns: `topic:memoization`, `topic:resource-prefetching`, `topic:asset-optimization`, `topic:critical-css`, `topic:hash-based-routing`, `topic:history-api-routing`, `topic:nested-routing`, `topic:dynamic-routing`, `topic:protected-routes`, `topic:route-guards`, `topic:layout-routes`, `topic:modal-routes`, `topic:parallel-routes`, `topic:catch-all-routes`, `topic:controlled-forms`, `topic:uncontrolled-forms`, `topic:form-validation`, `topic:command-pattern`, `topic:observable-pattern`, `topic:factory-pattern`, `topic:singleton-pattern`, `topic:observer-pattern`, `topic:strategy-pattern`, `topic:decorator-pattern`, `topic:adapter-pattern`, `topic:builder-pattern`, `topic:proxy-pattern`
• Additional UI/security/form patterns: `topic:soap`, `topic:event-mesh`, `topic:horizontal-scaling`, `topic:vertical-scaling`, `topic:cache-aside-pattern`, `topic:inversion-of-control`, `topic:flux-pattern`, `topic:redux-pattern`, `topic:publisher-subscriber-pattern`, `topic:form-state-management`, `topic:multi-step-forms`, `topic:dynamic-forms`, `topic:form-composition`, `topic:field-array-pattern`, `topic:form-builder-pattern`, `topic:form-wizard-pattern`, `topic:content-security-policy`, `topic:xss-prevention`, `topic:csrf-protection`, `topic:secure-authentication-patterns`, `topic:oauth-integration`, `topic:secure-storage-pattern`, `topic:input-sanitization`, `topic:permission-based-access`, `topic:security-headers-implementation`, `topic:responsive-design`, `topic:adaptive-design`, `topic:mobile-first-design`, `topic:progressive-disclosure`, `topic:skeleton-screen`, `topic:pull-to-refresh`, `topic:modal-dialog`, `topic:toast-notification`

Reused Atlas nodes instead of adding duplicates

• Retrieval-Augmented Generation (RAG) Setup reuses `skill-area:retrieval-augmented-generation`
• State Management reuses `skill-area:react-state-management` for the existing frontend-react branch
• GraphQL reuses the existing language and schema-design nodes rather than a broad duplicate topic: `language:graphql`, `topic:graphql-schema-design`, `skill-area:graphql-schema-design`
• API Gateway and Service Mesh map to existing stack parts instead of new topics: `stack-part:api-gateway`, `stack-part:service-mesh`
• Containerization & Orchestration, Secret & Secure Config Management, Model Serving & Deployment, and Canary-style deploy concepts reuse existing Atlas nodes: `skill-area:containerization`, `skill-area:secrets-rotation`, `stack-part:model-serving`, `specialization:ml-inference-serving`, `skill-area:canary-rollouts`
• Queue, scheduling, notification, and event-stream concepts are anchored to existing stack parts instead of duplicating vendor-specific abstractions: `stack-part:event-bus`, `stack-part:scheduler`, `stack-part:workflow-engine`, `stack-part:notification-service`, `stack-part:email-delivery`, `stack-part:cache`, `stack-part:search-index`
• Circuit Breaker, Contract Testing, Chaos Engineering, Hydration, and Hexagonal Architecture already existed and were retained as-is: `topic:circuit-breakers`, `skill-area:contract-testing`, `skill-area:chaos-engineering`, `skill-area:hydration`, `skill-area:hexagonal-architecture`
• Test-Driven Development (TDD) and Behavior-Driven Development (BDD) already exist in terminology: `term:test-driven-development`, `term:behavior-driven-development`
• Long-form and acronym variants that would otherwise duplicate Atlas concepts are captured as terminology aliases instead of new topic forks, including `term:rest-representational-state-transfer`, `term:event-driven-architecture-eda`, `term:backend-for-frontend-bff`, `term:single-page-application-spa`, `term:progressive-web-application-pwa`, `term:server-side-rendering-ssr`, and `term:incremental-static-regeneration-isr`
• Additional protocol and task aliases are also captured in terminology where the source taxonomy uses alternate naming forms, including `term:grpc-google-remote-procedure-call`, `term:server-sent-events-sse`, `term:jwt-json-web-tokens`, `term:circuit-breaker`, `term:canary-testing`, `term:internationalization-and-localization`, `term:routing`, `term:server-side-rendering-frameworks`, `term:backend-unit-testing`, and `term:backend-integration-testing`
• Additional name-form aliases also cover `term:rpc-remote-procedure-call`, `term:authentication`, `term:authorization`, `term:test-driven-development-tdd`, `term:behavior-driven-development-bdd`, and `term:multi-page-application-mpa`
• Mobile/task aliases now also capture `term:mobile-ui-components`, `term:authentication-libraries-tools-services-agents`, `term:device-compatibility-testing`, `term:push-notifications-task`, `term:offline-mode-testing-task`, `term:app-store-deployment-task`, `term:in-app-purchases-task`, and `term:mobile-offline-sync-task`

Why the bulk import was removed

The raw dump created duplicate and mis-typed nodes such as service-vs-tool, library-vs-tool, and framework-vs-service collisions. Examples included technology names already present elsewhere in Atlas under more accurate node kinds. That import was removed so Atlas remains coherent and connected to its existing graph structure.