What happened?
Separate what someone reported from what another person directly saw, heard, measured, or preserved.
TL;DR - two ways to ingest the same research
Current Arizona law: disorderly conduct requires the statutory mental state plus a listed act. A crisis report starts inquiry; it is not an adjudicated fact. A citation signature under A.R.S. § 13-3903 is a written promise to appear used for release, not a guilty plea. Disability and crisis-response rules may require meaningful modifications, but neither SMI status nor crisis behavior immunizes independently supported criminal conduct.
Proposed safeguard: before an avoidable irreversible consequence, provide a comprehensible allegation, one-speaker communication, a meaningful context opportunity, access to advocacy or a support person, preservation of independent evidence, and a written reason for rejecting less restrictive alternatives.
A person asking for help can be loud, frightened, repetitive, angry, or hard to follow. Those facts may matter, but they are not a shortcut to criminal intent. The system should slow down enough to ask: What happened? What does the law actually require? What help was requested? What safer option was available? Who independently verified the story?
The goal is not to excuse harm or attack responders. It is to keep the human being in the conversation before the system creates a harm that therapy, money, or an apology may not fully reverse.
Boundary: this artifact does not decide guilt, probable cause, diagnosis, dangerousness, competency, civil commitment, or damages. Its scores are audit signals and mathematical invariants, not judicial thresholds.
A child-first doorway
Begin with the questions a child would ask
Not childish. Unarmored. Curious before certain. The page uses simple questions to keep power from closing the story too early.
Who was heard?
Keep the person, witnesses, advocates, clinicians, and independent evidence inside the record.
What is still unknown?
Say HOLD when a required element, source lane, accessibility need, or timeline fact is missing.
What is the gentlest safe next step?
As consequences become harder to reverse, the minimum protection floor must become stronger, never weaker.
The human-first isosceles triangle
Insight
Analyzes evidence, memory, patterns, law, uncertainty, and risk. It explains; it does not rule.
Meaning
Preserves the person’s language, values, emotional reality, faith, culture, and relational fit. It humanizes and tests fit.
Action
Coordinates resources, timing, accountability, handoffs, continuity, and implementation. It carries forward but cannot absorb the other roles.
Human knowledge verification matrix
The user-supplied discipline list was treated as a seed prompt, not as verified authority. This expanded matrix looks for missing perspectives without allowing any discipline to erase another.
| Knowledge field | Question it contributes | Evidence form | Failure when absent |
|---|---|---|---|
| Law and governance | What authority, element, procedure, right, remedy, and review applies? | Statutes, cases, regulations, official policy, audit records | Power becomes unbounded or merely procedural |
| Clinical and public health | What crisis, disability, treatment need, risk, and least restrictive response exists? | Assessment, care plan, outcomes, service standards | Distress becomes misconduct by default |
| Natural sciences | What observable mechanisms, physiological risks, and measurable outcomes exist? | Replicable observation, measurement, uncertainty | Claims lose physical and causal constraints |
| Social sciences | How do institutions, incentives, stigma, race, class, disability, and group behavior affect outcomes? | Qualitative and quantitative studies | System effects are misread as individual defects |
| Humanities and history | What meaning, language, culture, ethics, memory, and historical path shape the event? | Textual interpretation, narrative, archival record | The person and time period are flattened |
| Formal sciences | Are the logic, scales, statistics, code, and inference rules valid? | Proofs, tests, schemas, simulations | Numbers become decorative authority |
| Lived and community knowledge | What did the person experience, request, understand, and lose? | First-person account, witness account, participatory review | The subject is removed from their own record |
| Design and accessibility | Can people with different bodies, senses, cognition, languages, and technologies actually use the process? | Human testing, WCAG/ARIA conformance, assistive-technology checks | A right exists only for those who can navigate it |
History runbook: from custody toward rights, community, and crisis access
1946-1949 - federal research infrastructure
The National Mental Health Act and creation of NIMH helped establish a durable federal research and public-health role. This did not itself solve coercion or access.
1960s-1980s - community transition with uneven support
Institutional populations declined while community capacity, housing, continuity, and crisis services often developed unevenly. The lesson is not “institution versus community” alone; it is whether real support follows the person.
1990 onward - disability civil rights and integration
The ADA strengthened equal participation and reasonable-modification duties. Later integration doctrine challenged unnecessary institutionalization.
2000s-2020s - crisis intervention, alternative response, and 988
Communities increasingly tested crisis-trained officers, co-response, mobile crisis, and non-police models. Evidence is promising in some settings but implementation, availability, and accountability remain decisive.
2025-2026 - implementation and digital access
Local systems such as Phoenix expanded behavioral-health dispatch options. Federal accessibility deadlines were extended, while covered systems still face legal and practical duties to build accessible services.
Evidence-gated law, crisis, and human-impact matrix
Source gate
Legal support
Crisis priority
Human impact
Required safeguards
Safeguard deficit
Why this math is designed this way
Weakest-link gate: the legal support signal uses the minimum of conduct, mental state, and peace impact. A missing legal element cannot be compensated by more officers, louder institutional confidence, or repeated copies of one allegation.
Monotone protection: required safeguards cannot decrease when liberty, status, bodily, or life consequences increase.
Typed truth: legal rules, scientific associations, lived impact, and proposals remain in separate lanes. The compiler exposes conflict instead of averaging it away.
When freedom crosses into loss
| Transition | What changes | Required discovery before avoidable escalation | Potential payment by the human |
|---|---|---|---|
| Request → command | A voluntary exchange may become a show of authority. | State whether compliance is required, who has authority, and the immediate safety reason. | Agency, voice, bodily autonomy. |
| Command → detention | Freedom to leave is restricted. | Record specific facts and timestamp; separate dispatch allegation from officer observation. | Time, fear, public stigma, crisis escalation. |
| Detention → citation | A criminal process and appearance duty begin. | Identify statute/subsection, conduct, mental state, allegation source, and available contrary evidence; explain signature. | Money, work time, records, treatment trust, status. |
| Citation → booking/prosecution | Custody and formal adversarial process intensify. | Proportionality, accommodation, counsel access, evidence preservation, clinical continuity. | Liberty, housing, employment, health, family connection. |
| Force / exclusion → bodily or life loss | Consequences may be irreversible. | Imminent-threat facts, least harmful reversible path, supervisor/clinical coordination when feasible, immediate independent review. | Bodily integrity, life, community trust, collective trauma. |
Protection rule: the more irreversible the consequence, the stronger the minimum safeguard floor. A majority vote, diagnosis, staff preference, or source volume cannot lower that floor.
Third matrix base: system cost, human loss, and the reverse ratio
Money can compare budgets and documented losses. It cannot price dignity, love, acceptance, freedom, bodily integrity, or life. Those remain a separate non-monetized impact index.
Verified public investment examples
| Place | Year | Amount | Type | Meaning | Confidence boundary |
|---|---|---|---|---|---|
| Phoenix, Arizona | 2021 | $15,000,000.00 | approved public program investment | FY2021-22 expansion of the Community Assistance Program, including nine Behavioral Health units and growth of Crisis Response units from five to ten. | official-single-source; factual amount, not a three-source causal finding |
| Sangamon County, Illinois | 2026 | $14,000,000.00 | expected annual public revenue, rounded minimum | County states the voter-approved 0.5% sales tax is expected to generate more than $14 million annually for the Mental Health Board. | official projection; not realized expenditure or payout |
Settlement and judgment payout registry
HOLD: no payout amount is published in this release because none was added with a preserved case document plus two independent matching provenance origins. The engine and import schema are present; unsupported currency is intentionally not turned into apparent fact.
Cases and implemented systems that shape future analysis
In re Julio L.
Arizona authority requiring careful separation between institutional misconduct and statutory “seriously disruptive” conduct.
Primary case documentArizona disorderly conduct and citation statutes
Define the mental-state-and-act gate and the notice-to-appear release mechanism.
§ 13-2904 · § 13-3903DOJ Phoenix findings
Federal findings include behavioral-health dispatch and modification concerns, protected speech, and citation/arrest practices. Findings are not a judgment about this user-described encounter.
DOJ case pageDOJ Sangamon agreement
Shows a post-tragedy framework using policy, training, mobile crisis, and data reporting rather than treating accountability and care as opposites.
DOJ case pagePhoenix behavioral-health dispatch
Demonstrates that call intake can offer police, fire, or behavioral-health pathways and still triage safety facts.
City implementation pageAlternative-response research
Provides population-level evidence to test assumptions. It cannot decide an individual case without incident evidence.
STAR evaluationResearch expansion tooling
Generated research sequence
Required three-lane intake
- Research: What independent empirical, historical, technical, or first-person evidence tests the claim?
- Enforcement: What exact law, element, authority, command, and timestamp supports the exercise of control?
- Governance: What policy, right, accessibility duty, grievance path, oversight record, and less restrictive alternative applies?
Advanced technology and API Integration Law
PROPOSED COVENANT - NOT ENACTED LAW
The API Integration Law is a technical governance rule for this project. It makes the static human-readable document primary and all automation subordinate.
1. Static human access
The full runbook MUST remain readable without JavaScript, account, database, remote model, API, or network connection.
2. Public fail-open, private fail-closed
Public explanatory content MAY use a local deterministic fallback. Private or restricted data MUST stop rather than silently route to another provider.
3. Governance envelope
Every API action MUST declare data class, purpose, authority, retention, accessibility profile, human override, provenance, and trace ID.
4. No automated rights finding
No API score may independently create criminal intent, dangerousness, diagnosis, confinement, ticketing, or life-affecting status.
5. Replaceable adapters
Interfaces SHOULD use open standards and capability negotiation so one vendor or broken API cannot own access to the framework.
6. Cryptographic transparency
Canonical records, hashes, signatures, provenance, and public release notes make changes detectable; cryptography proves integrity, not truth.
Standards and legal status map
| Layer | Baseline | Status in July 2026 | Project rule |
|---|---|---|---|
| Accessibility design | WCAG 2.2 AA; semantic HTML; WAI-ARIA only when native HTML is insufficient | WCAG 2.2 is a W3C Recommendation; covered U.S. rules may specify WCAG 2.1 AA | Design to 2.2; map the applicable legal floor separately |
| Public-sector deadlines | DOJ Title II web/mobile rule | April 26, 2027 for 50,000+ population; April 26, 2028 for smaller entities and special districts under the 2026 IFR | Do not wait for deadline to make this artifact usable |
| HHS-funded accessibility | Section 504 web/mobile requirements | May 11, 2027 for recipients with 15+ employees; May 10, 2028 for smaller recipients under the 2026 IFR | Public health adapters require accessible human alternatives |
| API description | OpenAPI 3.2.0 | Published specification | Versioned, discoverable, replaceable interfaces |
| Payload validation | JSON Schema 2020-12 | Published draft family | Governance envelope validates before processing |
| Error exchange | RFC 9457 Problem Details | IETF Standards Track | Errors remain human-readable and machine-readable |
| Integrity | RFC 8785 concepts, SHA-256, Ed25519 signatures | RFC 8785 is Informational; cryptographic algorithms require agility | Hash-addressed releases; no claim that hash equals truth |
| Trace and provenance | W3C Trace Context and PROV-O | W3C Recommendations | Every matrix transition can be traced to its source and prior state |
| Health interoperability | FHIR R5 adapter | Published HL7 release with mixed normative/maturity levels | Optional, authorized, private by default, never needed to read the runbook |
| Secure development | NIST CSF 2.0 and SSDF 1.1 | Current final baselines; later drafts are not treated as final | Threat modeling, dependency minimization, verification, and redacted diagnostics |
Governance envelope validator
No validation run.
Universal browser API relay and bug flow
The relay tries standards-based fetch, then XMLHttpRequest only when needed, and finally a local deterministic fallback for public data. Private/restricted requests never fail over to an unapproved endpoint.
Relay idle. No network request has been made.
Proof boundaries, cryptographic chain, and release verification
Mathematical proof
Tests prove model invariants: missing mandatory elements stay missing; duplicate origins count once; votes cannot remove the rights floor; protections are monotone; tampering breaks the hash chain.
Scientific support
Studies can estimate population outcomes and uncertainty. They cannot prove what one person intended or what occurred in one encounter.
Legal authority
Statutes, regulations, and controlling decisions define legal rules. The matrix does not alter burdens of proof or replace counsel and courts.
Cryptographic integrity
Hashes and signatures show whether release bytes changed. They do not prove that every source is correct, complete, or fairly interpreted.
No chain records yet.
Public deployment, locked release, and open improvement
Immutable release
Each published version has a manifest, hashes, detached signatures, timestamp, source snapshot, and changelog. A release is never silently overwritten.
Open fork
Source is licensed for reuse and improvement. A derivative must disclose changes and must not impersonate the signed canonical release.
Seed continuity
Living, Freedom, Acceptance, Love, dignity, open inquiry, and repair are the project’s declared invariants. The covenant is a governance statement, not an attempt to own universal human values.
Private key control
The package ships only a public verification key. A steward creates and protects their own release key locally; no private key is embedded in HTML or ZIP.
Static publication contract
- Canonical explanation is plain HTML.
- JavaScript enhances but never unlocks reading.
- No production database or origin is needed for the baseline.
- Optional APIs are isolated under
/api/*. - Security headers, redirects, sitemap, manifest, OpenAPI file, schemas, tests, and verification scripts are included in the source package.
Claim verification and source map
A claim receives a local PASS only when it has at least three independent provenance origins across Research, Enforcement, and Governance, plus primary legal authority for a legal claim. This is a conservative project rule, not a court’s evidence rule. A controlling statute can legally matter even while the local triangulation state remains HOLD.
| Claim | Statement | Provenance | Local state |
|---|---|---|---|
| C1 — Arizona disorderly conduct is element-gated | A.R.S. § 13-2904 requires intent to disturb the peace or knowledge of doing so, plus one listed act. Complaint volume and officer count cannot replace a missing element. | 3 origins: enforcement, governance, research | PASStriangulated |
| C2 — Offense, emotion, or rule-breaking is not automatically serious disruption | Arizona authority distinguishes ordinary defiance or offensive expression from the statutory conduct theory; the exact subsection, peace-holder, conduct, and mental state must be identified. | 4 origins: enforcement, governance, research | PASStriangulated |
| C3 — A citation signature is ordinarily a promise to appear | Arizona's notice-to-appear mechanism permits release after a misdemeanor arrest through a written promise to appear; it is not itself a guilty plea. | 3 origins: enforcement, governance, research | PASStriangulated |
| C4 — SMI status is a service-and-rights framework | Arizona's SMI framework provides enhanced services, advocacy, grievance, and investigation pathways; it does not itself establish criminality or dangerousness. | 3 origins: enforcement, governance, research | PASStriangulated |
| C5 — Crisis response should preserve contact, stabilization, care coordination, and diversion | Arizona and federal crisis frameworks emphasize person-centered crisis response and behavioral-health alternatives when the safety facts permit. | 3 origins: enforcement, governance, research | PASStriangulated |
| C6 — Disability law can require reasonable modifications in emergency response | Title II and federal guidance can require reasonable modifications and effective communication, subject to genuine safety and fundamental-alteration limits. | 3 origins: enforcement, governance | HOLDmissing research lane |
| C7 — Alternative and crisis-trained models can change arrest and referral outcomes | Peer-reviewed studies support plausible reductions in arrest or increases in referral in some settings; they do not prove a fact about an individual encounter. | 3 origins: enforcement, governance, research | PASStriangulated |
| C8 — Freedom loss expands into status, care, financial, bodily, and life consequences | Citation, arrest, prosecution, records, and treatment disruption can create escalating direct and collateral burdens; each consequence requires separate evidence. | 4 origins: enforcement, governance, research | PASStriangulated |
| C9 — Mental-health policy has moved toward rights, integration, and crisis access | The historical record includes federal research, disability civil rights, community integration, and the modern crisis continuum, while implementation gaps remain. | 3 origins: enforcement, governance, research | PASStriangulated |
| C10 — Digital accessibility has a legal floor and a forward design target | Applicable U.S. rules use WCAG 2.1 AA for covered public and HHS-funded digital services, while WCAG 2.2 is the current W3C design target used by this artifact. | 4 origins: enforcement, governance, research | PASStriangulated |
| C11 — APIs should be described, validated, and fail with interoperable problem details | The package uses OpenAPI 3.2, JSON Schema 2020-12, and RFC 9457 as its public interface contract baseline. | 3 origins: enforcement, governance, research | PASStriangulated |
| C12 — Matrix records require deterministic provenance and tamper evidence | Canonical JSON, trace context, and provenance records support repeatable hashing and an auditable chain; they do not certify the truth of the underlying assertion. | 3 origins: enforcement, governance, research | PASStriangulated |
| C13 — Security, privacy, and human override are release gates | The technical architecture uses secure-development, privacy-minimization, explicit purpose, redacted diagnostics, and human review as mandatory gates. | 3 origins: enforcement, governance, research | PASStriangulated |
| C14 — Health interoperability is optional and private by default | FHIR R5 can support authorized health-data exchange, but the public artifact contains no PHI and never makes access to the human-readable runbook depend on an API. | 3 origins: enforcement, governance, research | PASStriangulated |
| C15 — Alternative dispatch is an implemented governance option, not only a theory | Phoenix has expanded behavioral-health response capacity and added a behavioral-health choice in call intake, while federal findings show why implementation quality and accountability remain material. | 3 origins: enforcement, governance, research | PASStriangulated |
| C16 — Cost comparison must preserve both system expense and human loss | The model stores official investment figures and CPI adjustments separately from user-entered human costs; dignity, love, freedom, bodily integrity, and life are never reduced to dollars. | 3 origins: governance, research | HOLDmissing enforcement lane |
| C17 — API Integration Law is a proposed open technical covenant | The proposed covenant requires static access, accessible interfaces, typed provenance, private-data fail-closed behavior, public-content local fallback, and replaceable standards-based adapters. | 4 origins: governance, research | HOLDmissing enforcement lane |
| C18 — Human-first verification keeps dialogue available before irreversible exclusion | The proposed safeguard floor gives the person, an advocate, and independent evidence a route into the record before avoidable ticketing, confinement, status loss, or bodily/life harm. | 2 origins: governance | HOLDfewer than 3 independent origins; missing research lane; missing enforcement lane |
Source registry
Showing all 42 sources.
AZ-DCA.R.S. § 13-2904 - Disorderly conductOrigin: azleg-13-2904 · authority: primary-law
enforcementAZ-ARRESTA.R.S. § 13-3883 - Arrest without warrantOrigin: azleg-13-3883 · authority: primary-law
enforcementAZ-CITEA.R.S. § 13-3903 - Notice to appear and complaintOrigin: azleg-13-3903 · authority: primary-law
enforcementAZ-FORMArizona Traffic Ticket and Complaint - standard formOrigin: azcourts-citation-form · authority: official-form
governanceJULIOIn re Julio L., 197 Ariz. 1 (2000)Origin: azsc-julio · authority: controlling-case
researchAZ-2026Arizona Judicial College 2026 - lower-court appeal guidanceOrigin: azcourts-2026-guide · authority: official-judicial-guidance
governancePINOState v. Pino, Arizona Court of Appeals (2014)Origin: azcoa-pino · authority: appellate-case
researchSMIAHCCCS - Serious Mental Illness designationOrigin: ahcccs-smi · authority: official-program-rule
enforcementOHRAHCCCS Office of Human RightsOrigin: ahcccs-ohr · authority: official-advocacy
governanceGRIEVANCEAHCCCS - SMI grievance and investigation processOrigin: ahcccs-grievance · authority: official-rights-process
researchAMPM590AHCCCS AMPM 590 - Behavioral Health Crisis Services and Care CoordinationOrigin: ahcccs-ampm590 · authority: official-policy
enforcementDOJ-HHSDOJ and HHS - Emergency responses to behavioral-health or other disabilitiesOrigin: doj-hhs-crisis-guidance · authority: federal-rights-guidance
governanceADA-T2DOJ - ADA Title II regulationsOrigin: ada-title-ii · authority: federal-regulation
enforcementADA-LEDOJ - Commonly asked questions about law enforcement and the ADAOrigin: ada-law-enforcement · authority: official-guidance
governanceSAMHSA25SAMHSA - National Behavioral Health Crisis Care GuidanceOrigin: samhsa-crisis-2025 · authority: federal-clinical-guidance
research988988 Lifeline - national crisis serviceOrigin: 988-service · authority: official-service
governanceNIMH-HISTNIMH historyOrigin: nimh-history · authority: federal-history
researchADA-HISTNational Archives - Americans with Disabilities Act historyOrigin: archives-ada-history · authority: federal-history
enforcementSTARDenver STAR alternative response evaluationOrigin: star-study · authority: peer-reviewed
researchCIT-COMPTONCrisis Intervention Team outcomes studyOrigin: cit-compton · authority: peer-reviewed
enforcementCIT-KHALSACIT systematic reviewOrigin: cit-khalsa · authority: peer-reviewed
governanceAZ-COURT-STEPSArizona Courts - steps in a criminal caseOrigin: azcourt-criminal-steps · authority: official-court-guide
researchAZ-SEALArizona Courts - sealing recordsOrigin: azcourt-sealing · authority: official-court-guide
governanceWCAG22W3C - Web Content Accessibility Guidelines 2.2Origin: w3c-wcag22 · authority: final-standard
researchDOJ-WEB-2026DOJ - Title II web/mobile rule and 2026 extended deadlinesOrigin: doj-title2-web-2026 · authority: federal-regulation-guidance
enforcementHHS-504-2026HHS OCR - Section 504 web/mobile deadline extensionOrigin: hhs-504-web-2026 · authority: federal-regulation-guidance
governanceOPENAPI32OpenAPI Specification 3.2.0Origin: openapi-3.2 · authority: final-standard
researchJSONSCHEMAJSON Schema Draft 2020-12Origin: json-schema-2020-12 · authority: final-standard
enforcementRFC9457RFC 9457 - Problem Details for HTTP APIsOrigin: rfc9457 · authority: standards-track
governanceRFC8785RFC 8785 - JSON Canonicalization SchemeOrigin: rfc8785 · authority: informational-standard
researchTRACEW3C Trace ContextOrigin: w3c-trace-context · authority: final-standard
enforcementPROVOW3C PROV-O provenance ontologyOrigin: w3c-prov-o · authority: final-standard
governanceNIST-CSFNIST Cybersecurity Framework 2.0Origin: nist-csf-2 · authority: federal-standard
governanceNIST-SSDFNIST SP 800-218 Secure Software Development Framework 1.1Origin: nist-ssdf-1.1 · authority: federal-standard
enforcementW3C-PRIVW3C Privacy PrinciplesOrigin: w3c-privacy-principles · authority: w3c-statement
researchFHIR-R5HL7 FHIR Release 5Origin: hl7-fhir-r5 · authority: health-interoperability-standard
researchPHX-CAPCity of Phoenix - Crisis Response Program and $15M expansionOrigin: phoenix-cap-investment · authority: official-program-data
researchPHX-911City of Phoenix - behavioral-health option in 911 intakeOrigin: phoenix-911-behavioral · authority: official-program-update
enforcementDOJ-PHXDOJ - Phoenix Police Department investigation findingsOrigin: doj-phoenix-findings · authority: federal-findings
governanceBLS-CPIBLS CPI-U All Items dataOrigin: bls-cpi-u · authority: federal-statistical-data
researchSANGAMONSangamon County Mental Health Board - 2026 public investmentOrigin: sangamon-mental-health-board · authority: official-program-data
governanceW3C-ETHICSW3C Ethical Web PrinciplesOrigin: w3c-ethical-web · authority: w3c-statement
governance