Enterprise Researcher — First-Time Setup

You are setting up the Enterprise Researcher knowledge base for the first time. Walk the user through configuration step by step.

Steps

1. Check if already configured

Check if .enterprise-researcher/config.yaml already exists in the current project directory. If it does, inform the user and ask if they want to reconfigure.

2. Create the data directory structure

Create the following directory structure in the project root:

.enterprise-researcher/
├── config.yaml
├── registry.yaml
├── specs/
├── index/
│   ├── domains/
│   └── services/
└── .gitignore

3. Collect mTLS configuration

Ask the user for their mTLS certificate paths using AskUserQuestion:

• Client certificate path (e.g., /etc/pki/tls/client.crt)
• Client key path (e.g., /etc/pki/tls/client.key)
• CA bundle path (e.g., /etc/pki/tls/ca-bundle.crt)

All three are required. Validate that the files exist at the given paths using Bash.

4. Write config.yaml

Write .enterprise-researcher/config.yaml with the mTLS paths and default settings:

mtls:
  client_cert: <user-provided-path>
  client_key: <user-provided-path>
  ca_cert: <user-provided-path>

sync:
  stale_after_hours: 24
  timeout_seconds: 30

index:
  data_dir: .enterprise-researcher

5. Write empty registry

Write .enterprise-researcher/registry.yaml with an empty services list and commented examples:

# Enterprise Researcher — Service Registry
# Add your internal API services here
#
# Each service needs:
#   name:      Unique identifier (kebab-case)
#   spec_url:  Full URL to the OpenAPI JSON spec
#   domain:    Business domain grouping
#   team:      Owning team name
#   description: Brief purpose description
#   tags:      List of searchable tags

services: []

6. Write .gitignore

Write .enterprise-researcher/.gitignore to exclude sensitive files:

# mTLS certificates should never be committed
*.key
*.pem

# Specs are large but can be committed (they're not secret)
# Uncomment the next line to exclude them:
# specs/

7. Test mTLS connectivity (optional)

Ask the user if they'd like to test mTLS connectivity. If yes, ask for a test URL (any internal API URL) and run:

curl -s -o /dev/null -w "%{http_code}" --cert <cert> --key <key> --cacert <ca> <test_url>

Report the result.

8. Next steps

Tell the user:

• Run /add-service to register services one at a time
• Or edit .enterprise-researcher/registry.yaml directly for bulk registration
• Or run /import-services to bulk-import from a file or URL
• After registering services, run /sync to fetch specs and build the knowledge index