The five-layer Machine Relations operating framework: Earned Authority, Entity Optimization, Citation Architecture, GEO/AEO Distribution, and AI Visibility Measurement. Coined by Jaxon Parrott in 2024 and published by Machine Relations.
The MR Stack is the five-layer operating framework Machine Relations uses to separate different kinds of work that are often grouped together as AI visibility. It is an MR-authored analytical architecture, not a description of private answer-engine mechanics.
Premise: Each layer represents a distinct class of observable work. The stack does not claim that the layers have universal weights, that they must be completed in a fixed order, or that changing one layer causes a particular citation outcome.
Machine Relations defines Earned Authority as third-party editorial coverage and other independently published references to an entity.
Observable fields: publication, URL, publication date, named entity, attributed claims, and whether the reference is linked or unlinked.
What the layer records: the independently published references available for later comparison with answer-engine citations. Their presence does not by itself prove that an engine trusts, retrieves, or cites them.
Machine Relations defines Entity Optimization as the work of making public identity records consistent and inspectable across owned and third-party surfaces.
Observable fields: canonical name, aliases, founder and organization relationships, category description, structured-data identifiers, and conflicting records.
What the layer records: whether public identity information agrees across the surfaces being audited. Its scope is public identity evidence, separate from internal engine representations and attribution outcomes.
Machine Relations defines Citation Architecture as the organization of claims, definitions, data, and attribution inside a published document so they can be inspected as discrete units.
Observable fields: claim text, nearby source attribution, heading context, data labels, publication date, and stable URL.
What the layer records: whether a document contains identifiable claim-source units. Its scope is document structure, separate from later selection and citation observations.
Machine Relations uses GEO and AEO Distribution for the publication and discoverability work associated with answer-engine surfaces.
Observable fields: public URL, indexability, crawl directives, canonical URL, structured data, machine-readable representation, and observed answer-engine appearance.
What the layer records: where content is available and where it is later observed. Availability does not prove retrieval, ranking, or citation.
Machine Relations defines AI Visibility Measurement as repeated observation of named entities, cited sources, and answer outputs under a disclosed query and collection protocol.
Observable fields: engine, query, run time, answer text, cited URL, resolved domain, entity mention, and comparable observation window.
Premise: This layer records answer output from the disclosed engine panel and observation window. It keeps observed associations separate from causal explanations.
Working model (not measured): The five layers are reviewed together because they describe different evidence surfaces: independent references, identity records, claim structure, public availability, and observed answer output.
The framework does not require a universal sequence. A team can work on several layers at once and use the measurement layer to identify differences between observation windows. Any explanation for those differences remains a hypothesis until separately tested.
An MR Stack review can ask:
These questions produce an evidence inventory. They do not, on their own, prove why an engine produced an answer.
The comparison below describes how Machine Relations scopes the MR Stack. It is a taxonomy, not a claim that one framework replaces the other.
| Dimension | Common SEO scope | MR Stack scope |
|---|---|---|
| Observed surface | Search result pages and site behavior | Answer outputs, entity mentions, and cited sources |
| Content objective | Page discoverability in search | Claim and source inspection across answer surfaces |
| Measurement examples | Impressions, rankings, clicks | Citation rate, source share, entity resolution observations |
| Distribution scope | Search indexes | Disclosed answer-engine and search-engine panel |
| Authority evidence | Links and referring domains | Independently published references and observed citations |
| Change over time | Compare search observations across dates | Compare answer and citation observations across dates |
The MR Stack is not a claim that five hidden engine mechanisms exist. Its scope is the organization of evidence classes, not engine behavior or outcome prediction. It does not assign causal weight to earned media, entity records, document structure, distribution, or measurement.
The framework is an operating vocabulary for keeping those evidence classes separate while examining how they coincide in disclosed observations.
The MR Stack is the operating blueprint Machine Relations uses to organize its own methods, audits, and measurements. Work maps to whichever layers the stated method covers.
Premise: A shared layer vocabulary makes it easier to distinguish an observed gap from a proposed intervention and a proposed intervention from a measured outcome.
Yes. The framework does not prescribe a universal starting layer. Choose the evidence surface relevant to the question, record the baseline, and keep causal interpretation separate.
No supported universal timeline exists. Record the collection dates, the intervention dates, and comparable before-and-after observations instead of promising a schedule.
No. The framework is an evidence-classification system, so its structure does not depend on company size. The number of records, sources, queries, and engines in a measurement panel should be disclosed for each use.
Coined by Machine Relations. This term originated with Machine Relations founder Jaxon Parrott. The definition on this page is the canonical one.
Machine Relations' own methodology, dataset, and research pages related to this term. These are self-references, listed separately from Sources — they are not independent evidence.
Related concepts
Supporting research
Framework context