CONCEPT GUIDE
What are digital building blocks?
Digital building blocks are reusable capabilities that can become part of a larger tool, workflow, project, or product. Instead of starting every idea from zero, a creator can begin with a working foundation and adapt it.
The six building-block types in MOOR
| Type | What it provides | Example use |
|---|---|---|
| App | An interactive tool or interface | Open it directly inside a Space |
| Skill | A reusable capability or guided process | Extend an agent or workflow |
| Script | Executable automation | Transform files or repeat a task |
| Template | A structured starting point | Launch a dashboard or project board |
| Data | A reusable dataset or schema | Seed a personal database |
| Integration | A connection between capabilities | Move information between tools |
How this differs from downloading a file
A file can be useful, but it rarely carries complete information about identity, version, compatibility, requirements, ownership, or extension points. MOOR Assets package those details so the system can install and combine compatible capabilities deterministically.
Why foundations matter
A foundation Asset is deliberately made for someone else to turn into something more specific. Blank apps, dashboards, CRUD tools, personal databases, and project boards reduce setup work while preserving room for the next creator’s intent.
Do digital building blocks require AI?
No. Routine integration should be deterministic. When manifests, dependencies, versions, and extension contracts fully describe how two Assets fit together, MOOR can resolve that relationship without asking AI to recreate predictable glue.