Demo listing. This page uses illustrative seed metadata to demonstrate the Atlas. Claims shown here are not verified product facts.
Lexa Knowledge Desk
Enterprise Operations
Retrieval-augmented knowledge assistant over approved enterprise documents with citations, access control and answer feedback.
Last verified 15 Sept 2026 · Updated 23 Sept 2026 · Metadata v2
Problem
Employees cannot find current policies and procedures across shared drives, and answers vary by who they ask.
Outcome
Consistent, cited answers from approved sources and visibility of knowledge gaps.
Who uses it
- Operations Analyst
- CIO
Key capabilities
Document collections
IncludedCurated collections with owners and review dates.
Domain:
collectionsCited answers
AI-assistedIncludedAnswers grounded in retrieved passages with citations.
Domain:
answersPermission-aware retrieval
IncludedRetrieval filtered by document permissions.
Domain:
accessKnowledge-gap reporting
IncludedUnanswered questions and stale content.
Domain:
insights
Typical workflow
Question answering
Trigger: An employee asks a question
Task
Stage 1: Receive question
Employee
Automated
Stage 2: Retrieve permitted passages
System
AI-assisted
Stage 3: Generate cited answer
System
Task
Stage 4: Rate answer
Employee
Human checkpoint
Stage 5: Review gaps
Content owner
Task Automated AI-assisted Human checkpoint Decision
About this foundation
Lexa Knowledge Desk answers employee questions from approved document collections. Answers cite their sources, respect document permissions and can be rated. Content owners see unanswered questions and stale documents.
This reference implementation is publicly inspectable as an example of the fazeZERO architecture.
Related applications
- • Addresses the same problem: Document Overload, Fragmented Systems
- • Shared capabilities: Knowledge Retrieval
- • Addresses the same problem: Fragmented Systems
- • Shared capabilities: Summarization, Reporting
- • Addresses the same problem: Document Overload, Fragmented Systems
- • Used by the same roles: Operations Analyst
- • Addresses the same problem: Fragmented Systems
- • Same industry: Enterprise Operations
- • Addresses the same problem: Fragmented Systems
- • Same industry: Enterprise Operations
- • Addresses the same problem: Fragmented Systems
- • Same industry: Enterprise Operations
Question answering
Trigger: An employee asks a question
Task
Stage 1: Receive question
Employee
Automated
Stage 2: Retrieve permitted passages
System
AI-assisted
Stage 3: Generate cited answer
System
Task
Stage 4: Rate answer
Employee
Human checkpoint
Stage 5: Review gaps
Content owner
Actors
Employee, Content owner
Outputs
- Cited answer
- Knowledge-gap report
Evidence generated
- Answer feedback log
Exceptions
- No relevant source returns "not found" rather than guessing
Task Automated AI-assisted Human checkpoint Decision
Included ships in the foundation · Configurable is switched or tuned per customer · Extension is customer-specific build scope · Planned is on the roadmap and not available today.
Document collections
IncludedCurated collections with owners and review dates.
Domain:
collectionsCited answers
AI-assistedIncludedAnswers grounded in retrieved passages with citations.
Domain:
answersPermission-aware retrieval
IncludedRetrieval filtered by document permissions.
Domain:
accessKnowledge-gap reporting
IncludedUnanswered questions and stale content.
Domain:
insights
- Architecture class
- Domain-driven design, OpenAPI-first
- Bounded contexts
- 5
- API-first
- Yes — OpenAPI contracts are authoritative
- Identity
- Enterprise OIDC / SAML via the fazeZERO identity blueprint; tenant-aware role-based access.
- Multi-tenancy
- Tenant-aware
- Service boundaries
- 5 bounded contexts behind one API server.
- Integration approach
- Ports-and-adapters: every external system sits behind an adapter; OpenAPI contracts for inbound APIs.
- Eventing
- Integration events via transactional outbox.
- Storage abstraction
- Repository interfaces; DynamoDB or relational adapters.
- Deployment pattern
- Containerized API + web application; infrastructure as code per cloud profile.
- Architecture version
- 1.0
Approved domain names
- collections
- documents
- answers
- feedback
- identity
- Web Application
- API Server
- Application Services
- Domain / Generated Core
- Adapters
- Customer Systems
Generator source, templates and factory orchestration are proprietary and are not part of this listing.
Reference Adapter: shipped and tested · Previously Integrated: delivered before · Standard API Pattern: integrates via a documented pattern · Customer-Specific: built in your implementation.
Document Management
| Integration | Status | Direction | Method |
|---|---|---|---|
| SharePoint | Reference Adapter | inbound | Graph API |
AI / Model
| Integration | Status | Direction | Method |
|---|---|---|---|
| Model providers | Standard API Pattern | bidirectional | REST API |
Identity
| Integration | Status | Direction | Method |
|---|---|---|---|
| Microsoft Entra ID | Reference Adapter | bidirectional | OIDC |
Deployment
- Deployment models
- Customer Cloud, fazeZERO Managed
- Cloud profiles
- Azure Profile, AWS Profile, Cloud-Neutral
- Containerized
- Yes
- Regions
- GLOBAL
Cloud profiles describe approved deployment patterns. They are not formal marketplace certifications.
Data handling
- Stores customer data
- Yes
- Data leaves customer environment
- Configurable
- Uses external AI provider
- Configurable
- Sends logs externally
- No
- PII expected
- Determined during customer configuration
- Data-residency support
- Yes
- Subprocessors required
- Determined during customer configuration
Identity & access
- Authentication
- OIDC, Entra ID, SAML
- Authorization
- Role-Based, Tenant-Aware
- Source availability
- Open Reference
- License
- Apache-2.0
- Reference source
- https://example.com/demo/lexa-knowledge-desk
Support
- Implementation
- Delivered by fazeZERO or a certified partner during the Solution Definition and AI Production Sprints.
- Production support
- Production support available under a separate support agreement.
- Contact
- support@fazezero.com
Badges
Deployment-Ready Foundation
Application has passed the defined fazeZERO scaffold, build and testing baseline.
Customer-specific integration, security, configuration, hardening and acceptance remain part of implementation.
Issued 23 Sept 2026
fazeZERO Verified
Listing metadata and published technical claims have been reviewed by fazeZERO.
Issued 23 Sept 2026
Open Reference
An approved reference implementation is publicly inspectable.
Issued 23 Sept 2026
Evidence shows that this listing represents real engineering. Internal metrics are only published when fazeZERO has approved them for publication.
Build
Automated tests
Deployment validation
- Last verification
- 15 Sept 2026
- Release
- 1.0.0
- Architecture version
- 1.0
- Listing metadata version
- 2
- Last published
- 23 Sept 2026