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. Create one project for the application, with each input as a named source. Naming sources is what lets you limit a reader to some of them later:
ekos project add erp --source app=/src/erp --source docs=/src/erp-docs --detect
ekos --project erp source add wiki --path ~/wiki-snapshot
ekos --project erp database add erp-db --connect db:1521/ERP --user ekos_ro \
    --password-env ERP_DB_PASSWORD --owner APP
  1. Connect the sources you have:
System How
Source repositories [[sources]] (ekos source add) or [observe] paths
Live databases (Oracle, PostgreSQL, ClickHouse) [[databases]] (ekos database add) — see Indexing a Database
Documentation sites kept as Markdown (Docusaurus, MkDocs, docs/) a source like code; front matter becomes the document's properties
MediaWiki scripts/wiki-snapshot.py turns a Special:Export file or the API into a Markdown directory with each page's URL, revision and licence; add it as a source
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 a source
Pentaho / dbt / SQL files under a source
  1. Join them by ticket. Legacy estates cite their tracker in file names, comments and commit messages. With exact keys set, every ticket a commit names becomes a Ticket object, linked at ekos commit to the migration change sets, code and documentation sections that cite it:
[tickets]
keys = ["IDEMPIERE"]          # exact keys only; ekos init --detect proposes the ones it finds

[observe]
git-max-commits = 500         # the default; raise it to read more history

On iDempiere's full history (16,260 commits): 4,597 tickets, linked to 3,074 change sets, and 1,743 documentation sections linked to tickets.

  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 ekos review identity or the ekos_identity_review tool — see Human Review. Where sources disagree about one fact, ekos conflicts list shows both claims for a person to decide.

  2. Ask cross-system questions: "what breaks if customers.email changes?" → ekos_impact. "Which names point at nothing?" → ekos check refs.

For a legacy ERP that is headed for a lakehouse, the same project continues through review, sign-off and the pipeline steps: see The Seven-Step Operator Workflow.

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