Developer / Maintainer documentation

This section is intentionally separate from the user guide. It documents implementation boundaries and operational invariants for contributors; it is not the primary navigation for product users.

System architecture

• Canonical data model
• Worker boundaries
• Platform ingestion and rendering
• Canonical resource access inventory
• Editor architecture

AI system

• AI chat architecture
• Prompt construction and credits

Maintenance policy

• Implementation docs use English as their canonical language.
• Paths and owners must describe the current staging branch, not an intended future design.
• Inventories should be generated or checked where practical; prose that duplicates source code must identify its source of truth.
• A product change that alters a user-visible workflow must update the user guide in the same change.