MathGov is a governance framework for people, institutions, and intelligent systems. RippleLogic is the decision engine inside it: a rights-first, auditable system that defines who is affected, protects what must be protected, models downstream ripple effects, bounds tail risk, and records reasoning so every decision can be reviewed, challenged, and improved.
Together they form a disciplined method for ethical governance and decision-making. The framework defines the principles and structure; the engine applies them to real choices in a way that is legible, testable, and operational.
UBE begins with interdependence. It asks who is affected, what obligations exist across that union, and which rights and protections must not be traded away. It provides the ethical floor beneath all later optimization.
Ripple Alignment looks beyond the first-order result. It evaluates whether a choice remains coherent as consequences propagate through time, institutions, incentives, downstream systems, and future stakeholders.
RippleLogic turns principles into process. It scopes the union, sets rights floors, models ripple effects, bounds tail risk, compares options, and produces auditable decision records that can be reviewed and improved.
The implementation layer makes claims explicit. It standardizes scope declarations, assumptions, evidence, decision notes, manifests, and conformance levels so adoption can be tracked rather than merely asserted.
Every decision passes through five levels in strict order. Earlier levels cannot be overridden by later scoring. Options that violate rights or create catastrophic exposure are removed before any welfare optimization begins. This is what makes the system trustworthy: constraints come first.
Use this before any decision: a message to a friend, a business choice, a policy proposal, an AI deployment. The cascade keeps you honest.
Your choices ripple outward through nested scopes of connection. RippleLogic tracks impact across all seven union scopes and optimizes under constraints. What helps you but harms your community is not optimization, it is extraction.
A two-minute decision practice you can run on anything, from sending a message to deploying a system. Each cycle builds clearer judgment. You do not need to be perfect. You need to be willing to see, willing to check, willing to learn.
Three ways to enter: learn the framework, use it right now, or dive into the research. There is no wrong door. The only mistake is not walking through one.
You should not trust a governance system because it sounds good. You should trust it to the degree that it makes claims explicit, protects against abuse, preserves evidence, and remains open to correction.
The framework is designed so efficiency or strategic gain does not automatically override protected interests. Rights floors are handled as constraints, not as optional preferences that can be traded away.
Scope, assumptions, evidence, and rationale are captured in decision records. That makes disagreement actionable: critics can point to specific premises, methods, or omissions rather than arguing in the abstract.
Visitors can see what is operative, what is exploratory, and what is historical. That reduces confusion, prevents accidental reliance on outdated material, and increases institutional credibility.
Versioned updates, manifests, and archived superseded releases make change visible. Improvement is treated as accountable revision, not quiet replacement.
The current release line includes the governing canon, the sentience/status interface, the deployment model, the implementation wrapper, the aligned workbook companion, and the release-integrity pack. The package is version-frozen, SHA-256 verified, and manifest-linked.
The anchor specification for the full system. Defines the governing cascade, equations, admissibility gates, PCC requirements, SGP binding, PLSS/FLGG local-use architecture, audit flags, and release-line interpretation rules for all companion artifacts.
A conservative companion protocol for questions of moral status and protective duty across biological and artificial substrates. Its role is to reduce negligent exclusion in uncertain cases and make protection logic explicit and falsifiable.
The operational behavior layer for deployment. Covers permissions, refusals, escalation, governance controls, security boundaries, evaluation harnesses, incident handling, and publishable Agent Card documentation.
The portable alignment contract and assurance wrapper for implementations and deployments. It structures declared scope, assumptions, evidence, decision notes, release manifests, and conformance claims so wrapped deployments stay legible and reviewable.
The aligned workbook companion for replay, disclosure, training, and worked examples. It is publication-clean and useful for runs, but it is not the repository-level validator or schema surface.
Use the package when you want the full public release bundle: the core ZIP, ZIP SHA-256, SHA256SUMS, release manifest, and ProofPack integrity documentation. This is the cleanest entry point for GitHub, website, and public verification.
Status guide: Canonical = active operative spec. Stable companion = required support layer. Operational = deployable behavior model. Implementation standard = adoption and conformance wrapper. The workbook is an aligned worked-run companion. The freeze package is the public verification bundle.
The intellectual foundations and ongoing research behind the operative system. These papers are valuable, but they are presented with disciplined status labels so readers can distinguish active canon from concept or working papers.
The moral architecture underlying MathGov. Examines interdependence, protected unions, obligations across stakeholders, and the conditions under which shared flourishing can be pursued without collapsing individual dignity into aggregate utility.
Argues that alignment cannot be treated as a hidden objective function alone. Durable alignment requires visible obligations, permissions, veto conditions, and accountability structures across the parties affected by the system.
Connects interdependence, distributed effects, and ethical propagation. Explores the mathematical scaffolding behind union calculus and how it informs the structure of multi-scale ethical reasoning within MathGov.
Every canonical release is version-frozen, hash-verified, and publicly auditable. No hidden binaries. No opaque execution layers. You can independently verify the integrity of every artifact in the system.
Download any release asset, compute the SHA-256 hash locally, and confirm it matches the published hash on the GitHub release page. Full lineage and historical versions are preserved in the transparent archive.
For public download and verification, the homepage can expose the package ZIP, ZIP hash, SHA256SUMS, release manifest, and ProofPack integrity docs directly.
The complete v9.0 public bundle for the core synced document/workbook set.
Use this file to verify that the downloaded ZIP matches the published release artifact.
The file-level SHA-256 record for the core release assets inside the published bundle.
JSON and YAML manifest files bind the filenames, versions, and hashes for the public release line.
A document-form release manifest and SHA-256 record for public-facing reference and archive use.
The release-integrity companion document for the public ProofPack line.
