# gh0stcloud AI / Agent Context

Use this file as the entrypoint when an AI agent helps a tenant operate
gh0stcloud or write GitOps manifests.

Canonical user docs:
- Task map: /gh0stcloud/docs/use-gh0stcloud
- Agent guide: /gh0stcloud/docs/agent-guide
- Projects and namespaces: /gh0stcloud/docs/projects-and-namespaces
- GitOps and secrets: /gh0stcloud/docs/gitops-and-secrets
- Storage, services, backups: /gh0stcloud/docs/storage-services-backups
- Network and exposure: /gh0stcloud/docs/network-exposure
- Observability and troubleshooting: /gh0stcloud/docs/observability-troubleshooting
- Billing and change requests: /gh0stcloud/docs/billing-and-change-requests

Reference manifests:
- https://github.com/gh0stservice/ghc-gitops-example

Hard rules:
- gh0stportal and gh0stplane are the authority for tenant-specific values.
- Never invent namespaces, hostnames, OpenBao paths, service accounts, quota,
  egress catalog entries, or cert-manager issuers.
- Never commit secret values to Git.
- Do not suggest direct kubectl mutations for tenant workloads.
- Do not treat projects as RBAC boundaries.
- Use change requests for privileged changes outside tenant policy bounds.
- Use the example repository as a manifest reference, not as tenant truth.

Before generating YAML, ask for:
- portal namespace
- app name
- image and version
- service port
- portal-provided hostname
- storage intent/PVC name if stateful
- secret path names, not secret values
- required egress catalog entries
- required operator/service capabilities