Documentation Operations
OPERATIONS / EXPERT

Add another application

Extend the portal without changing the production AI contract.

A catalog rather than arbitrary query access

An extensible system can still have bounded interfaces. Curated query identifiers make caching, testing, and public/private review tractable. Exposing a generic datasource proxy would turn the portal into a much broader data-access surface.

Integration versus migration

Centralizing investigation is usually less disruptive than centralizing every service's infrastructure ownership. Preserve one writer for each resource. If ownership must move, import existing state and disable the old writer before enabling the new one.

Acceptance criteria

The integration is complete only when the application can be diagnosed from symptoms to dependencies with real evidence. Empty charts and links alone are not a substitute for working telemetry. Document any unavailable signal explicitly and retain the established production compatibility checks.

ON THIS PAGE

THREE WAYS TO UNDERSTAND

Same system.
Your level of detail.

Switch reading modes above to find the explanation that fits.

Explore Technical →

Keep exploring

Backups & recovery

Protect existing data and know which recovery path to use.

Documentation that follows code

How release checks keep all three reading versions aligned with implementation.