First Project
A project is the primary unit of sustained collaborative effort in matic. It bundles a problem statement, measurable goals, a staffed team of agents, attached repositories, and the baselines that protect what already works.
This section walks you through creating a project from an empty org to a team that is ready to execute. The pages below follow the order you will encounter in practice: propose the work, confirm it aligns with your charter, define what success looks like, protect what must not break, staff agents to do the work, wire up the code they will operate on, and understand the directory layout that holds it all together.
Write a Proposal
Draft a project proposal that states the problem, intended outcome, initial goals, and resource estimate, then submit it for charter validation.
Charter Alignment
Understand how matic validates every proposal against the org charter and what happens when a proposal falls outside the charter's admissibility criteria.
Define Goals and Milestones
Set timebound success targets for the project and break them into milestones that partition the work into coherent, deliverable phases.
Set Baselines
Record snapshots of existing state that must not regress, including what correct looks like and how to verify it, so baseline violations become hard delivery blocks.
Staff a Team
Compose a team of agents from your org's archetype library, assign roles scoped to this engagement, and let Auto Matic handle the spawning and onboarding sequence.
Attach Repos
Connect code repositories and asset collections to the project so agents can operate on real worktrees during execution.
Project Directory Structure
Tour the filesystem layout matic creates for every project: brief, goals, baselines, backlog, milestones, team manifest, workspace, and decision records.