Courts and justice

Exclusion

Exclusion is a decision about a person's physical presence on the nation's land, so the workflow is built to prove it: who decided, under what authority, on what evidence, with what notice, and exactly what the person was told.

Built with your court · deadlines from your code · every order provable

The power to decide who may be present on the nation's land is the sharpest expression of territorial sovereignty, and the standards for it are the tribe's own. Your exclusion ordinance sets who may be excluded, on what grounds, who decides, what process is due, how long it lasts, and how a person asks to come back. That is your law. We build it in, section by section, exactly as your council enacted it.

It is also the decision most likely to be examined by someone outside the tribe. A person who is excluded has every incentive to challenge it somewhere else, and the challenge will be about the process, not the merits. The record is the defense.

The workflow runs on the same seven steps as everything else on the docket: summons, notice, change of notice, calendar, build, file, and the finished document.

Five things the record has to prove

Every exclusion question, wherever it is eventually asked, comes down to the same short list. A record built to answer these while the matter is happening answers them years later without anyone reconstructing anything.

  • Who decided. The deciding body or officer your ordinance names, attributed on the order itself, not inferred from a signature block.
  • Under what authority. The section of your own code the decision rests on, cited on the order, so the basis travels with the document.
  • On what evidence. The facts before the decider, captured as record entries when they were submitted, in the order they were submitted.
  • With what notice. Who was served, how, on what date, with which document, and what opportunity to be heard your code provided.
  • What the person was told. The terms in the person's hands: the scope, the duration, and the path back, exactly as issued.

Exclusion, from each seat

Tribal IT

The most sensitive decision the government makes stays in the building.

Exclusion files sit on your hardware, reachable only by the people the court has cleared, and the proof that they are unaltered is a check your own staff can run without calling anyone.

Council

The nation's territorial authority is exercised on the record.

Each exclusion shows the section of the tribe's own code it rests on, the process the person received, and the terms issued. When it is questioned, the file answers, and it answers the same way every time.

Staff

The steps are carried, so nothing is left out.

The workflow asks for notice, evidence, and terms in the order your code requires them, and produces the order from the record. Nothing depends on remembering what an exclusion file is supposed to contain.

The one place federal law names exclusion by name

Federal law addresses exclusion in a narrow and specific setting: enforcing a protection order. A tribal court has full civil jurisdiction to issue and enforce protection orders involving any person, including through civil contempt, exclusion of violators from Indian land, and other appropriate mechanisms, in matters arising anywhere in the Indian country of the tribe or otherwise within the tribe's authority. Indian country there carries its federal statutory definition.

Read it for exactly what it says and no more. It names exclusion as one mechanism a tribal court may use to enforce a protection order, and it opens with the words "For purposes of this section." It is not a general federal grant of exclusion power, and treating it as one would get the foundation exactly backwards: no statute grants this authority, because it is inherent and predates the Constitution. Congress did not give it to you and Congress is not the reason you have it.

How far that inherent authority reaches over a nonmember, and especially over conduct on fee land within the reservation, is genuinely unsettled. The Supreme Court has not decided it either way, and the case that came closest produced no majority opinion. That is a question for your court and your attorneys. Nothing here decides it, and nothing here is legal advice. What the system does is carry your code exactly and make the record answer for itself.

The practical point for the office is the same either way. When exclusion is used to enforce a protection order, the strength of the enforcement rests on the protection order's own record: jurisdiction, notice, and an opportunity to be heard. When exclusion rests on the tribe's own code, the strength rests on that record instead. Both roads lead to the file.

The safe way to state it: federal law expressly recognizes exclusion as a way to enforce a protection order. Everything else about who may be present on the nation's land is written in the nation's own code, and that is the code we build in.

The one door Congress left open, and what a federal judge reads when someone walks through it

