The motives and goals of this corner are several:
- To explain the ideas, status, and connections between different projects
- To describe the areas of knowledge covered by those projects
- To document the usage of the tools used by those projects
- To serve as a syllabus of what needs to be studied to continue or understand those projects
- To hold the notes, summaries and reflections product of such studies
- To use such derivative work to create educational materials
- To be a living and evolving applied proof of concept of metadata architecture
- To use the content and structure to feed models and aid the organizational rituals
- To invite others
To work in the crucible, we define a structure in three steps:
- classes: based on the fileClass from the metadata menu obsidian plugin, defines the different things, and the relations between them.
- templates: the structure of the content that a thing will follow.
- specs: the formal definition of both classes and templates in one document that can be transformed into standards.
The definition and usage of these things are guided by the motives and goals of the corner, and we can differentiate three major different kind of things:
Learning Relationships
Any pair of those things can be connected together through a learning pair, and each of those learning pairs exercises one of the Learning Modes through a set of Learning Actions.
Fragments
During the learning exercise, fragments can be created. A fragment can be a note from a book, a summary from a unit of a course, a graph, a drawing.
Weave
Fragments can be stitched together to create new things. A script for an audio narration or a video, slides for a workshop, the definition of the workshop, the final audio or video.
Weaving can also be a set of Building Actions to make progress in one of the projects.
Crucible
The current project was born as crucible. But this lead to forge later, both started to sound very much clunky clunky clunky, the oven pass to be then the initial index, and the last step.
