You've been there. A government form with a dropdown. A research database with required fields. A system that needs to put you somewhere. The dropdown gives you choices. None of them are right.
You pick the closest one. The system records it. The record moves through pipelines you'll never see. Somewhere downstream, it produces output -- a statistic, an allocation, a policy decision -- that looks like it's about you. It isn't. It's about what the dropdown could hold.
When a system forces your identity into a category it wasn't built to hold, it produces output. The output looks real. It has a value in a field. It travels. Other systems use it. But it's been severed from the relations that made the data mean something -- the political history, the governance obligations, the kinship, the sovereignty. Those didn't fit in the dropdown.
SRA calls this an artifact: output that looks like knowledge but has been cut from the conditions that made it true. Not an error in the sense of a mistake you can correct by entering the right value. An error in the architecture. The system cannot represent what it needs to represent, so it substitutes something it can. The lie is built into its structure.
The system can't tell the difference between an artifact and a representation. That's the problem. It processes both the same way.
selection ↓
Most data systems share an assumption so deep it rarely gets named: the thing already exists before you put it into the system. You're just capturing it. The question is who gets access.
SRA asks a prior question: what happens to a thing when you move it into a system?
Some things survive. A photograph of a chair is still about a chair. The chair's persistence conditions -- the conditions under which it remains what it is -- are compatible with photography. But some things don't survive, because they're constituted by their relations. Break the relation and you don't have a piece of the thing. You have something else entirely. The dropdown doesn't give you part of MHA nationhood. It gives you an artifact.
SRA names these persistence conditions: the relational configuration under which a pattern can present a stable interface to a given observer or system. Their absence signals not withdrawal but incommensurability -- the pattern has not retreated; the system encountering it has lost the capacity to receive it. What conventional data governance reads as absence or refusal is often incommensurability it cannot distinguish from nothing. Before any decision about access or storage, SRA asks: can this survive becoming data? If yes -- under what constraints? If no -- what is the correct system behavior?
The answer to the last question is not "store it anyway and add a warning label." The answer is refusal. And refusal, in SRA, is not a failure state. It is a designed outcome. The system working correctly.
Relations with land, water, and more-than-human persons are not an extension of this framework. They are its original ground. The Missouri River was a relative before it was a resource. When the Army Corps enclosed the Garrison Dam in April 1953 and dedicated it that June, the river did not merely change course; it ceased to be what it had been. 156,000 acres of the best bottomland drowned. Cottonwood groves stopped regenerating. The seasonal flood patterns that Maaxiiriwia knew when teaching which plants grew along those banks -- patterns that her knowledge was constituted by -- were replaced by regulated releases calibrated to downstream hydropower demand. The dam did not ask whether the Missouri River's persistence conditions could survive enclosure. It built. That is the artifact problem at civilizational scale.
SRA at the more-than-human scale is not resource management or ecological data capture. It is relational maintenance infrastructure: the work of sustaining conditions under which both knowledge and the relations that constitute it can remain what they are.
Among the plants she carried was Macúahca, sweetgrass: medicine, ceremonial relative, a presence that marked which places were still in right relation with those who gathered her.
The dam reorganized the moisture patterns along the old banks. Some growing places moved. She moved with them, and the People who gather her followed, as they have always followed, because that is what relation means.
We keep a pot of Macúahca on the deck in Carlisle. Our neighbors mow. We protect her. We comb her hair, trim her ends. We sing near her and eat near her and talk to her and let her hear us living. She gives back what she always has. We are girasháaci: pitiful, young, and ignorant. Little siblings next to our elder doing the best we can in the ways we know how.
The Garrison Dam did not ask whether the Missouri River's persistence conditions could survive enclosure. It built. The river became a reservoir -- 156,000 acres of bottomlands drowned, the cottonwoods stopped regenerating, the ceremonies had to adapt to a body of water that no longer kept time the way it once had. The Army Corps called the output water management. Every diagnostic criterion from the artifact problem applies: ontological truncation, authorization loss, context collapse, governance attenuation, predictable downstream misfires. The dam and the dropdown share a logic. The difference is scale.
The artifact problem does not stop at data.
Most frameworks built to address the misrepresentation of Indigenous peoples assume that authority can be located -- in a named person, a committee, a title -- and used as ground for governance. That assumption carries the same structure as the dropdown. Take something relational, locate it in a bounded node, circulate the result as if it were the thing itself.
Authority is also an artifact. It is always a partial transmission of something it cannot fully carry. Strip the relations that generate it -- accumulated practice, recognized obligation, the presence of those whose standing makes the authorization real -- and what remains is institutionally legible, administratively tractable, and bearing no reliable correspondence to what it claims to represent. The systems that do not know this keep producing the same failure at scale, because they have accepted the premise that makes it inevitable.
SRA is built from the opposite premise: that the relay who writes a warrant is not the authority. They are transmitting, under acknowledged loss, what they have witnessed -- on behalf of relations whose authority remains elsewhere. That elsewhere is not mystification. It is living practice, recognized relation, accumulated proof of good relation across time, place, species, and community.
SRA is not a policy. It is an architecture: a set of components that work together to prevent artifact production before it starts. The architecture follows an argument. Each component answers a question that the previous one could not ask from within itself.
The first question is not "who gets access?" It is: can this resource's persistence conditions survive digitization without producing artifacts or turning relational governance into surveillance categories?
DVA is community-defined and produces three determinations. Digitizable with persistence conditions: the resource can enter a data system; its conditions encode as warrant constraints. Digitizable with governance constraints only: some conditions cannot be made machine-readable without creating surveillance risk; they remain in community governance space, still governing, not encoded. Non-digitizable: encoding would produce the harm. The system returns "no record" -- not as failure, but as integrity protection.
DVA is not arithmetic. It does not score conditions against a threshold. It is a governance determination, made by the community, contestable by the community.
A warrant is a transmission record, not an authorization document. It is produced by a relay -- someone who has witnessed what the system can and cannot receive -- and records that transmission occurred under acknowledged loss. What the system receives is partial. What it cannot receive still governs.
The warrant encodes the relay identity and quorum, what was witnessed, the relational remainder the document cannot carry, which persistence conditions can be expressed as system constraints, and which must remain outside the system's sight. The authority remains in the relations. The warrant records its trace.
The relay is answerable to those in whose name transmission occurs -- bounded in claim, prohibited from substitution. A relay who begins to stand in for rather than transmit toward has ceased, relationally, to occupy the role.
The gate does not ask: does this user have permission? It asks: is this interaction compatible with the resource remaining what it is? Three checks must pass in sequence: preservation (do the invariants survive the transformation?), commutation (does the policy transport hold?), and warrant (does the transmission record authorize this context?). The commuting square closes only when all three pass.
Admission means the interaction produces a representation. Refusal means it would not -- and that refusal is a success condition, not a failure. When two faithful relays transmit divergent readings of the same conditions, the gate enters a CONTESTED state and holds the resource in protected interval. This is not an error. It is the system recognizing genuine governance complexity.
Refusal is not absence. It is a positive data state: sovereignty exercised, evidenced, and made visible at whatever tier the community decides. The community decides what is visible, to whom, and under what conditions.
Three visibility states: Publicly citable -- the refusal is externally visible; sovereignty exercised, not data absent. Restricted -- recorded for audit and governance but not discoverable outside authorized partners. Non-disclosure of existence -- the system does not confirm whether the resource exists at all. An external query returns the same response whether the resource is under NDE protection or does not exist.
The three tiers prevent the record from becoming a targeting list. What is visible depends entirely on the relation between the viewer and the resource.
Governance constraints persist and can only intensify -- never attenuate -- as data moves across system boundaries. A warrant specifying seasonal access cannot be received by a system that strips temporal constraints for interoperability. The gate rejects the transfer or quarantines the resource.
The warrant travels with the resource. The governance is not upstream of the system. It is the system. Receiving institutions are required to accept the warrant as binding, not as advisory.
Infrastructure cannot be the ground of relational accountability. It can only express it. SRA addresses specific structural problems. It does not address them all.
SRA cannot create the relational conditions that governance requires. It assumes a trust root: a community governance process that can produce legitimate relays, legitimate warrants, and legitimate DVA determinations. Where that trust root is absent, compromised, or contested under institutional pressure, SRA's protections do not hold. The architecture can make the absence legible. It cannot manufacture trust.
SRA cannot prevent governance capture. An institution that controls the implementation of SRA controls the conditions under which warrants are evaluated. The correct implementation model is: community governance shapes the warrant; the warrant shapes the infrastructure. Not: infrastructure is built; communities are asked to configure it within its permitted options. The difference is not technical. It is political.
SRA cannot protect resources transmitted through channels that bypass the gate, resolve political conflicts about who speaks for a community, or substitute for the trust, ceremony, and ongoing relation that warrant production depends on.
Partial implementation is not failure. Implementing DVA without warrants is still an advance over beginning after the digitization decision. Implementing warrants without full gate evaluation is still an advance over no transmission record. The goal is honest implementation -- knowing what the infrastructure can and cannot do, and building governance capacity alongside technical deployment rather than expecting the technical deployment to substitute for it.
AI systems are doing this at scale. Every training dataset built from Indigenous-authored content without consent builds the wrong assumption deeper into infrastructure. Every model trained on that data learns to produce artifacts and passes them downstream as representations.
SRA isn't only for Indigenous data -- the architecture is general, applicable anywhere persistence conditions matter. But it was developed from the specific: from MHA Nation, from the Missouri River, from Maaxiiriwia's plant knowledge, from what happens when a system can't see what it's destroying.
The general theory is earned from particular ground. The particular ground is not an example of the theory. The theory is an account of the ground.
The question is whether systems get built that can ask the prior question before the dam closes.
Systems that cannot read persistence conditions do not see absence where there is absence. They see absence where there is incommensurability -- where the thing is present but has refused the terms of the encounter. The outputs they generate are not representations of nothing. They are ghost outputs: references to a relationship only one party is pretending to have.
Relation comes before data. It came before the dropdown, before the first federal survey that handed us a box to locate ourselves in, before every form that has minted administrative unreality from our political history and sent it into circulation as fact. Infrastructure honest enough to know this asks, before the first record is created: what kind of thing is this system capable of producing? That question is the first and most consequential act of governance.