verisimiser augments any existing database with VeriSimiser’s fixed
eight-concern Octad (ADR-0004/ADR-0014), drawing on capabilities from
VeriSimDB’s eight-modality Octad upstream. It reads the target
database schema and a verisimiser.toml manifest, then generates a
sidecar overlay, query interceptors, drift detection, provenance chains,
and temporal version history — without requiring schema migrations.
verisimiser is priority #3 in the -iser family and is the primary path
for adding VeriSimDB capabilities to legacy PostgreSQL, SQLite, or
MongoDB deployments.
verisimiser/ ├── src/ │ ├── main.rs # CLI entry point (clap): init, generate, start, drift, provenance, history, status, octad │ ├── lib.rs # Library API │ ├── manifest/mod.rs # verisimiser.toml parser │ ├── codegen/mod.rs # Sidecar overlay and query interceptor generation │ ├── intercept/ # Query interception layer │ ├── tier1/ # Tier-1 concern modules (concern Octad) │ ├── tier2/ # Tier-2 overlay modality stubs (six, not an octad) │ └── abi/ # Idris2 ABI bridge stubs ├── examples/ # Worked examples ├── verification/ # Proof harnesses ├── container/ # Stapeln container ecosystem └── .machine_readable/ # A2ML metadata
verisimiser.toml manifest
│
┌────▼────┐
│ Manifest │ parse + validate database backend, [octad] concerns, [tier2] overlay selection
│ Parser │
└────┬────┘
│ validated augmentation config
┌────▼────┐
│ Analyser │ introspect target database schema, plan sidecar overlay
└────┬────┘
│ schema IR + octad plan
┌────▼────┐
│ Codegen │ emit generated/verisimiser/ (sidecar overlay, query interceptors,
│ │ provenance chains, temporal history, drift detectors)
└────┬────┘
│ concern-Octad augmentation artifacts (sidecar schema + interceptors)
┌────▼────┐
│ Daemon │ start augmentation daemon alongside target database
└─────────┘