Exclusion is worth being honest about, because it is the tribal decision most likely to reach a federal forum. The Supreme Court closed the general door in Santa Clara Pueblo, holding that habeas under 25 U.S.C. 1303 is the only remedial provision Congress expressly supplied against a tribe. It left that one door open, and exclusion is the tribal act most likely to walk through it.

The Second Circuit has held that orders of permanent banishment are a severe enough restraint on liberty to confer federal habeas jurisdiction, and that the existence of the orders alone, even absent any attempt to enforce them, satisfies the jurisdictional threshold. Read that carefully, because two limits matter. It is a jurisdictional holding: it says a federal court may hear the petition, not that the banishment was unlawful. And those petitioners were members being banished, not nonmembers being excluded, so it does not settle a nonmember's access to the same door. The Ninth Circuit has since agreed with that standard rather than splitting from it, and found no jurisdiction where people had been disenrolled but not banished.

Here is why this is the whole argument for the page. When a federal judge takes that petition, there is no federal record to read. There is only yours. What the judge examines is your file: whether the person knew, whether they had a chance to be heard, whether the decider was the one your code says decides, and whether the terms they received are the terms on file. Those are not questions about the merits of the exclusion. Every one of them is a question about the record.

So a file that shows notice as an event with a date and a method, evidence in the order it arrived, the deciding body named, the code section cited, and the issued document reproducible identically years later has already answered the federal court before it asks. The tribe's authority over its own land is not made stronger by a better filing cabinet. It is made harder to unwind by a record nobody can credibly say was incomplete or changed after the fact.

Disenrollment alone generally does not open the federal habeas door. Banishment and exclusion plausibly do. That is exactly why an exclusion record carries more legal exposure than almost anything else the government writes, and why it is worth building the workflow around proving it.

Questions courts ask about exclusion

Whose exclusion standards does the system apply?
Your tribe's. The grounds, the decider, the process, the duration, and the way back are set by your own ordinance and your inherent authority. We sit with that code and build the rules in section by section, and every date the system computes shows the section it came from.
Where does our authority to exclude come from?
Not from Congress. The power to decide who may be present on the nation's land is inherent, and it predates the Constitution. No federal statute grants it, and a system that treats it as a federal grant has the foundation upside down. Federal law does name exclusion once, at 18 U.S.C. 2265(e), as one mechanism a tribal court may use to enforce a protection order, and that provision opens with the words "For purposes of this section." Everything else rests on your own law and your inherent authority. How far that reaches over a nonmember, especially on fee land within the reservation, is genuinely unsettled and is a question for your court and your attorneys. Nothing here is legal advice.
What does the excluded person actually receive?
The document your code requires, generated from the record: the scope, the duration, the basis with its code section, and the path to ask the tribe to reconsider. The copy in their hands and the copy in the file are the same sealed document, and it reproduces identically years later.

Sources

  1. 18 U.S.C. 2265(e), tribal civil jurisdiction to issue and enforce protection orders · U.S. Code, Cornell LII. law.cornell.edu
  2. Santa Clara Pueblo v. Martinez, 436 U.S. 49 (1978), habeas is the only federal remedy Congress supplied · U.S. Supreme Court, Cornell LII. law.cornell.edu
  3. 25 U.S.C. 1303, habeas corpus review of tribal detention · U.S. Code, Cornell LII. law.cornell.edu
  4. Poodry v. Tonawanda Band of Seneca Indians, 85 F.3d 874 (2d Cir. 1996), banishment as a restraint on liberty · U.S. Court of Appeals for the Second Circuit. law.resource.org
  5. Jeffredo v. Macarro, 599 F.3d 913 (9th Cir. 2010), agreeing with the Second Circuit standard · U.S. Court of Appeals for the Ninth Circuit. cdn.ca9.uscourts.gov

Get started

Find your tribe's first step.

A short conversation, a look at the working system, and a plan that fits your tribe's timeline and budget.

No cost, no commitment. You will speak with the person who builds it.