Knowledge Graph · FAQ
The boundaries are part of the product.
Clear answers about authority, identity, security, AI, pricing, and what must be proven before production.
Private Implementation Program · Selected engagements
01Is this a new CRM or ERP?
No. It is a projection and intelligence module. Existing systems remain authoritative for the records they own.
02Is graph software required?
No. The contract is event and relationship based. Storage is selected during implementation and can start with relational projections.
03Does it need AI?
No. Ingestion, identity, projection, reconciliation, search, and task views are deterministic. AI is disabled by default.
04Can AI change prices or merge products?
No. Commercial actions and identity changes require controlled human workflows. Recommendations are stored separately from facts.
05How is tenant data isolated?
Every event, entity, query, token, and task view is tenant-scoped and protected by role policy.
06Are the published prices annual?
No. The displayed ranges are one-time assessment or implementation fees. Hosting, support, maintenance, and optional model usage are scoped separately.
07What is public on GitHub?
Only a safe conceptual package: boundaries, redacted examples, synthetic data, and integration patterns. The production schema and implementation remain private.
08What is the first production gate?
A source-system inventory followed by a shadow projection whose counts and identities reconcile to authoritative records.
Design Partner Module
Start with one revenue path you need to explain.
Inventory the authoritative sources, define the identity contract, and prove a shadow projection before changing an operational workflow.