Derive module hierarchy from curriculum
Packaged know-how that tells an agent how to do a job well.
You might say…
“The curriculum outline and the platform's content tree are different shapes — this maps one to the other before I start creating content slots.”
What it does
Translates the finished curriculum outline into a concrete platform module/section/lesson hierarchy with naming conventions the platform will accept.
Trigger: Use after base platform config is done and before creating any content slots, to translate the curriculum structure into platform-ready hierarchy.
I/O: Finished curriculum outline + platform naming constraints → platform module/section/lesson hierarchy
Recognise the problem?
The primitives are the commodity part. The fastest next step is a conversation about composing them into something that works for you.
Start a conversation