Website release
v0.5.76 is prepared for review. Deployment and owner release disposition are not recorded by this package.
Public trust & proof layer
How this work is made
This page shows what the Institute checks before public work is offered, how source dates and authority boundaries are handled, what has actually been tested, what remains open, and how a reader can inspect or correct the record.
Release note: this is the v0.5.76 review candidate, reconciled from the prepared v0.5.75 package. Owner release disposition, deployment, and human validation remain open. The candidate content manifest identifies these files; it does not authorize release or broader use of a held tool.
At a glance
Rigor should be inspectable without becoming a barrier.
The main help routes stay focused on the reader’s next step. This layer carries the deeper questions about evidence, maintenance, testing, and institutional responsibility.
Public help routes
General Navigation and Family Care remain public within their stated boundaries. The responsible Tribe, court, school, clinic, program, provider, or agency still makes the underlying decision.
Source currentness
A website update does not silently renew source verification. Each route keeps its own checked dates, limits, and recheck needs.
Children & Family
The public site provides status and starting options. The complete interactive build remains a bounded institutional test and is not authorized for ordinary operational reliance.
Education Program
Public inspection and feedback are permitted. The program now separates K–12 & Family Education from Adult Education & Workforce Pathways while retaining one shared control system. Consequential reliance remains held while source renewal, human use, accessibility, device/print, maintenance, and exact release evidence remain open.
Institutional proof
The next proof is operational: observed reader use, one correction cycle, one second-operator handoff, contact-form verification, and real accessibility/device evidence where applicable.
Public work
Status travels with the thing being used.
A website release cannot strengthen a guide or tool beyond that object’s own evidence and release boundary.
| Work line | Public function now | Current boundary | Evidence needed next |
|---|---|---|---|
| General Navigation | Find a defensible first contact, call script, and fallback when the reader does not know the office. | Receiving organizations decide availability, eligibility, deadlines, and outcomes. | Observe a reader using the no-office-name route without coaching. |
| Family Care | Public 56-page guide plus short starting pages for older-adult or dependent-family care navigation. | Current guide v2.3.0; contacts on the guide are last recorded as verified July 31, 2026. Confirm changing facts with the responsible source. | Maintenance event, observed reader task, current-source triage, and second-operator handoff. |
| Children & Family | Public status/options doorway; complete interactive prototype retained for bounded institutional testing. | No claim of legal sufficiency, Tribal approval, family usefulness, accessibility, or operational reliance. | Qualified review, synthetic scenarios, accessibility/device review, output checks, source renewal, exact release decision. |
| Education Program | Public inspection and feedback on the K–12/family and adult/workforce pathways and their supporting material. | Schools, districts, programs, Tribes, funders, employers, licensing bodies, and other responsible institutions control consequential decisions in their own roles. | Source renewal; K–12/family and adult-returner scenarios; accessibility/community-reader testing; device/print use; maintenance/correction proof; exact reliance decision. |
| Community Information | Stable doorway to The Long Return’s Pit River Weekly Check-In. | The Long Return owns current reporting, source maintenance, archive state, and corrections for that work. | Observed reader task and a dated maintenance/correction event. |
Sources & currentness
A citation is not enough; the source has to be doing the right job.
Project-level ledgers may use more detailed categories. These are reader-facing source roles for understanding what kind of support a public claim has.
Controlling or official
Law, official Tribal/government action, agency rules, responsible-program information, or other material that actually owns the decision being described.
Direct evidence
Primary records, archival objects, datasets, filings, maps, meeting records, and official reports close to the fact being established.
Field or expert guidance
Native field guidance, professional standards, peer-reviewed scholarship, and established subject-matter methods used within their stated limits.
Context or comparison
Neighboring scholarship, reporting, commentary, analogous systems, and counterpoints that help explain but do not silently become controlling authority.
Discovery lead
Flyers, community posts, search results, inherited links, and informal reports can identify something worth checking. Consequential details are independently verified before promotion.
Institute synthesis
Institute interpretation, frameworks, explanations, or recommendations are labeled as synthesis rather than presented as though they came directly from an external authority.
Currentness rule: the date a webpage changes is not the date every source became current. Source-level checked dates stay visible where they matter, and the Institute should say when a recheck is still open.
Process
Six stages, with deeper controls available when the stakes require them.
The public version is simple. Internal registers, ledgers, audits, and review records carry the more granular work.
1 · DefineExact object, audience, purpose, stakes, authority boundary.
2 · SourceLoad-bearing claims, source jobs, dates, limits, unresolved questions.
3 · BuildPlain form, necessary complexity, protected-context limits, useful exhibits.
4 · TestAudit depth matched to risk; human or qualified review where required.
5 · ReleaseExact object, explicit disposition, constituent holds, rollback.
6 · MaintainFreshness, corrections, proof events, supersession, second-operator capacity.
Proof & open work
What the current record shows—and what it does not.
The PROVE phase is about maintained operation and real use. Static checks can support that work; they do not substitute for it.
Release and boundary control
The controlled predecessor records explicit website and constituent-tool states, rollback, source-date separation, corrections, and non-promotion of held tools.
Static and synthetic checks
Prior candidates include structural, route, focus, text-resize, print, and browser-harness checks. These are engineering evidence, not representative human-use evidence.
Observed reader task
One bounded real-reader task with hesitation, assistance, outcome, defect, and repair still needs to be recorded for the PROVE phase.
Correction cycle
Carry one non-sensitive real correction from report → source check → repair → public correction → follow-up and record what it proves and does not prove.
Second operator
A second person still needs to demonstrate that they can find status, locate sources, recognize stop conditions, make a controlled correction, and restore/rollback.
Live handling & accessibility
Exact-host contact-form receipt/retrieval and applicable real-device, keyboard, screen-reader, zoom, touch, and physical-output checks remain separate operational gates.
Institutional Proof Register
When a real event occurs, the internal record should capture: Date · Domain · Object · Person/role · What happened · Evidence · Defect · Repair · Owner · Follow-up · What this proves · What it does not prove. Only privacy-safe, non-endorsing summaries should reach the public site.
Corrections & inspection
A trustworthy public object needs a repair path.
Material changes should be traceable without exposing private case facts or rewriting the history of what was previously released.
Report a problem
Wrong number, changed rule, broken route, confusing instruction, or other defect.
See corrections
Inspect material public corrections and what changed.
Inspect sources
See source reconciliation, existing-service boundaries, checked dates, and unresolved maintenance work.
Inspect standards
Review the public methods, adoption status, and operational standards used by the Institute.
Inspect technical records
Review deeper release, QA, provenance, and implementation records when available.
See current work
Distinguish what is available, what is in review, and what still needs a partner or authority.