MathSphere Nexus
A lockable, unlockable, rollback-capable, externally anchorable integrity ledger for project state — the integrity layer version control does not provide, built to sit on top of version control itself.
MathSphere Nexus Arbiter is a project-state integrity engine. It seals the state of files and directory trees, records their cryptographic fingerprints in an append-only, hash-chained ledger, and provides controlled mechanisms to verify, update, lock, and restore that state over time — restore today covers individual records; whole-tree restore is first on the build list in the honesty audit (docs/records/HONESTY_AUDIT_2026-11-04.md).
Version control tracks change, but its history is mutable. Backups restore content but provide no tamper-evident proof. Checksums detect corruption but offer no recovery path. MathSphere Nexus Arbiter is the seal, lock, and audit layer that sits above version control and alongside backup.
| Capability | Guarantee |
|---|---|
| Seal | SHA-256 fingerprints of files or trees, with monotonic version numbers |
| Verify | Constant-time comparison, plus per-file diff of what changed |
| Update | Optimistic concurrency — caller presents the previous hash |
| Lock | Record-level seal; a locked record rejects update and rollback |
| Unlock | Present the exact one-time token issued at locking — only the token's hash is ever stored, so the key itself is kept nowhere — verified against that hash, and the unlock is written to the audit log. A lost token means the lock is permanent, by design |
| Rollback | Restore a record from a content-addressed snapshot, verified before restore (whole-tree restore: build list, audit §2) |
| Audit | Append-only, hash-chained log, optionally anchored externally via OpenTimestamps (mechanism built; first live proof: build list, audit §4) |
update, not a rewrite.Requires Node.js 18+.
git clone https://github.com/rewardsbycode-eng/MathSphere-Nexus-Arbiter.git
cd MathSphere-Nexus-Arbiter
chmod +x bin/*
guard-add --project demo report.pdf ./report.pdf
guard-verify --project demo report.pdf ./report.pdf
guard-snapshot-tree --project alpha alpha@v1.4.2 .
guard-verify-tree --project alpha alpha@v1.4.2 .
guard-lock --project alpha alpha@v1.4.2 <manifest_hash>
| Document | Purpose |
|---|---|
| docs/MathSphere-Nexus-Arbiter.md | The professional introduction / pitch |
| docs/threat-model.md | What MathSphere Nexus Arbiter protects against, and what it does not |
| docs/design.md | Invariants, data model, hash chain, why no Fix/Correct |
| docs/operations.md | Backup, key rotation, GC cadence, anchor cadence |
| docs/record-format.md | Schema, schema_version, migration rules |
| docs/rollback-semantics.md | Append-not-rewrite; forward-history survival |
| docs/lock-semantics.md | Token loss = permanent lock; this is by design |
| docs/compatibility.md | Git, VAULT, backup tools — what composes |
| docs/faq.md | Common questions |
| MATHSPHERE-NEXUS-ARBITER-READINESS-CHECKLIST.md | Definition of "professional" and build sequence |
Documentation note: every row in this table is a document that exists in this repository (verified against the tree on 2026-11-04; see the honesty audit (docs/records/HONESTY_AUDIT_2026-11-04.md), §6).
Pre-1.0. Data model and invariants are stable; CLI surface may change.