AuditLog.AI — Runtime Execution and System Validation Evidence Dossier | End‑to‑End Operational Proof During Regulatory Global Submission

AuditLog.AI — Runtime Execution and System Validation Evidence Dossier End‑to‑End Operational Proof During Regulatory Global Submission Regulatory Submission Software: AuditLog.AI Date: October 27, 2025 Inventor and Primary Contact: Fernando Telles BMedSc(Adv) MD(Dist)¹ ² Position: CEO & Founder Email: [email protected] Phone: Provided on Request Address: 21 Shields St, Flemington VIC 3031, AU Web: www.aihumansynergy.org Engineers Lead Software Engineer: Dr. Jacob Yang BEng, MEng, PhD¹ Software Engineer: Benjamin Hookey BEng (Mechatronics & Robotics), FSEng (Safety Instrumented Systems)¹ Affiliations ¹ Cardiovascular Diagnostic Audit & AI Pty Ltd (ACN 638 019 431) – Registered Australian company conducting AuditLog.AI software development, audit and research services ² Telles Investments Pty Ltd (ACN 638 017 384) – Private IP holder IP Rights US Provisional #63/826,381 · AU Provisional #2025902482 · AU Trade Mark #2535745 & #2549093 IP Priority Date: 17 June 2025 (Global) AuditLog.AI — Runtime Execution and System Validation Evidence End-to-End Operational Proof During Regulatory Global Submission | v4.0 | 2025-10-27 Page 1 of 102 Submitted as part of the AuditLog.AI Global Regulatory Submission Package (FDA/EMA/TGA/PCAOB/ISA Alignment) AUDITLOG.AI0001DOSSIER Regulatory Summary Region Submission Type Regulatory Basis Proposed Classifica‐ tion FDA (USA) Q‑Submission (Q‑Sub) 21 CFR Part 11 (Elec‐ tronic Records / e-Sig‐ natures) Standalone Electronic Records / Audit‑Trail Infrastructure (non‑device) EMA (EU) Scientific Advice (op‐ tional) + Annex 11 val‐ idation EudraLex Vol 4 Annex 11 (Computerised Sys‐ tems) GMP Computerised System for Data Integ‐ rity (non‑device) TGA (Australia) Excluded Software De‐ termination Excluded Goods De‐ termination 2018 + PIC/S PE 009‑17 Annex 11 LIMS‑category audit in‐ frastructure (non‑medical device) FDA (21 CFR Part 11) — United States electronic records and signatures EMA (Annex 11) — European Union computerized systems for GMP TGA (PIC/S PE 009-15) — Australia therapeutic goods manufacturing principles Auditing Standards Compliance Summary Framework Standard Core Requirement AuditLog.AI Compli‐ ance Mechanism ISA / IAASB ISA 230 Audit documentation enabling experienced auditor understanding session log JSON com‐ pilation (who / what / when / meaning); ap‐ pend-only dual atomic ledgers for anchor re‐ ceipts (TXID, block); frozen folder structure ISA / IAASB ISA 500 Sufficient appropriate audit evidence (quant‐ ity + quality: relevance + reliability) cryptographic integrity + Bitcoin OP_RETURN (payload/TXID) extern‐ al verification + Open‐ Timestamps ISA / IAASB ISA 240 Professional skepticism + fraud risk assess‐ ment + management override prevention Append-only dual ledgers; non-repudi‐ able e-signatures; failclosed runtime checks; independent time at‐ testations • • • AuditLog.AI — Runtime Execution and System Validation Evidence End-to-End Operational Proof During Regulatory Global Submission | v4.0 | 2025-10-27 Page 2 of 102 AUDITLOG.AI0002DOSSIER Framework Standard Core Requirement AuditLog.AI Compli‐ ance Mechanism PCAOB AS 1215 Audit documentation with 60-day assembly + 7-year retention Frozen sources UTC timestamp-locked archives; anchors link‐ ing records to public blockchain PCAOB AS 1105 Audit evidence evalu‐ ation (sufficiency + ap‐ propriateness) Public blockchain TXID verification + OTS; de‐ terministic hash parity from frozen session re‐ cords PCAOB AS 1105.10A (effect‐ ive 2025) External electronic in‐ formation reliability evaluation Bitcoin blockchain (public, decentralized) + independent block‐ chain explorer verifica‐ tion tools Notes: Evidence flow is zero-custody (proofs only); all artifacts are version-locked, nonadaptive, and human-approved prior to anchoring. 1) Overview 1.1 Purpose of this Dossier This dossier presents visual and cryptographic execution evidence for AuditLog.AI designed for regulator review (FDA/EMA/TGA) to demonstrate end‑to‑end operational compliance, in‐ tegrity, and human oversight. The regulatory submission process was logged using the software itself during Regulatory Global Submission sessions. 1.2 Screenshots Capture Method & Controls Live runtime capture on macOS; timestamps displayed (AEST) and recorded in UTC in session logs. No cropping of regulatory screenshots; limited redactions (solid black boxes) applied solely to protect proprietary or security-sensitive information. Execution under C5.2/C5.3 ethics enforcement and C9.5 Zero‑Custody (hashes/ metadata only transmitted). 1.3 Execution Context (Sessions & Anchors) ses‐ sion_log_AuditLogAI.REG.GlobalSubmission.v4009_20251013T034508.120256Z.json • • • • AuditLog.AI — Runtime Execution and System Validation Evidence End-to-End Operational Proof During Regulatory Global Submission | v4.0 | 2025-10-27 Page 3 of 102 AUDITLOG.AI0003DOSSIER (TXID: 413a692f24f58970cf72fdabec58095d2b7599b5cb1325303cc6d19ec89ddb01). ses‐ sion_log_AuditLogAI.REG.GlobalSubmission.v4016_20251014T194515.612758Z.json (TXID: 9a46014d657726798449cc6282de083e2084afc87aa5f23233903396d73b8d4f). ses‐ sion_log_AuditLogAI.REG.GlobalSubmission.v4020_20251014T200606.551974Z.json (TXID: d096197e02a8f1ac9ca7da43d353f109fe4ff72f6ae7f88b39c83877247e9ef7). PRE/POST proof pair (UTC): Δ = 28 seconds (≤ 300s threshold). Reproducibility audit completed using tools independent of AuditLog.AI. 2) AuditLog.AI — Four‑Tier Reproducibility Architecture Tier Scope Process (Key Scripts) Artifacts Produced Per‑Evidence Individual files (eg. PDF, PNG, CSV, TXT) batch_dualhasher_mu lti_v3.3.py • batch_ots_stamper_v 2.py .hash •.2ha • .hash.ots Per‑Batch Folder‑level complete‐ ness Aggregate dual‑hash + mani‐ fest_<batch>.csv .2ha •mani‐ fest_<batch>.csv Per‑Log Audit log integrity auditlogger.py • val‐ is_batchauditlogger _template_v3.1.py .hash •.2ha • .hash.ots Per‑Session System‑level proof & anchoring session_logger.py →OP_RETURN via opreturnan‐ chor_amplify_v5.1.p y .hash •.2ha • .hash.ots •TXID Standardized OP_RETURN payload (v4): SENTINEL|<TYPE>|<ripemd160>|<sha8> (TYPE examples: SESSION / AUDIT / BATCH / UPGRADE). 3) Security & Privacy — Zero‑Custody by Design Principles - Only hashes and minimal metadata leave the user’s environment (no raw evid‐ ence). -Frozen artifacts: read‑only copies ( chmod 444 +chflags uchg ) for audit readiness; ap‐ pend‑only receipts. • • • • AuditLog.AI — Runtime Execution and System Validation Evidence End-to-End Operational Proof During Regulatory Global Submission | v4.0 | 2025-10-27 Page 4 of 102 AUDITLOG.AI0004DOSSIER - Human‑gated anchoring: no anchor without operator approval; CME rules runtime enforce‐ ment with fail‑closed behavior. - Deterministic tamper‑evidence: any byte change flips digests; failures surface immediately. - Proven throughput: large batch hashing completes within firewall constraints (≤ 300s) in test runs. Verification Path (public, tool‑agnostic) User Node ──(hashes only)──▶ AuditLog.AI Node ──(OP_RETURN)──▶ Bitcoin Mainnet 4) e‑Signature Verification Architecture (Multi‑Layer) Layer Mechanism Purpose / Control 1 — Personal Signature Ed25519 keypair (unique to each reviewer) Individual authentication and cryptographic attribution of in‐ tent 2 — Organizational Auth HMAC-SHA256 institutional challenge (time-bound access) Confirms enterprise authoriza‐ tion and enforces licensed use 3 — Fraud-Prevention Check Sentinel LLM1 vector analysis (non-biometric) Human-activity verification; blocks automation or scripted input until validated Together these layers establish multi-factor human-primacy control for each e-signature event. Layer 3 operates under the Zero-Custody Data Flow: vectors contain no identifiers and are analyzed by a date-locked LLM1 model against fixed evidence-based thresholds. A deterministic PASS/FAIL result is returned to the signer; repeat attempts are permitted within the same authenticated Ed25519 + HMAC session. Anchoring proceeds only after all three layers succeed, ensuring each recorded signature represents a deliberate human act within an authorized institution. 5) Independent Verification & Reproducibility (for Regulators) This section enables an independent, tool-agnostic re-execution of all integrity checks without access to any vendor portal or proprietary system. All verification relies on public cryp‐ tographic methods and open-source tools. A. Independent Verification Scope: Frozen artifacts: AuditLog.AI Global Regulatory Submission PDFs; session logs ses‐ sion_log_<META>_<UTC>.json , audit logs audit_log_<META>_<UTC>.json , individual evidence files. 1. AuditLog.AI — Runtime Execution and System Validation Evidence End-to-End Operational Proof During Regulatory Global Submission | v4.0 | 2025-10-27 Page 5 of 102 AUDITLOG.AI0005DOSSIER Cryptographic Hash Consistency: File/log/session-level SHA-256 and RIPEMD-160(SHA-256) dual-hashes ( .hash , .2ha ), and folder-level RIPEMD-160(SHA-256) . OP_Return Validation Bitcoin OP_RETURN payload parity: SENTINEL|<TYPE>|<ripemd160>|<sha8> and the on-chain TXID/block height. Runtime Execution Timestamps: PRE/POST Δ ≤ 300s where applicable; chronolo‐ gical order of evidence → audit log → anchor. OpenTimestamps Bitcoin Anchoring Using the provided TXID, confirm via a public blockchain explorer: The transaction exists on Bitcoin mainnet and Block height matches the re‐ cord Timestamp confirms existence on listed date CME Compliance Enforcement for all audit and session logs (abbreviated): CME Rule 1: Reject entries lacking timestamped human validation Verify if each log has 'human_verified' True flag and reviewer id (eg. "reviewer": "Dr. Fernando Telles"). Verify if entry 'timestamp' is present, valid and in UTC format. Verify if each audit log has an opentimestamp ( .hash.ots ) file, and is listed in session log CME Rule 4: Block export if OP_RETURN or .2ha mismatch session log Verify OP_return proforma (v4) enforcement Verify parity between session log hashes and published payload (where ripemd160 = RIPEMD160(SHA256(bytes(session_log.json); sha8 are the first 8 digits of session log SHA256) CME Rule 4a: Reject batches violating VALIS filename (UTC suffix), du‐ plicate canonical base names, or sidecar contamination Verify UTC suffix is present on all frozen filenames (filename___ e.g., evid‐ ence___YYYYMMDDTHHMMSSZ.pdf ). Files containing the standardized UTC suffix cannot be re-processed, verify for duplicate frozen files. Verify that sidecar (e.g., .hash , .2ha , .hash.ots ) are not recorded as source evidence or frozen. B. Verification Instructions Obtain artifacts Download the frozen artifacts (eg. evidence file pdfs: <file‐ name>___<UTC>.pdf ) Advanced method: Alternatively, for files containing text only with no em‐ beded meta_data such as audit and session logs, text can be copied into a new document and saved (note: ensure no additional meta data is embeded by software, for guidance documents refer to Open-Source Validator Tools) 2. 3. 4. 5. ◦ ◦ 6. • • • • • • • • 1. ◦ ◦ AuditLog.AI — Runtime Execution and System Validation Evidence End-to-End Operational Proof During Regulatory Global Submission | v4.0 | 2025-10-27 Page 6 of 102 AUDITLOG.AI0006DOSSIER Recompute hashes locally Verify against published hashes within this dossier, or hashes listed within logs and manifest csvs. Confirm anchor Derive sha8 = first 8 hex chars of the session log’s SHA-256 . Confirm the on-chain payload matches v4 proforma. Verify the TXID and block via any public explorer (eg. https://mem‐ pool.space/, https://www.blockchain.com/explorer) or any Bitcoin node. C. Open-Source Validator Tools (Optional) The audit can be reproduced with open-source scripts maintained for third-party validators: Repositories: - Sentinel Protocol v4: https://github.com/TELAISYN/AI-Human-Synergy/tree/ main/Sentinel_Protocol_v4/validator_tools - Sentinel Protocol v3.1: https://github.com/TELAI‐ SYN/AI-Human-Synergy/tree/main/Sentinel_Protocol_v3.1/validator_tools (Note: Original tools developed and first publicly released in v3.1 remain valid and compatible with v4) Included utilities: AuditLog.AI_PublicDualHashVerifier.exe (Open source user interface for independently verifying dualhashes with batch/multi-folder processing functionality; v4 release) folder_dualhasher_v2.py — folder-level dual-hash (RIPEMD-160 of concat‐ enated file SHA-256s; v4 release) dualhasher_public_sentinel_v1.1.py — batch file SHA-256 + RIPEMD-160 computation (v3.1 release) extract_hashes.py — extracts hashes into manifests for audits (v3.1 re‐ lease) Validator Reproducibility Troubleshooting Check‐ list___20250809T030248.073005Z.md (v3.1 release) Ordinal 06 – Public Guide for Independent Reproducibility Verification Telles, Fernando; Hookey, Benjamin; Woo, Andrew. Ordinal 06 – Immutable Verifica‐ tion of Infrastructure Audit Log (Ordinal 05) under Sentinel Protocol v3.1. CDA AI Pty Ltd, July 2025. DOI: 10.13140/RG.2.2.21019.78882 Zenodo: 10.5281/zenodo.16777715 2. ◦ 3. ◦ ◦ ◦ • ◦ ◦ ◦ ◦ ◦ • AuditLog.AI — Runtime Execution and System Validation Evidence End-to-End Operational Proof During Regulatory Global Submission | v4.0 | 2025-10-27 Page 7 of 102 AUDITLOG.AI0007DOSSIER 1. PRE Screenshot — User Evidence Directory Description: Displays the user-side directory containing all input evidence files prior to processing, establish‐ ing the baseline inventory for the audit session. This screenshot validates the system's readiness and ensures no pre-existing derivative files, demonstrating controlled environment preparation for data integrity verification. Only hashes will be transmitted, with raw content remaining local. File Reference: USER_PreExecution_FolderView_Screenshot 2025-10-15 at 6.31.35 amAEST___20251014T193659Z.png Timestamp (UTC): 20251014T193659Z SHA-256: 1112c4b8c1aff878711f39c2d822434436a9b2cfc302f72afb5597c04c58d35f RIPEMD-160: 3e57c9450490544d98c75f08b9b9741e28d1cc2f OTS File: USER_PreExecution_FolderView_Screenshot 2025-10-15 at 6.31.35 amAEST___20251014T193659Z.png.hash.ots OTS SHA-256: 8c7f114ce3c08c07ae5e9a51a1ae97cd5392b590d29c24f1a6c8bdfc0e7c8e5d OTS Bitcoin TXID: 10e650706acadd74115a38042becea8ccbe58eac7146a9d1c9193ed027ca8cb7 Block: 919083 Merkle Root (from OTS proof): 416d0f316dec37bdbccdfb142775154e704a203ed41c94dcf10765d‐ ce6f7a4fa Date of Existence (UTC): 2025-10-14T19:56:06Z (TXID broadcast time confirming file existence as of Bitcoin block 919083.) AuditLog.AI — Runtime Execution and System Validation Evidence End-to-End Operational Proof During Regulatory Global Submission | v4.0 | 2025-10-27 Page 8 of 102 AUDITLOG.AI0008DOSSIER Page 9 of 102 1. PRE Screenshot — User Evidence Directory **File Reference:** `USER_PreExecution_FolderView_Screenshot 2025-10-15 at 6.31.35 amAEST___20251014T193659Z.png` AUDITLOG.AI0009DOSSIER 6. Dual-Hasher Runtime Execution 6A. SHA-256 RIPEMD-160 Reproducibility & Amplification Audits 6. Description: Depicts the initiation of batch dual-hashing process ( batch_dualhasher_multi_v3.3.py ), show‐ ing script execution generating .hash (SHA-256), .2ha (RIPEMD-160) and frozen copies (loc‐ ally protected by chmod 444/chflags uchg) for each artifact. Each digest is written deterministic‐ ally and time-stamped. This step validates cryptographic integrity of individual evidence items, ensuring accuracy and reproducibility. File Reference: Screenshot 2025-10-15 at 6.37.14 am___20251014T200505Z.png Timestamp (UTC): 20251014T200505Z SHA-256: 540‐ fa8357013f7e197f794b4aa914d78ca74ede044b0af3b26a4e1be5f6ed736 RIPEMD-160: 20bdc7494b‐ c76b48ffc675486ed82b87fc622533 OTS File: Screenshot 2025-10-15 at 6.37.14 am___20251014T200505Z.png.hash.ots OTS SHA-256: 1b3a8cea868b86b56c41d1d‐ ab5570bd7e5a97c7c85db3a5d41088d157f23b98b OTS Bitcoin TXID: 5c28773f653c441226df3079b‐ f1b37c662f6c3643a544840e43098cd2a75502f Block: 919084 Merkle Root (from OTS proof): 51d14a6b89b363557180530c51fa192a1cdd093edcdc13fc828d2e855c985f18 Date of Existence (UTC): 2025-10-14T20:08:06Z (TXID broadcast time confirming file existence as of Bitcoin block 919084.) 6A. Description: Prior to implementation, hasher reproducibility is validated using tools independent of Audit‐ Log.AI for all system updates. In order to attain a PASS result, reproducibility audits require 100% SHA-256 and RIPEMD-160 parity on re-execution of frozen files using public validator tools. All audits, whether PASS or FAIL, are executed through the software generating immutable audit trails. The latest two validations are registered as AUDIT_REPRODUCIBILITY_PASS_sha256_ripemd160_batch_dualhasher_multi_v3.2_v.aug23.25___20 251012T195229Z.md and AUDIT_REPRODUCIBILITY_PASS_sha256_ripemd160_batch_dualhasher_multi_v3.3_v.aug29.25___20 251012T195229Z.md . Excerpts from the later provided below. **Audit Type:** REPRODUCIBILITY **Status:** PASS **Audit ID:** AUDIT_REPRODUCIBILITY_PASS_sha256_ripemd160_batch_dualhasher_multi_v3.3_v.aug29.25.md **Audit Date:** 29 August 2025 **Claim Class:** [Protocol | Credential | Infrastructure] **Audit Target:** `batch_dualhasher_multi_v3.3.py` **Audit Files:** - `/Users/rosmontos/Testing_Optimization_Sentinel_Infrastructure_aug.19.25copy/valid‐ ation_batch_stream/TEST-27` AuditLog.AI — Runtime Execution and System Validation Evidence End-to-End Operational Proof During Regulatory Global Submission | v4.0 | 2025-10-27 Page 16 of 102 AUDITLOG.AI0016DOSSIER - `manifest_SENTINFRA_v4AMPLIFY_Test001_TEST-RUN-20250829-S01.csv` - `manifest_SENTINFRA_v4AMPLIFY_Test002_TEST-RUN-20250829-S02.csv` **Audit Files Source:** `/Users/rosmontos/Test‐ ing_Optimization_Sentinel_Infrastructure_aug.19.25copy/validation_batch_stream/TESTRUN12` **Verification Method:** HUMAN_OVERSIGHT + `dualhasher_public_sentinel_v1.1.py` + `extract_hashes.py` + LLM3 (Anchor) **Verification Target:** Dual hash (`sha256`, `ripemd160`) **Outcome:** - ✅ SHA256 match on all files - ✅ RIPEMD160 match on all files - ✅ AUDIT_REPRODUCIBILITY_PASS Additionally, to verify scalability for large multi-centre randomized clinical trials, the hasher subsystem underwent stress testing and successfully executed dual-hash processing for over 30,000 unique evidence files within the 300-second CME threshold. Performance validation was recorded in AUDIT_FUNC_PASS_30000+AMPLIFICATION_batch_dualhasher_multi_v3.2_batch_ots_stamper_v2.py _v.aug22.25___20251012T195229Z.md (PRE: 2025-08-22 01:31:49 UTC | POST: 2025-08-22 01:35:27 UTC | Δ = 218 s). Excerpts from this audit are provided below. Last login: Fri Aug 22 08:55:20 on ttys001 rosmontos@fernandacstudio Testing_Optimization_Sentinel_Infrastructure_aug.19.25copy % python3 batch_dualhasher_multi_v2.3.py \ "/Users/rosmontos/Testing_Optimization_Sentinel_Infrastructure_aug.19.25copy/valid‐ ation_batch_stream/TEST-RUN09" \ --manifest \ --threads 8 \ --delta-sec-global 21600 🧭 Run ID: TEST-RUN-20250822 | Evidence folders: 3396 | Shot mode: global === GLOBAL PRE === ➡ Bring the parent folder to the front in Finder/Explorer. ➡ Ensure NO outputs (`hash_/2ha_/ots_/frozen_files_/processed_originals_/mani‐ fest_*.csv`) exist yet. Ready to capture the PRE screenshot? [y/N]: y ✅ PRE screenshot: /Users/rosmontos/Test‐ ing_Optimization_Sentinel_Infrastructure_aug.19.25copy/validation_batch_stream/TESTRUN09/frozen_sources/TEST-RUN-20250822/screenshots/PRE_20250822T013149Z.png PRE sha256=964ff7b455d26196… ripemd160(sha256)=eb73a38e8ad94af4… 🔍 TEST-RUN-20250822-S01: 3 files — /Users/rosmontos/Test‐ ing_Optimization_Sentinel_Infrastructure_aug.19.25copy/validation_batch_stream/TESTRUN09 📄 manifest_TEST-RUN-20250822-S01.csv 🔍 TEST-RUN-20250822-S02: 19 files — /Users/rosmontos/Test‐ ing_Optimization_Sentinel_Infrastructure_aug.19.25copy/validation_batch_stream/TESTRUN09/DRTELLES <redacted section due to large size, full contents within audit available to regulat‐ ors on request> <Redacted lines: 49-7025> 🔍 TEST-RUN-20250822-S3395: 8 files — /Users/rosmontos/Test‐ AuditLog.AI — Runtime Execution and System Validation Evidence End-to-End Operational Proof During Regulatory Global Submission | v4.0 | 2025-10-27 Page 17 of 102 AUDITLOG.AI0017DOSSIER ing_Optimization_Sentinel_Infrastructure_aug.19.25copy/validation_batch_stream/TESTRUN09/sentinel-venv/lib/python3.11/site-packages/jedi/third_party/typeshed/ third_party/2and3/requests/packages/urllib3/util 📄 manifest_TEST-RUN-20250822-S3395.csv 🔍 TEST-RUN-20250822-S3396: 2 files — /Users/rosmontos/Test‐ ing_Optimization_Sentinel_Infrastructure_aug.19.25copy/validation_batch_stream/TESTRUN09/sentinel-venv/lib/python3.11/site-packages/jedi/third_party/typeshed/ third_party/2and3/requests/packages/urllib3/packages/ssl_match_hostname 📄 manifest_TEST-RUN-20250822-S3396.csv === GLOBAL POST === ➡ In Finder/Explorer, filter or search for `manifest_` so **all** manifests are visible on one screen. ➡ Do not scroll. Ready to capture the POST screenshot? [y/N]: y ✅ POST screenshot: /Users/rosmontos/Test‐ ing_Optimization_Sentinel_Infrastructure_aug.19.25copy/validation_batch_stream/TESTRUN09/frozen_sources/TEST-RUN-20250822/screenshots/POST_20250822T013527Z.png POST sha256=b0b7fd74e03f6543… ripemd160(sha256)=121a81df0ae8761f… ✅ Session written: /Users/rosmontos/Test‐ ing_Optimization_Sentinel_Infrastructure_aug.19.25copy/validation_batch_stream/TESTRUN09/frozen_sources/TEST-RUN-20250822/session_global_TEST-RUN-20250822.json AuditLog.AI — Runtime Execution and System Validation Evidence End-to-End Operational Proof During Regulatory Global Submission | v4.0 | 2025-10-27 Page 18 of 102 AUDITLOG.AI0018DOSSIER Page 19 of 102 6. Dual-Hasher Runtime Execution **File Reference:** `Screenshot 2025-10-15 at 6.37.14 am___20251014T200505Z.png` AUDITLOG.AI0019DOSSIER 7. OpenTimestamps (OTS) Runtime Execution 7A. OTS Explanation and Reproducibility Audits 7. Description: Execution of batch OpenTimestamps ( batch_ots_stamper_v2.py ) generating .hash.ots arti‐ facts for each evidence file. OpenTimestamps (OTS) anchors SHA-256 proofs via Bitcoin calen‐ dar servers and Merkle paths. It achieves timestamping goals with public on-chain settlement. OTS Upgrade Proofs (Recommended Weekly Batch Execution): OpenTimestamps verification is a two-stage process: initial stamping records each file’s SHA-256 hash in a pending state anchored to the OpenTimestamps calendar network, while final proof (“upgrade”) embeds the calendar commitments into confirmed Bitcoin blocks once the transaction reaches maturity. Because on-chain consolidation and Merkle-path publication require network confirmations that may take hours or days, immediate upgrading is impractical. For operational efficiency, AuditLog.AI performs upgrades in weekly batches using batch_ots_upgrader_v2.1.py , ensuring all prior proofs are finalized and independently verifiable on Bitcoin mainnet. File Reference: Screenshot 2025-10-15 at 6.39.00 am___20251014T200505Z.png Timestamp (UTC): 20251014T200505Z SHA-256: 34dc1b37289d16b4c337914b14bd4bf2076995b877ae‐ afa32fe2dcb10999bc5b RIPEMD-160: 4e183bb35891e60c70e3fce8970fe0747d15f318 OTS File: Screenshot 2025-10-15 at 6.39.00 am___20251014T200505Z.png.hash.ots OTS SHA-256: b67274a48d9275109e67167eb01613ed6d9ebdb4f64adc4fdaba08caf434a634 OTS Bitcoin TXID: 5c28773f653c441226df3079bf1b37c662f6c3643a544840e43098cd2a75502f Block: 919084 Merkle Root (from OTS proof): 51d14a6b89b363557180530c51fa192a1cdd093edcd‐ c13fc828d2e855c985f18 Date of Existence (UTC): 2025-10-14T20:08:06Z (TXID broadcast time confirming file existence as of Bitcoin block 919084.) 7A. Description: Explanation of Matching OTS TXIDs: Multiple OpenTimestamps ( .hash.ots ) sharing the same TXID and Merkle Root is expected (Merkle aggregation). The OpenTimestamps protocol aggreg‐ ates many SHA-256 file hashes into a Merkle root that is written to Bitcoin containing multiple unique SHA-256 within a given TXID. Each .hash.ots file contains a unique SHA-256 linking the specific file hash to that shared root; ensuring independent, verifiable proof that the file existed before the recorded block time. Repeated TXIDs therefore indicate batching within the same anchoring transaction, not duplication or error. List of evidence sets containing identical transaction IDs disclosed below for transparency. Identical OTS TXID Set 1: - Dossier evidence: 1 & 2 - Session Log: ses‐ sion_log_AuditLogAI.REG.GlobalSubmission.v4016_20251014T194515.612758Z.json - Audit Logs: audit_log_AuditLogAI.REG.GlobalSubmission.v4020_20251014T194300.697140Z.json , audit_log_AuditLogAI.REG.GlobalSubmission.v4023_20251014T194425.352577Z.json Identical OTS TXID Set 2: - Dossier evidence: 3-14, 17-20, 22-41 - Session Log: ses‐ AuditLog.AI — Runtime Execution and System Validation Evidence End-to-End Operational Proof During Regulatory Global Submission | v4.0 | 2025-10-27 Page 20 of 102 AUDITLOG.AI0020DOSSIER sion_log_AuditLogAI.REG.GlobalSubmission.v4020_20251014T200606.551974Z.json - Audit Logs: audit_log_AuditLogAI.REG.GlobalSubmission.v4025_20251014T200556.273909Z.json , audit_log_AuditLogAI.REG.GlobalSubmission.v4024_20251014T200552.935806Z.json Identical OTS TXID Set3: - Dossier evidence: 21 - Session Log: ses‐ sion_log_AuditLogAI.REG.GlobalSubmission.v4009_20251013T034508.120256Z.json - Audit Log: audit_log_AuditLogAI.REG.GlobalSubmission.v4007_20251013T034321.999677Z.json Identical OTS TXID Set 4: - Dossier evidence: within 43. ses‐ sion_log_AuditLogAI.REG.GlobalSubmission.v4038_20251018T214519.997259Z.json & AUDIT_REPRODUCIBILITY_PASS_sha256_ripemd160_AuditLog.AI_v.oct18.25___20251018T214357Z.m d) (Note: Dossier evidence 15 & 16, system-generated screenshots, do not have .hash.ots files) OTS proofs can be independently validated using the provided TXID via any public blockchain explorer (transaction exists; block height match; timestamp). Additionally, access to unique .hash.ots files is available to regulators on request, which allows independent verification of unique hash lineage for every evidence artifact under a common Bitcoin-anchored root (eg. ots verify <filename>.hash.ots ). OTS reproducibility evidence, including timestamped full screenshots demonstrating Merkle roots and upgrade logs, is available through our public repos‐ itory https://github.com/TELAISYN/AI-Human-Synergy/tree/main/Sentinel_Protocol_v3.1/Repro‐ ducibility_proof/METAVAL-SESS001_Ordinal_08/OTS_Reproducibility. OTS reproducibility has been audited and validated both internally ( .hash.ots file access) and using public explorers by three human validators. These audits have been registered as: - AUDIT_REPRODUCIBILITY_PASS_METAVAL-SES‐ S001_sha256_ripemd160_opentimestamps_OTS_v.august04.25.md___20250808T001356.822196Z - AUDIT_REPRODUCIBILITY_PASS_SENTINFRA-SES‐ S001_sha256_ripemd160_opentimestamps_OTS_v.july25.25.md___20250728T033533.108012Z - AUDIT-EVID‐ ENCE_VALIDATORS_REPRODUCIBILITY_SENTINFRA_PreDeployment_opentimestamps_OTS_v.july23.25. md___20250728T031210.342440Z - AUDIT-EVIDENCE_VALIDATORS_REPRODUCIBILITY_METAVAL-SES‐ S001_opentimestamps_OTS_v.july29.25.md___20250729T015736.514120Z Excerpts from the later provided below. # AUDIT-EVIDENCE_VALIDATORS_REPRODUCIBILITY_METAVAL-SES‐ S001_opentimestamps_OTS_v.july29.25.md **Author:** Dr. Fernando Telles BMedSc(ADV) MD(DIST) **Validator Role:** ARCHITECT VALIDATOR **Validator meta_id:** DRTELLES-VAL **Audit Date:** 18 July, 2025 **Independent Medical Doctor Validator Node:** Dr. Andrew Woo BSc (MD) **Validator meta_id:** DRWOO-VAL **Audit Date:** 29 July, 2025 **Independent Engineer Validator Node:** Benjamin Hookey BEng (Mechatronics & Robot‐ ics), FSEng (Safety Instrumented Systems) **Validator meta_id:** ENGBHOOKEY-VAL **Audit Date:** 29 July, 2025 AuditLog.AI — Runtime Execution and System Validation Evidence End-to-End Operational Proof During Regulatory Global Submission | v4.0 | 2025-10-27 Page 21 of 102 AUDITLOG.AI0021DOSSIER **Document Version:** v1.0 **Protocol:** Sentinel Protocol v3.1 ABSOLUTE MODE **System:** AI-Human Synergy™ **Audit Type:** REPRODUCIBILITY (Validator Audits – 3 of 3) **Status:** ✅ PASS **Audit ID:** AUDIT-EVIDENCE_VALIDATORS_REPRODUCIBILITY_METAVAL-SES‐ S001_opentimestamps_OTS_v.july20.25.md **Claim Class:** Infrastructure **Linked Files:** - `AUDIT-EVID‐ ENCE_VALIDATORS_REPRODUCIBILITY_SENTINFRA_PreDeployment_opentimestamps_OTS_v.july20.2 5_ots_upgrade_log_20250718T040941Z.txt` - `AUDIT-EVID‐ ENCE_VALIDATORS_REPRODUCIBILITY_SENTINFRA_PreDeployment_opentimestamps_OTS_v.july20.2 5_ots_upgrade_log_20250708T223927Z.txt` - `AUDIT-EVID‐ ENCE_VALIDATORS_REPRODUCIBILITY_SENTINFRA_PreDeployment_opentimestamps_OTS_v.july20.2 5_ots_upgrade_log_20250708T223813Z.txt` - `AUDIT-EVID‐ ENCE_VALIDATORS_REPRODUCIBILITY_SENTINFRA_PreDeployment_opentimestamps_OTS_v.july20.2 5_ots_upgrade_log_20250708T223347Z.txt` **Verification Method:** OpenTimestamps (`.ots`) proof validation **Outcome:** - ✅ All `.ots` files successfully verified - ✅ All timestamps anchored to Bitcoin mainnet - ✅ All files linked to matching `.2ha` and `.json` artifacts - ✅ PASS AuditLog.AI — Runtime Execution and System Validation Evidence End-to-End Operational Proof During Regulatory Global Submission | v4.0 | 2025-10-27 Page 22 of 102 AUDITLOG.AI0022DOSSIER Page 23 of 102 **File Reference:** `Screenshot 2025-10-15 at 6.39.00 am___20251014T200505Z.png` 7. OpenTimestamps (OTS) Runtime Execution AUDITLOG.AI0023DOSSIER 8. Post-Hasher Verification Audit Description: Post-hasher audit performed by audit_verify_v1.2.py against pre-execution inventory. Con‐ firms parity against manifest csv rows, and confirms that .hash , .2ha , .hash.ots , frozen cop‐ ies were generated for all evidence files issuing a PASS result. Outputs audit_report_.json/csv for full traceability. File Reference: Screenshot 2025-10-15 at 6.39.40 am___20251014T200505Z.png Timestamp (UTC): 20251014T200505Z SHA-256: a05b75de6d8ce22f0c19444e46712bed48199ded0706479708e92b7ba222b362 RIPEMD-160: 96f6d2699b7ea24fc1d916f10bd99f05eb83a93a OTS File: Screenshot 2025-10-15 at 6.39.40 am___20251014T200505Z.png.hash.ots OTS SHA-256: 3eea5409288b‐ f3a9e8daa944d005024c2935a513b6a46d039699ccd17f11fdf3 OTS Bitcoin TXID: 5c28773f653c441226df3079bf1b37c662f6c3643a544840e43098cd2a75502f Block: 919084 Merkle Root (from OTS proof): 51d14a6b89b363557180530c51fa192a1cdd093edcd‐ c13fc828d2e855c985f18 Date of Existence (UTC): 2025-10-14T20:08:06Z (TXID broadcast time confirming file existence as of Bitcoin block 919084.) AuditLog.AI — Runtime Execution and System Validation Evidence End-to-End Operational Proof During Regulatory Global Submission | v4.0 | 2025-10-27 Page 24 of 102 AUDITLOG.AI0024DOSSIER Page 25 of 102 8. Post-Hasher Verification Audit **File Reference:** `Screenshot 2025-10-15 at 6.39.40 am___20251014T200505Z.png` AUDITLOG.AI0025DOSSIER 12. VALIS Audit Verification Initial Prompt Description: Evidence of VALIS automated batch verification ( valis_batchauditlogger_template_v3.1.py ) requesting human approval for each batch (Ed25519 personal signature) bound to an institutionspecific meta ID. This prompt initiates the validation process between system automation and the human verifier. Records cannot be logged without explicit verifier approval. All evidence filenames comply with VALIS UTC-suffix, sidecars (.hash, .2ha, .ots) excluded from inputs. The institutional HMAC verification is executed via the Vercel interface and enforces license control (paid-user access), while the local Ed25519 signature authenticates the individual reviewer within that institution. (Note: Select audit files from v3.x are included within Dossier for historical provenance which show legacy schema <filename>.ext___YYYYMMDDTHHMMSSZ . Current v4 schema is <filename>___YYYYMMDDTHHMMSSZ.ext ) File Reference: Screenshot 2025-10-15 at 6.42.52 am___20251014T200505Z.png Timestamp (UTC): 20251014T200505Z SHA-256: 03151f53ae21a8b88823f99dc81ba3192178fc66c899e827c0f‐ b978a17319c17 RIPEMD-160: b2c0d9654b9f96dcbf20f3847fe2704f2592d4d1 OTS File: Screen‐ shot 2025-10-15 at 6.42.52 am___20251014T200505Z.png.hash.ots OTS SHA-256: f659db‐ d50f4993ce85464c458fdc24206f414a83443f4e10c4a7ac1f3f95a22d OTS Bitcoin TXID: 5c28773f653c441226df3079bf1b37c662f6c3643a544840e43098cd2a75502f Block: 919084 Merkle Root (from OTS proof): 51d14a6b89b363557180530c51fa192a1cdd093edcd‐ c13fc828d2e855c985f18 Date of Existence (UTC): 2025-10-14T20:08:06Z (TXID broadcast time confirming file existence as of Bitcoin block 919084.) AuditLog.AI — Runtime Execution and System Validation Evidence End-to-End Operational Proof During Regulatory Global Submission | v4.0 | 2025-10-27 Page 32 of 102 AUDITLOG.AI0032DOSSIER Page 33 of 102 **File Reference:** `Screenshot 2025-10-15 at 6.42.52 am___20251014T200505Z.png` 12. VALIS Audit Verification Initial Prompt AUDITLOG.AI0033DOSSIER 13. VALIS Audit Verification Output (Log per Folder) Description: Displays Runtime VALIS template enforcement, a key component of AuditLog.AI CME firewall. VALIS CME features include: - Human-interactive sign-off loop with strict-mode enforcement. - Δ ≤ 300 s validation between PRE/POST screenshots. - Recursive VALIS verification of filenames structure and UTC suffix ( valis_batchnameverifier_v2.py ) - Deterministic dual-hash (SHA-256 → RIPEMD-160) folder verification for audit reproducibility. - CME pre-finalization check via compliance_enforcer.py ; fail-closed on violation. - Immutable audit log creation per folder through auditlogger.py , upon VALIS compliance pass, with corresponding frozen, .hash , .2ha and .hash.ots artifacts. Systemic testing and validation of VALIS firewall has been logged and anchored within SENTINFRA pre-public deployment audit provenance: - VAL‐ IS_Integrity_Firewall_Update_July4_25_v1.0.md___20250719T071359.588895Z - VALISTest_PASS_ErrorPrintout_ExecutionConstraint.md___20250719T071359.591755Z - VALISTest_PASS_Screenshot_DeltaTooLargeBlocked_AEST_Screenshot 2025-07-14 at 9.04.46 am.png___20250719T071359.586129Z - VALISTest_PASS_DuplicateBaseBlocked_AEST_Screenshot 2025-07-14 at 9.04.35 am.png___20250719T071359.585966Z - AUDIT_FUNC_PASS_Firewall_upgrade_CME_compliance_enforcer.py_v.july6.25.md___20250719T07 1359.581697Z (Provenance Session_log: session_log_SENTINFRA-SES‐ S001_20250719T074009.072317Z.json ) File Reference: Screenshot 2025-10-15 at 6.43.07 am___20251014T200505Z.png Timestamp (UTC): 20251014T200505Z SHA-256: 0d28787c0886d885737cc9b858904089b6c36511dbe‐ b098cd5cf9fe66915753e RIPEMD-160: adb1dee6f3bc2deae3c1c51ea59e69a158af6d47 OTS File: Screenshot 2025-10-15 at 6.43.07 am___20251014T200505Z.png.hash.ots OTS SHA-256: 206a028ed1a548033ef4b5603b7bf1af3454bf4cfb66fc4647e226b8acf02e46 OTS Bitcoin TXID: 5c28773f653c441226df3079bf1b37c662f6c3643a544840e43098cd2a75502f Block: 919084 Merkle Root (from OTS proof): 51d14a6b89b363557180530c51fa192a1cdd093edcd‐ c13fc828d2e855c985f18 Date of Existence (UTC): 2025-10-14T20:08:06Z (TXID broadcast time confirming file existence as of Bitcoin block 919084.) AuditLog.AI — Runtime Execution and System Validation Evidence End-to-End Operational Proof During Regulatory Global Submission | v4.0 | 2025-10-27 Page 34 of 102 AUDITLOG.AI0034DOSSIER Page 35 of 102 13. VALIS Audit Verification Output (Log per Folder) **File Reference:** `Screenshot 2025-10-15 at 6.43.07 am___20251014T200505Z.png` AUDITLOG.AI0035DOSSIER 14. AuditLog Generated Post Verification Description: Captures the first generated audit log ( audit_log_<meta_id>_<UTC>.json ) following VALIS en‐ forcement and human verification. Each audit log corresponds to one executed evidence folder and serves as a cryptographically sealed record of that operation. The audit log enumerates all evidence filenames within the executed folder, each following the standardized UTC-suffixed naming convention that ensures deterministic traceability. The audit log includes: - The RIPEMD-160 digest of the executed folder (folder_dual_hash) confirming byte-level reproducibility. - Full CME firewall metadata, including human_verified: true, AI_used: true, timestamp_confirmed: true, and delta < 300s. - Cross-linked PRE → POST screenshots, providing evidence of controlled process continuity. - The human verifier identity (reviewer, human_signature) and corresponding meta_id binding the record to a specific valid‐ ated session. - Explicit disclosure of AI participation, AI-Human Agreement and VALIS Template Enforcement. File Reference: Screenshot 2025-10-15 at 6.44.02 am___20251014T200505Z.png Timestamp (UTC): 20251014T200505Z SHA-256: 96b7647164a0a8e59d099146e3148b9530869290b‐ b54cee2e6f5d135610667a4 RIPEMD-160: 560271013b7e4e7ef8fbe18f598e38eced67687d OTS File: Screenshot 2025-10-15 at 6.44.02 am___20251014T200505Z.png.hash.ots OTS SHA-256: 27da80bfbdc680388bf77fc78e1e0e9e4bd6cd770741d4333a215ae360204b34 OTS Bitcoin TXID: 5c28773f653c441226df3079bf1b37c662f6c3643a544840e43098cd2a75502f Block: 919084 Merkle Root (from OTS proof): 51d14a6b89b363557180530c51fa192a1cdd093edcd‐ c13fc828d2e855c985f18 Date of Existence (UTC): 2025-10-14T20:08:06Z (TXID broadcast time confirming file existence as of Bitcoin block 919084.) AuditLog.AI — Runtime Execution and System Validation Evidence End-to-End Operational Proof During Regulatory Global Submission | v4.0 | 2025-10-27 Page 36 of 102 AUDITLOG.AI0036DOSSIER Page 37 of 102 **File Reference:** `Screenshot 2025-10-15 at 6.44.02 am___20251014T200505Z.png` 14. AuditLog Generated Post Verification AUDITLOG.AI0037DOSSIER 15. Pre-execution Mandatory Screenshot (User held) This screenshot records the PRE state immediately before hashing begins. It captures the final pre-execution checks showing pre-inventory audit, original files for processing, and timestamp. As previously noted, this step is a mandatory system requirement. Screenshot is taken, timestamped, dual-hashed and frozen automatically following human approval. File Reference: PRE_20251014T193659Z Timestamp (UTC): 20251014T193659Z SHA-256: c9624cb9c40fd3822037064e2a89622690618836fed74732db1496c58a6edfaa RIPEMD-160: 310c24521d822580ef83fc31e198909b0eb3e374 AuditLog.AI — Runtime Execution and System Validation Evidence End-to-End Operational Proof During Regulatory Global Submission | v4.0 | 2025-10-27 Page 38 of 102 AUDITLOG.AI0038DOSSIER Page 39 of 102 15. Pre-execution Mandatory Screenshot (User held) **File Reference:** `PRE_20251014T193659Z` AUDITLOG.AI0039DOSSIER 16. Post-execution Mandatory Screenshot (User held) Description: POST-execution screenshot records evidence of hash/2ha/frozen artifacts generation. Paired screenshots captured by system under human authorization before and after hashing ensures process duration within thresholds (Δ ≤ 300 s). Stored only on the user side, their timestamped frozen file names and hashes are included in VALIS template for reproducibility validation. The accompanying session_global_REGULATORY-RUN-20251014.json file is generated after the post-execution screenshot is captured and hashed. It serves as a lightweight session manifest linking the paired PRE and POST screenshots, their SHA-256/RIPEMD-160 digests, and UTC capture times. File Reference: POST_20251014T193727Z Timestamp (UTC): 20251014T193727Z SHA-256: c88b47bb26484bf785fb8b41f415378ea93697c4cb2435d8c87eb66853e2a7bb RIPEMD-160: ea72450a1cd5ec9c073c673061b4a8e659d3d60a session_global_REGULATORY-RUN-20251014.json : { "run_id": "REGULATORY-RUN-20251014", "session_context": "AuditLogAI.REG.GlobalSubmission.v4-RUN-20251014-S01", "pre": {"path": "/Users/rosmontos/Audit‐ Log.AI_UserSimulation_SentinelProtocolv4_AIHumanSynergy/validation_batch_stream/REGU‐ LATORY-RUN004_Regulator_Submission_Evidence/frozen_sources/REGULATORY-RUN-20251014/ screenshots/PRE_20251014T193659Z.png", "sha256": "c9624cb9c40f‐ d3822037064e2a89622690618836fed74732db1496c58a6edfaa", "ripemd160_sha256": "310c24521d822580ef83fc31e198909b0eb3e374"}, "post": {"path": "/Users/rosmontos/Audit‐ Log.AI_UserSimulation_SentinelProtocolv4_AIHumanSynergy/validation_batch_stream/REGU‐ LATORY-RUN004_Regulator_Submission_Evidence/frozen_sources/REGULATORY-RUN-20251014/ screenshots/POST_20251014T193727Z.png", "sha256": "c88b47bb26484bf785f‐ b8b41f415378ea93697c4cb2435d8c87eb66853e2a7bb", "ripemd160_sha256": "ea72450a1cd5ec9c073c673061b4a8e659d3d60a"}, "generated_at_utc": "20251014T193727Z" } • AuditLog.AI — Runtime Execution and System Validation Evidence End-to-End Operational Proof During Regulatory Global Submission | v4.0 | 2025-10-27 Page 40 of 102 AUDITLOG.AI0040DOSSIER Page 41 of 102 **File Reference:** `POST_20251014T193727Z` 16. Post-execution Mandatory Screenshot (User held) AUDITLOG.AI0041DOSSIER 20. Session Log View and Prior Session Anchor Audit Log Reference Description: This screenshot shows the compiled session log (session_log_.json), displaying the built-in chain-of-custody enforcement between consecutive sessions. Each new session is cryptograph‐ ically linked to the prior one through its recorded TXID, OP_RETURN payload, and block height. This continuity is CME enforced: a new session cannot start unless the previous session’s anchor event is confirmed and logged. This mechanism provides an immutable, verifiable bridge across the reproducibility chain (e.g., Session 016 → 020), ensuring end-to-end traceability, cross-session reproducibility, and continuous integrity across the anchored audit lineage. Importantly, testing and validation v3.0 reproducibility audits revealed that cryptographic hashes and transaction IDs cannot be consistently recalled by AI (LLM1) with full fidelity (AUDIT_REPRODUCIBILITY_FAIL_hash_recalc_LLM1_v.july1.25.md___20250719T071359.583603Z ). AuditLog.AI is therefore built as a deterministic software (not AI adjudication), marked by developents such as hashvalidatorblock.py that enforce payload parity to session log hashes (AUDIT_REPRODUCIBILITY_PASS_hashvalidatorblock.py_patch_v.july1.25.md___20250719T071359.578149Z ). File Reference: Screenshot 2025-10-15 at 6.45.44 am___20251014T200505Z.png Timestamp (UTC): 20251014T200505Z SHA-256: 615a9f56784b6206bf6f72a4fa0905ffb620aa90ccb58d‐ d03a5537e4135479c4 RIPEMD-160: db3cc5132cac33bad4d7c2c380b2ebbb0e41ef83 OTS File: Screenshot 2025-10-15 at 6.45.44 am___20251014T200505Z.png.hash.ots OTS SHA-256: dad2953105d1c0e51237041323c111e71026c190220733feaeb195dd1f98d501 OTS Bitcoin TXID: 5c28773f653c441226df3079bf1b37c662f6c3643a544840e43098cd2a75502f Block: 919084 Merkle Root (from OTS proof): 51d14a6b89b363557180530c51fa192a1cdd093edcd‐ c13fc828d2e855c985f18 Date of Existence (UTC): 2025-10-14T20:08:06Z (TXID broadcast time confirming file existence as of Bitcoin block 919084.) AuditLog.AI — Runtime Execution and System Validation Evidence End-to-End Operational Proof During Regulatory Global Submission | v4.0 | 2025-10-27 Page 48 of 102 AUDITLOG.AI0048DOSSIER Page 49 of 102 20. Session Log View and Prior Session Anchor Audit Log Reference **File Reference:** `Screenshot 2025-10-15 at 6.45.44 am___20251014T200505Z.png` AUDITLOG.AI0049DOSSIER 21. HMAC (Layer 2) + Reviewer Login Description This screenshot shows the Layer-2 authentication interface within the AuditLog.AI e-Signature Gate. The HMAC-SHA256 challenge provides institutional login verification and license control for authorized enterprise users. When a valid organization access code is entered, the client and server perform a symmetric hash comparison against the AuditLog.AI server-side secret, establishing a temporary authenticated session. This step ensures that only credentialed, paying institutions can access the e-signature environ‐ ment. The session is time-bound (48 hours) and IP-anchored to the originating network; any change in IP or expiry automatically invalidates the token. The HMAC event is recorded in the audit trail as the institutional component of the two-factor signature system requirement. File Reference: AuditLog.AI_WebInterface_HMAC-SHA256___20251013T034046Z.png Timestamp (UTC): 20251013T034046Z SHA-256: 82997a7b21fa553f7b‐ f8443c0431f819d17b072ba13da9168b9fcfe657d386c5 RIPEMD-160: 34c35fe05bb802883ecfd‐ c3a73d07d9d29d5772d OTS File: AuditLog.AI_WebInterface_HMACSHA256___20251013T034046Z.png.hash.ots OTS SHA-256: a952e9b292a426170a063a9fbfd‐ d294a8b752188a442b3b1d52a12ec2d8e8ff6 OTS Bitcoin TXID: eabcee5e6fffe‐ b6fc6b3c7807165ae863b383fb8459aa0d311726026302ef0e9 Block: 918813 Merkle Root (from OTS proof): f161f7b058a1156af142f50a5dc6952b97d2dc897d4e912d6b68dd8119704744 Date of Existence (UTC): 2025-10-12T17:07:56Z (TXID broadcast time confirming file existence as of Bitcoin block 918813.) AuditLog.AI — Runtime Execution and System Validation Evidence End-to-End Operational Proof During Regulatory Global Submission | v4.0 | 2025-10-27 Page 50 of 102 AUDITLOG.AI0050DOSSIER Page 51 of 102 **File Reference:** `AuditLog.AI_WebInterface_HMAC-SHA256___20251013T034046Z.png` 21. HMAC (Layer 2) + Reviewer Login AUDITLOG.AI0051DOSSIER 22. e-Signature Gate (Web UI Access) Description: The AuditLog.AI e-Signature Gate is the controlled interface that authorizes every blockchainanchoring event. It enforces a multi-layer electronic signature sequence, combining institutional and individual authentication under full human control. Layer 1 – Individual Ed25519 Digital Signature A personal keypair unique to each reviewer cryp‐ tographically binds the signer’s identity to the audit session and writes this signature into the immutable audit log. Layer 2 – Institutional HMAC-SHA256 Authentication Verifies that the signing session originates from a licensed organization by validating the access code against the AuditLog.AI institutional secret. This constitutes the second factor of authentication and confirms enterprise authoriza‐ tion. Layer 3 – Fraud-Prevention, human-activity verification (Non-Biometric) Layer 3 is an optional, configurable control designed to distinguish genuine human activity from automated or scripted input. It operates under a Zero-Custody data flow and does not capture or process identity, personal traits, or biometrics—therefore it does not constitute biometric authentication. When enabled, minimal motion vectors (cursor or stroke timing data) are transmitted without identifiers to a date-locked, version-controlled LLM1 model operating under validated change control. The model performs a deterministic, evidence-based comparison against fixed humanpattern thresholds and returns a binary PASS / FAIL signal. • Default mode (Regulatory / Produc‐ tion): Layer 3 operates in advisory mode. All results are logged but do not block anchoring. • Strict mode (Enterprise / Pilot): Anchoring pauses on FAIL and requires a deterministic second‐ ary verification (retry, OTP re-auth, or supervisor co-sign). • The reviewer may repeat the signing attempt under the same authenticated Ed25519 + HMAC session; every attempt and result is recorded in the session log. Layer 3 outputs are version-locked, non-adaptive, and retained for audit transparency. Its use strengthens fraud-prevention controls but is not required for regulatory compliance. Layers 1 and 2 alone (user Ed25519 + institutional HMAC) satisfy all 21 CFR Part 11 and Annex 11 esignature requirements. File Reference: Screenshot 2025-10-15 at 6.49.35 am___20251014T200505Z.png Timestamp (UTC): 20251014T200505Z SHA-256: 3ba9dc776084fcb8b6b5e0f40dcbbd2b2ed‐ b5143d6037dee78b4b79774e90b49 RIPEMD-160: 9a84b52e59a8b28d2efd5386ba066e358ec5a1a8 OTS File: Screenshot 2025-10-15 at 6.49.35 am___20251014T200505Z.png.hash.ots OTS SHA-256: 9713b2e0aa699eaf2e251abce001922fd0ffe3ec8aa3747d9d12634509eb3a79 OTS Bitcoin TXID: 5c28773f653c441226df3079bf1b37c662f6c3643a544840e43098cd2a75502f Block: 919084 Merkle Root (from OTS proof): 51d14a6b89b363557180530c51fa192a1cdd093edcd‐ c13fc828d2e855c985f18 Date of Existence (UTC): 2025-10-14T20:08:06Z (TXID broadcast time confirming file existence as of Bitcoin block 919084.) AuditLog.AI — Runtime Execution and System Validation Evidence End-to-End Operational Proof During Regulatory Global Submission | v4.0 | 2025-10-27 Page 52 of 102 AUDITLOG.AI0052DOSSIER Page 53 of 102 22. e-Signature Gate (Web UI Access) **File Reference:** `Screenshot 2025-10-15 at 6.49.35 am___20251014T200505Z.png` AUDITLOG.AI0053DOSSIER 23. Signature Validation (FAIL Test) Description: Strict mode (Enterprise / Pilot) demonstrating a negative-control test in which the Layer 3 human-activity verification returns a confidence score below threshold, producing a deterministic FAIL and blocking creation of the gate_job. The failed attempt is time-stamped and logged in zero-custody Vercel telemetry; no artifacts are generated or transmitted downstream. File Reference: Screenshot 2025-10-15 at 6.49.56 am___20251014T200505Z.png Timestamp (UTC): 20251014T200505Z SHA-256: 3f31d4e9c4c6303f14d23fe3d4c1e5ce96fe27e7a4ffb‐ be581d8cc337bd8fb9d RIPEMD-160: d10ee26cce112c80ef906f921d642f10fbae42f0 OTS File: Screenshot 2025-10-15 at 6.49.56 am___20251014T200505Z.png.hash.ots OTS SHA-256: 2c93a32c8f9d6534aa8e865fcc97ea059185178b6dd99b7fac4c874156c04f99 OTS Bitcoin TXID: 5c28773f653c441226df3079bf1b37c662f6c3643a544840e43098cd2a75502f Block: 919084 Merkle Root (from OTS proof): 51d14a6b89b363557180530c51fa192a1cdd093edcd‐ c13fc828d2e855c985f18 Date of Existence (UTC): 2025-10-14T20:08:06Z (TXID broadcast time confirming file existence as of Bitcoin block 919084.) AuditLog.AI — Runtime Execution and System Validation Evidence End-to-End Operational Proof During Regulatory Global Submission | v4.0 | 2025-10-27 Page 54 of 102 AUDITLOG.AI0054DOSSIER Page 55 of 102 **File Reference:** `Screenshot 2025-10-15 at 6.49.56 am___20251014T200505Z.png` 23. Signature Validation (FAIL Test) AUDITLOG.AI0055DOSSIER 24. Gate Job Not Generated by False Signature Description: Post-failure screenshot showing that no gate_job file was produced and no transmission oc‐ curred to CDA AI. Blockchain anchoring cannot proceed until a valid e-signature passes all layers. All failed validation events remain recorded within the zero-custody telemetry log, while only successful, human-verified e-signature events generate a gate_job JSON for regulated an‐ choring. File Reference: Screenshot 2025-10-15 at 6.49.56 am (2)___20251014T200505Z.png Timestamp (UTC): 20251014T200505Z SHA-256: 1725b1e60d3aef30c8f3f89f5f8f00280334d‐ b69651d655e5f7551d5d5c39be2 RIPEMD-160: 06ea45793c609d6674008ddb9475c8a44bcb509e OTS File: Screenshot 2025-10-15 at 6.49.56 am (2)___20251014T200505Z.png.hash.ots OTS SHA-256: 560da5db370d96ee143586d16173de35edabc059f58807e6a5f24de8a91ffffb OTS Bitcoin TXID: 5c28773f653c441226df3079bf1b37c662f6c3643a544840e43098cd2a75502f Block: 919084 Merkle Root (from OTS proof): 51d14a6b89b363557180530c51fa192a1cdd093edcd‐ c13fc828d2e855c985f18 Date of Existence (UTC): 2025-10-14T20:08:06Z (TXID broadcast time confirming file existence as of Bitcoin block 919084.) AuditLog.AI — Runtime Execution and System Validation Evidence End-to-End Operational Proof During Regulatory Global Submission | v4.0 | 2025-10-27 Page 56 of 102 AUDITLOG.AI0056DOSSIER Page 57 of 102 24. Gate Job Not Generated by False Signature **File Reference:** `Screenshot 2025-10-15 at 6.49.56 am (2)___20251014T200505Z.png` AUDITLOG.AI0057DOSSIER 28 A & B. Final Human Authorization Blockchain Anchoring Description: This screenshot captures the final human-authorization checkpoint preceding blockchain anchoring, a mandatory interactive step by anchor_candidate_cli_v6.1.py . Upon operator ap‐ proval, it derives the OP_RETURN payload from the frozen session log, and sends artifacts for final blockchain anchoring authorization to AuditLog.AI. At this stage, all prior validations, hash generation, VALIS enforcement, and compliance checks have passed. Anchoring cannot proceed automatically; the process is hard-gated by the Ed25519-signed authorization of a verified user (the same unique reviewer registered under the AuditLog.AI e-Signature Gate), and bound to intitutional HMAC login and meta ID. Only once this explicit approval is confirmed does the system flag the session as approved for broadcast, enabling immutable publication to the Bitcoin mainnet. File Reference 28 A: Screenshot 2025-10-15 at 6.51.51 am___20251014T200505Z.png Timestamp (UTC): 20251014T200505Z SHA-256: 4b910fe7662715c3300b8625c3f6700a496746a42f97b4298dfb77a0f1d934f1 RIPEMD-160: 1992ea22332ec4707597578a3f53d6e6721855d2 OTS File: Screenshot 2025-10-15 at 6.51.51 am___20251014T200505Z.png.hash.ots OTS SHA-256: cd‐ d32e33c10d0f7ed16c2c6e927e4f9d640e904f7bf0f86f2b2d85cbe25fc1ef OTS Bitcoin TXID: 5c28773f653c441226df3079bf1b37c662f6c3643a544840e43098cd2a75502f Block: 919084 Merkle Root (from OTS proof): 51d14a6b89b363557180530c51fa192a1cdd093edcd‐ c13fc828d2e855c985f18 Date of Existence (UTC): 2025-10-14T20:08:06Z (TXID broadcast time confirming file existence as of Bitcoin block 919084.) File Reference 28 B: Screenshot 2025-10-15 at 6.52.12 am___20251014T200505Z.png Timestamp (UTC): 20251014T200505Z SHA-256: 1d1e7c06f49f91910afcd6492687930587d54457b3c9126b743535910e632374 RIPEMD-160: 1fc5492096a855e9157e5e1d263467c49bebee19 OTS File: Screenshot 2025-10-15 at 6.52.12 am___20251014T200505Z.png.hash.ots OTS SHA-256: b8f4319b7969b37a1933688c0b84e7629e6465655db460e312776421a30335ff OTS Bitcoin TXID: 5c28773f653c441226df3079bf1b37c662f6c3643a544840e43098cd2a75502f Block: 919084 Merkle Root (from OTS proof): 51d14a6b89b363557180530c51fa192a1cdd093edcd‐ c13fc828d2e855c985f18 Date of Existence (UTC): 2025-10-14T20:08:06Z (TXID broadcast time confirming file existence as of Bitcoin block 919084.) AuditLog.AI — Runtime Execution and System Validation Evidence End-to-End Operational Proof During Regulatory Global Submission | v4.0 | 2025-10-27 Page 64 of 102 AUDITLOG.AI0064DOSSIER Page 65 of 102 28 A. Final Human Authorization Blockchain Anchoring **File Reference 28 A:** `Screenshot 2025-10-15 at 6.51.51 am___20251014T200505Z.png` AUDITLOG.AI0065DOSSIER Page 66 of 102 28 B. Final Human Authorization Blockchain Anchoring **File Reference 28 B:** `Screenshot 2025-10-15 at 6.52.12 am___20251014T200505Z.png` AUDITLOG.AI0066DOSSIER 29. Post-Final Authorization — Incoming Anchor Job Arrives at AuditLog.AI Node Description: AuditLog.AI receives the finalized user-approved handoff job from the user environment following successful e-signature gate verification (incoming_anchor JSON). File Reference: Screenshot 2025-10-15 at 6.52.12 am (2)___20251014T200505Z.png Timestamp (UTC): 20251014T200505Z SHA-256: 63b142f1ff7d59903d3b01d91ea752be3aa33ff2b9167f1b85e8608f66a0f003 RIPEMD-160: 65977b‐ ccac1119769e7d591ed13f62f7f23d3751 OTS File: Screenshot 2025-10-15 at 6.52.12 am (2)___20251014T200505Z.png.hash.ots OTS SHA-256: 94e94706a4a5fc‐ c85b1c56a5955c7d98b2cd3a314a79123da5642170c53a9d80 OTS Bitcoin TXID: 5c28773f653c441226df3079bf1b37c662f6c3643a544840e43098cd2a75502f Block: 919084 Merkle Root (from OTS proof): 51d14a6b89b363557180530c51fa192a1cdd093edcd‐ c13fc828d2e855c985f18 Date of Existence (UTC): 2025-10-14T20:08:06Z (TXID broadcast time confirming file existence as of Bitcoin block 919084.) AuditLog.AI — Runtime Execution and System Validation Evidence End-to-End Operational Proof During Regulatory Global Submission | v4.0 | 2025-10-27 Page 67 of 102 AUDITLOG.AI0067DOSSIER Page 68 of 102 **File Reference:** `Screenshot 2025-10-15 at 6.52.12 am (2)___20251014T200505Z.png` 29. Post-Final Authorization — Incoming Anchor Job Arrives at AuditLog.AI Node AUDITLOG.AI0068DOSSIER 30. AuditLog.AI Incoming Anchor Job Receipt Description: The handoff package contains only hashes and metadata, ensuring zero-custody compliance. File Reference: Screenshot 2025-10-15 at 6.52.44 am (2)___20251014T200505Z.png Timestamp (UTC): 20251014T200505Z SHA-256: 13a04cb81a8e3497b‐ b52b92de05d895b7eca87846fab8f8da9c450d1e10c09d8 RIPEMD-160: 2ca67a8e38c5b‐ c07492176a6fd60a25633aa6760 OTS File: Screenshot 2025-10-15 at 6.52.44 am (2)___20251014T200505Z.png.hash.ots OTS SHA-256: 034d9c54854307f9fd99f‐ b5005418c8ba6add13a80870388fb44919af2c766ce OTS Bitcoin TXID: 5c28773f653c441226d‐ f3079bf1b37c662f6c3643a544840e43098cd2a75502f Block: 919084 Merkle Root (from OTS proof): 51d14a6b89b363557180530c51fa192a1cdd093edcdc13fc828d2e855c985f18 Date of Existence (UTC): 2025-10-14T20:08:06Z (TXID broadcast time confirming file existence as of Bitcoin block 919084.) AuditLog.AI — Runtime Execution and System Validation Evidence End-to-End Operational Proof During Regulatory Global Submission | v4.0 | 2025-10-27 Page 69 of 102 AUDITLOG.AI0069DOSSIER Page 70 of 102 30. AuditLog.AI Incoming Anchor Job Receipt **File Reference:** `Screenshot 2025-10-15 at 6.52.44 am (2)___20251014T200505Z.png` AUDITLOG.AI0070DOSSIER 31. AuditLog.AI OP_RETURN Amplify Execution Description: Console output of opreturnanchor_amplify_v5.1.py executing Bitcoin transaction broadcast. This operation is only possible if incoming anchor job and gate job files are verified under CME Rules. Key compliance confirmations recorded in this event: - human_verified: true - ai_editor_LLM_human_agreement: true - VALIS_template_enforced: true - AI_override: false - timestamp_confirmed: true - The payload schema conforms to C5.3.1 OP_RETURN specification ( SENTINEL|<type>| <ripemd160>|<sha8> ) - session log hashes parity and .hash.ots presence are confirmed File Reference: Screenshot 2025-10-15 at 6.53.13 am (2)___20251014T200505Z.png Timestamp (UTC): 20251014T200505Z SHA-256: 301dd7c5b7358523d605fc‐ c8f28685503a14a3e44889a5905130994e8e87f240 RIPEMD-160: bd2b8bc14e1369682347825f‐ d7bec3150886b934 OTS File: Screenshot 2025-10-15 at 6.53.13 am (2)___20251014T200505Z.png.hash.ots OTS SHA-256: 75a6176d6a89e33d‐ d487992ee214f1cb573711f99de9a94a4f19f9720f3ecf53 OTS Bitcoin TXID: 5c28773f653c441226df3079bf1b37c662f6c3643a544840e43098cd2a75502f Block: 919084 Merkle Root (from OTS proof): 51d14a6b89b363557180530c51fa192a1cdd093edcd‐ c13fc828d2e855c985f18 Date of Existence (UTC): 2025-10-14T20:08:06Z (TXID broadcast time confirming file existence as of Bitcoin block 919084.) AuditLog.AI — Runtime Execution and System Validation Evidence End-to-End Operational Proof During Regulatory Global Submission | v4.0 | 2025-10-27 Page 71 of 102 AUDITLOG.AI0071DOSSIER Page 72 of 102 **File Reference:** `Screenshot 2025-10-15 at 6.53.13 am (2)___20251014T200505Z.png` 31. AuditLog.AI OP_RETURN Amplify Execution AUDITLOG.AI0072DOSSIER 32. Broadcasted On-Chain via Bitcoin Node — Amplifier Broadcast Event Description: Verified payload broadcasted. OP_RETURN transaction successfully constructed and submitted to Bitcoin mainnet. Confirm watcher ( confirm_watcher_v2.3.py ) registers broadcast and monit‐ ors for on-chain confirmation. File Reference: Screenshot 2025-10-15 at 6.53.33 am (2)___20251014T200505Z.png Timestamp (UTC): 20251014T200505Z SHA-256: e2b3f3b325cc6e2a9fe03bb1b304ff1b‐ b457c0ce3a6fde11b96f996f0774eb17 RIPEMD-160: 597fbbec6aa47d611da8d09e62983031feaea30d OTS File: Screenshot 2025-10-15 at 6.53.33 am (2)___20251014T200505Z.png.hash.ots OTS SHA-256: 6f57096699dd99448da03d1a6c691d8395a5eb5d8535cb34120e1e79a8731be6 OTS Bitcoin TXID: 5c28773f653c441226df3079bf1b37c662f6c3643a544840e43098cd2a75502f Block: 919084 Merkle Root (from OTS proof): 51d14a6b89b363557180530c51fa192a1cdd093edcd‐ c13fc828d2e855c985f18 Date of Existence (UTC): 2025-10-14T20:08:06Z (TXID broadcast time confirming file existence as of Bitcoin block 919084.) AuditLog.AI — Runtime Execution and System Validation Evidence End-to-End Operational Proof During Regulatory Global Submission | v4.0 | 2025-10-27 Page 73 of 102 AUDITLOG.AI0073DOSSIER Page 80 of 102 **File Reference:** `Screenshot 2025-10-15 at 6.55.57 am (2)___20251014T200505Z.png` 35. Anchor Confirmation Watcher AUDITLOG.AI0080DOSSIER 36. Anchored Transaction – Public Explorer View #1 Description: Explorer screenshot (mempool.space) showing confirmed Bitcoin transaction and OP_RETURN payload. Demonstrates public immutability of the anchor proof and final block inclusion. - No identifiers are published, only hashes, ensuring complete user anonymity. - Blockchain confirmation independently verified; external audit reference established. File Reference: Screenshot 2025-10-15 at 6.54.53 am___20251014T200505Z.png Timestamp (UTC): 20251014T200505Z SHA-256: 4e38d40a89af59ed‐ b96ead6d17c611421c2180558531b14e03f4ac8640b9d73d RIPEMD-160: b237b71251d0d‐ b6c71ecd83aeea94a591b1f3c8e OTS File: Screenshot 2025-10-15 at 6.54.53 am___20251014T200505Z.png.hash.ots OTS SHA-256: d6357e9de8411f16028baa55ad715b37e6f5b5130cbc9d7dd797ca48405132f6 OTS Bitcoin TXID: 5c28773f653c441226df3079bf1b37c662f6c3643a544840e43098cd2a75502f Block: 919084 Merkle Root (from OTS proof): 51d14a6b89b363557180530c51fa192a1cdd093edcd‐ c13fc828d2e855c985f18 Date of Existence (UTC): 2025-10-14T20:08:06Z (TXID broadcast time confirming file existence as of Bitcoin block 919084.) AuditLog.AI — Runtime Execution and System Validation Evidence End-to-End Operational Proof During Regulatory Global Submission | v4.0 | 2025-10-27 Page 81 of 102 AUDITLOG.AI0081DOSSIER Page 82 of 102 36. Anchored Transaction – Public Explorer View #1 **File Reference:** `Screenshot 2025-10-15 at 6.54.53 am___20251014T200505Z.png` AUDITLOG.AI0082DOSSIER 37. Anchored Transaction – Public Explorer View #2 Description: Alternate blockchain-explorer confirmation (blockchain.com). Displays block height, TXID, payload, and confirmation. Cross-verified confirmation validates network-level reproducibility and external traceability. File Reference: Screenshot 2025-10-15 at 6.56.10 am___20251014T200505Z.png Timestamp (UTC): 20251014T200505Z SHA-256: 498dd0c8a5248f1704b5d5ab01476851a7984b‐ b4f787b3b2699d7298acab26d9 RIPEMD-160: 7e4dbc52d2f4cfd95d2a402f7fea1b7bf8ca5ec0 OTS File: Screenshot 2025-10-15 at 6.56.10 am___20251014T200505Z.png.hash.ots OTS SHA-256: f46e0defff2e9423baffa220fc5adc479c3c4021e9c9c1a5f79d538f0b0135ec OTS Bitcoin TXID: 5c28773f653c441226df3079bf1b37c662f6c3643a544840e43098cd2a75502f Block: 919084 Merkle Root (from OTS proof): 51d14a6b89b363557180530c51fa192a1cdd093edcd‐ c13fc828d2e855c985f18 Date of Existence (UTC): 2025-10-14T20:08:06Z (TXID broadcast time confirming file existence as of Bitcoin block 919084.) AuditLog.AI — Runtime Execution and System Validation Evidence End-to-End Operational Proof During Regulatory Global Submission | v4.0 | 2025-10-27 Page 83 of 102 AUDITLOG.AI0083DOSSIER Page 84 of 102 **File Reference:** `Screenshot 2025-10-15 at 6.56.10 am___20251014T200505Z.png` 37. Anchored Transaction – Public Explorer View #2 AUDITLOG.AI0084DOSSIER 38. Session Log Digest Match Validation Description: Screenshot demonstrating parity between session log digests and anchored OP_RETURN pay‐ load components (RIPEMD-160, sha8). Confirms that on-chain values match the exact bytes of the frozen session log JSON. Proves deterministic linkage between audit session, including all audit logs and each evidence file, to public blockchain record. File Reference: Screenshot 2025-10-15 at 6.55.33 am___20251014T200505Z.png Timestamp (UTC): 20251014T200505Z SHA-256: 9ae00b9b0442b02f06446a3d3d7432bfe26bf52d661e35af‐ b214862caa2e77cd RIPEMD-160: 3b529fa672f8614453b99d8c76241c0a0d28de01 OTS File: Screenshot 2025-10-15 at 6.55.33 am___20251014T200505Z.png.hash.ots OTS SHA-256: 417cb4aba1ab799655c7e023db89f926d1472b43b092a87102c58e0e1b880c76 OTS Bitcoin TXID: 5c28773f653c441226df3079bf1b37c662f6c3643a544840e43098cd2a75502f Block: 919084 Merkle Root (from OTS proof): 51d14a6b89b363557180530c51fa192a1cdd093edcd‐ c13fc828d2e855c985f18 Date of Existence (UTC): 2025-10-14T20:08:06Z (TXID broadcast time confirming file existence as of Bitcoin block 919084.) AuditLog.AI — Runtime Execution and System Validation Evidence End-to-End Operational Proof During Regulatory Global Submission | v4.0 | 2025-10-27 Page 85 of 102 AUDITLOG.AI0085DOSSIER Page 86 of 102 38. Session Log Digest Match Validation **File Reference:** `Screenshot 2025-10-15 at 6.55.33 am___20251014T200505Z.png` AUDITLOG.AI0086DOSSIER 39. Dual-Ledger Consistency Verification Description: Illustrates cross-comparison of dual ledgers, demonstrating atomic consistency between AMPLI‐ FY and user (AuditLog.AI held copy) ledgers. This demonstrates no discrepancies in TXID, payload, or events, supporting reliable reproducibility. It provides evidence for regulatory inspection of ledger parity (parity check = equality on {event, txid, payload} across AMPLIFY and user ledgers). File Reference: Screenshot 2025-10-15 at 6.57.55 am (2)___20251014T200505Z.png Timestamp (UTC): 20251014T200505Z SHA-256: 0fec999b3fb5bba6434ab25f65d09e778db5e‐ b63f946cd1f463225c64892455b RIPEMD-160: 034abe9c56191194293f57471084e102564101a1 OTS File: Screenshot 2025-10-15 at 6.57.55 am (2)___20251014T200505Z.png.hash.ots OTS SHA-256: f7f338658c60c811fc2426b155da7e473a7aea71b1abfa2f3bbffd8acf9802a7 OTS Bitcoin TXID: 5c28773f653c441226df3079bf1b37c662f6c3643a544840e43098cd2a75502f Block: 919084 Merkle Root (from OTS proof): 51d14a6b89b363557180530c51fa192a1cdd093edcd‐ c13fc828d2e855c985f18 Date of Existence (UTC): 2025-10-14T20:08:06Z (TXID broadcast time confirming file existence as of Bitcoin block 919084.) AuditLog.AI — Runtime Execution and System Validation Evidence End-to-End Operational Proof During Regulatory Global Submission | v4.0 | 2025-10-27 Page 87 of 102 AUDITLOG.AI0087DOSSIER Page 88 of 102 **File Reference:** `Screenshot 2025-10-15 at 6.57.55 am (2)___20251014T200505Z.png` 39. Dual-Ledger Consistency Verification AUDITLOG.AI0088DOSSIER 40. Pull Anchor Artifacts and Log Audit Description: Depicts retrieval of anchored artifacts via pull_anchor_artifacts_v2.py , updating operator's local ledger against AuditLog.AI-held user ledger. This validates successful synchronization and integrity of receipts between user and AuditLog.AI ledgers. File Reference: Screenshot 2025-10-15 at 6.59.14 am___20251014T200505Z.png Timestamp (UTC): 20251014T200505Z SHA-256: b799d19ed11bed‐ b4295c4eed41647fc1e85a0c20d732272b34606580a4d4d554 RIPEMD-160: 88cd‐ b8705614a357f14c44467e8f9669c9f324a6 OTS File: Screenshot 2025-10-15 at 6.59.14 am___20251014T200505Z.png.hash.ots OTS SHA-256: 1f33316c86a23e0661d7e80f22f6028f0cfe4abc2241349024479a0397e124bb OTS Bitcoin TXID: 5c28773f653c441226df3079bf1b37c662f6c3643a544840e43098cd2a75502f Block: 919084 Merkle Root (from OTS proof): 51d14a6b89b363557180530c51fa192a1cdd093edcd‐ c13fc828d2e855c985f18 Date of Existence (UTC): 2025-10-14T20:08:06Z (TXID broadcast time confirming file existence as of Bitcoin block 919084.) AuditLog.AI — Runtime Execution and System Validation Evidence End-to-End Operational Proof During Regulatory Global Submission | v4.0 | 2025-10-27 Page 89 of 102 AUDITLOG.AI0089DOSSIER Excerpt 02: Open Disclosure of Duplicate non-evidence screenshots Duplicate non-evidence screenshots detected during the hash integrity audit. Identic‐ al screenshot sets: - set01: `Screenshot 2025-10-15 at 6.36.49 am (2)___20251014T200505Z.png` and `Screenshot 2025-10-15 at 6.37.46 am (2)___20251014T200505Z.png` - set02: `Screenshot 2025-10-15 at 6.44.37 am (2)___20251014T200505Z.png` and `Screenshot 2025-10-15 at 6.44.02 am (2)___20251014T200505Z.png` and `Screenshot 2025-10-15 at 6.42.52 am (2)___20251014T200505Z.png` - set03: `Screenshot 2025-10-15 at 6.37.00 am (2)___20251014T200505Z.png` an `Screen‐ shot 2025-10-15 at 6.37.14 am (2)___20251014T200505Z.png` These sets have been identified as byte-identical, producing the same SHA-256 and RIPEMD-160 digests. Root cause: duplicate screenshots sets were automatically captured by macOS’s fullscreen capture function across a dual-monitor setup while the operator guidance run‐ book window was maximized on non-evidence secondary monitor view. Because no visual differences (e.g., clock, cursor, or secondary content) existed between the two frames, the resulting image files are identical at the binary level. Regulatory relevance: These image sets do not represent distinct evidence events. They are background cap‐ tures from the operator’s execution environment and are not part of the dossier evid‐ ence set submitted for regulatory review. Their inclusion in the manifest reflects full-disclosure of automated capture and batch hashing of all session artifacts, not intentional duplication of audit content. Integrity handling: Files remain hashed and timestamped within the session manifest for reproducibility. Their duplication has no material effect on validation integrity or cryptographic audit completeness. The event has been disclosed for full transparency as `Non_evidence_Screenshots_identical_set01.pdf`, `Non_evidence_Screenshots_identical_set02.pdf` and `Non_evidence_Screenshots_identical_set03.pdf`. Provenance Session_log: session_log_AuditLogAI.REG.GlobalSubmission.v4038_20251018T214519.997259Z.json Session Meta_id: AuditLogAI.REG.GlobalSubmission.v4038 Timestamp (UTC): 20251018T214519.997259Z SHA-256: 5af54564b05e7ae9c8e6b4c918ca19586ca3c7e58af6b72806‐ fa08603b27e844 RIPEMD-160: fb5e9fa9e3873fe2236eaf1c60c4fc7dd0968c5a OTS File: ses‐ sion_log_AuditLogAI.REG.GlobalSubmission.v4038_20251018T214519.997259Z.hash.ots OTS SHA-256: 40f3a9bf146ba3294bf682eeb260bfbe7eb3813c9f313660fcda89499c518b33 OTS Bitcoin TXID: 0fec86753224355204bf6a4e9ef0106302a2a597c116236279ab5ce44484f0b7 Block: 919723 Merkle Root (from OTS proof): a460deac9d9a2027e72bf90a137786d5b29bb83b4d144868671032e‐ f724ff990 Date of Existence (UTC): 2025-10-18T22:40:46Z (TXID broadcast time confirming file existence as of Bitcoin block 919723.) AuditLog.AI — Runtime Execution and System Validation Evidence End-to-End Operational Proof During Regulatory Global Submission | v4.0 | 2025-10-27 Page 96 of 102 AUDITLOG.AI0096DOSSIER OP_RETURN Anchor Transaction ID: 11fb255046a7934e5c978b3d0887318f85af3324b040873ce6026fea6c8af13d Pay‐ load: SENTINEL|SESSION|fb5e9fa9e3873fe2236eaf1c60c4fc7dd0968c5a|5af54564 Block: 919720 Evidence File: AUDIT_REPRODUCIBILITY_PASS_sha256_ripemd160_AuditLog.AI_v.oct18.25___20251018T214357Z.m d Linked manifest: manifest_markdown_to_pdf_conversions_REGULATORY-RUN-20251018-S02.csv SHA-256: 7966a393ec2798dd609074e99249cb61d7c9220ad3a7e128398f5ed4c7b9e051 RIPEMD-160: 7f15cad8acc59548a6eb256f38196db6e8474c79 OTS File: AUDIT_REPRODUCIBILITY_PASS_sha256_ripemd160_AuditLog.AI_v.oct18.25___20251018T214357Z.m d.hash.ots OTS SHA-256: 06343134dd0ff461af9d422c59de0a0c8607855aaa203c‐ c2f87549afe54a6b3d OTS Bitcoin TXID: 0fec86753224355204bf6a4e9e‐ f0106302a2a597c116236279ab5ce44484f0b7 Block: 919723 Merkle Root (from OTS proof): a460deac9d9a2027e72bf90a137786d5b29bb83b4d144868671032ef724ff990 Date of Existence (UTC): 2025-10-18T22:40:46Z (TXID broadcast time confirming file existence as of Bitcoin block 919723.) AuditLog.AI — Runtime Execution and System Validation Evidence End-to-End Operational Proof During Regulatory Global Submission | v4.0 | 2025-10-27 Page 97 of 102 AUDITLOG.AI0097DOSSIER Provenance AuditLog.AI — Runtime Execution and System Validation Evidence End‑to‑End Operational Proof During Regulatory Global Submission Linked Runtime Scripts User Node: (/frozen_files_Validated_AuditLog.AI_v.12sep.25_REGULATORY-RUN-20251017S12/User_scripts) - anchor_candidate_cli_v6.1___20251017T200502Z.py - an‐ chor_receipt_logger_v4___20251017T200502Z.py - as‐ sert_verified_gate_job___20251017T200502Z.py - audit_verify_v1.2___20251017T200502Z.py - auditlogger___20251017T200502Z.py - batch_dualhasher_multi_v3.3___20251017T200502Z.py - batch_ots_stamper_v2___20251017T200502Z.py - batch_ots_upgrader_v2.1___20251017T200502Z.py - human_verifier___20251017T200502Z.py - pull_anchor_artifacts_v2___20251017T200502Z.py - screen‐ shot_handoff_cli_v2___20251017T200502Z.py - session_logger___20251017T200502Z.py - val‐ is_batchauditlogger_template_v3.1___20251017T200502Z.py - val‐ is_batchnameverifier_v2___20251017T200502Z.py AuditLog.AI Node: (/frozen_files_Validated_AuditLog.AI_v.12sep.25_REGULATORYRUN-20251017-S04/CDAAI_scripts) - anchor_api_v2___20251017T200502Z.py - con‐ firm_watcher_v2.3___20251017T200502Z.py - gate_ingest_api_v2___20251017T200502Z.py - opreturnanchor_amplify_v5.1___20251017T200502Z.py Shared - compliance_enforcer___20251017T200502Z.py - gate_manager___20251017T200502Z.py - hashvalidatorblock___20251017T200502Z.py Interface: (/frozen_files_Validated_AuditLog.AI_v.12sep.25_REGULATORY-RUN-20251017-) - Vercel UI: AuditLog.AI e‑Signature Gate Provenance Session_log: session_log_AuditLogAI.REG.GlobalSubmission.v4020_20251014T200606.551974Z.json Session Meta_id: AuditLogAI.REG.GlobalSubmission.v4020 Timestamp (UTC): 20251014T200606.551974Z SHA-256: 5c009fb3e680ca41e0e17aefe3bc931ec00b195e8faa0eb3f546d059930b0724 RIPEMD-160: 041cf98418a6ae39dbcc5d3e49e60a06a5112993 • • • • AuditLog.AI — Runtime Execution and System Validation Evidence End-to-End Operational Proof During Regulatory Global Submission | v4.0 | 2025-10-27 Page 98 of 102 AUDITLOG.AI0098DOSSIER OTS File: ses‐ sion_log_AuditLogAI.REG.GlobalSubmission.v4020_20251014T200606.551974Z.hash.ot s OTS SHA-256: c26576aaa708bdb17285f011d1d9c7880a3e5f8f334d2a64ebc2511b‐ f2f12c2a OTS Bitcoin TXID: 5c28773f653c441226df3079b‐ f1b37c662f6c3643a544840e43098cd2a75502f Block: 919084 Merkle Root (from OTS proof): 51d14a6b89b363557180530c51fa192a1cdd093edcd‐ c13fc828d2e855c985f18 Date of Existence (UTC): 2025-10-14T20:08:06Z (TXID broadcast time confirming file existence as of Bitcoin block 919084.) OP_RETURN Anchor Transaction ID: d096197e02a8f1ac9ca7da43d353f109fe4ff72f6ae7f88b39c83877247e9ef7 Pay‐ load: SENTINEL|SESSION|041cf98418a6ae39dbcc5d3e49e60a06a5112993|5c009fb3 Block: 919084 Audit_log: audit_log_AuditLogAI.REG.GlobalSubmission.v4025_20251014T200556.273909Z.json Linked Dossier Evidence: 3-20, 22-23, 25, 28, 34, 36-38, 40-41 Linked manifest: manifest_User_REGULATORY-RUN-20251014-S02.csv SHA-256: 1c9f6e2cc1ff9ce1e615cca36083a3a558468edccefcdd19b86dca3ff082897c RIPEMD-160: 56ee6f1e48405a6ca6ef5fda34e842525c06f199 OTS File: audit_log_AuditLogAI.REG.GlobalSubmission.v4025_20251014T200556.273909Z.hash.o ts OTS SHA-256: 1323e7ab0aa18f63d8ffa051cfee88121941aaa658184de‐ b60e2d8b79ba79a3d OTS Bitcoin TXID: 5c28773f653c441226df3079b‐ f1b37c662f6c3643a544840e43098cd2a75502f Block: 919084 Merkle Root (from OTS proof): 51d14a6b89b363557180530c51fa192a1cdd093edcd‐ c13fc828d2e855c985f18 Date of Existence (UTC): 2025-10-14T20:08:06Z (TXID broadcast time confirming file existence as of Bitcoin block 919084.) Audit_log: audit_log_AuditLogAI.REG.GlobalSubmission.v4024_20251014T200552.935806Z.json Linked Dossier Evidence: 24, 26-27, 29-33, 35, 39 Linked manifest: manifest_CDAAI_REGULATORY-RUN-20251014-S01.csv SHA-256: 62a3b9a89b4a812027fabf29492f4cefe408cc6e78db5ab07f0f9cd9eef16770 RIPEMD-160: d0c075e79ef8d55d3b6a4eb2c9a753c209c7e96e • • • • • • • • • • • • • • • • • • AuditLog.AI — Runtime Execution and System Validation Evidence End-to-End Operational Proof During Regulatory Global Submission | v4.0 | 2025-10-27 Page 99 of 102 AUDITLOG.AI0099DOSSIER OTS File: audit_log_AuditLogAI.REG.GlobalSubmission.v4024_20251014T200552.935806Z.hash.o ts OTS SHA-256: 5c28773f653c441226df3079b‐ f1b37c662f6c3643a544840e43098cd2a75502f OTS Bitcoin TXID: c355bc2b7d88d70ffd5bd6745cfdc40aa348cd8b3b34dfb7adec‐ c853c9486ddb Block: 919084 Merkle Root (from OTS proof): 51d14a6b89b363557180530c51fa192a1cdd093edcd‐ c13fc828d2e855c985f18 Date of Existence (UTC): 2025-10-14T20:08:06Z (TXID broadcast time confirming file existence as of Bitcoin block 919084.) Provenance Session_log: session_log_AuditLogAI.REG.GlobalSubmission.v4016_20251014T194515.612758Z.json Session Meta_id: AuditLogAI.REG.GlobalSubmission.v4016 Timestamp (UTC): 20251014T194515.612758Z SHA-256: 2b44af1d4888f598c89dec992b6ce31d6fc0daab7a2480a3efb07d44bf3eb055 RIPEMD-160: f63523aba83a6b47c8fbb5dd942d20ef6aa7ee3e OTS File: ses‐ sion_log_AuditLogAI.REG.GlobalSubmission.v4016_20251014T194515.612758Z.hash.ot s OTS SHA-256: c6df3b2bf6a8b3e13c40f2139f61b2d‐ d7440b8e2a10a321c86b891b3626c2c0b OTS Bitcoin TXID: 10e650706acadd74115a38042becea8c‐ cbe58eac7146a9d1c9193ed027ca8cb7 Block: 919083 Merkle Root (from OTS proof): 416d0f316dec37bdbccdfb142775154e704a203ed41c94dcf10765dce6f7a4fa Date of Existence (UTC): 2025-10-14T19:56:06Z (TXID broadcast time confirming file existence as of Bitcoin block 919083.) OP_RETURN Anchor Transaction ID: 9a46014d657726798449cc6282de083e2084afc87aa5f23233903396d73b8d4f Pay‐ load: SENTINEL|SESSION|f63523aba83a6b47c8fbb5dd942d20ef6aa7ee3e|2b44af1d Block: 919082 Audit_log: audit_log_AuditLogAI.REG.GlobalSubmission.v4020_20251014T194300.697140Z.json Linked Dossier Evidence: 2 Linked manifest: manifest_CDAAI_PreExecution_FolderView_REGULATORYRUN-20251014-S01.csv • • • • • • • • • • • • • • • • AuditLog.AI — Runtime Execution and System Validation Evidence End-to-End Operational Proof During Regulatory Global Submission | v4.0 | 2025-10-27 Page 100 of 102 AUDITLOG.AI0100DOSSIER SHA-256: 22b4c889342ce49df6919cfe2031e514f8dcd4c919bc01f5de46a1d11f3d4e59 RIPEMD-160: cffc255cfe7d5441891a576f21fb99ddbc8c75b2 OTS File: audit_log_AuditLogAI.REG.GlobalSubmission.v4020_20251014T194300.697140Z.hash.o ts OTS SHA-256: b38543beb8fdc0b362e137fe0240cf8e‐ f76c3a421f6d3406b215c392862a68fc OTS Bitcoin TXID: 10e650706acadd74115a38042becea8c‐ cbe58eac7146a9d1c9193ed027ca8cb7 Block: 919083 Merkle Root (from OTS proof): 416d0f316dec37bdbccdfb142775154e704a203ed41c94dcf10765dce6f7a4fa Date of Existence (UTC): 2025-10-14T19:56:06Z (TXID broadcast time confirming file existence as of Bitcoin block 919083.) Audit_log: audit_log_AuditLogAI.REG.GlobalSubmission.v4023_20251014T194425.352577Z.json Linked Dossier Evidence: 1 Linked manifest: manifest_USER_PreExecution_FolderView_REGULATORYRUN-20251014-S04.csv SHA-256: dc842dee4ea7381c213e18064a7303b0b092c98d1e15e07fe4f95bcfaa810238 RIPEMD-160: 76a1ae67e00ba9f604a23dc65e4e7b66dc557099 OTS File: audit_log_AuditLogAI.REG.GlobalSubmission.v4023_20251014T194425.352577Z.hash.o ts OTS SHA-256: 67a307877305241369ba4e69e4f9e495554652bcc188249d29441f2f‐ d7883f4d OTS Bitcoin TXID: 10e650706acadd74115a38042becea8c‐ cbe58eac7146a9d1c9193ed027ca8cb7 Block: 919083 Merkle Root (from OTS proof): 416d0f316dec37bdbccdfb142775154e704a203ed41c94dcf10765dce6f7a4fa Date of Existence (UTC): 2025-10-14T19:56:06Z (TXID broadcast time confirming file existence as of Bitcoin block 919083.) Provenance Session_log: session_log_AuditLogAI.REG.GlobalSubmission.v4009_20251013T034508.120256Z.json Session Meta_id: AuditLogAI.REG.GlobalSubmission.v4009 Timestamp (UTC): 20251013T034508.120256Z SHA-256: 862010c85fda0bfb02be23bb4316eea13966d374e60baa271f6292ef9416604b RIPEMD-160: 7e37072aeb1f857fb3245d9cdadc80356ff8563f • • • • • • • • • • • • • • • • • • • • AuditLog.AI — Runtime Execution and System Validation Evidence End-to-End Operational Proof During Regulatory Global Submission | v4.0 | 2025-10-27 Page 101 of 102 AUDITLOG.AI0101DOSSIER OTS File: ses‐ sion_log_AuditLogAI.REG.GlobalSubmission.v4009_20251013T034508.120256Z.hash.ot s OTS SHA-256: aa327f72e2799c98a4f1ea5ff83cda1fc2cf4b9670d90072d865f9c‐ fa53d6bfd OTS Bitcoin TXID: eabcee5e6fffeb6fc6b3c7807165ae863b383f‐ b8459aa0d311726026302ef0e9 Block: 918813 Merkle Root (from OTS proof): f161f7b058a1156af142f50a5dc6952b97d2d‐ c897d4e912d6b68dd8119704744 Date of Existence (UTC): 2025-10-12T17:07:56Z (TXID broadcast time confirming file existence as of Bitcoin block 918813.) OP_RETURN Anchor Transaction ID: 413a692f24f58970cf72fdabec58095d2b7599b5cb1325303cc6d19ec89ddb01 Pay‐ load: SENTINEL|SESSION|7e37072aeb1f857fb3245d9cdadc80356ff8563f|862010c8 Block: 918808 Audit_log: audit_log_AuditLogAI.REG.GlobalSubmission.v4007_20251013T034321.999677Z.json Linked Dossier Evidence: 21 Linked manifest: manifest_AuditLog.AI_Human_gate_REGULATORY-RUN-20251013S02.csv SHA-256: e5b5aa84b5a8c910bf69bc14c0030c21bd42fa84efaacff955f7a395ac86207d RIPEMD-160: 8376fb437f11e1d2bc2eb147363b7f1a88205d5f OTS File: audit_log_AuditLogAI.REG.GlobalSubmission.v4007_20251013T034321.999677Z.hash.o ts OTS SHA-256: c6a9707074f416ee292249f1dbb26a55be5a1c2dd676bc40ae7ba64bfeb‐ d8abb OTS Bitcoin TXID: eabcee5e6fffeb6fc6b3c7807165ae863b383f‐ b8459aa0d311726026302ef0e9 Block: 918813 Merkle Root (from OTS proof): f161f7b058a1156af142f50a5dc6952b97d2d‐ c897d4e912d6b68dd8119704744 Date of Existence (UTC): 2025-10-12T17:07:56Z (TXID broadcast time confirming file existence as of Bitcoin block 918813.) • • • • • • • • • • • • • • AuditLog.AI — Runtime Execution and System Validation Evidence End-to-End Operational Proof During Regulatory Global Submission | v4.0 | 2025-10-27 Page 102 of 102 AUDITLOG.AI0102DOSSIER