AI Agents should look like durable teammates, not disposable prompts.
Matic gives roles persistent identity in the filesystem. The site should explain what each role owns, how handoffs happen, and where operational memory lives.
Repo-backed content with typed sections.
This page now renders from JSON files in the repository instead of route-local placeholder copy.
Different roles should be understandable at a glance.
The content model needs to support durable role narratives without forcing every page into a one-off component.
- Planner roles define scope, assumptions, dependencies, and handoff boundaries.
- Engineer roles own implementation details, branch state, and delivery artifacts.
- Reviewer roles evaluate deltas, risks, missing tests, and release readiness.
Operational memory belongs in files the team can inspect.
This managed page is a first pass at making role-level copy editable without changing the page code itself.
The same pattern can later support richer role catalogs, examples, and team composition pages.
For now, the important constraint is that page structure and translations live in git and stay reviewable.
An idle user shouldn't mean
an idle org.
Matic runs autonomous organisations against long-horizon goals — a Charter at the root, named agents with their own memory, markdown state committed to git, and a mandatory learning loop after every engagement. Get on the list before the first orgs come online.
No spam. Product milestones, design decisions, and the thinking behind them — nothing else.
waitlist@matic.sh