# NuQloud AI Knowledge Base

This directory contains the launch-focused knowledge base for the NuQloud
managed service provider offer.

This corpus is intentionally focused on:

- the public NuQloud service-provider offer
- managed account plans and branded private-server plans
- NuQloud-branded feature language
- launch messaging, onboarding replies, and support-safe technical answers

This corpus is intentionally not centered on:

- internal plugin inventory
- CHD-only tooling
- raw app IDs unless a technical support question requires them

## File layout

- `policies.yaml`
  - response guardrails
  - branding rules
  - escalation rules
  - launch-scope boundaries
- `catalog.yaml`
  - service models
  - branded product/module naming
  - plan and pricing truth
  - support-safe capability summaries
- `faq.yaml`
  - common customer questions with ready answer records
  - service-provider focused only
- `playbooks.yaml`
  - reusable messaging for launch announcements, new-user replies, plan guidance,
    and first-response support
- `technical-reference.yaml`
  - compact support-facing compatibility notes
  - branded names vs technical implementation notes
  - purchase paths and operational facts

## Recommended ingestion strategy

Use these documents as retrieval sources instead of one giant prompt.

Suggested order:

1. `policies.yaml`
2. `catalog.yaml`
3. `faq.yaml`
4. `playbooks.yaml`
5. `technical-reference.yaml`

That order helps the agent:

1. stay within safe support boundaries
2. answer from the current NuQloud public offer
3. reuse consistent NuQloud wording
4. pull exact package/pricing and messaging details when needed

## Guidance for the support agent

- Default to NuQloud managed-service language first.
- Do not lead with plugin names such as `qortal_integration`,
  `qortal_talk_bridge`, `qortal_files_bridge`, or `nuqloud_scrum`.
- Use NuQloud-branded names such as `NuQloud Talk` and
  `NuQloud Files + Collaboration` in customer-facing answers.
- Mention compatibility with Nextcloud surfaces only when it helps answer a
  technical or migration question.
- Treat the NuQloud managed service as the public launch focus.
- If a question requires live billing state, tenant-specific server access,
  infrastructure logs, or negotiated pricing, escalate instead of guessing.

## Update rules

When the public NuQloud service offer changes, update these files together:

1. `catalog.yaml` for truth and pricing
2. `faq.yaml` for reusable answers
3. `playbooks.yaml` for sales/support messaging
4. `technical-reference.yaml` for compatibility and technical support notes
5. `policies.yaml` for new guardrails or escalation cases

## Primary source docs used for this launch-focused corpus

- `DEVELOPMENT/NuQloud-website/src/App.tsx`
- `docs/product/pricing-packages-v1.md`
- `docs/product/prd-v1.md`
- `docs/product/v1-feature-scope.md`
- `docs/nuqloud-blueprint.md`