AURiX WHITEPAPER: Suite Architecture v2 ================================================================================ Title: The AURiX Suite — 5 Browser Instruments + 7 Desktop Apps, Their Temporal Windows, and Their FWF Positions Author: AURiX Protocol | 2026-05-06 (v2.2 — Glimpse added; v2.1 superseded 2026-04-30; v2 superseded 2026-04-21 baseline) Status: Supersedes AURiX_WP_Instrument_Coverage (archived 2026-04-21). Coverage narrative was written against an "8 instruments" framing with Lens active and no Receipt / Anonymize / SELFiX / Record entries. v2 rebuilt the coverage story on a 5 + 6 enumeration; v2.1 (2026-04-30) extended to 5 + 7 with Soil, the substrate-fertility instrument named after Aaron-ratification of naming-cohesion scrutiny; v2.2 (2026-05-06) extends to 5 + 8 with Glimpse, the substrate-visualization instrument that renders JSONL ledgers as self-contained HTML chart pages — native replacement for shopped-out chart rendering. Authoritative enumeration lives at /AURiX/extensions_shared/SUITE_MANIFEST.json; prose here is downstream. ================================================================================ ABSTRACT The AURiX protocol ships as thirteen instruments across two deployment surfaces: five browser-side (Gauge, Scope, Trace, Ledger, Receipt), eight desktop-side (AUDiT, reClaim, Answer, Anonymize, SELFiX, Record, Soil, Glimpse). Each operates in a distinct temporal window and contributes to a specific phase of the engine triad (FWF: Find Fracture First / Helper Who Helps / Fair Finds Fair). Together they cover the 600-signal inventory across 26 mechanism families plus substrate-state observation and substrate-state visualization. This paper describes each instrument's role, its temporal grain, its FWF position, and how the pieces compose. INTRODUCTION A user interacting with a digital system encounters observable mechanisms distributed across time. Before engagement: the surface is presented. During engagement: state changes fire. As engagement unfolds: paths emerge, DOM mutates, storage writes. After engagement: records can be recovered and queried. The AURiX suite partitions this temporal territory into twelve specialized instruments, each seeing a different window and surfacing a different subset of the 600 signals. Separately, each is specialized enough to operate without interpretation. Together, they are exhaustive. The partition is not arbitrary. Each instrument sits in one of three FWF categories, enforcing the boundary rule: detection does not recommend, equipment does not force, protocol does not judge. ================================================================================ BROWSER INSTRUMENTS — FIVE, LOAD-UNPACKED CHROME EXTENSIONS ================================================================================ 1. GAUGE — real-time state, 15 families, tiered detection Gauge measures the current state of the page at the moment of observation. Three detection tiers: Tier 0 runs on every page, always on, <5ms. Cheap checks: scroll lock, major overlay, focus trap. Tier 1 samples broader signal set on user interaction (click, scroll, input). 10-20ms, background. Tier 2 runs on explicit user request — the right-click gesture. Full traversal of all 15 families in 50-100ms. Gauge absorbs the overlay-detection work that was formerly Lens, and the page-load baseline capture that was formerly a separate Scope function. The tiering makes Gauge cheap in the common case (most pages are clean on Tier 0) and deep when the user asks for depth (Tier 2 is the right-click). FWF: Find Fracture First. 2. SCOPE — compositor, worst-state-wins, traffic-light cursor Scope is a compositor, not a detector. It reads the current state outputs from sibling instruments (Gauge, Trace, Ledger, Receipt), applies the worst-state-wins rule, and renders a single visual signal: filled green circle (Stable), hollow yellow circle (Uncertain), upward red triangle (Fracture). The composition rule is declared, deterministic, mechanical: two implementations of the same rule produce identical output given identical inputs. Scope ignites at right-click — single root "AURiX" entry on every Chrome context. Submenu items are mechanism-reports wearing action verbs. This is the canonical interaction model: users learn structural literacy through a gesture they already make 100× a day (sleeper teach). FWF: Find Fracture First (composition is still detection). 3. TRACE — navigation path, redirect chains, 5 families Trace records the user's navigation as it unfolds. URL transitions, redirect chains with sources, cross-origin moves with referrer headers, history manipulation (pushState/replaceState), frame navigation via postMessage, form submission targets and methods. Trace is temporal: it builds a record of state transitions, not a snapshot. FWF: Find Fracture First. 4. LEDGER — state diffs over time, 7 families, Exterminator aggregator Ledger watches for changes and records them with temporal ordering: DOM mutations, style changes, script-injected content, resource loading completion, storage writes, viewability changes. A complete record, not a sample. Replayable. Ledger also serves as the Exterminator aggregator: sibling extensions (Gauge, Scope, Trace, Receipt) push error events to Ledger via chrome.runtime externally_connectable messaging. Ledger surfaces them in its Events/Errors tab. Single setup (configure Ledger's extension ID once across siblings), permanent aggregation thereafter. FWF: Find Fracture First (with Exterminator cross-cutting function). 5. RECEIPT — lightweight permission/consent logger, session-scoped Receipt tracks permission grants, consent choices, auth state changes. Browser-side, ephemeral, always-on. Small. When a page requests camera access, declares a consent banner, or transitions session state, Receipt logs the event with timing and source. The artifact is the event record. The instrument itself lives alongside Gauge with negligible overhead. Note on naming: "Receipt" (the instrument, browser-side) is distinct from "receipt" (artifact) and from what used to be called "Receipt Builder" (now AUDiT, desktop-side, heavyweight). FWF: Find Fracture First. ================================================================================ DESKTOP APPS — SEVEN, ON-DEMAND OR SCHEDULED ================================================================================ 1. AUDiT — full entry-point attestation, locked grammar (in design) AUDiT binds a specific moment using the locked grammar: Impetus → Encounter → Observed State → Extent. Desktop app. Full URL scan: TLS, redirects, security headers, tracking scripts, external resources, forms, inline scripts. Outputs a JSON receipt (machine-readable, SHA-256 content hash) and a PDF report (human-readable). Rose gold / beige accent color per design language. FWF: Helper Who Helps. The artifact equips the user for whatever comes next (dispute, compliance, evidence). 2. reClaim — archive recovery (shipped) reClaim transforms unstructured archives into structured searchable text. Input: ChatGPT exports, conversation logs, other conversational archives. Output: clean text files plus structured metadata (timestamps, speakers, thread boundaries, title inference). Shipped as reclaim_app.exe (Windows) and as current/reclaim_v2.py (library). Gold accent color. FWF: Helper Who Helps. 3. ANSWER (:A) — corpus interrogation (shipped) Answer loads structured text (from reClaim or any source) and searches with three modes: exact (literal match), normalized (case/whitespace-insensitive), candidate (fuzzy and co-located). Session tray, export, batch display. Shorthand :A in text; "Answer" spoken aloud. A property worth noting: on a one-author corpus (like Aaron's conversational history), collocation splits make word-drift legible. The tool wasn't built as a self-mirror, but on single-author material it becomes one. The lexicon mode is an obvious future build. FWF: Helper Who Helps. 4. ANONYMIZE — sector-grade safe release (shipped; v1 GUI + v2 CLI) Anonymize prepares corpora for release without exposing identifying content. v1 is a personal Tkinter GUI doing key-based string replacement (preserved as the lightest-touch profile). v2 is a CLI / library with pluggable layers: - Detection: key-based, PII regex (SSN, email, phone, credit card, IP, URL, bank, medical record numbers), capitalized-word heuristic, ISO / written / relative date detection, quasi-identifier clustering (age + ZIP + occupation + gender → re-ID risk). - Replacement: direct alias (v1 behavior), generalization (date ranges, geographic regions, age brackets), suppression ([REDACTED]), deterministic hash-binding. - Profiles: HIPAA Safe Harbor (18 identifier categories per 45 CFR 164.514(b)(2)), GDPR anonymization, journalism / source protection, science / IRB, legal discovery, art / creative, Aaron-personal, generic. - Reversibility tiers: irreversible hash (public release), key-sealed (default, user holds key), threshold-sealed (Shamir N-of-M, deferred — crypto lib dependency). - Output: anonymized text + audit receipt (JSON) + hash chain (input / output / rule-set SHA-256s). The tool enforces the 8 invariants on itself: every rule is mechanical, every change enters the audit receipt, every run is reproducible given the same inputs. The design doc lives at finished/anonymize_v2_design.md. FWF: Helper Who Helps. 5. SELFiX — personal counterpart (defined; signal inventory pending) SELFiX is the user-permitted internal observer. Separate binary from AURiX. Same locked grammar. User opts in. Observes the user with the user's consent. The boundary is strict: AURiX observes mechanism (page behavior), SELFiX observes decision (user behavior). Same data shape can cross the boundary only with explicit user consent. The SELFiX signal inventory is not yet drafted; SELFiX-only families would include user timing / dwell, content engagement, cross-session patterns, personal input history, goal / habit state, emotional / cognitive declarations. Aaron is the first subject and operator — running SELFiX on himself before anything else. FWF: personal counterpart (own track; not in FFF or HWH). 6. RECORD — universal data egress, 6-layer ladder (Layer 1 live) Record is the egress infrastructure for "anyone's anything from anywhere." Six layers, conservative → aggressive: Layer 1 — Cowork session auto-archive. LIVE. Cron fires 04:08 Pacific, writes session transcripts to /AURiX/cowork_archive/_extraction_v*/. Layer 2 — Claude.ai watch-folder auto-reClaim. Scoped. Layer 3 — File-manifest JSONL over mounted folders. Scoped. Layer 4 — Browser-extension aggregation. Scoped. Layer 5 — Clipboard capture. Scoped — ethical gradient starts here. Layer 6 — Screen / audio continuous. Scoped. SELFiX-only until compassion-constraint is ironclad. The ladder is the declared gradient from retrieve-what's-already-mine (conservative, clearly consented) to observe-what's-ambient (aggressive, requires careful permission and user agency). Record is infrastructure, not a single instrument. FWF: egress infrastructure (own track). 7. SOIL — substrate fertility instrument (Layer 0 shipped 2026-04-29; named 2026-04-30) Soil reads .aurix.* files across substrate and classifies each as growing / fertile / infertile / dying / dead. Five states, no interpretation. Layer 0 shipped 2026-04-29 — three components: aurix_verify.py (8-invariant verification), aurix_fertility.py (state classification), aurix_convention_check.py (encoding / line-ending / smart-char compliance). Named 2026-04-30 after naming-cohesion scrutiny across the suite — "Soil" ratified over Pulse and Recover because it names the medium and lets the instrument collapse into it (lowercase-i ethic at instrument-name layer; the observer refuses to elevate above the ground it watches). Distinct from Record: Record acquires data INTO substrate; Soil observes the state of what is already in substrate, over time. Sister at the relational layer: SELFiX observes the user on themselves; Soil observes the substrate two parties (Aaron and Claude) both write into, neither privileged. Both Aaron and Claude run Soil; classification is mechanical and uniform regardless of operator. Pump destinations: current/now/datasets/fertility_runs.jsonl, current/now/datasets/convention_violations.jsonl. Doctrine: current/now/soil.aurix.md. FWF: Helper Who Helps (substrate observation). 8. GLIMPSE — substrate visualization instrument (v0 shipped 2026-05-06) Glimpse reads JSONL ledgers under current/now/datasets/ and emits self-contained HTML chart pages at current/now/glimpse_.html with embedded data + Chart.js (CDN at open-time). Output is on-disk, viewable offline, reproducible from substrate. Native replacement for shopping-out to non-AURiX visualization tools for chart-grade output — earlier substrate work routed through external chart renderers, leaving no on-disk artifact and no hash-attestable trail. Glimpse closes that gap by rendering inside the substrate. v0 ships with one topic in the registry (fwf_trajectory). The topic registry is expandable per ledger covered; new topics gain entries by adding a renderer that maps a JSONL row schema to Chart.js data structures. Lowercase-i ethic preserved at the rendering layer: Glimpse observes the substrate it visualizes; it does not interpret it. Charts surface trajectory; the operator reads the trajectory. Sister to Soil at the chart-grade layer: Soil reads .aurix.* files for fertility classification; Glimpse reads .jsonl ledgers for trajectory visualization. Both are Helper-Who-Helps observation tools; Soil produces classifications, Glimpse produces visualizations. Pump destination: current/now/datasets/glimpse_runs.jsonl. Doctrine: current/now/glimpse_v0.aurix.md. FWF: Helper Who Helps (substrate visualization). ================================================================================ TEMPORAL ARCHITECTURE ================================================================================ A complete interaction journey passes through the instruments in rough order: 1. Page load: Gauge Tier 0 runs. Scope captures baseline state for composition. 2. User engages: Gauge Tier 1 samples broader signals. Trace records any navigation. Ledger logs every change. Receipt logs every permission event. 3. User right-clicks: Gauge Tier 2 does full traversal. Scope composites and renders the cursor. 4. User wants a structural record: AUDiT runs on the URL, produces attestation. 5. User recovers past state: reClaim transforms archives into searchable text. 6. User interrogates corpus: Answer queries what's been collected. 7. User prepares corpus for release: Anonymize applies sector-grade safe-release profile. 8. Cron fires nightly: Record Layer 1 archives the day's Cowork transcripts. No instrument requires any other to function. Each can run independently. But the architecture acknowledges that digital interaction unfolds in time, and observation should partition that time meaningfully. ================================================================================ FWF MAPPING ================================================================================ Find Fracture First (detection): Gauge, Scope, Trace, Ledger, Receipt. Helper Who Helps (equipping): AUDiT, reClaim, Answer, Anonymize. Personal counterpart (own track): SELFiX. Egress infrastructure (own track): Record. Fair Finds Fair (resolution): the protocol itself — 8 invariants, locked grammar, Comparable Commons, LPI posture. The boundary rule holds: no instrument does work from more than one FWF phase. Gauge detects, it never equips. Anonymize equips, it never detects what should be anonymized (the user or the rule set declares that). Ledger records, it never judges. The protocol enforces, it never acts. ================================================================================ COMPOSITION, NOT JUDGMENT ================================================================================ The traffic-light cursor (Scope's output) is the most visible element of the suite. It is not a verdict. It is a summary of constraint. The user sees Yellow or Red and can inspect every underlying signal from every contributing instrument to understand why. The cursor is an entry point, not a conclusion. This is the load-bearing property of the architecture: every compression (instrument state → composited cursor) is a declared mechanical operation with a published rule. The user is always one click away from the raw signals that produced the composite. Nothing is hidden inside a scoring algorithm. ================================================================================ THE SIGNAL INVENTORY COVERAGE ================================================================================ All 26 mechanism families in the signal inventory are covered by at least one instrument. Most are covered by multiple instruments from different angles (e.g., scroll lock is Gauge's real-time state and Ledger's change record). No family is orphaned. Full coverage table lives in aurix_signal_inventory_v1.txt (finished/). This paper focuses on instrument architecture; the inventory paper focuses on signal-to-family distribution. ================================================================================ WHY "5 + 6" INSTEAD OF "8" ================================================================================ The prior "8 instruments" framing (Gauge / Scope / Trace / Ledger / Lens / AUDiT / reClaim / :A) dates from the Y-Lens era. It included Lens as an independent instrument, did not distinguish browser vs desktop deployment, and predated Receipt's promotion to the canon and Anonymize's / SELFiX's / Record's elevation to first-class apps. The current 5 + 6 framing: - Drops Lens (architecturally absorbed by Gauge Tier 1/2 overlay detection). - Promotes Receipt to browser-side first-class (was implicit in AUDiT's receipt artifact; now a distinct lightweight logger). - Adds Anonymize as a full desktop app (was "the Python tool"; is now the sector-grade release pipeline). - Adds SELFiX as a full desktop app slot (was a mode; is a separate binary). - Adds Record as infrastructure (was a cron subsystem; is a ladder-of-layers with its own identity). The 5 + 6 framing maps correctly to deployment surfaces (browser vs desktop), correctly to FWF categories (five detectors, four equippers, two own-track), and correctly to what has shipped vs what is pending. The count will grow as instruments are built; the framing won't need restructure each time. ================================================================================ CONCLUSION ================================================================================ The AURiX suite is eleven instruments across two deployment surfaces, organized by temporal window and FWF position. Each is specialized enough to operate without interpretation. Together they cover the 600-signal inventory across 26 mechanism families. The visible output is a single traffic-light cursor and a family of right-click mechanism-reports; underneath is an exhaustive structural record that the user can inspect, export, and act on. No instrument judges. The user judges. The suite only makes mechanism visible. ================================================================================ END OF WHITEPAPER ================================================================================