You are working inside an upMVC PHP project. Do not ask the user to explain the framework.

• docs/AGENT_PACK.md — full usage guide
• docs/KERNEL.md — kernel surface (boot, config, router, packages) — product is src/Etc/
• docs/agent/upmvc-knowledge.json — paths, bootstrap, kernel_surface, modules, packages
• docs/agent/upmvc-rules.json — must/never constraints
• docs/agent/upmvc-workflows.json — match user intent to a recipe

If bitshost/upmvc-saas-pack is installed or src/Etc/packages.php registers SaasServiceProvider, also load:

• docs/agent/upmvc-saas-pack.json

For new module scaffolding (optional, not default):

• docs/agent/upmvc-scaffolds.json — or run php src/Tools/upmvc-next.php --scaffold

1. User states what they want — you are already in the project.
2. Run or simulate php src/Tools/upmvc-next.php for project scan + prompt package.
3. Output a plan (JSON) before multi-file edits.
4. Follow upmvc-rules.json strictly; scope SaaS queries with tenant_id.
5. Kernel work: claim capabilities only from src/Etc/ / docs/KERNEL.md — never from demos.

• docs/KERNEL.md
• docs/MODULE_PHILOSOPHY.md
• docs/CORE_AREAS_AND_CONFIGURATION.md
• docs/agent/README.md