Extended Matrix
The method itself: the node types, the connectors, how a stratigraphic reading becomes a graph that another archaeologist can argue with. Start here if you are new — every other manual assumes these words.
Each tool keeps its manual beside its own code, and publishes it at one
of two addresses: the Extended Matrix manuals live under
docs.extendedmatrix.org,
the StratiGraph ones under
docs.stratigraph-eccch.eu.
Every manual has a version menu at the bottom left of its pages: when you
cite one in a publication, cite the version you read rather than
latest, so that the sentence stays where you found it.
The method itself: the node types, the connectors, how a stratigraphic reading becomes a graph that another archaeologist can argue with. Start here if you are new — every other manual assumes these words.
The standalone editor, recommended for authoring from EM 1.6 onwards: six workspaces, the native em.json, and the legacy GraphML graphs opened in place. Published in English and Italian, and downloadable as PDF or EPUB for a field computer with no network.
Where the graph meets the 3D model: proxies, representation models, epochs and the panels that keep the reconstruction and its argument in the same file.
The photogrammetric pipeline and the import of survey data into Blender, including the georeferencing and the levels of detail the EM workflow expects.
The Python implementation of the language: the datamodel every tool reads and writes, the CRMem declarations, and the API for whoever scripts against a study outside Blender.
What a visitor, a peer or a reviewer meets in a browser: the exported reconstruction with its paradata, and how a study gets there.
StratiGraph is the Horizon Europe project that builds the shared node around the Extended Matrix. Its manuals have an address and a look of their own, and they cite these ones where a step of the work passes through an EM tool.
The place a team shares: rooms, studies, documents, the signatures that say who may see what, and the catalogue that publishes what a room decides to publish. Two parts — working in a room, and running a node of your own.
The field assistant: recording on site, on a phone or on a laptop with no network, and the synchronisation with the node when there is one.
The sheets and the controlled vocabularies a team starts from: the stratigraphic unit record, the axes of status and origin, the modules a discipline adds. English and Italian.
Not a manual: the place where you learn the craft — the competence nodes and the five working phases of an investigation, citing the manuals rather than copying them.
A manual is changed in the repository of its own tool: the code map lists them, and each repository's README carries the same table of manuals you see here. Mistakes and gaps are welcome as issues — a page that answered the wrong question is a defect like any other.