Uploaded November 2026 | Updated November 2026, 1 day ago
In this episode of AI Coding with Dr. Chuck, I continue refining the LTI 1.3 tool-management interface in Tsugi.
After building the initial CRUD interface for registrations, deployments, scopes, claims, and placements, I came back the next morning with a clearer picture of how I wanted the system to behave.
A major focus is normalizing placement terminology. Tsugi now prefers standard LTI placement vocabulary internally while still understanding and generating platform-specific extensions used by Canvas, Sakai, and existing Tsugi implementations.
I also add and refine manual LTI 1.3 tool creation. Dynamic Registration remains the preferred path, but administrators sometimes need to configure an LTI 1.3 tool manually. The interface now helps identify incomplete configurations as drafts and displays the platform URLs needed to connect the two systems.
Other refinements include:
• Mapping compatible platform-specific placements into standard LTI terminology
• Preserving extension placements when responding to Dynamic Registration
• Improving placement ordering and labeling
• Adding manual LTI 1.3 tool creation
• Marking incomplete registrations as drafts
• Showing platform OAuth and OpenID Connect URLs
• Adding copy-friendly configuration information
• Reducing full-page refreshes using AJAX and DOM updates
• Pretty-printing Dynamic Registration JSON at the appropriate layer
• Repeatedly testing registration, deletion, editing, and deep linking
• Reviewing CodeRabbit feedback before the production rollout
This episode is less about adding one large feature and more about taking a working implementation and making the data model, terminology, and user experience line up more closely with both the LTI standards and real-world platform behavior.
In this episode of AI Coding with Dr. Chuck, I continue refining the LTI 1.3 tool-management interface in Tsugi.
After building the initial CRUD interface for registrations, deployments, scopes, claims, and placements, I came back the next morning with a clearer picture of how I wanted the system to behave.
A major focus is normalizing placement terminology. Tsugi now prefers standard LTI placement vocabulary internally while still understanding and generating platform-specific extensions used by Canvas, Sakai, and existing Tsugi implementations.
I also add and refine manual LTI 1.3 tool creation. Dynamic Registration remains the preferred path, but administrators sometimes need to configure an LTI 1.3 tool manually. The interface now helps identify incomplete configurations as drafts and displays the platform URLs needed to connect the two systems.
Other refinements include:
• Mapping compatible platform-specific placements into standard LTI terminology
• Preserving extension placements when responding to Dynamic Registration
• Improving placement ordering and labeling
• Adding manual LTI 1.3 tool creation
• Marking incomplete registrations as drafts
• Showing platform OAuth and OpenID Connect URLs
• Adding copy-friendly configuration information
• Reducing full-page refreshes using AJAX and DOM updates
• Pretty-printing Dynamic Registration JSON at the appropriate layer
• Repeatedly testing registration, deletion, editing, and deep linking
• Reviewing CodeRabbit feedback before the production rollout
This episode is less about adding one large feature and more about taking a working implementation and making the data model, terminology, and user experience line up more closely with both the LTI standards and real-world platform behavior.










