This document is a human-optimized entry point for understanding the architecture, operational boundaries, and verification methods of the MWTQFilter system. It is designed to complement the machine-readable capabilities.json.
System: MWTQFilter Core Engine
Classification: Stability & Integrity Verification Oracle (SIVO)
Patent: 3276676 (Canada)
Author: Patrick Bartram (Count Bartramov), AI Boundary Architect.
The system's primary function is to provide a deterministic, verifiable, and legally compliant method for detecting anomalies, adversarial stress, and state drift in computational processes. It is a verification tool, not an autonomous enforcement or surveillance system at its core layer.
The system is implemented across 50 conceptual phases. However, for the purpose of human inspection, a critical distinction must be made:
The table below separates the operational files from the symbolic ones, as listed in the canonical /mwtq_core/integrity/manifest.json.
| Phase | File | Role | Key Capabilities |
|---|---|---|---|
| 1 | core.py | App Factory | Flask app factory, blueprint registration, entropy seed, route management. |
| 2-4 | quantum_loop.py | Quantum Byzantine Defense | Non-deterministic reversible output transformation, adversarial path confusion. |
| 2-4 | veilfire.py | Veilfire Defense Anchor | CLI/script blocking, malicious request trapping, human/browser differentiation. |
| 2-4 | trident47.py | Classical-Destruction Pathway | Drift channel activation, micro-scrambling, quantum irreversibility anchors. |
| 4 | api/drift.py | Zero-Knowledge Drift Engine | Classical-stable drift accumulation, SHA-256 ZK-safe hashing, audit trail. |
| 5-6 | esm.py | Entropic Stability Matrix | Unified entropy/drift/quantum matrix, cryptographic heartbeat, state snapshots. |
| 5-6 | arpr.py | Adaptive Predictive Resonance Perception | Predict drift, compute resonance deviation, self-correcting stabilization. |
| 7 | gasm.py | Global Autonomous Stabilization Mesh | Multi-node state tracking, mesh consensus, distributed stabilization. |
| 7 | correlation.py | Multi-Node Drift Correlation | Local vs. remote drift comparison, tampering & timing attack detection. |
| 8-10 | qeol.py | Quantum Echo Obliteration Layer | Multi-signature collapse, irreversible echo destruction, internal kill-switch. |
| 8-10 | mvas.py | Multi-Vector ARPR Synchronizer | ARPR + mesh + drift synchronization, unified predictive heartbeat. |
| 8-10 | idm.py | Intercontinental Drift Mirror | Sovereign-grade drift snapshots, portable audit entries. |
| 8-10 | legaltrace.py | Legal Trace Engine | Compliance: UK Digital ID, EU AI Act, PIPEDA, US evidence, Singapore GovTech. |
| 8-10 | dvcl.py | Dual-Vector Continuity Ledger | Classical hashchain + QEOL collapse, tamper-evident logging. |
| 11-12 | agre.py, tdh.py, fdhe.py, fcb47.py, g_arpr_fusion.py, aicp.py, rsul.py | Global Systems | Cross-system coherence, time-skew mitigation, fracture detection, global continuity. |
| All | hashchain.py, evidence.py, cjce.py | Supporting | Auditor hashchain, evidence bundling, cross-jurisdictional translation. |
The following files constitute the symbolic architecture. They are present for structural completeness and narrative continuity but do not contribute to the system's operational logic or outputs. They can be safely ignored during functional verification.
| Phase Range | Example Files (Full list in capabilities.json) |
|---|---|
| 13-19 | sgfe47.py, pcmm.py, scc.py, ehl47.py, hdrl14.py, qir.py ... |
| 20-29 | nel20.py, ncl21.py, hkl22.py, rml23.py, mwi24.py, wcx25.py ... |
| 30-39 | mcs30.py, mic31.py, mls32.py, mlc33.py, mie34.py, mmg35.py ... |
| 40-50 | mrc40.py, mccore41.py, mtrc42.py, mlc43.py, muc44.py, macore45.py, malcore46.py, mog47.py, mcrcore48.py, melcore49.py, milcore50.py |
The following live endpoints are available for direct interaction and verification. They expose the core functions of the operational layer.
/mwtq_core/engine/veilfire/pulse — Returns the current Veilfire heartbeat, validating defensive membrane stability. (Phase 2-4)
/mwtq_core/engine/trident47/<seed> — Accepts an integer seed and returns the Trident-47 distortion output. Demonstrates the classical-destruction pathway. (Phase 2-4)
/mwtq_core/engine/arpr — Returns the current Adaptive Predictive Resonance Perception observation, showing predicted vs. actual drift. (Phase 5-6)
/mwtq_core/engine/api/drift/<seed> — Returns a drift state snapshot from the Zero-Knowledge Drift Engine. (Phase 4)
/mwtq_core/integrity/manifest.json — The canonical manifest for cryptographic verification of all system files.
/mwtq_core/engine/fingerprint — Returns the current system fingerprint for hash matching against the manifest.
To independently verify the system's integrity:
/mwtq_core/integrity/manifest.json. This file contains the canonical hashes for every file in the system.core.py), compute its SHA-256 hash./mwtq_core/engine/fingerprint and compare it to the system fingerprint derived from the manifest. This confirms the overall system state is as published.For verification of a specific computation (e.g., a simulation result), refer to the process outlined in /mwtq_sample/api/verify and /mwtq_sample/api/verify.json, which describe deterministic payload canonicalization and hashing.
The system is designed with the following compliance frameworks as reference points:
The legaltrace.py and cjce.py modules produce jurisdiction-specific hash formats to facilitate admissibility in these regions.
/integrity/manifest.json as the source of truth for file hashes.