Production services · Governed knowledge
Faiber Knowledge
Publish trusted knowledge and retrieve the right guidance with context.
Faiber Knowledge combines governed authoring, nested knowledge structures, immutable releases, profile-aware matching, action outputs, runtime retrieval, and complete auditability.
01
Feature map
The production behaviors this service owns, expressed as concrete product features instead of generic modules.
Versioned items, graph edges, drafts, and immutable releases
Profile-aware declarative matching and guided outputs
Runtime retrieval tools, action inbox, and audit log
02
Best-fit products
AI support knowledge
Publish trusted knowledge and retrieve the right guidance with context.
Policy and procedure guidance
Publish trusted knowledge and retrieve the right guidance with context.
Profile-aware onboarding and next actions
Publish trusted knowledge and retrieve the right guidance with context.
03
Operational gains
Governed AI context
Faiber Knowledge combines governed authoring, nested knowledge structures, immutable releases, profile-aware matching, action outputs, runtime retrieval, and complete auditability.
Reproducible releases
Faiber Knowledge combines governed authoring, nested knowledge structures, immutable releases, profile-aware matching, action outputs, runtime retrieval, and complete auditability.
Auditable guidance
Faiber Knowledge combines governed authoring, nested knowledge structures, immutable releases, profile-aware matching, action outputs, runtime retrieval, and complete auditability.
04
Connected services
Production wiring
How it runs in a Faiber project
Select the capability during deployment. Faiber records the manifest, wires service references, exposes the API boundary, and keeps lifecycle, health, logs, and administration visible in project context.
API boundary
Application code uses the service API or typed SDK contract. Identity, permissions, tenant scope, and project context stay explicit at every read and write boundary.
Manage-ready operations
Faiber Manage opens this service beside the rest of the enabled stack, so teams can inspect records, adjust settings, review health, and ask the Manage agent for guided service changes.
Publish the onboarding knowledge release and connect it to profile-aware support answers.
Technical reference
infera-knowledgeInternal API port: 8070These values support deployment wiring. Product code should use configured endpoints or SDK clients, not hard-coded internal addresses.
FAQ
Questions teams ask before enabling it
What does Faiber Knowledge add to a Faiber application?
Faiber Knowledge combines governed authoring, nested knowledge structures, immutable releases, profile-aware matching, action outputs, runtime retrieval, and complete auditability.
How is Faiber Knowledge provisioned?
Select it as a project capability. Faiber records the service manifest, resolves its dependencies, and reconciles it inside the project's isolated Kubernetes namespace.
Can Faiber Knowledge be used with an existing frontend?
Yes. Faiber Knowledge exposes a defined API surface and can be integrated from an existing React application or a new Faiber project.
Faiber
Provision the capabilities your product actually needs.
Start with a real project, select services explicitly, and keep code, access, deployment, and operations connected.