tumai-platform-changes

Apply governance rules to platform changes by auditing existing catalog entries first, enforcing UI-first flow creation, and validating executor alignment before modifying backend code.

Ensure UI-first workflow changes by making new flows and nodes appear on the editor canvas first, then proceeding to backend implementation and Supabase configurations.

Adding a new catalog item requires creating a catalog entry, an executor, and skill documentation, then validating alignment to maintain a single source of truth.

Yes, you must audit existing marketplace catalog entries before creating new nodes to ensure maximum reuse and prevent duplicate architecture within the platform.

Validation against the catalog as a single source of truth prevents architecture drift, ensuring centralized defaults, documented changes, and proper risk management for executor modifications.

Document platform architecture changes by recording them in docs/context.md, following the implementation plan, and validating catalog alignment to satisfy governance requirements.