structured knowledge assetsenterprise knowledge base
Structured Knowledge Assets Knowledge should not only be stored, but discovered, understood, and connected
Publish the facts, experience, and expertise that businesses and professionals accumulate to their own domains, forming searchable public knowledge assets organized by articles, categories, topics, tags, and entity relationships.
Specifications
| Content source | Argus Knowledge Base API |
|---|---|
| Sync method | Scheduled sync into PostgreSQL |
| Public form | Article, category, topic, and tag pages |
Capabilities
- Knowledge content is synced into the database on a schedule; public pages never call external APIs at request time
- Content units are organized with summary, key points, body, sources, and FAQ, each independently understandable
- Categories, topics, tags, and entity pages form a navigable, interlinked knowledge network
- Knowledge belongs to an independent site and language, accumulating under your own domain and published openly
FAQ
How does structured knowledge get updated on the website?
Once knowledge base sync is enabled, an external scheduled job calls the protected sync endpoint, pulling content from the Argus Knowledge Base API into PostgreSQL. The website then reads and displays it from the database.
Is knowledge base content shared across customers?
No. Configurations, knowledge base articles, analytics, and all other child tables are tenant-isolated by an immutable site_id.