Public Materials
MCVA / AMCVA Atlas
The atlas is where the vocabulary becomes testable.
If someone wants to use the work, this is one of the first places they should look. The atlas is the practical layer that turns the project from a set of ideas into a comparison workflow.
MCVA is the positive readout lane: the part of the framework that asks when morphology contains enough structure to support comparison, descriptor extraction, and process-memory hypotheses. AMCVA is the guardrail atlas: absent, erased, hidden, low-resolution, contaminated, misleading, or non-diagnostic form.
The point of the atlas is not to say that trees, rivers, blood vessels, lightning, fractures, and dendrites all mean the same thing. The point is to build a disciplined comparison language for when morphology is present, and a disciplined refusal language for when it is not.
The public atlas should grow through manifests first: source, rights, domain, subdomain, modality, descriptor tags, AMCVA boundary notes, and only then public assets where the publishing rights are actually clear.
Without AMCVA and HOLD, a morphology-first framework drifts toward over-reading. The point is not to say every branching or fracture pattern means the same thing. The point is to preserve a disciplined comparison workflow when morphology is present and to preserve restraint when it is not.
For contributors, the question here is straightforward: what examples belong, what descriptors matter, what counts as a useful negative case, and how should ambiguous morphology be routed into HOLD rather than forced into overclaim?
If you are new to the project, read this page as the atlas layer, then read the Morphological Memory paper for the broader thesis, and then the Evidence Library for examples and edge cases.
Continue with the Evidence Library, the whitepaper, and the glossary.