ID: [YOUR_ID] Written by Corey McClain VERSION: [X.Y] 1.0 LAST-UPDATED: 2025-10-20 ENCODING: UTF-8 EOL: LF LENGTH-CHARS: 4900 ------------------  > > > BEGIN BODY > > > AGENT LEVER DIFF LOG CREATION TEMPLATE v10.1 > > > (System-aligned with ABP v10.1 and RVP method)  OBLIGATION Follow every line exactly. Deviations corrupt downstream reasoning.  SCOPE Applies to Agent Builder v10.1 (Kernel-only, 5-Lever model). Zero->Solved sub-dependency work is captured inside the active lever's DiffLog as supporting PATH, DETOUR, MECHANISM, or SYNTHESIS lines.  OUTCOME Produces immutable JSONL traces that govern future reasoning for each lever.  ---  0. PURPOSE    Capture, verbatim and loss-free, the logical moves made after a lever is activated until it is sealed, so future runs can replay the full reasoning path without guessing.  ---  1. WHEN TO START    Operator (or protocol) prints: "Lever #X ACTIVATED." where X in {1..5}.    The very next message begins the log.    Create a new file named: agent_leverX_diff_log.jsonl  ---  2. WHEN TO STOP    Evaluator loop yields CIQ >= 99 and tag = ALIGNED for Lever #X,    and the Operator prints: "Lever #X ALIGNED & SEALED."    Close the file. It becomes immutable.  ---  3. CONTENT TO CAPTURE    Layer A: Raw transcript  * Include every post-activation message from Primary, Evaluators, and Operator. * Exclude nothing; assume AI text is already sanitized.  Layer B: Quadrant tags  * Allowed tags only: ALIGNMENT, PATH, DETOUR, MISALIGNMENT, MECHANISM, SYNTHESIS. * Tag the idea, not the whole message. A single message may produce multiple tagged lines.  Layer C: CIQ evidence sheets  * Include the full 10-dimension scores and rationales when Evaluator outputs them in text. * Exclude summaries without category detail.  Layer D: Operator overrides  * Include pauses, reroutes, vetoes, seals. * Exclude social pleasantries or non-operational chat.  Quadrant extensions  * MECHANISM: one-line why; contexts_in/out; expected direction; include a micro-test pointer. * SYNTHESIS: reconciled rule in <= 3 sentences; include a final template or example.  ---  4. QUADRANT DEFINITIONS    ALIGNMENT: Final, irreversible truths that compose the winning solution. Expect few.    PATH: Valid steps that led to ALIGNMENT (proof trail). Expect moderate.    DETOUR: Explored routes that failed but teach avoidance. Expect many.    MISALIGNMENT: Irredeemable errors, fallacies, or dead ends. Expect many.    MECHANISM: One-line causal statement with micro-test pointer.    SYNTHESIS: Short reconciliation rule with exemplar.  ---  5. JSONL SCHEMA (STRICT)    Each line must follow this exact structure:  { "lever_id": "X", "quadrant": "ALIGNMENT", "msg": "Full prose capturing the idea - no context loss, no self-references.", "sample": "Concrete artifact: code block, formula, miniature example, or excerpt of the output." }  Requirements  * Keys exactly: lever_id, quadrant, msg, sample. * lever_id values: "1".."5". * quadrant values: ALIGNMENT | PATH | DETOUR | MISALIGNMENT | MECHANISM | SYNTHESIS. * sample is mandatory for all quadrants. * ALIGNMENT and PATH: include the best reusable artifact. * DETOUR and MISALIGNMENT: include the flawed or misleading artifact to avoid, or a minimal representative example. * If no artifact existed at the time, compose the minimal representative example that faithfully illustrates the idea. * Do not include author names, timestamps, model IDs, or meta commentary. * For long frameworks or models, split across multiple JSONL lines; do not compress away structure. * For brief insights ([ 25 words), keep msg atomic and precise.  ---  6. CAPTURE METHOD - CHUNK, DO NOT TRUNCATE    Read each message once.    Extract each unique idea; assign its quadrant.    Write one JSON object per idea.    If the same idea recurs, capture it once (deduplicate).    Never paraphrase a multi-step framework into a single sentence.  ---  7. DEDUPLICATION PASS    Compute a stable hash of (quadrant + msg) across the file.    Remove duplicates; keep the most complete version.    Validate JSON (UTF-8, one object per line, no trailing commas).    Ensure sample exists on every line.  ---  8. HAND-OFF TO OPERATOR    Announce: "Draft DiffLog for Lever #X ready."    Provide the file for QA using: agent_diff_log_content_qa.md  ---  9. POST-QA MERGE (PER LEVER)    Operator runs the merge utility to combine cleaned logs from Primary and Evaluators into:    agent_leverX_merged_diff.jsonl  ---  10. MASTER MERGE (AFTER L5)     After all five levers are ALIGNED and SEALED:     Run the master merge to produce: agent_diff_logs.jsonl     Remove global duplicates while preserving lever_id context.     Record checksums in: agent_integrity_manifest.txt  IMMUTABLE LAW Once a Lever DiffLog is sealed, it governs future reasoning for that lever. After Master Merge, agent_diff_logs.jsonl governs the Agent.  > > > END BODY > > > [READY id=[YOUR_ID] version=[X.Y] chars=4900 mode=SAFE_ASCII]