Appendix

This appendix collects the conceptual and architectural material that the rest of the reference assumes but does not re-explain. It matters because matic’s schemas, filesystem layout, CLI surfaces, and runtime behavior only make sense if you understand the shared vocabulary, the canonical model of the system, and the implementation boundaries that let teams build it in parallel. Use these pages when you need to resolve naming, trace a primitive back to its source contract, or connect operator-facing docs to the underlying runtime design.

Glossary

A domain-organized reference of the terms matic uses for venture primitives, actors, work, governance, infrastructure, and coordination. Read more

Implementation Architecture

The package, process, and integration architecture for the runtime, showing how filesystem, git, signal flow, execution, adapters, CLI, and daemon responsibilities fit together. Read more

Ontology

The authoritative ontology for matic’s primitives, relationships, scopes, and behavioral contracts, from org structure through agents, work, governance, and continuous improvement. Read more