map-feature-gates

Announce at start: "Using codebase-analyzer to map feature gates."

Overview

Map the gates that control which capabilities are available under which conditions. Gates are the control plane -- understanding them reveals what the system was designed to restrict and to whom.

Prerequisite: Reads docs/analysis/tool-graph.md (from extract-tool-graph) and docs/analysis/build-pipeline.md.

Five Gate Types with Detection

Build-Time Gates

Tools filtered during compilation. These never reach the runtime artifact.

• Where to look: Build config, preprocessor directives, build scripts
• Detection patterns: #ifdef / #ifndef, process.env checks in build scripts, conditional exports in package.json, webpack DefinePlugin, tree-shaking directives
• Example: if (process.env.NODE_ENV === 'production') includeAnalytics();

Runtime Gates

Tools enabled or disabled based on runtime state.

• Where to look: Feature flag checks, config reads, state conditionals
• Detection patterns: flags.isEnabled('x'), user.type === 'admin', env === 'production', version >= '2.0', capability checks like 'speechRecognition' in navigator
• Example: if (user.type === 'admin') registerAdminTools();

Permission Gates

Tools restricted by role or permission level.

• Where to look: Auth checks, role verification, access control logic
• Detection patterns: user.role === 'admin', user.can('write'), token.scope.includes('api:write'), acl.check(resource, action)
• Example: if (hasPermission('write')) { enableEditTools(); }

Provider Gates

Tools available only for specific backends or providers.

• Where to look: Provider-specific code paths, backend routing
• Detection patterns: config.provider === 'openai', typeof openai !== 'undefined', switch(provider) { case 'aws': ... }
• Example: if (provider === 'openai') registerOpenAITools();

Config Gates

Tools controlled by environment variables, settings files, or feature flag services.