EKOSdocs
Docs / Guides Build

Indexing Enterprise Applications

Combine code, databases, documents, tickets and wikis into one cross-system model.

Enterprise knowledge rarely lives in one place. The cross-system workflow:

  1. Observe each system in one workspace (or one workspace per system, then a shared ledger container — see Storage).
  2. Connect the sources you have:
System How
Source repositories [observe] paths
Confluence EKOS_CONFLUENCE_BASE_URL, EKOS_CONFLUENCE_SPACE, optional EKOS_CONFLUENCE_TOKEN
GitHub EKOS_GITHUB_OWNER, EKOS_GITHUB_REPO, optional EKOS_GITHUB_TOKEN
Documents (PDF, DOCX, email) files under an observe path
Pentaho / dbt / SQL files under an observe path
  1. Compile. Then discover cross-system matches:
ekos identity scan

This writes candidates such as Informix cust_mstr ≈ Postgres customers ≈ Databricks gold.dim_customer as unconfirmed relationships. Nothing is merged automatically.

  1. Review them with the ekos_identity_review tool — see Human Review.

  2. Ask cross-system questions: "what breaks if customers.email changes?" → ekos_impact.

Salesforce, SAP, Oracle, Fabric and Snowflake connectors exist as scaffolded proofs of concept (real API shapes, mock-tested) and are not yet exercised against live accounts.