Search Configuration

Search Configuration

Status as of 2026-11-05: Search federation is not operational. This page describes intended configuration rules for restoration.

Rules

Search configuration must follow DB-first rules.

• Store runtime config, settings, jobs, metrics, and audit logs in PostgreSQL suite.
• Use environment variables only for bootstrap values (DSN and secret references).
• Runtime state belongs in PostgreSQL. Config files, JSON, YAML and file stores are not a runtime store in touched areas (owner ruling 2026-11-09: durable state lives only in PostgreSQL).
• Make settings editable at runtime through an operator console or API.
• Record every change in an audit log with operator and time.

Safety constraints

• Enforce egress law in all routing and fetch settings.
• Do not allow settings that bypass the proxy pool.
• Do not allow unsafe probing or restricted address access.
• Do not store secrets or credentials in tables as plain text. Use secret references.

Example settings (intended)

Area	Setting	Notes
Rerank	rerank.k	RRF normalization factor
Rerank	rerank.weights	Weight per source type
Rerank	rerank.cutoff	Max results to rank
Federation	sources.enabled	Enabled source types
Egress	egress.guard_required	Must be true before start
Proxy	proxy.min_verified	Minimum verified proxies

Actual schema and migrations must live in the service repo with tests.

Audit requirements

Each config change should record:

• Operator identity
• Action and table or key
• Old and new value (or redacted diff)
• Time and source IP or agent

Validation

Before applying a change:

• Validate types and ranges.
• Check impact on egress and source permissions.
• Run EXPLAIN on new hot queries.
• Keep a rollback path.

Related pages

• Search Architecture
• Massprox Architecture
• Massprox Configuration
• Verify Egress Compliance
• Search Restoration Runbook