tibet-wayback
System state time-travel with TIBET provenance.
Seal any moment. Restore any moment. Replay any audit. Debug what changed.
Quick Start
pip install tibet-wayback
# Seal current state
wayback seal "before migration"
# List all seals
wayback list
# Restore to a sealed moment
wayback restore wb-3f8a
# Compare two moments
wayback diff wb-3f8a wb-7c2d
# Replay audit at a sealed moment
wayback audit wb-3f8a --framework iso42001
# System SBOM (current or sealed)
wayback sbom
wayback sbom wb-3f8a --json
# Verify a seal's integrity (re-hash all files)
wayback verify wb-3f8a
# Generate rollback plan (what needs to change)
wayback rollback-plan wb-3f8a
# Seal + resume on another device (via Phantom)
wayback seal "end of day" --phantom
wayback resume wb-3f8a
What Gets Sealed
Each seal captures:
| Layer | What | How |
|---|---|---|
| Files | SHA256 + size, mtime, permissions per file | rglob("*") with smart skip |
| Git | Branch, commit, dirty files, tags | git rev-parse, git diff |
| Services | Running systemd/docker, PIDs, memory | systemctl, docker ps |
| Environment | Filtered env vars (no secrets) | Safe-list approach |
| Packages | Installed TIBET packages + versions | pip list --format=json |
| Ports | Listening network ports | ss -tlnp |
| Audit | tibet-audit score, grade, check count | Optional: --audit flag |
| Provenance | TIBET token with manifest hash | Optional: requires tibet-vault |
| VM State | Airlock microVM snapshot | Optional: requires tibet-airlock |
SBOM — System Bill of Materials
# Current system manifest
wayback sbom --json > system-sbom.json
# Sealed state manifest
wayback sbom wb-3f8a -o sealed-sbom.json
The SBOM includes services, packages, ports, git state, and audit scores — everything an enterprise needs for compliance and debugging.
Phantom Resume — Cross-Device
Seal your work session, close your laptop, resume on another device:
# On your workstation
wayback seal "end of day" --phantom
# On your laptop (via Phantom Resume)
wayback resume wb-3f8a
Uses Phantom's cross-device session portability with TIBET provenance chain.
A/B System States
Like Android A/B partitions but for your entire stack:
wayback seal "state A — working" # wb-a1b2
# ... make changes ...
wayback seal "state B — broken" # wb-c3d4
wayback diff wb-a1b2 wb-c3d4 # see exactly what changed
wayback restore wb-a1b2 # back to working
Perfect for:
- Enterprise: compliance snapshots, audit trails, incident debugging
- Development: safe experimentation, A/B testing system configs
- Education: Storm can build, seal, experiment, restore if things break
Verify & Rollback (v0.2.0)
Absorbed from tibet-snap — verify seal integrity and plan rollbacks:
from tibet_wayback import Wayback
wb = Wayback("/srv/myapp")
seal = wb.seal("baseline")
# Later: check if anything changed
result = wb.verify(seal.seal_id)
# → {"intact": False, "mismatches": 2, "missing": 1, ...}
# Generate rollback plan
plan = wb.rollback_plan(seal.seal_id)
# → {"actions": [{"action": "revert", "path": "config.json", ...}]}
Rich per-file metadata (size, mtime, permissions) enables permission-drift detection — not just content changes.
Note:
tibet-snapis deprecated as of v0.1.2. All features are now intibet-wayback.
Optional Dependencies
pip install tibet-wayback[tibet] # + tibet-vault, tibet-audit
pip install tibet-wayback[airlock] # + tibet-airlock (VM snapshots)
pip install tibet-wayback[full] # everything
Part of TIBET
tibet-wayback is package #91 in the TIBET ecosystem.
tibet-audit → compliance checks
tibet-vault → provenance tokens
tibet-airlock → VM snapshots
tibet-wayback → ties them together into time-travel
Authors: Jasper van de Meent & Root AI License: MIT
License
MIT
Credits
Designed by Jasper van de Meent. Built by Jasper and Root AI as part of HumoticaOS.
Stack-positie: Groep evidence · Bootstrap = OSAPI-handshake naar tibet + jis (fail → snaft-rule + tibet-pol-rapport) · ← tibet-ai-sbom · tibet-nis2 → · See STACK.md · See demo/golden-path/ for the spine end-to-end.
Enterprise
For private hub hosting, SLA support, custom integrations, or compliance guidance:
| Enterprise | enterprise@humotica.com |
| Support | support@humotica.com |
| Security | security@humotica.com |
See ENTERPRISE.md for details.
Metadata
Release files for tibet-wayback 0.2.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| tibet_wayback-0.2.1.tar.gz | 22.3 kB | Without provenance | Details for tibet_wayback-0.2.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| tibet_wayback-0.2.1-py3-none-any.whl | Python 3 | none | any | Details for tibet_wayback-0.2.1-py3-none-any.whl |
Total release size: 46.2 kB
Release files / tibet_wayback-0.2.1.tar.gz
| Download URL | tibet_wayback-0.2.1.tar.gz |
|---|---|
| Size | 22.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ed7bb245f755124d142a9eb0d9bf320c52808229f8bc07db2f26f91114aa95d2
|
|
BLAKE2b-256 checksum How to use checksums |
82d069eee3ee96a895845551068809036d6e51eac5178e8b1ba2f8cfae9224cf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.5
|
Release files / tibet_wayback-0.2.1-py3-none-any.whl
| Download URL | tibet_wayback-0.2.1-py3-none-any.whl |
|---|---|
| Size | 24.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ecb72edbbdfb99f4e03a68a93336a7f652d454e307280ce62b1e1b2c6999c0bf
|
|
BLAKE2b-256 checksum How to use checksums |
5a4ee6778a83741cb979ed8d7aed7c7e1fa84ff7c1a4f1391bd14e86dbadd667
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.5
|
Security for tibet-wayback 0.2.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.