Appeals

On the record means the record is the case

In an appeal, nobody re-tries the matter. No new witnesses, no new evidence, no second version of the facts. The panel reviews what happened below, and what happened below is whatever the record says happened below. The record is not documentation of the case. On appeal, the record is the case.

That is why a partial record is not an inconvenience, it is a different outcome. If a transcript is missing, if an exhibit was never indexed, if a notice went out but the proof of service lives in a drawer, then the appeal turns into an argument about the file instead of an argument about the case. The party with the weaker position on the merits gets to litigate the paperwork, and sometimes wins there.

The sharper version of the problem is alteration. If anyone with access could have changed a document after the fact, then the record's completeness is a matter of trust rather than proof, and trust is exactly what a losing party has an incentive to attack. A sealed, hash-chained record removes the question. Each entry is stamped when it happens, chained to the one before it, and any change to any part breaks the chain visibly. The panel does not have to take the clerk's word that the file is whole. The file proves it.

• Every filing sealed at the moment it happens, not reconstructed later from memory or a folder.
• Each entry chained to the one before it, so the trial court's history is one continuous, verifiable object.
• Service and notice captured as events, with who, how, when, and which document, because the appellate clock usually runs from one of them.
• Orders reproducible identically years later, generated from the record rather than stored as a copy of a copy.
• The record on appeal assembled from the sealed history, so what transmits up is complete by construction, not by checklist.
• Every computed date shows its section, so a question from the panel about why a deadline falls where it does has an immediate answer.

The most unforgiving clock in the building starts itself

An appeal deadline is the one date that forgives nothing. Miss it and the merits stop mattering; there is often no version of the argument that survives. Yet in most courts it is tracked the same way as everything else, which is to say in someone's head, on a sticky note, or in a calendar entry that depends on a person remembering to make it.

The deadline itself is your code's decision. How many days, counted how, from which event, with which exceptions: that is your appellate ordinance, and we build it in with your court rather than assuming another jurisdiction's numbers. What the system contributes is that the triggering event is already on the record. Entry of judgment is a record event. Service of notice of entry is a record event. The clock does not need to be started by hand because the thing that starts it has already been captured.

So the date computes the moment the trigger happens, it appears on the calendar without anyone deciding to put it there, and it shows the section of your code it came from. A party asking why the deadline falls on a given day gets the section, not an explanation.

Your appellate decisions are your common law

Every opinion your Court of Appeals issues is a statement of what your code means. Taken together, over years, those opinions are the tribe's own body of law: the accumulated interpretation that tells a judge how this nation reads its own ordinances, and tells a party what to expect before they file.

That body only exists if it can be found. An opinion in a binder in a back office is not precedent in any working sense, because the judge deciding the next case cannot see it and the clerk cannot cite it. Courts lose their own law this way, quietly, one retirement at a time, and end up reasoning from other jurisdictions because that is what is searchable.

Decisions here are stored as governed records: sealed, attributed, and findable by the code section they construe, by the people involved, and by the question decided. A judge writing today can see what this court held before. That is the difference between a court that accumulates law and a court that starts over.

A tribe's appellate opinions are the clearest evidence that its court is a real forum, deciding real questions under its own code, consistently, over time. Keeping them findable is how that evidence compounds.

The Supreme Court already conceded the point, by its own method

In Iowa Mutual Insurance Co. v. LaPlante the Court needed to know whether an interlocutory appeal from a jurisdictional ruling was available in the Blackfeet courts. It consulted no federal statute and no regulation. It read the tribe's code, and said so: "Although the Blackfeet Tribal Code establishes a Court of Appeals, see ch. 11, sec. 1, it does not allow interlocutory appeals from jurisdictional rulings."

That is the whole argument for building your deadlines from your ordinance rather than from a default somebody else chose. When the highest court in the country wanted to know what your appellate procedure was, it opened your code. So does this system.

The doctrine also leans on your appellate layer without ever building it. Iowa Mutual holds that exhaustion means, at a minimum, that tribal appellate courts must have the opportunity to review the determinations of the lower tribal courts, and that until appellate review is complete, the federal courts should not intervene. Federal law assumes the layer exists. It does not create one, staff one, or set its deadlines. Your code does all three, and your record is what makes the review it contemplates possible.

Exhaustion is a rule of comity rather than a jurisdictional bar, and it has exceptions: bad faith, a patent violation of express jurisdictional prohibitions, and futility. It is a strong default, not an absolute. As always, that is a question for your court and your attorneys.

Questions courts ask about appeals

Whose appellate rules does it follow?

Yours, and only yours. The deadline, the panel, the contents of the record on appeal, and the form of the notice all come from your appellate ordinance. We sit with your code and build those rules in section by section, and every date the system computes shows the section it came from.

How does the panel know the record is complete?

Each entry was sealed when it happened and chained to the one before it, so the record verifies as one object. Completeness is checkable rather than asserted, and any alteration to any part shows up as a broken chain.

What if our Court of Appeals sits only occasionally?

That is common and the workflow is built for it. The record is ready whenever the panel convenes, the clocks keep running from your code regardless of the sitting schedule, and a panel member coming to a matter cold opens a complete file rather than a partial one.