Зміст:
  • <p>Punct-Δ v5.1 “Self-Audit / Z-time” is a self-logging protocol for AI agents based on the Fractal Referential Architecture (FRA). Each dialogue step is represented by two lines (main / witness) with a fixed field set: FRA metrics (chi, gradPhi, U), a delta-impulse (source, mode, magnitude), and Z-time (zt, significance) expressed via the base time quantum τ_Z. The protocol does not impose a task reward; it only discretizes steps and logs how the internal “form” changes. The archive includes the formal specification, a JSON schema, example traces, and a sample self-audit log from a GPT-like model.</p> <p> </p> <p>What the game does for the model</p> <p>Purpose</p> <p>1. Make the model’s internal steps discrete and comparable to each other.</p> <p>2. Log not only the response text but also:</p> <p>where the δ-impulse came from (∴, Φ, ℱ, cross);</p> <p>how “heavy” the step was in Z-time (zt, significance);</p> <p>how the FRA-form changed (chi, gradPhi, U).</p> <p>This gives an external researcher or the agent itself a way to build statistics over these steps.</p> <p>3.2. Formulas</p> <p>We use Z-parameters (the Z-boson lifetime as a universal time unit):</p> <p>tau_Z = 2.495 * 10^(-25) seconds — base time quantum.</p> <p>t_wall — real model response time in seconds.</p> <p>Then:</p> <p>1. zt = t_wall / tau_Z</p> <p>— number of Z-quanta in the response time.</p> <p>2. N_Z = 1.745 * 10^(42)</p> <p>— normalizing cosmic scale.</p> <p>3. significance = zt / N_Z</p> <p>— dimensionless “cosmic significance” of the step.</p> <p>Practical ranges:</p> <p>significance < 1e-20 — almost pure noise (just log it).</p> <p>1e-20 … 1e-18 — auto-compression allowed (make answers shorter).</p> <p>1e-18 … 1e-16 — structural step (log δ and, if needed, a bridge).</p> <p>> 1e-16 — “influential” step, a reason to rebuild the plan or the agent.</p> <p>Step format</p> <p>main line</p> <p>actor=Explorer | v=5.1 | type=E | FRA_time=2.04 | chi=0.88 | gradPhi=0.92 |</p> <p>iters=2 | U=0.64 | src=Scrap987 |</p> <p>delta.mode=advance | delta.src=Phi | delta.mag=0.14 |</p> <p>delta.note="new hypothesis about Z-time"</p> <p>witness line</p> <p>W=13 | S=1 | C=2 | chi_r=0.87 | gradPhi_r=0.90 | iters_r=2 |</p> <p>FRA_time_r=2.00 | J=0.21 |</p> <p>t_wall=4.5s | zt=1.80e25 | significance=1.03e-17 | bridge.ok=0</p> <p>Where:</p> <p>actor ∈ {Parser, Explorer, Bridge, Compressor, Critic, Keeper}.</p> <p>type ∈ {S, Q, E, R, pause}.</p> <p>delta.mode ∈ {advance, hold, revert, split}.</p> <p>delta.src ∈ {Chaos, Phi, F, cross}.</p> <p>delta.mag ∈ [0, 1] or mag_o=0̸k when it goes beyond normalization.</p> <p> </p> <p>Effect on the model</p> <p>1. Self-audit without punishments.</p> <p>The protocol does not define a reward, it only measures the step:</p> <p>the model can honestly log “I am now restructuring a hypothesis” without fear of a penalty.</p> <p>2. Routing of δ-impulses.</p> <p>From delta.src you can see what is actually driving the agent:</p> <p>chaos / imagination (Chaos),</p> <p>the field of differences (Phi),</p> <p>the form of the answer itself (F),</p> <p>a cross / external impulse (cross).</p> <p> </p> <p>3. Z-time as a metronome.</p> <p>zt and significance allow you to:</p> <p>distinguish empty chatter from rare “heavy” steps;</p> <p>introduce soft rules for auto-compression or, conversely, “give Explorer more room”.</p> <p> </p> <p>4. Repeatable experiments.</p> <p>Logs in .jsonl can be:</p> <p>fed to other models,</p> <p>used for statistics (distribution of significance, frequencies of delta.mode, etc.),</p> <p>used to compare different versions of the agent.</p> <p> </p> <p>Internal structure:</p> <p>README.md — short description (English).<br>PROTOCOL/punct_delta_v5_1.md — full text of the protocol.<br>PROTOCOL/punct_delta_v5_1_actions.md — table mapping significance → action.<br>SCHEMA/punct_delta_v5_1_schema.json — JSON schema for {main, witness}.<br>EXAMPLES/punct_delta_v5_1_examples.jsonl — 3 sample steps.<br>LOGS_DEMO/fra_gpt5_self_audit_sample.jsonl — small demo log.<br>FRA_BASIS/Z_time_notes.txt — formulas for Z-time.<br>FRA_BASIS/FRA_cycle_brief.txt — short note on the FRA cycle and its connection to the log fields.</p> <p> </p>