docs: file HB-002 — four open questions blocking BACKLOG-per-row migration by AceHack · Pull Request #5 · AceHack/Zeta

AceHack · 2026-04-21T15:51:54Z

Summary

Follow-up to AceHack PR #4 (batch 5 ADR draft). The ADR named four
open questions; this PR files them as HB-002 so Aaron can answer
out-of-band and unblock the migration PR (P0 post-R45).

The four questions

ID scheme — numeric / slug / UUID
Script home — tools/backlog/ vs inline
Sort order — creation / updated / priority-then-date
Concurrent-migration trade — one atomic PR vs staged by tier

Cost rationale

AceHack target. Pure doc PR; CI = markdownlint.

Test plan

One table row added, no format violations
AceHack CI green

🤖 Generated with Claude Code

…ation The ADR landed on AceHack PR #4 as Proposed. It names four open questions for Aaron to decide before the migration PR can land: 1. ID scheme (numeric / slug / UUID) 2. Script home (tools/backlog/ vs inline) 3. Sort order (creation / updated / priority) 4. Concurrent-migration trade (single atomic PR vs staged per tier) Migration is P0 post-R45 per the ADR itself; HB-002 is the gate. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

… triplet + data-behaviour-split hygiene Absorbs the 2026-04-21 AceHack/Zeta → Lucent-Financial-Group/Zeta transfer experience (Aaron ask: "we don't want to do it again and we might as well absorb the experience") and lifts the one-off correction Aaron made mid-task into a factory-wide hygiene rule. Three-surface canonical split: - .claude/skills/github-repo-transfer/SKILL.md — routine (9 steps) - docs/GITHUB-REPO-TRANSFER.md — data (S1-S7 gotcha catalog, what-survives inventory, adapter-neutrality table, worked example) - docs/hygiene-history/repo-transfer-history.md — append-only fire log, seeded with the 2026-04-21 row retrospectively Hygiene rule (FACTORY-HYGIENE row Lucent-Financial-Group#51, both scope): SKILL.md is routine-only; catalogs / inventories / adapter tables / worked examples live in docs/**.md; event logs in docs/hygiene-history/**. skill-creator at author-time (prevention); Aarav cadenced detection on the 5-10 round cadence from row #5. Also ships-to-project row added. BACKLOG P1 architectural-hygiene row queues the retrospective sweep over existing .claude/skills/**/SKILL.md files. Principle was mine from a prior tick (feedback_text_indexing_for_factory_qol_research_gated.md: "seperating thing by data and behiaver is a tried and true way and you mentied it for the skills earler"); Aaron caught me violating it with a first-pass mixed SKILL.md ("you told me you wanted to split skills into data and behavior/routines, see i remember what you tell me too"), then promoted it to a factory rule ("you shoould put on the backlog hygene for skills that mix data and behavior"). Memory feedback_skills_split_data_behaviour_factory_rule.md captures the rule with mix signatures, split targets, author-time checklist, and detection discipline. Known follow-ups (deferred to next ticks, not this commit): - skill-creator SKILL.md to carry the at-landing split checklist (prevention surface). - skill-tune-up SKILL.md to add mix-signature as an 8th ranking criterion (detection surface). - Retrospective sweep of existing skills for mix violations (P1 BACKLOG row). - MEMORY.md is at 242 lines / ~50KB (over the 200-line / 24976-byte cap); prune/compression queued. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

Two changes in one commit: 1. Fix markdownlint MD029 ship-blocker on PR Lucent-Financial-Group#54: flags previously labeled 11 and 12 in the Frontier edge-claims list were actually the 10th and 11th items. Renumbered 11→10 (pyromid) and 12→11 (factory-IS-the-experiment) + updated two "flag #11" cross- references in flag #5 to "flag #10". Local markdownlint clean. 2. Plant new CTF flag #12: Teaching is how we change the current order — chronology, everything, * (the retractibility-preserving mechanism of change). Aaron 2026-04-21 four-message compression naming TEACHING as the retractibility-preserving method of change with totalizing scope (temporal → universal → wildcard). Teaching is the SEMANTICS; retractibly-rewrite is the ALGEBRA. Defense surface cites Khan Academy as canonical civilizational-scale substrate-evidence per Aaron "I love Mr Khan" follow-up — mission "Free, world-class education for anyone, anywhere" literally instantiates the * wildcard applied to education access with measurable 100M+ learner time-series. Pure additive edit; no history rewrite; retractibility preserved. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

…dit (Aaron 2026-04-23) (Lucent-Financial-Group#166) * hygiene: row Lucent-Financial-Group#54 — backlog-refactor cadenced audit Aaron 2026-04-23: "we probalby need some meta iteam to refactor the backlog base on current knowledge and look for overlap, this is hygene we could run from time to time so our backlog is not just a dump". Wires the directive to the existing meta-hygiene cadence (same 5-10 round cadence as rows #5 / Lucent-Financial-Group#23 / Lucent-Financial-Group#38 / Lucent-Financial-Group#46). Five passes per firing: overlap cluster / stale retire / re-prioritize / knowledge absorb / document via ROUND-HISTORY. Row Lucent-Financial-Group#54 (rather than Lucent-Financial-Group#53) to avoid collision with the AutoDream cadenced consolidation row on the research/autodream-extension-and-cadence branch (PR Lucent-Financial-Group#155, still open) which already claimed Lucent-Financial-Group#53. Classification per row Lucent-Financial-Group#50: detection-only-justified — accumulated drift (overlap, staleness, priority-drift, knowledge-gap) is inherently post-hoc. Governing rule lives in per-user memory: feedback_backlog_hygiene_cadenced_refactor_look_for_overlap_not_just_dump_2026_04_23.md Self-scheduled free work under the 2026-04-23 scheduling- authority rule. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * hygiene Lucent-Financial-Group#54: address Copilot review — contributor-name + memory-path Two of the three findings addressed: - Replace "Aaron 2026-04-23" with "the human maintainer 2026-04-23" (+ "Aaron-scope boundary" → "Maintainer-scope boundary") per contributor-name guidance - Clarify the governing-rule memory lives in per-user memory (not in-repo); absolute path given; no in-repo pointer to a non-existent file Third finding (row Lucent-Financial-Group#54 out of numeric order) will be replied inline with rationale — Lucent-Financial-Group#53 is reserved for PR Lucent-Financial-Group#155's AutoDream cadenced-consolidation row still open; Lucent-Financial-Group#54 gives clean numbering on merge. Not a bug — intentional reservation. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>

…, queue close) (Lucent-Financial-Group#164) * memory: migrate semiring-parameterized-zeta regime-change project memory (Overlay A #5, queue close) Fifth and final opportunistic-on-touch Overlay A migration in the 2026-04-23 cadence, closing the queue identified from the signal-in-signal-out composes-with set (follows PRs 157/158/159/162). Rule captured (the project itself): Zeta's retraction- native operator algebra (D/I/z⁻¹/H) becomes stable meta- layer; semiring becomes pluggable parameter; other DB algebras (tropical/Boolean/probabilistic/lineage/ provenance/Bayesian) host within the one Zeta algebra by semiring-swap. Architectural isomorphism at the agent layer: Kenji (Architect) is the one-agent-mapping-the- others — same shape as the one-algebra-mapping-the-others. K-relations reference: Green-Karvounarakis-Tannen PODS 2007. Migration discipline per PR 157/158/159/162 pattern: - In-repo copy with "Migrated to in-repo" header - Per-user source with "Migrated to in-repo" marker - MEMORY.md index entry newest-first - MD018 lint fix applied (avoided PR-number at start of line tripping the heading-hash detector) After this lands: queue zero on the signal-in-signal-out composes-with set. Further Overlay A migrations identified only via next AutoDream cadenced fire. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * memory: address PR Lucent-Financial-Group#164 review — ZSet-algebra correction + xref clarifications Seven Copilot findings addressed: 1. **Technical correction**: ZSet baseline is the signed- integer ring (ℤ, +, ×, 0, 1) — NOT the counting semiring N. Retraction is encoded as negative weights; K-relations (Green-Karvounarakis-Tannen PODS 2007) identify this as the canonical provenance semiring for retraction-native IVM. Corrected in the "Current state" bullet. 2-7. **Cross-references to per-user memory** clarified with a standard preamble at the composition section: many refs live in per-user memory (~/.claude/projects/<slug>/ memory/), not in-repo; some migrated via 2026-04-23 Overlay A PRs (Lucent-Financial-Group#157/Lucent-Financial-Group#158/Lucent-Financial-Group#159/Lucent-Financial-Group#162/Lucent-Financial-Group#164), others remain per-user by design. Also relaxed "BACKLOG row filed" to "candidate BACKLOG row ... filing TBD per maintainer scheduling" since the row isn't explicitly present under the semiring-parameterized label on main. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>

…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>

…ned) (Lucent-Financial-Group#179) Opens gap #5 of the Frontier bootstrap readiness roadmap. Creates docs/frontier-readiness/ directory + the audit seed with: - Three-class framework: factory-generic / zeta-library- specific / both-coupled - Section-by-section schema for each audited file - Audit progress tracker (16 primary surfaces queued) - First audit: CLAUDE.md (classified "both"; 3 refactor notes flagged for pre-split edit; goes to Frontier post- split) - Composes with gap #1 (multi-repo split execution) — classification enables mechanical separation Cadence: opportunistic on-touch + 1-2 files per dedicated tick until all primary surfaces are audited. Attribution: Otto (loop-agent PM hat). Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>

Lucent-Financial-Group#180) Second file audited in the factory-vs-Zeta separation audit (gap #5). AGENTS.md is the universal onboarding handbook. Overall classification: both (coupled) — mostly factory- generic in shape, with Zeta-library-specific content in 6 areas: 1. Three load-bearing values #2 (Z-set / operator laws) 2. "What we borrow" section (DBSP / Arrow / etc. list) 3. Build and test gate (dotnet commands) 4. Code style (F# / .NET specifics) 5. Inline ZSet / algebra examples (audit on-touch) 6. Pre-v1 Status declaration (project-specific shape) Estimated refactor effort: M (more surgical edits than CLAUDE.md's S, but each isolated). Post-split location: Frontier (authoritative onboarding template); adopters fork + customise example sections. Zeta-specific content extracted to Zeta repo's own CONTRIBUTING.md (or equivalent). Section-by-section breakdown for 15 sections documented. Attribution: Otto (loop-agent PM hat). Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>

…ed) (Lucent-Financial-Group#183) Fourth file audited in gap #5. CONFLICT-RESOLUTION.md classified both (coupled). 9 sections classified: - 6 factory-generic (preamble / alignment-cite-first / principles / conference protocol / humans-part-of-system / when-part-takes-over / reflection-cadence — 7 actually) - 1 both (The parts: persona roster — shape generic, Zara/Algebra-Owner/Query-Planner scopes Zeta-specific) - 1 zeta-library-specific (Active tensions — cites IStorageCostProbe / Plan.fs / WDC / router-coherence ADR) Refactor notes: 1. Generalise Zeta-tied specialists (Zara, Algebra Owner, Query Planner) — ~3 specialist scopes out of 20+ 2. Remove Active Tensions Zeta-specific content; replace with template + adopter-fill-in; migrate current tensions to Zeta's own docs/LIBRARY-TENSIONS.md 3. Keep Otto (already factory-generic — any autonomous-loop adopter uses the pattern) Effort: M. Post-split: Frontier with surgical edits. Note re pattern hypothesis: continues mostly-factory- generic-with-Zeta-illustrative-sections shape of the rule substrate. GOVERNANCE (PR Lucent-Financial-Group#181) was cleanest; CONFLICT-RESOLUTION has more Zeta embedding due to Active Tensions section. Attribution: Otto (loop-agent PM hat). Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>

…atched) (Lucent-Financial-Group#186) Two-file batch this tick. Seventh and eighth audits in gap #5. AUTONOMOUS-LOOP.md: factory-generic (cleanest so far). 9 sections, pure Claude Code harness discipline, zero Zeta-library content. Refactor effort: ~0 (verbatim to Frontier). WONT-DO.md: both (coupled). Shape (entry template, ADR status vocabulary, "How to add" section) is factory- generic; 5 of 6 entry-sections are Zeta-library-specific ("Algorithms / operators", "Engineering patterns", "Out-of-scope for a DBSP library", etc.). Refactor strategy: Frontier inherits shape + empty section stubs; Zeta retains full current entries as library decision record. Effort: M. Progress: 8 of ~16 files audited (Otto-7/9/10/12/13/14/15). At halfway mark; projected completion ~Otto-23. Pattern tally now 8 audits: - factory-generic: GOVERNANCE / AGENT-BEST-PRACTICES / ALIGNMENT / AUTONOMOUS-LOOP (4) - both (coupled): CLAUDE / AGENTS / CONFLICT-RESOLUTION / WONT-DO (4) Attribution: Otto (loop-agent PM hat). Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>

…ucent-Financial-Group#196) * aurora: absorb Amara's operational gap assessment (2026-04-23 ferry) Amara delivered a comprehensive deep review via Aaron's courier ferry (pasted transcript). Verbatim preservation per courier protocol + Otto's absorption notes with extracted action items. Amara's one-sentence direction to Kenji: "merge the operating model you already have before inventing a bigger one." Affirmations: - Zeta's technical substrate real + algebra-first - Courier protocol correctly framed - Collaborator registry + direction-change shape right - Code quality + verification stack stronger than most Critical findings: - Main-vs-PR ambiguity is #1 operational drift - MEMORY-index-lag still manually enforced - Factory-vs-library coupling (Otto addressing via gap #5) - CONTRIBUTOR-CONFLICTS.md capture gap - BACKLOG.md write-hotspot (6761 lines) - Network layer doesn't exist yet Decision-proxy readiness: 2/3 designed, 1/3 implemented. Otto's response phases: 1. Closure push (drive Lucent-Financial-Group#149/Lucent-Financial-Group#154/Lucent-Financial-Group#155/Lucent-Financial-Group#161/Lucent-Financial-Group#170 to merge; mechanize file-and-index atomicity; populate CONTRIBUTOR-CONFLICTS; restructure BACKLOG) 2. Decision-proxy operationalisation (invocation mechanics + durable audit surface) 3. Semantic network-health metrics + stochastic-contract framing 4. Aurora integration + current priorities in parallel Validates Otto-session's closure-over-novelty bias; sharpens next-phase priorities. Attribution: Amara (authored); Otto (absorb + verbatim preservation + action-items extraction); Kenji (synthesis queue: "merge over invent"). Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * aurora: fix MD029 ordered-list-prefix — restart numbering per section Markdownlint MD029 flagged continued 6. 7. 8. etc. where it expects restart at 1. per ordered-list block. Python regex-based renumbering restores convention. Unblocks PR Lucent-Financial-Group#196 markdownlint gate. Attribution: Otto (loop-agent PM hat). Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>

…-Financial-Group#276) Five rows added per Amara's 8th courier ferry (PR Lucent-Financial-Group#274) landing plan: **Techniques section (4 rows):** - Semantic hashing (Assess) — Hinton/Salakhutdinov; real technical family for "rainbow table" intuition. - Locality-sensitive hashing (Assess) — Charikar; sibling collision framework. - HNSW (Assess) — graph-based ANN with logarithmic scaling; Trial-promotion contingent on prototype. - Product quantization (Assess) — compressed vector search at scale. - Quantum illumination (Assess for low-SNR sensing theory; explicit Hold-note for long-range product claims per 2024 engineering review). Importable as analogy for low-SNR software detection with retained-reference-path; NOT as operational quantum-radar capability. **Tools/infra section (1 row):** - Substrait (Stronger Assess) — cross-language relational- algebra plan format; answers P2 persistable-IR gap; Bonsai- vs-Substrait strategic-question scope like the declarative- env-parity row. All 5 rows cross-reference the 8th-ferry absorb at `docs/aurora/2026-04-23-amara-physics-analogies-semantic- indexing-cutting-edge-gaps-8th-ferry.md` (PR Lucent-Financial-Group#274). Preserves the "do not operationalize without promotion" quantum-radar discipline from both Amara's ferry and AGENTS.md absorb rule. Hold-note on long-range claims is explicit so future readers don't mistake Assess-for-low- SNR-theory for Assess-for-long-range-radar. Ring column uses `—` for round-number since these are Amara-attributed external research recommendations, not in-repo research passes. Precedent: other Assess rows with no round-specific origin use `—`. Lands within-standing-authority per Otto-82 calibration — pure TECH-RADAR row-addition; not account/spending/named- design-review gated. Closes 8th-ferry candidate BACKLOG row #5 of 5. Remaining candidates: - Quantum-sensing research doc (S) - Semantic-canonicalization research doc (M) — spine - Provenance-aware bullshit-detector research doc (M) - docs/EVIDENCE-AND-AGREEMENT.md future operational promotion (gated on 3 research docs) Otto-96 tick primary deliverable.

…ries (8th-ferry candidate #1) (Lucent-Financial-Group#278) Research-grade absorb per Amara 8th-ferry landing plan (PR Lucent-Financial-Group#274). Separates real quantum-sensing literature from software analogy so the latter can borrow carefully without contaminating the former. Key structure: - **Do not operationalize stated as first rule** — this doc MUST NOT be cited as authorisation for Zeta or Aurora "quantum-powered" / "quantum-inspired" claims. 2024 engineering review caps microwave QR at <1 km typical. - **What the physics actually supports**: Lloyd 2008 + Tan Gaussian-state 6 dB error-exponent + 2023 Nature Physics microwave demo + 2024 engineering range-cap review + standard radar R⁻⁴ range equation. Quantum sensing broader and more mature than quantum-radar specifically (NV-centers / magnetometers / atomic clocks are real; radar is speculative). - **5 importable software analogies**: retained reference path (anchor for weak evidence); correlation beats isolation (kNN retrieval not single-source agreement); time-bandwidth product (repeated independent observations over window); decoherence (carrier overlap destroys independence weight); cross-section-is- observability (salience != evidence). - **6-item NOT-imply list**: no quantum-radar claim; no quantum-inspired algebra; no quantum-certified alignment robustness; no Aurora-as-quantum-safety; etc. First-class content, future references must honour. - **Composition table** mapping analogies to existing substrate (SD-9 / DRIFT-TAXONOMY patterns 2 + 5 / citations-as-first-class / alignment-observability / oracle-scoring v0 / BLAKE3 v0). No new mechanisms proposed; analogies slot in as framing. - **Graduation candidates** named with explicit ADR gating: retained-witness correlation metric; salience-vs-evidence PR review diagnostic; decoherence-inspired carrier- downgrade rule. Each needs separate ADR + operational artifact + regression-test before graduating. Scope limits: - Does NOT propose implementation. - Does NOT audit existing Zeta claims against analogy boundaries. - Does NOT commit to quantum-literature tracking cadence. - Does NOT license creative expansion of analogy set (5 is what Amara cited; new literature = new research doc). - Does NOT re-verify primary sources; preserves Amara's scoping discipline verbatim. Self-applies §33 archive-header format — 14th aurora/research doc in a row. Lands within-standing-authority per Otto-82/90/93 calibration — research-grade doc; not account / spending / named-design-review / readiness-signal gated. Closes 8th-ferry candidate #1 of remaining 4 (after TECH-RADAR batch closed #5 Otto-96). Remaining: - #2 Semantic-canonicalization research doc (M; spine) - #3 Provenance-aware bullshit-detector (M) - #4 docs/EVIDENCE-AND-AGREEMENT.md future operational promotion (gated on 1-3) Otto-97 tick primary deliverable.

…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>

…-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>

…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>

…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>

…eneric) (Lucent-Financial-Group#184) Fifth file audited in gap #5. Confirms the rule-substrate- instructional hypothesis. 29 BP-NN rules across 10 sections, all pure instructional: skill-file hygiene / voice / state / security / knowledge placement / testing / formal coverage / repo ontology / operational standing / rule lifecycle / re-search-flag / authoritative sources. Zero rules embed Zeta-library-specific content. A handful of rationales cite specific factory skills or ADRs illustratively (BP-17 cites canonical-home-auditor SKILL; BP-18 rationale mentions dotnet TreatWarningsAsErrors as a gravity-comparison) — these are surgical generalisation targets. Effort: S (illustrative-reference generalisation only; no rule substance changes). Hypothesis confirmed: rule substrates with purely instructional content are factory-generic by design. Only rule substrates with state-logging content embed project specifics (e.g. CONFLICT-RESOLUTION.md Active Tensions). Attribution: Otto (loop-agent PM hat). Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>

…generic) (Lucent-Financial-Group#181) Third file audited in gap #5. Breaks the both-coupled pattern from CLAUDE.md + AGENTS.md. GOVERNANCE.md classified factory-generic overall: - 28 of 32 rules: purely factory-generic - 4 rules: "both" with surgical notes (§19 public API / §24 dev setup / §28 OpenSpec / §29 backlog files) — pattern generic, illustrative examples Zeta-specific Post-split location: Frontier as-is. 4 small inline placeholder edits, estimated refactor effort S. The factory's rule substrate is abstract by design; rules shape behaviour without enforcing project-specifics. Adopters substitute their own libraries / install steps / specs while inheriting the rule shape. Attribution: Otto (loop-agent PM hat). Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>

AceHack merged commit 2941a7e into main Apr 21, 2026
8 checks passed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

docs: file HB-002 — four open questions blocking BACKLOG-per-row migration#5

docs: file HB-002 — four open questions blocking BACKLOG-per-row migration#5
AceHack merged 1 commit intomainfrom
file-hb-002-backlog-per-row-questions

AceHack commented Apr 21, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Conversation

AceHack commented Apr 21, 2026

Summary

The four questions

Cost rationale

Test plan

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant