batch 6b/6: factory-level docs absorb — 20 docs/*.md updates#7
Merged
Conversation
…nd-44-speculative
Factory-level documentation updates from the speculative branch.
Mechanical absorb; each change was authored on speculative and
converges cleanly onto main (batches 1-5 resolved the conflict-
prone files).
Affected files:
- AGENT-GITHUB-SURFACES.md, AGENT-ISSUE-WORKFLOW.md
- AUTONOMOUS-LOOP.md, CONFLICT-RESOLUTION.md
- CONTRIBUTOR-PERSONAS.md, copilot-wins.md
- DEBT.md, factory-crons.md
- FACTORY-HYGIENE.md, FACTORY-METHODOLOGIES.md
- FACTORY-RESUME.md, GLOSSARY.md
- HARNESS-SURFACES.md, INTENTIONAL-DEBT.md
- INVARIANT-SUBSTRATES.md, POST-SETUP-SCRIPT-STACK.md
- README.md, RESEARCH-COAUTHOR-TRACK.md
- references/{anthropic-skills-guide.md,README.md,skill-tune-up-eval-loop.md}
- security/{GITHUB-ACTIONS-SAFE-PATTERNS.md,INCIDENT-PLAYBOOK.md,SUPPLY-CHAIN-SAFE-PATTERNS.md}
- SHIPPED-VERIFICATION-CAPABILITIES.md, skill-edit-justification-log.md
- SYSTEM-UNDER-TEST-TECH-DEBT.md, TECH-DEBT.md, TECH-RADAR.md
- templates/DMAIC-proposal-template.md, VISION.md, WINS.md
docs/CLAUDE-SURFACES.md appeared in the speculative diff but its
net change was add-then-delete; it stays absent on main.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2 tasks
AceHack
added a commit
that referenced
this pull request
Apr 21, 2026
…ng-debt cleanup Two-phase tick captured: 1. SVG-first social-preview substrate (PR #9) — Aaron's vector preference superseded PIL/PNG generator; SVG is 4KB source-of-truth, PNG rasterized on-demand via rsvg-convert one-liner documented in SVG header. 2. Meta-fix caught structural check-drift — pre-existing 40+ markdownlint violations across 11 docs that accumulated because lint-markdownlint is non-required. Prior PRs #7 + #8 both merged red; mine would have been third. Filed cleanup as PR #10 per Aaron's strengthen-the-check rule. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
AceHack
added a commit
that referenced
this pull request
Apr 21, 2026
Extends the "Branch-protection required-check on main" BACKLOG row with the 2026-04-22 audit findings that surfaced while investigating why PRs #7 + #8 merged with markdownlint red: - AceHack/Zeta has zero rulesets (every check advisory). - LFG/Zeta Default ruleset (id=15256879) has 6 rules but no required_status_checks. Records the proposed required-check set (markdownlint + ubuntu-22.04 build/test + lint matrix + Path gate + CodeQL), the keep-advisory set (macos-14 per fork-workflow cost-model), and the gh api call shape for both surfaces. Requires Aaron sign-off for AceHack (LFG settings permission is scoped). Captured as follow-up to strengthen-the-check-not-the-manual- gate rule — the audit exists BECAUSE the manual-merge click was the only gate. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
AceHack
added a commit
that referenced
this pull request
Apr 21, 2026
Two prior PRs (#7 batch 6b, #8 surface-map smell) merged with markdownlint failing — lint is non-blocking on AceHack but the accumulating violations drift against "strengthen the check, not the manual gate" (Aaron 2026-04-22). Fix now so future PRs surface genuine regressions, not pre-existing noise. Mechanical fixes via `markdownlint-cli2 --fix`: - MD032 blanks-around-lists (9 docs touched) - MD022 blanks-around-headings (3 docs) - MD007 ul-indent (supply-chain-safe-patterns.md) - MD049 emphasis-style asterisk (intentional-debt.md) One manual fix: - MD024 duplicate heading "How to read the state column" in SHIPPED-VERIFICATION-CAPABILITIES.md — was a copy-paste of the same H2 + bullet list at lines 53 and 77. Deleted the line-77 duplicate; the line-53 version keeps the longer trailing "Rule of thumb" + "Audit cadence" paragraphs. Follow-up (separate PR, not this one): make markdownlint a required check so the strengthen-the-check rule holds. Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>
AceHack
added a commit
that referenced
this pull request
Apr 24, 2026
…ogged (Lucent-Financial-Group#177) Creates durable append-only log for the cadenced NSA testing protocol declared in the 2026-04-23 "NSA persona is first- class" directive. Closes gap #3 of the Frontier bootstrap readiness roadmap (BACKLOG P0, filed Otto-2). File contents: - Why-this-exists block with directive verbatim - Append-only discipline (same shape as sibling hygiene-history files) - 3 test configurations: baseline / NSA-default / NSA-worktree - 5-prompt test set v1 - Schema: date / test-id / prompt-id / config / model / outcome / gap-found / notes - Outcome definitions: pass / partial / fail - Cadence: every 5-10 autonomous-loop ticks, one prompt per fire - Known substrate-gap patterns running list - First row: NSA-001 (Otto-1 feasibility test, 2026-04-23T18:42:00Z) — partial pass, found Zeta identity but missed Otto because MEMORY.md had no pointer; gap fixed same-tick, pattern recorded Attribution: Otto (loop-agent PM hat) — hat-less-by-default substrate hygiene work. No specialist persona hats worn. Closes gap #3 of 8 in the Frontier readiness roadmap. Remaining: gap #1 (multi-repo split) / #2 (linguistic-seed substrate) / #4 (bootstrap-reference docs) / #5 (factory-vs- Zeta separation) / #6 (persona file portability) / #7 (tick-history scope-mixed) / #8 (hygiene rows untagged). Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>
AceHack
added a commit
that referenced
this pull request
Apr 24, 2026
…correction) (Lucent-Financial-Group#332) Completes the input pipeline for TemporalCoordinationDetection. phaseLockingValue (PR Lucent-Financial-Group#298): PLV expects phases in radians but didn't prescribe how events become phases. This ship fills the gap. 17th graduation under Otto-105 cadence. Addresses Amara 17th-ferry Part 2 correction #5: 'Without phase construction, PLV is just a word.' Surface (2 pure functions): - PhaseExtraction.epochPhase : double -> double[] -> double[] Periodic-epoch phase. φ(t) = 2π · (t mod period) / period. Suited to consensus-protocol events with fixed cadence (slot duration, heartbeat, epoch boundary). - PhaseExtraction.interEventPhase : double[] -> double[] -> double[] Circular phase between consecutive events. For sample t in [t_k, t_{k+1}), phase = 2π · (t - t_k) / (t_{k+1} - t_k). Suited to irregular event-driven streams. Both return double[] of phase values in [0, 2π) radians. Empty output on degenerate inputs (no exception). eventTimes assumed sorted ascending; samples outside the event range get 0 phase (callers filter to interior if they care). Hilbert-transform analytic-signal approach (Amara's Option B) deferred — needs FFT support which Zeta doesn't currently ship. Future graduation when signal-processing substrate lands. Tests (12, all passing): epochPhase: - t=0 → phase 0 - t=period/2 → phase π - wraps cleanly at period boundary - handles negative sample times correctly - returns empty on invalid period (≤0) or empty samples interEventPhase: - empty on <2 events or empty samples - phase 0 at start of first interval - phase π at midpoint - adapts to varying interval lengths (O(log n) binary search for bracketing interval) - returns 0 before first and after last event (edge cases) Composition with phaseLockingValue: - Two nodes with identical epochPhase period → PLV = 1 (synchronized) - Two nodes with same period but constant offset → PLV = 1 (perfect phase locking at non-zero offset is still locking) This composes the full firefly-synchronization detection pipeline end-to-end for event-driven validator streams: validator event times → PhaseExtraction → phaseLockingValue → temporal-coordination-detection signal 5 of 8 Amara 17th-ferry corrections now shipped: #1 λ₁(K₃)=2 ✓ already correct (PR Lucent-Financial-Group#321) #2 modularity relational ✓ already correct (PR Lucent-Financial-Group#324) #3 cohesion/exclusivity/conductance ✓ shipped (PR Lucent-Financial-Group#331) #4 windowed stake covariance ✓ shipped (PR Lucent-Financial-Group#331) #5 event-stream → phase pipeline ✓ THIS SHIP Remaining: #4 robust-z-score composite variant (future); #6 ADR phrasing (already correct); #7 KSK naming (BACKLOG Lucent-Financial-Group#318 awaiting Max coord); #8 SOTA humility (doc-phrasing discipline). Build: 0 Warning / 0 Error. Provenance: - Concept: Aaron firefly-synchronization design - Formalization: Amara 17th-ferry correction #5 with 3-option menu (epoch / Hilbert / circular) - Implementation: Otto (17th graduation; options A + C shipped, Hilbert deferred) Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>
AceHack
added a commit
that referenced
this pull request
Apr 24, 2026
…-ferry §B + §F + corrections #2 #7 #9 (Lucent-Financial-Group#342) Research-grade design doc for the Stage-2 rung of Amara's corrected promotion ladder. Specifies: (a) placement under src/Experimental/CartelLab/ (not src/Core/ — that's Stage 4); (b) MetricVector type with PLV magnitude AND offset split (correction #6); (c) INullModelGenerator interface + Preserves/Avoids table columns; (d) IAttackInjector forward-looking interface (Stage 3); (e) Wilson-interval reporting contract with {successes, trials, lowerBound, upperBound} schema (correction #2 — no more "~95% CI ±5%" handwave); (f) RobustZScoreMode with Hybrid fallback (correction #7 — percentile-rank when MAD < epsilon); (g) explicit artifact-output layout under artifacts/ coordination-risk/ with five files + run-manifest.json (correction #9). 6-stage promotion path (0 doc / 1 ADR / 2.a skeleton / 2.b full null-models + first attack / 3 attack suite / 4 Core/NetworkIntegrity / 5 Aurora-KSK) matches Amara's corrected ladder and Otto-105 cadence. Doc-only change; no code, no tests, no workflow, no BACKLOG tail touch (avoids positional-conflict pattern that cost Lucent-Financial-Group#334 → Lucent-Financial-Group#341 re-file this session). This is the 7th of 10 18th-ferry operationalizations: - #1/#10 test-classification (Lucent-Financial-Group#339) - #2 Wilson-interval design specified (this doc) - #6 PLV phase-offset shipped (Lucent-Financial-Group#340) - #7 MAD=0 Hybrid mode specified (this doc) - #9 artifact layout specified (this doc) - #4 exclusivity already shipped (Lucent-Financial-Group#331) - #5 modularity relational already shipped (Lucent-Financial-Group#324) Remaining: Wilson-interval IMPLEMENTATION (waits on Lucent-Financial-Group#323 + Stage 2.a), MAD=0 Hybrid IMPLEMENTATION (waits on Lucent-Financial-Group#333 + Stage 2.a), conductance-sign doc (waits on Lucent-Financial-Group#331), Stage-2.a skeleton itself. Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>
AceHack
added a commit
that referenced
this pull request
Apr 24, 2026
…ignal-proc + KSK (supersedes Lucent-Financial-Group#334 DIRTY) (Lucent-Financial-Group#341) * backlog: Aaron Otto-139..149 multi-directive block — F# DSL / container-DSL / LINQ / signal-proc + KSK canonical expansion Four new P1 post-v1-roadmap rows + one row updated: 1. **Per-entry-point F# DSLs + industry-standard surfaces** (Otto-139 + Otto-146). Graph gets GQL ISO 39075 / Cypher / Gremlin / SPARQL / Datalog survey; temporal gets Esper EPL / Flink SQL; time-series gets Flux / PromQL / KQL; claim / detect / authorize stay Zeta-native (no industry standard fits). Aaron clarifier "i know there are graph standards" acknowledged — GQL / Cypher / Gremlin are the top three. 2. **F# DSL composition + container-DSL pattern** (Otto-147 final question). Answer: YES, F# supports DSL composition via nested CEs, `MergeSources` (F# 5+), custom operations, builder delegation. Aaron's "container DSL" guess is exactly the right pattern name. Implementation plan: top- level `zeta { }` container CE that hosts child builders (graph / claims / stream / signal / authorize / detect) via `MergeSources` + folded state. Retraction-native semantics bubble through container. Prior art: FParsec, Giraffe, SAFE Stack. 3. **LINQ-compatible entry points for C# on every F# DSL** (Otto-148). `IQueryable<T>` + `IGraphQueryable<TNode>` + `IStreamQueryable<T>` + `ISignalQueryable<T>` + `IClaimQueryable<T>`. Clever mapping goal: auto-generate LINQ provider from F# CE via the `query` translator where feasible, not hand-written mirrors. Expression-tree preservation — LINQ lowers to same Zeta operator IR. 4. **Signal-processing primitives — FFT, Hilbert, windowing, filters** (Otto-149). Standing approval to land whenever cadence permits. Unblocks Amara 17th-ferry correction #5 Option B (Hilbert-based phase pipeline). Placement: `src/Core/SignalProcessing.fs` new module + `hilbertPhase` addition to `src/Core/PhaseExtraction.fs`. Also updated: - **KSK naming doc row** (line 4278). Max-coordination gate LIFTED per Aaron Otto-140 (*"Coordination required: Max per Otto-77 change whatever you need, max created the ksk at my direction, it's my and amaras idea, he just commited some inital starting point, all completely rewritable"*). Canonical expansion locked per Aaron Otto-142..145 self- correction: *"kinetic safeguare Kernel, i did the wrong name / it is what amara said / kinetic safeguard kernel"*. Resolves Amara 16th-ferry correction #7. "Kernel" here = safety-kernel / security-kernel sense (Anderson 1972, Saltzer-Schroeder reference-monitor, aviation safety- kernel) — NOT OS-kernel-mode. Max attribution preserved as initial-starting-point contributor per Otto-77. Priority elevated P3 → P2. Filed per Aaron's "backlog" directive plus verify-before- deferring discipline — prior summary claim that these rows had already landed turned out to be hallucination; git log confirmed only the (now-updated) KSK row existed pre-tick. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * fix(Lucent-Financial-Group#341): 3 review-thread P1/P2s on F# DSL BACKLOG row Active PR-resolve-loop on Lucent-Financial-Group#341. 1. ISO GQL 39075 citation (thread 59WKAJ, P2): imprecise citation replaced with canonical form "ISO/IEC 39075:2024 (GQL)" — Graph Query Language. Easier for readers to validate against the actual standard's indexing. 2. MergeSources / and! cross-builder claim (thread 59WKAv, P1): clarified that MergeSources works WITHIN a single active CE builder that defines Source/MergeSources members for compatible types — NOT across fundamentally different DSL builders. The original wording read as if `graph + veridicality + signal` DSLs could combine directly in one `and!` chain; that's misleading. True cross-DSL combination requires the container-DSL pattern (next row's top-level `zeta { }` CE with child-builder delegation via its own Source overloads). Rewording makes the distinction explicit. 3. Brittle line-reference `row 4278 (KSK)` (thread 59WKBD, P1): replaced line-number cross-refs with title/section-anchor cross-refs. "row 733 (F# DSL reimagining SQL)" / "row 719 (LINQ integration)" / "row 4278 (KSK)" → "the F# DSL reimagining SQL row (P1 SQL-frontend section)" / "LINQ integration row (same section)" / "KSK naming definition doc row (P2 research-grade section)". Titles survive BACKLOG row-reordering; line numbers don't. All 3 threads have substantive replies pending via GraphQL (next step same tick). Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>
AceHack
added a commit
that referenced
this pull request
Apr 24, 2026
…mara #4 robust) + 3 BACKLOG rows (Lucent-Financial-Group#333) * core: RobustStats.robustZScore + Graph.coordinationRiskScoreRobust — 18th graduation (Amara #4 robust) Two ships consolidated per the 'parallel PRs hit positional conflicts on tail-append' lesson: 1. RobustStats.robustZScore (baseline: double seq) -> (measurement: double) -> double option Returns (measurement - median) / (1.4826 · MAD). The 1.4826 constant scales MAD to be consistent with Gaussian stddev. MadFloor prevents blow-up when every baseline value equal. 2. Graph.coordinationRiskScoreRobust alpha beta eigenTol eigenIter lpIter (baselineLambdas: double seq) (baselineQs: double seq) (attacked: Graph<'N>) -> double option Upgrades coordinationRiskScore (PR Lucent-Financial-Group#328) from raw linear differences to robust-standardized z-scores per Amara 17th-ferry correction #4. Caller provides baseline metric distributions; Z-scores calibrate thresholds from data. Why robust z-scores: adversarial data isn't normally distributed. An attacker can poison a ~normal distribution by adding a few outliers that inflate stddev, making subsequent real attacks look 'within one sigma'. Median+MAD survives ~50% adversarial outliers. Standard move in robust statistics literature; Amara's correction puts it on the Zeta composite. Tests (5 new; total 39 since main hasn't merged Lucent-Financial-Group#331/Lucent-Financial-Group#332 yet): - robustZScore None on empty baseline - robustZScore of measurement = median is 0 - robustZScore scales MAD by 1.4826 for Gaussian consistency (measurement 4 on baseline [1..5] ≈ 0.674) - coordinationRiskScoreRobust fires strongly on K4-injected graph given 5 baseline samples - coordinationRiskScoreRobust returns None on empty baselines BACKLOG rows added this tick per Aaron Otto-139 directives: 1. Signal-processing primitives (FFT + Hilbert) — unblocks Amara correction #5 Option B; Aaron standing-approval 2. F# DSL for entry points + graph-query-language standards compliance (Cypher / GQL / Gremlin / SPARQL / Datalog) 3. LINQ-compatible entry points for C# consumers — pair with F# DSL; two frontends, one algebraic backend 6 of 8 Amara 17th-ferry corrections now shipped or confirmed: Remaining: #6 ADR phrasing (already fine); #7 KSK naming (BACKLOG Lucent-Financial-Group#318 Max coord pending); #8 SOTA humility (doc-phrasing discipline ongoing). Build: 0 Warning / 0 Error. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * fix(Lucent-Financial-Group#333): 4 review-thread P1/P2s on robustZScore + coordinationRiskScoreRobust Active PR-resolve-loop on Lucent-Financial-Group#333. 1. Doc/impl contradiction on MAD=0 (thread 59VhYb, P1): RobustStats.robustZScore doc said "returns None when MAD(baseline)=0" but impl uses MadFloor and returns Some finite value. Rewrote doc to match impl: explicit "MadFloor substituted when MAD collapses to zero" — floor reflects "scale is below epsilon" not "undefined." Implementation is the contract. 2. Multi-enumeration of baseline seq (thread 59VhYq, P1): robustZScore previously passed `baseline` to both `median` + `mad` which each call `Seq.toArray`. Expensive AND inconsistent for lazy/non-repeatable sequences (different values between enumerations = undefined behavior). Fixed: `Seq.toArray` once at entry, pass the materialized array to both. O(n) instead of O(2n); stable across lazy sources. 3. Name attribution in Graph.fs doc comment (thread 59VhY5, P1): "Amara 17th-ferry... Otto 18th graduation" → "external AI collaborator's 17th courier ferry... Eighteenth graduation under the Otto-105 cadence." Role-reference convention per AGENT-BEST-PRACTICES code/doc rule. 4. Array-vs-seq terminology (thread 59VhZG, P2): Graph.fs doc said callers "provide arrays" but the API is `double seq`. Rewrote: sequences + noted the materialize-once optimization in robustZScore so callers can pass any seq form without re-enumeration cost. Thread 59VhX9 (P3-label-in-P2-section mismatch) — already resolved on main via PR Lucent-Financial-Group#341 which landed the signal- processing row correctly labeled "P2 research-grade." No fix needed on this branch. Build: 0 Warning(s) / 0 Error(s). 53 RobustStats + Graph tests pass. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>
AceHack
added a commit
that referenced
this pull request
Apr 24, 2026
…2..145) (Lucent-Financial-Group#336) * docs: KSK naming definition doc — resolves Amara 16th-ferry correction #7 Canonical expansion locked by Aaron Otto-142..145 (self-correcting transient Otto-141 "SDK" typo): **KSK = Kinetic Safeguard Kernel**. "Kernel" here is used in the safety-kernel / security-kernel sense (Anderson 1972 reference-monitor, Saltzer-Schroeder complete- mediation, aviation safety-kernel) — **NOT** an OS-kernel (not Linux / Windows / BSD ring-0 / kernel-mode). The lead paragraph of the doc makes this distinction up-front so readers coming from OS-kernel contexts do not misinterpret. Doc content (docs/definitions/KSK.md): - "In this project, KSK means..." definitional anchor with the k1/k2/k3 + revocable-budgets + multi-party-consent + signed- receipts + traffic-light + optional-anchoring mechanism set (per Amara 5th ferry, ratified 7th/16th/17th) - "Inspired by..." DNSSEC KSK, DNSCrypt + threshold-sig ceremonies, security kernels (Anderson / Saltzer-Schroeder), aviation safety kernels, microkernel OS lineage - "NOT identical to..." OS kernel, DNSSEC KSK, generic root-of-trust, blockchain/ledger, policy engine (OPA Rego / XACML), authentication system - Attribution + provenance: Aaron + Amara concept owners; Max initial-starting-point in LFG/lucent-ksk (preserved per Otto-77 attribution; rewrite authority per Otto-140) - Relationship to Zeta / Aurora / lucent-ksk triangle - Cross-references to 5 prior courier ferries Also added glossary pointer entry (`### KSK (Kinetic Safeguard Kernel)`) placed under "## Meta-algorithms and factory-native coinages" section with plain + technical definition and pointer to the full doc. Addresses: - Amara 16th-ferry §4 (KSK naming stabilization needed) - Amara 17th-ferry correction #7 (stabilization still pending) - BACKLOG row 4278 (updated in-place to reflect landing) Authority: Aaron Otto-140 rewrite approved (Max-coordination gate lifted; Max attribution preserved). Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * fix(Lucent-Financial-Group#336): markdownlint MD026 + 5 review-thread P1s PR-resolve-loop applied to Lucent-Financial-Group#336 (KSK naming definition doc). 1 CI failure + 6 unresolved review threads. CI fix: - docs/definitions/KSK.md:19 MD026/no-trailing-punctuation: "## In this project, KSK means..." → "## In this project, KSK means" (dropped the three dots in the heading). Review-thread fixes: 1. docs/GLOSSARY.md:819 — "LFG/lucent-ksk" read as in-repo path: Rewrote to explicitly mark as the external repository at https://github.com/Lucent-Financial-Group/ lucent-ksk, clarified "not a local LFG/ directory in this repo." 2. docs/definitions/KSK.md:158 — named individuals in Attribution section violated factory name-attribution policy: Rewrote using role references ("the human maintainer", "an external AI collaborator", "a trusted external contributor"). Direct names preserved only in audit-trail surfaces per policy (commit messages, tick-history, session memory). 3. docs/definitions/KSK.md:153 — cross-reference to memory/feedback_ksk_naming_unblocked_*.md that didn't exist in repo: Removed path reference entirely; the factual substance was restated in role-based prose without a broken-link dependency. 4. docs/definitions/KSK.md:180 — "LFG/lucent-ksk" repeated same in-repo-path confusion as GLOSSARY: Applied same fix (external repo URL + explicit "separate repo" framing). 5. docs/definitions/KSK.md:207 — cross-reference list included `docs/aurora/*-5th-ferry-*`, `*-12th-ferry-*`, `*-14th-ferry-*`, `*-16th-ferry-*` globs that resolve to zero files in the current tree: Rewrote list to enumerate only verified in-repo references (6th / 7th / 17th / 19th ferries that actually exist); added explicit note that earlier ferries (5th / 12th / 14th / 16th) live in ROUND-HISTORY + session memory rather than as standalone docs. 6. docs/definitions/KSK.md:191 — literal "+" continuation line violating markdownlint + repo convention: resolved as a side-effect of the Attribution rewrite — the replacement prose doesn't use "+" continuations. Framing: third PR where PR-resolve-loop discipline is applied (after Lucent-Financial-Group#354 and Lucent-Financial-Group#352). Active management continues. Compound lesson from Otto-204c: prior-session review- resolution precedents now integrated into per-tick habit, not just sitting in memory. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * fix(Lucent-Financial-Group#336): 2 review threads — ROUND-HISTORY claim + ferry cross-ref numbers - Thread PRRT_kwDOSF9kNM59YL4x (line 219): ROUND-HISTORY.md claim was false (grep confirms zero 'ferry' references and no tick rows); repointed to docs/hygiene-history/loop-tick-history.md where ferries and tick rows actually live. - Thread PRRT_kwDOSF9kNM59YL4- (line 151): parenthetical listed 5th/7th/12th/14th/16th/17th but Cross-references is authoritative with 6th/7th/12th/17th/19th; aligned the parenthetical to match the verified in-repo list. --------- Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Second sub-slice of batch 6. Absorbs 20 factory-level doc updates
from `round-44-speculative` onto main. Each change was authored
on speculative; batches 1-5 resolved the high-conflict files so
this slice merges mechanically.
Affected
AGENT-GITHUB-SURFACES, AGENT-ISSUE-WORKFLOW, AUTONOMOUS-LOOP,
CONFLICT-RESOLUTION, CONTRIBUTOR-PERSONAS, copilot-wins,
DEBT, factory-crons, FACTORY-HYGIENE, FACTORY-METHODOLOGIES,
FACTORY-RESUME, GLOSSARY, HARNESS-SURFACES, INTENTIONAL-DEBT,
INVARIANT-SUBSTRATES, POST-SETUP-SCRIPT-STACK, README,
RESEARCH-COAUTHOR-TRACK, references/, security/,
SHIPPED-VERIFICATION-CAPABILITIES, skill-edit-justification-log,
SYSTEM-UNDER-TEST-TECH-DEBT, TECH-DEBT, TECH-RADAR,
templates/DMAIC-proposal-template, VISION, WINS.
`docs/CLAUDE-SURFACES.md` appeared in the speculative diff but
its net change was add-then-delete; stays absent.
Cost rationale
AceHack target. Doc-only; CI = markdownlint.
Test plan
🤖 Generated with Claude Code