Every component published through metafactory is a blueprint. Nine types describe what a blueprint is, organized across two dimensions. The execution stack builds upward, each layer composing from below. Shaping artifacts apply horizontally, guiding behaviour at any level. A bundle packages any combination into a cohesive whole.
A single executable that does one thing well. Deterministic input/output, no AI judgment involved. Tools are the building blocks that everything else composes from.
A hand tool: a wrench, a saw, a level.
A tool plus AI judgment. Skills observe, decide, and adapt. They declare workflows and activation triggers, routing between strategies based on context.
A trained craftsperson who knows when and how to use the tools.
A directed acyclic graph (DAG) of executable steps: deterministic nodes, agentic nodes, and human gates wired together. Processes do the work automatically. Each node declares its dependencies and runs in isolation.
An assembly line where each station does its job and parts flow to the next.
A process plus autonomy and persistent memory. Agents observe, decide, and act in loops. They run processes, use skills, and remember context across sessions.
A team member with judgment, memory, and the ability to work independently.
Multiple agents running multiple processes through shared state under governance rules. A graph decides which agent runs which process when, and how they communicate. The highest level of the execution stack.
A company: departments, roles, communication channels, and governance.
Structured instructions that shape how an AI model approaches a task. Prompts define perspective, constraints, and output expectations without executing anything. They can be applied to any level of the execution stack.
A design brief: it shapes the work without doing the work.
Declarative boundaries that govern what can and cannot happen. Rules don't do work; they prevent wrong work. Applied across projects, teams, or pipelines at any level of the stack.
Building codes: they don't design the building, they ensure it's safe.
A structured step-by-step procedure with ordered steps, optional gates, and decision points. Playbooks teach; they don't execute. They may reference tools and skills but don't compose them into an automated pipeline.
A recipe: it tells you what to do, step by step. You do the cooking.
Multiple blueprints of different types, packaged together because they belong together. A bundle groups skills, tools, processes, and documentation into a cohesive whole. Use this when a single type doesn't capture what your blueprint contains.
A roll of blueprints tied together, carried to the drafting floor because they're all part of the same project.