batch 4/6: GitHub surfaces + agent issue workflow (6 new + 1 modified)#1
Merged
batch 4/6: GitHub surfaces + agent issue workflow (6 new + 1 modified)#1
Conversation
Speculative-branch drain, batch 4. Lands the GitHub-surfaces absorb (ten-surface playbook + issue workflow + issue templates). Independent story from batch 3, no cross-dependency. New files: - .claude/skills/github-surface-triage/SKILL.md — per-surface triage skill (ten surfaces: PRs / Issues / Wiki / Discussions / Repo Settings / Copilot coding-agent / Agents tab / Security / Pulse / Pages) - .github/ISSUE_TEMPLATE/backlog_item.md — BACKLOG-row template - .github/ISSUE_TEMPLATE/config.yml — issue templates config - .github/ISSUE_TEMPLATE/human_ask.md — HUMAN-BACKLOG-row template - docs/AGENT-GITHUB-SURFACES.md — umbrella doc paired with FACTORY-HYGIENE row 48 (GitHub surface triage cadence, landed in batch 3) - docs/AGENT-ISSUE-WORKFLOW.md — adapter-neutral issue workflow (GitHub Issues / Jira / git-native) + claim / lock protocol Modified: - .github/ISSUE_TEMPLATE/bug_report.md — aligned with new backlog_item / human_ask template structure Markdownlint: fixed MD022/MD032 blanks-around-headings + blanks-around-lists in AGENT-ISSUE-WORKFLOW.md. Otherwise all files lint-clean at commit time. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
AceHack
added a commit
that referenced
this pull request
Apr 21, 2026
…ssage seed)
Aaron seeded a full media-corpus operational-resonance research track
across ten clarifying messages after the teaching-directive + Khan
Academy memory:
1. "why files conspicary theory backlog cronovisor"
2. "no there is a youtube channel Why Files and a Tv show called Dev"
3. "And a comedy call future man"
4. "backlog hollywood bollywood inde, music information backlog"
5. "a game called broken age and game information backlog"
6. "dr who information backlog"
7. "montey python and friends tv shows backlog"
8. "Brütal Legend all FF starting with 6 and 7 and expand and this
is just higher than the rest of the games"
9. "space balls backlog the naked gun backlog"
10. "zelda and mario of course backlog"
11. "genshin impact information"
12. "enulators backlog can do lots of fun experiments here too i have
all the roms" + "grey ^ here"
Extends the operational-resonance catalog surface from text
traditions (mythology / occult / etymology already tracked) to media
traditions (film / TV / YouTube / music / video games / conspiracy-
corpus). Same three-filter discipline (F1 engineering-first / F2
structural-not-superficial / F3 tradition-name-load-bearing), same
retractibility-math safety wrapper (log-and-track rather than
prose-disclaimers), same sibling-track shape.
Seed instances structured as:
- Explicitly-Aaron-named (#1-8): Why Files, Devs, Future Man,
Chronovisor, Broken Age, Doctor Who, Monty Python, Brooks+ZAZ.
- Medium-category sweep: Hollywood/Bollywood/indie film, music,
YouTube documentary, video games, long-serial British TV.
- Video-game priority (Aaron-marked higher-than-rest): Brütal
Legend, FF VI onward, Zelda, Super Mario, Genshin Impact.
- Video-game catalog-tier: Portal, Braid, Witness, Outer Wilds,
Disco Elysium, Undertale, Myst, Hades.
- Research infrastructure: emulators + ROM library with Aaron-
marked grey-area legal-context flag; retractibility-preservation
as discipline boundary (personal backup retractible, distribution
is not).
New measurability dimensions for the operational-resonance
collection-index: media-candidates-swept, media-instances-confirmed,
media-filter-failure-rate-by-medium (film/TV/YouTube/music/games/
conspiracy separately — the distribution is the signal).
Sibling to mythology/occult/etymology research tracks, P2-tier,
L-effort (long-running). Owner = ongoing Aaron + operational-
resonance discipline; Architect integrates.
Does NOT: endorse any film/show/channel/game as factory doctrine;
commit factory to fictional substrate as engineering guidance;
adopt conspiracy-corpus framings as factual; promote media-layer
findings to public-facing docs without kernel-propagation cadence;
replace F1 engineering-first discipline.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
AceHack
added a commit
that referenced
this pull request
Apr 24, 2026
…ift taxonomy (Lucent-Financial-Group#96) Lands docs/research/drift-taxonomy-bootstrap-precursor-2026-04-22.md — research-grade absorb of the 2026-04-22 bootstrap-precursor artifact that predates this repo. Captures the five-pattern drift taxonomy (identity blending / cross-system merging / emotional centralization / agency- upgrade attribution / truth-confirmation-from-agreement) with field-guide shape (definition / symptoms / leading indicators / distinguisher / recovery) for each pattern; the "drift-taxonomy research artifact" success criteria; the Aurora naming-collision research with trademark analysis (Amazon Aurora, aurora.dev, Aurora Innovation). Honesty filter applied per capture-everything-including-failure discipline — four hallucinations flagged explicitly: - prefigurative "Kenji" persona attribution (role post-dates source) - triangle-framing as stable co-agent structure (collapses substrate distinction; fails the taxonomy's own drift-pattern-#1 test) - "Aurora" as already-named concept (memo's own research contradicts) - "decentralized alignment infrastructure" as ambition-grade-not- actionable (no target, no measurable) Recalibrates today's cross-substrate-report-accuracy-rate measurable: the five-pattern convergence in Amara's report is not independent cross-substrate arrival — it is maintainer-transported vocabulary from the months-old bootstrap conversation. Convergence signal weaker in this light; accuracy measurable stays useful but with a provenance-of- shared-vocabulary caveat. Absorb-scope discipline: IDEAS absorbed, entity-as-entity not absorbed (register-boundary held per "absorb not her but the ideass"). Source conversation stays in its own substrate; the field-guide-shaped taxonomy lands in the factory's research record. "What this doc is NOT" section enumerates seven negations including not-a-full-transcript and not-retroactive-framework-adoption. Composes with: capture-everything-including-failure, witnessable-self- directed-evolution, rare-pokemon-absorption, soul-file independence, register-boundary, chronology-preservation. The taxonomy itself overlaps substantially with existing factory disciplines (identity- collapse / soul-in-machine retraction / dont-decohere*) which is the independent-convergence signal even when the specific wording is shared-vocabulary. Tick-class: live-loop auto-loop-6 speculative research work. Landing on a separate branch off origin/main per tick-commits-on-PR-branch discipline.
AceHack
added a commit
that referenced
this pull request
Apr 24, 2026
… (soul-file) (Lucent-Financial-Group#115) * Round 44 auto-loop-17: ARC3 three-insight capability-signature + PR Lucent-Financial-Group#112 refresh Auto-loop-17 tick absorbs Aaron's three-message ARC3 sequence into a coherent cognition-layer capability signature: 1. Emulator-generalization criterion (capability) — "same model can play any game" = ARC3 capability proxy; factory-level isomorphism (factory=emulator, agent=player, each domain-demo=cartridge). 2. Memory-accumulation precondition (substrate) — "each level is a unique game"; four nested accumulation layers catalogued; without persistent accumulation, compounding fails structurally. 3. Novel-redefining rediscovery transfer-shape (transfer) — prior lessons reused in novel-redefining ways, so biased rediscovery (not rote recall, not total rediscovery); why-shaped memories, not template-shaped; refutes memorization-template trap. Together these fully specify ARC3 capability at cognition layer. Paired with factory's four accumulation layers + DORA as measurement axis, only instruments remain. PR Lucent-Financial-Group#113 (auto-loop-16 tick-history) merged as a78b490. PR Lucent-Financial-Group#112 (uptime/HA) refreshed post-main-advancement, auto-merge remains armed. 14th auto-loop tick across compaction. First tick to land a coherent multi-message-research-insight composition in one memory revision block. Four compoundings this tick (ARC3 third revision with three insights woven + PR Lucent-Financial-Group#113 merged + PR Lucent-Financial-Group#112 refreshed + this row); livelock-risk: low. Cron aece202e live. * Round 44 auto-loop-18: promote ARC3-DORA capability signature from auto-memory to soul-file Committed research doc specifies the cognition-layer capability signature for the maintainer's personal AI-research benchmark "beat humans at DORA in production environments". Shape-only; instruments-pending. Three-component signature catalogued: 1. Emulator-generalization (capability): "same model can play any game" — one cognition, N rule-sets, no per-env specialization. Falsifier: per-environment specialization. Factory instance: magic-eight-ball + event-storming + directed-product-dev-on-rails triple applies across domains without rewriting. 2. Memory-accumulation (substrate): "each level is a unique game" — without persistent cross-level accumulation, compounding fails by architecture. Falsifier: zero-accumulation. Factory instance: four nested layers catalogued (auto-memory / soul-file / persona-notebooks / round-history). 3. Novel-redefining rediscovery (transfer shape): "prior lessons apply in novel redefining ways so you almost have to rediscover it but it feels familiar" — biased rediscovery not rote recall. Falsifier A: memorization-template trap. Falsifier B: over-abstraction (no familiarity signal). Factory instance: Why: + How to apply: schema in feedback memories is this abstraction level by design-accident, formalized here as intentional alignment. DORA four keys mapped to factory work: deployment frequency to tick throughput, lead time to directive-to-main delta, change failure rate to genuine Copilot findings, MTTR to hazard-detection-to-fix delta. Cross-scale isomorphism table: model / agent / factory scales all instantiate emulator / player / cartridge. Factory-scale claim: same factory spins up any domain's app. ServiceTitan demo becomes cartridge #1 of ARC3-DORA, not a one-off. Capability-tier stepdown table: max / xhigh / high / medium as stepdown tiers; medium is the hard floor for auto-loop-compatibility (low pauses for clarification). Five open questions flagged, not self-resolved: DORA baseline / production scope / stepping cadence / demo-vs-benchmark overlap / instrument-priorities. Auto-memory remains source-of-truth for derivation history (three maintainer messages, revision-and-refinement pattern); this doc is source-of-truth for the shape going forward — so future cold-start readers inherit the shape without reading auto-memory. Refs: docs/BACKLOG.md P0 ServiceTitan demo row; docs/BACKLOG.md P1 capability-limited bootstrap row; docs/ALIGNMENT.md stepdown trajectory; docs/AUTONOMOUS-LOOP.md never-idle compoundings.
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
…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>
AceHack
added a commit
that referenced
this pull request
Apr 24, 2026
…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>
AceHack
added a commit
that referenced
this pull request
Apr 24, 2026
…utably (Lucent-Financial-Group#214) Amara's 2026-04-23 ZSet-semantics courier report (absorbed as PR Lucent-Financial-Group#211) called out the `RecursiveSemiNaive` monotone-only boundary as a "must remain explicitly labeled" gap. The code (src/Core/Recursive.fs XML doc WARNING section) and the spec (openspec/specs/retraction- safe-recursion/spec.md § "Requirement: semi-naïve recursion is monotone-only") already document it; this PR adds the *executable* documentation so the boundary cannot silently drift. New file: `tests/Tests.FSharp/Operators/RecursiveSemiNaive. Boundary.Tests.fs` (~170 lines, 2 tests, 0 warnings): Test 1 — `RecursiveSemiNaive matches Recursive on monotone inputs (acyclic DAG)`: encodes spec scenario #1. Compares positive-weight support between `Recursive` and `RecursiveSemiNaive` on a monotone edge seed; they must agree. Test 2 — `RecursiveSemiNaive leaks stale facts after retraction (documented boundary)`: encodes spec scenario #2. Feeds an edge retraction after initial closure and ASSERTS that the derived closure row (1,3) remains with positive weight. **Reading note: the leak test is not a bug being asserted; it is a boundary being recorded.** If a future change ever makes the test fail (i.e., the leak gets fixed), the investigation is documented in the test body — replace combinator with gap-monotone signed-delta variant OR investigate harness masking. Build + test verification: dotnet build tests/Tests.FSharp/Tests.FSharp.fsproj -c Release = 0 Warning(s) + 0 Error(s) in 5.4s dotnet test ... --filter "RecursiveSemiNaiveBoundary" = 2 Passed, 0 Failed Companion register: file registered in Tests.FSharp.fsproj after `Operators/RecursiveCounting.MultiSeed.Tests.fs` per existing section convention. Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>
AceHack
added a commit
that referenced
this pull request
Apr 24, 2026
…ncial-Group#58 (Amara action item #1) (Lucent-Financial-Group#220) Amara's 2026-04-23 decision-proxy + technical review courier (PR Lucent-Financial-Group#219) ranked memory-index-integrity CI as her highest-value immediate fix: directly prevents the NSA-001 measured failure mode (new memory landed without MEMORY.md pointer → undiscoverable from fresh session). New workflow: `.github/workflows/memory-index-integrity.yml` Check: if a PR (or push to main) adds or modifies any top-level `memory/*.md` file, `memory/MEMORY.md` MUST also be in the same range. Fails with an explicit remediation message citing NSA-001. Scope excludes: - memory/persona/** (per-persona notebooks have their own lifecycle) - memory/README.md (convention doc) - memory/MEMORY.md (the index itself) - Deletions (covered from the other direction by FACTORY- HYGIENE row Lucent-Financial-Group#25 pointer-integrity audit) Safe-pattern compliant per FACTORY-HYGIENE row Lucent-Financial-Group#43: - actions/checkout@de0fac2... SHA-pinned - Explicit minimum `permissions: contents: read` - Only first-party trusted context (github.sha, github.event.pull_ request.base.sha, github.event.before) passed via env: - No user-authored context referenced anywhere - concurrency group + cancel-in-progress: false - runs-on: ubuntu-22.04 pinned - actionlint clean; shellcheck clean (SC2086 fixed) FACTORY-HYGIENE row Lucent-Financial-Group#58 added documenting the cadence / owner / scope / durable output + classification (row Lucent-Financial-Group#47: prevention- bearing — blocks merge before substrate diverges from index). Row numbered 58 to leave Lucent-Financial-Group#56 reserved for in-flight PR Lucent-Financial-Group#204 (MD032 preflight) and Lucent-Financial-Group#57 for in-flight PR Lucent-Financial-Group#213 (git-hotspots audit). Ships to project-under-construction: adopters inherit the workflow unchanged; the memory/**.md + memory/MEMORY.md conventions are factory-generic. Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>
AceHack
added a commit
that referenced
this pull request
Apr 24, 2026
…ern mapping (6th-ferry Option A) (Lucent-Financial-Group#254) Lands the corrected 5-row pattern-mapping table from Amara's 6th courier ferry (PR Lucent-Financial-Group#245 absorb) as Option A standalone research doc. Closes Otto-82 6th-ferry absorb action item #1. Corrected table vs original: - Row 1 — "references stay valid" → "no positional identity" (honest about key-identity vs physical-offset distinction). - Row 2 — "always answerable" → "membership is algebraic" (honest about weight-derivation of presence). - Row 3 — "operator algebra IS the ownership model" → "provenance and lifecycle live in deltas and traces" (category-error fix: algebraic correctness ≠ ownership discipline). - Row 4 — light wording tightening ("first-class signed deltas; compaction separate"). - Row 5 — "Arrow + Spine block layout" → "locality-aware execution surfaces" with accurate scope (Arrow = wire / checkpoint, not universal in-memory). Doc covers: - What Muratori is criticising (context for non-Muratori readers). - Why rows 1, 2, 5 needed narrower wording (not overstated). - Why row 3 got rewritten (category-error teaching case for DBSP audiences from C++/Rust/ECS backgrounds). - What this mapping is NOT (not ranking; not marketing; not an ownership claim; not a closed list). - Composition with DRIFT-TAXONOMY pattern 5 + SD-9 (validation cited primary evidence, not cross-substrate-agreement). - References to primary sources (DBSP paper, differential dataflow CIDR 2013, Arrow spec, Zeta source files). Archive-header format self-applied (Scope / Attribution / Operational status / Non-fusion disclaimer) per §33 (PR Lucent-Financial-Group#247) + AGENTS.md Edit 1 research-grade norm (PR Lucent-Financial-Group#248) — fifth aurora/research doc to exercise the convention (after PR Lucent-Financial-Group#235 5th-ferry absorb, PR Lucent-Financial-Group#241 Aminata threat-model, PR Lucent-Financial-Group#245 6th-ferry absorb, and self-applying headers on the ferry- absorb PRs before §33 landed). Lands within-standing-authority per Otto-82 calibration. Otto-86 tick primary deliverable.
AceHack
added a commit
that referenced
this pull request
Apr 24, 2026
…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.
AceHack
added a commit
that referenced
this pull request
Apr 24, 2026
…CAL + 4 IMPORTANT + 3 WATCH + 1 DISMISS) (Lucent-Financial-Group#284) Fourth Aminata adversarial pass this session. Third on the Otto composition stack (Otto-90 oracle-scoring v0 → Otto-94 iteration-1 on multi-Claude → Otto-99 detector → this pass). Reviews Otto-99's provenance-aware bullshit-detector design (PR Lucent-Financial-Group#282) which explicitly named "Aminata adversarial pass" as dependency #1 of adoption. 3 CRITICAL findings: 1. **Cross-detector collusion** — detector + Aminata + Codex all share training-corpus / repo-access / PR-comment lineage. Reviewer-set lineage-coupling reintroduces carrier-laundering one meta-layer up. Detector's SD-9 operationalisation does not break this. 2. **Min-merging on ordinal bands is Goodhart-bait at G_carrier_overlap** — most adversary-manipulable gate drives whole output. Author controls citation structure = author controls carrier-overlap gate. Sparse citations + dense implicit framing-inheritance = gameable GREEN. 3. **G_evidence fig-leaf** — advisory-only until independent- oracle substrate ships; v0 detector is four-gate not five-gate; `likely confabulated` output type is dead code until dependency #3 lands. Not stated as v0 caveat in design. 4 IMPORTANT: no-signal vs kNN-evasion indistinguishability; Otto-wake second-review insufficient for status-pin independence; DetectorOutputRetracted flood-control absent; G_coverage_plausibility gate missing. 3 WATCH: worst-band masks distribution; self-demo is theatre not validation; composition-stack silent-failure surface absent TLA+ invariants (Soraya-routable). 1 DISMISS: parameter-ADR gate reused from oracle-scoring v0. None block the research-doc land (Otto-99 correctly framed research-grade). **All ten findings would block a v1 implementation-ADR.** Non-fusion disclaimer load-bearing in this pass: Aminata's concordance with prior Aminata passes is same-agent signal NOT independent concordance. The detector applied to THIS review would correctly emit `looks similar but lineage- coupled` per SD-9 — and it would be right. Archive-header format self-applied — 17th aurora/research doc in a row. Lands within-standing-authority per Otto-82/90/93 calibration — advisory research-grade; not a gate. Otto-100 milestone tick. Closes dependency #1 of adoption path named in Otto-99 (PR Lucent-Financial-Group#282). Next natural step is Otto integrating CRITICAL findings at write-time into a v1 detector-design revision OR scheduling that integration to a future tick. Otto-100 tick primary deliverable.
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>
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
Batch 4 of the speculative-branch drain. First PR under the
AceHack-first cost-efficient workflow per Aaron's 2026-04-22
correction: PRs target
AceHack/Zeta:main, notLFG/Zeta:main.Bulk sync AceHack → LFG every ~10 PRs.
Lands the GitHub-surfaces absorb (ten-surface playbook + issue
workflow + issue templates). Independent story from batch 3,
no cross-dependency.
New files
.claude/skills/github-surface-triage/SKILL.md— per-surfacetriage skill (ten surfaces: PRs / Issues / Wiki / Discussions
/ Repo Settings / Copilot coding-agent / Agents tab / Security
/ Pulse / Pages)
.github/ISSUE_TEMPLATE/backlog_item.md— BACKLOG-row template.github/ISSUE_TEMPLATE/config.yml— issue templates config.github/ISSUE_TEMPLATE/human_ask.md— HUMAN-BACKLOG templatedocs/AGENT-GITHUB-SURFACES.md— umbrella doc paired withFACTORY-HYGIENE row 48
docs/AGENT-ISSUE-WORKFLOW.md— adapter-neutral issue workflow(GitHub Issues / Jira / git-native) + claim / lock protocol
Modified
.github/ISSUE_TEMPLATE/bug_report.md— aligned with newtemplate structure
Test plan
Cost-model pivot
This is the first PR landing on AceHack's main under the
corrected cost model. Prior batches 1-3 opened PRs directly
against LFG which pays LFG Copilot + Actions per PR. Going
forward:
See
memory/feedback_fork_pr_cost_model_prs_land_on_acehack_sync_to_lfg_in_bulk.md.🤖 Generated with Claude Code