Council & Governance

A resolution is an instrument, not a document

When a council adopts a resolution, it is exercising sovereign authority. That act may later authorize a contract, waive immunity in a specific instance, set an enrollment criterion, approve a budget, or bind the tribe in a matter worth a great deal of money.

Which means the question that eventually gets asked is never really about the paperwork. It is: what exactly did the council adopt, on what date, by what vote, and is this the text? A minute book that can be edited without a trace cannot answer that question with authority. A sealed record can.

• The text as adopted, sealed at the moment of adoption, so the version question has an answer.
• Every amendment on the floor, kept, so the path from the draft to the adopted text is visible.
• The vote, attributed, member by member, sealed with the resolution it carried.
• The minutes and the record together, so the decision and its context are one object rather than two files.
• Reproducible copies, so a certified resolution produced three years later is byte for byte what was adopted.
• Searchable across years, so the council can find what it has already decided before it decides again.

Immunity, inspection, and the discipline of a clean record

Sovereign immunity protects the tribe, and it is strongest when the tribe's own record is clear about what was and was not authorized. A waiver is a deliberate act of the council, and the question of whether one was made is answered by the resolution, exactly as adopted.

Records inspection expectations vary by tribe and are set by your own law. A complete, attributed, versioned record makes either posture straightforward: you can produce precisely what your law requires you to produce, and you can show that what you produced is what exists.

The ordinance is the source the whole government runs on

Here is the argument that matters most from the council table, and it is not about software. When the council amends a section of the code, that section is the same section a deadline on the court's guardianship docket cites, the same section an enrollment determination applies, and the same section a license condition comes from. The council's legislative act and the system's behavior are one fact, not two things kept in agreement by whoever remembers to do it.

That is only true if it is built that way. We sit with the government and build your code in, section by section. The clocks, the criteria, the conditions, and the limits come from your published law, and every date or determination the system produces shows the section behind it. Nothing is carried over from another jurisdiction's assumptions about how long an order should last or who qualifies for what.

Federal law occasionally makes this concrete in a way that is hard to argue with. Under the Indian Child Welfare Act, a tribe may by resolution establish a different order of placement preference, and the agency or court must follow the tribe's order so long as the placement is the least restrictive setting appropriate to the child's needs. That is a federal statute directing an outside court to apply the council's resolution. A resolution that reaches that far deserves to reach the tribe's own decisions too, and it does when it is built in rather than filed.

So the council is not really buying software. It is watching its own law run, with each act cited back to it in plain sight.

1. The council adoptsThe amendment passes and is sealed with its vote and its date, exactly as adopted.
2. The rule is builtWe build the amended section into the rule the office runs: the clock it starts, the criterion it sets, or the condition it attaches. It comes from your published law, and the build is a conversation with the people who apply it.
3. The citation followsThe next order, determination, or license condition names the amended section, so anyone reading it can see which law produced it and check that law for themselves.
4. The history staysThe prior version of the section, and every decision made under it, stay on the record. A matter decided last year can still be read under the law that governed it then.

A build has a useful side effect: it sets the written code beside the office's actual practice. Where the two differ, the system shows both and names the difference. Which one changes, the code or the practice, is the council's decision to make, and now it is a decision rather than an accident.

Minutes, agendas, and the record of how a decision was made

A resolution's authority does not rest on its text alone. It rests on how it was adopted: that a quorum was present under your constitution and bylaws, that a motion was made and carried, that a vote was taken on a date, and that the text being read now is the text voted on then. None of that is legal theory. Those are record facts, and either the record carries them or the question gets answered from memory.

So the agenda, the minutes, and the resolution are one object here rather than three files that reference each other. The agenda shows what was noticed. The minutes show who was present and what was moved. The resolution carries the text as adopted. Open any one of them and the other two are already attached, which is exactly the position you want to be in when someone asks about a vote taken four years ago.

How long the council keeps all of it is the council's call, and that is the actual legal position. There is no single federal schedule governing a tribe's internal records the way a state schedule governs its counties. As sovereigns, tribes enact their own records-management ordinances and retention schedules, and tribal codes commonly establish a tribe-administered records program with schedules of its own. Where council records touch a federal award, the Uniform Guidance sets a floor of three years from the date the final financial report is submitted, held open longer by an ongoing litigation, claim, or audit until final action is taken. A floor is not a ceiling: governance records, minutes, resolutions, ordinances, land and trust records, are routinely kept far longer or permanently by tribal ordinance.

• The agenda as noticed, kept with the meeting it belongs to rather than in a folder of its own.
• Attendance and quorum, recorded against the requirement your constitution and bylaws actually set.
• Motions and seconds in order, so the path from the floor to the vote reads the way it happened.
• The meeting and its instruments as one object, so a resolution opens with its agenda, its minutes, and its vote already attached.
• Your own retention schedule, built in, so what the council keeps, and for how long, follows the council's ordinance rather than a default somebody else chose.
• The federal floor tracked where it applies, so records tied to an award stay through their 3-year window and stay longer while an audit, claim, or litigation is open.

Questions councils ask

Can a resolution be changed after adoption?

A correction can be adopted, and both the original and the correction stay on the record, each sealed and dated. What nobody can do is quietly replace the adopted text, which is the failure mode this design exists to close.

Does this open our records to the public?

No. What is published is a decision for the tribe under its own law. The system makes the record complete and provable; it does not decide who may read it, and it defaults to nothing being visible without a grant.

When can we turn council on?

Council runs on the same record model as everything else, and it is built with your government from your own procedures. Every deployment is a build on a kernel that already runs, so what gets stood up first is a decision you make with us rather than one a product roadmap makes for you.