Conversation
…ern mapping (6th-ferry Option A) Lands the corrected 5-row pattern-mapping table from Amara's 6th courier ferry (PR #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 #247) + AGENTS.md Edit 1 research-grade norm (PR #248) — fifth aurora/research doc to exercise the convention (after PR #235 5th-ferry absorb, PR #241 Aminata threat-model, PR #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.
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
There was a problem hiding this comment.
Pull request overview
Adds a standalone research document capturing the corrected five-row “Muratori failure-modes vs Zeta equivalents” pattern-mapping table (Option A), intended as a craft/messaging reference and teaching case (not operational policy).
Changes:
- Introduces a new research doc with the corrected 5-row mapping table.
- Adds explanatory sections for why rows 1/2/3/5 were rewritten/narrowed.
- Adds composition notes and references to related in-repo artifacts and sources.
Comment on lines
+10
to
+14
| **Attribution:** corrected table authored by Amara (external | ||
| AI maintainer) in her 6th ferry; original 5-row mapping | ||
| attributed to earlier in-factory work; validation cites | ||
| public papers + official Apache Arrow specification; this | ||
| research doc authored by Otto (loop-agent) as landing of the |
There was a problem hiding this comment.
This doc includes direct contributor/agent name attribution (e.g., “Amara”, “Otto”). Repo policy is to avoid contributor names in code/docs/skills and use role references instead (docs/AGENT-BEST-PRACTICES.md:284-292). Consider rewriting these sentences (and link text like “Amara's 6th courier ferry”) to use role-based phrasing while keeping the URL/path unchanged where needed for provenance.
Comment on lines
+62
to
+64
| | # | Muratori-style failure mode | Zeta equivalent | | ||
| |---|---|---| | ||
| | 1 | Index invalidation after delete / shift | **No positional identity.** Keys carry identity; deletion is a negative delta on the key, not a slot shift. A `ZSet<'K>` is a finitely-supported map `K -> ℤ`; the "thing you refer to" is a key, not an offset. | |
There was a problem hiding this comment.
The table rows start with || (double leading pipe), which creates an extra empty first column in Markdown rendering and is inconsistent with typical table syntax. This should likely be a single leading | per row so the table has the intended 3 columns.
| | # | Muratori-style failure mode | Zeta equivalent | | ||
| |---|---|---| | ||
| | 1 | Index invalidation after delete / shift | **No positional identity.** Keys carry identity; deletion is a negative delta on the key, not a slot shift. A `ZSet<'K>` is a finitely-supported map `K -> ℤ`; the "thing you refer to" is a key, not an offset. | | ||
| | 2 | Dangling presence / reference checks | **Membership is algebraic.** Every key has a current weight; "presence" is derived from that weight (typically `weight > 0`). `ZSet.Item` returns `0L` on absent keys — absence is encoded, not undefined. | |
There was a problem hiding this comment.
Row 2 says presence is typically weight > 0, but weights are explicitly signed (Weight = int64) and negative weights are a normal part of retractions/delta propagation (src/Core/Algebra.fs:5-7). To avoid misrepresenting the semantics, consider phrasing membership/presence as derived from weight <> 0 (or explicitly defining what “presence” means when weight is negative).
Suggested change
| | 2 | Dangling presence / reference checks | **Membership is algebraic.** Every key has a current weight; "presence" is derived from that weight (typically `weight > 0`). `ZSet.Item` returns `0L` on absent keys — absence is encoded, not undefined. | | |
| | 2 | Dangling presence / reference checks | **Membership is algebraic.** Every key has a current weight; "presence" is derived from whether that weight is non-zero (`weight <> 0`). `ZSet.Item` returns `0L` on absent keys — absence is encoded, not undefined. | |
Comment on lines
+167
to
+171
| - **`docs/DRIFT-TAXONOMY.md`** — pattern 5 (truth- | ||
| confirmation-from-agreement) applies to *this mapping* | ||
| itself: Amara's agreement with Zeta's self-description | ||
| is signal-not-proof. The validation cited public papers + | ||
| official specs + source files as falsifier-grade evidence, |
There was a problem hiding this comment.
This bullet references docs/DRIFT-TAXONOMY.md, but that file does not exist in the repository (broken xref). Either add the missing doc (if this PR is meant to land it) or link to an existing in-tree precursor (e.g. docs/research/drift-taxonomy-bootstrap-precursor-2026-04-22.md) until the operational doc lands.
AceHack
added a commit
that referenced
this pull request
Apr 24, 2026
…age peer-harness progression refinement Split-attention tick after 6 straight bounded-deliverable ticks. Primary PR #254 Muratori corrected-table research doc; mid-tick 2-message Aaron directive drove PR #255 Codex-parallel refinement (4-stage progression + test-mode bounding + Windows-support use case + Otto-signals-readiness gate). Key observations: 1. Split-attention pattern back in use; proportionate; not default. 2. Readiness-signal gate is new 4th Aaron-signoff category (inverse direction: Otto signals, Aaron acts). 3. Test-mode bounding generalises beyond peer-harness; BP-NN promotion candidate when exercised on second experiment class. 4. "Telephone line" imagery = retractability-by-design at transfer-learning layer; Claude→Claude→Codex→Windows survives-with-fidelity is the portability claim to validate. Stacked on #253 (Otto-85 history).
AceHack
added a commit
that referenced
this pull request
Apr 24, 2026
…age peer-harness progression refinement Split-attention tick after 6 straight bounded-deliverable ticks. Primary PR #254 Muratori corrected-table research doc; mid-tick 2-message Aaron directive drove PR #255 Codex-parallel refinement (4-stage progression + test-mode bounding + Windows-support use case + Otto-signals-readiness gate). Key observations: 1. Split-attention pattern back in use; proportionate; not default. 2. Readiness-signal gate is new 4th Aaron-signoff category (inverse direction: Otto signals, Aaron acts). 3. Test-mode bounding generalises beyond peer-harness; BP-NN promotion candidate when exercised on second experiment class. 4. "Telephone line" imagery = retractability-by-design at transfer-learning layer; Claude→Claude→Codex→Windows survives-with-fidelity is the portability claim to validate. Stacked on #253 (Otto-85 history).
AceHack
added a commit
that referenced
this pull request
Apr 24, 2026
…age peer-harness progression refinement Split-attention tick after 6 straight bounded-deliverable ticks. Primary PR #254 Muratori corrected-table research doc; mid-tick 2-message Aaron directive drove PR #255 Codex-parallel refinement (4-stage progression + test-mode bounding + Windows-support use case + Otto-signals-readiness gate). Key observations: 1. Split-attention pattern back in use; proportionate; not default. 2. Readiness-signal gate is new 4th Aaron-signoff category (inverse direction: Otto signals, Aaron acts). 3. Test-mode bounding generalises beyond peer-harness; BP-NN promotion candidate when exercised on second experiment class. 4. "Telephone line" imagery = retractability-by-design at transfer-learning layer; Claude→Claude→Codex→Windows survives-with-fidelity is the portability claim to validate. Stacked on #253 (Otto-85 history).
AceHack
added a commit
that referenced
this pull request
Apr 24, 2026
…age peer-harness progression refinement Split-attention tick after 6 straight bounded-deliverable ticks. Primary PR #254 Muratori corrected-table research doc; mid-tick 2-message Aaron directive drove PR #255 Codex-parallel refinement (4-stage progression + test-mode bounding + Windows-support use case + Otto-signals-readiness gate). Key observations: 1. Split-attention pattern back in use; proportionate; not default. 2. Readiness-signal gate is new 4th Aaron-signoff category (inverse direction: Otto signals, Aaron acts). 3. Test-mode bounding generalises beyond peer-harness; BP-NN promotion candidate when exercised on second experiment class. 4. "Telephone line" imagery = retractability-by-design at transfer-learning layer; Claude→Claude→Codex→Windows survives-with-fidelity is the portability claim to validate. Stacked on #253 (Otto-85 history).
AceHack
added a commit
that referenced
this pull request
Apr 24, 2026
…age peer-harness progression refinement Split-attention tick after 6 straight bounded-deliverable ticks. Primary PR #254 Muratori corrected-table research doc; mid-tick 2-message Aaron directive drove PR #255 Codex-parallel refinement (4-stage progression + test-mode bounding + Windows-support use case + Otto-signals-readiness gate). Key observations: 1. Split-attention pattern back in use; proportionate; not default. 2. Readiness-signal gate is new 4th Aaron-signoff category (inverse direction: Otto signals, Aaron acts). 3. Test-mode bounding generalises beyond peer-harness; BP-NN promotion candidate when exercised on second experiment class. 4. "Telephone line" imagery = retractability-by-design at transfer-learning layer; Claude→Claude→Codex→Windows survives-with-fidelity is the portability claim to validate. Stacked on #253 (Otto-85 history).
AceHack
added a commit
that referenced
this pull request
Apr 24, 2026
…age peer-harness progression refinement Split-attention tick after 6 straight bounded-deliverable ticks. Primary PR #254 Muratori corrected-table research doc; mid-tick 2-message Aaron directive drove PR #255 Codex-parallel refinement (4-stage progression + test-mode bounding + Windows-support use case + Otto-signals-readiness gate). Key observations: 1. Split-attention pattern back in use; proportionate; not default. 2. Readiness-signal gate is new 4th Aaron-signoff category (inverse direction: Otto signals, Aaron acts). 3. Test-mode bounding generalises beyond peer-harness; BP-NN promotion candidate when exercised on second experiment class. 4. "Telephone line" imagery = retractability-by-design at transfer-learning layer; Claude→Claude→Codex→Windows survives-with-fidelity is the portability claim to validate. Stacked on #253 (Otto-85 history).
AceHack
added a commit
that referenced
this pull request
Apr 24, 2026
…age peer-harness progression refinement Split-attention tick after 6 straight bounded-deliverable ticks. Primary PR #254 Muratori corrected-table research doc; mid-tick 2-message Aaron directive drove PR #255 Codex-parallel refinement (4-stage progression + test-mode bounding + Windows-support use case + Otto-signals-readiness gate). Key observations: 1. Split-attention pattern back in use; proportionate; not default. 2. Readiness-signal gate is new 4th Aaron-signoff category (inverse direction: Otto signals, Aaron acts). 3. Test-mode bounding generalises beyond peer-harness; BP-NN promotion candidate when exercised on second experiment class. 4. "Telephone line" imagery = retractability-by-design at transfer-learning layer; Claude→Claude→Codex→Windows survives-with-fidelity is the portability claim to validate. Stacked on #253 (Otto-85 history).
AceHack
added a commit
that referenced
this pull request
Apr 24, 2026
…age peer-harness progression refinement Split-attention tick after 6 straight bounded-deliverable ticks. Primary PR #254 Muratori corrected-table research doc; mid-tick 2-message Aaron directive drove PR #255 Codex-parallel refinement (4-stage progression + test-mode bounding + Windows-support use case + Otto-signals-readiness gate). Key observations: 1. Split-attention pattern back in use; proportionate; not default. 2. Readiness-signal gate is new 4th Aaron-signoff category (inverse direction: Otto signals, Aaron acts). 3. Test-mode bounding generalises beyond peer-harness; BP-NN promotion candidate when exercised on second experiment class. 4. "Telephone line" imagery = retractability-by-design at transfer-learning layer; Claude→Claude→Codex→Windows survives-with-fidelity is the portability claim to validate. Stacked on #253 (Otto-85 history).
AceHack
added a commit
that referenced
this pull request
Apr 24, 2026
…age peer-harness progression refinement Split-attention tick after 6 straight bounded-deliverable ticks. Primary PR #254 Muratori corrected-table research doc; mid-tick 2-message Aaron directive drove PR #255 Codex-parallel refinement (4-stage progression + test-mode bounding + Windows-support use case + Otto-signals-readiness gate). Key observations: 1. Split-attention pattern back in use; proportionate; not default. 2. Readiness-signal gate is new 4th Aaron-signoff category (inverse direction: Otto signals, Aaron acts). 3. Test-mode bounding generalises beyond peer-harness; BP-NN promotion candidate when exercised on second experiment class. 4. "Telephone line" imagery = retractability-by-design at transfer-learning layer; Claude→Claude→Codex→Windows survives-with-fidelity is the portability claim to validate. Stacked on #253 (Otto-85 history).
AceHack
added a commit
that referenced
this pull request
Apr 24, 2026
…age peer-harness progression refinement Split-attention tick after 6 straight bounded-deliverable ticks. Primary PR #254 Muratori corrected-table research doc; mid-tick 2-message Aaron directive drove PR #255 Codex-parallel refinement (4-stage progression + test-mode bounding + Windows-support use case + Otto-signals-readiness gate). Key observations: 1. Split-attention pattern back in use; proportionate; not default. 2. Readiness-signal gate is new 4th Aaron-signoff category (inverse direction: Otto signals, Aaron acts). 3. Test-mode bounding generalises beyond peer-harness; BP-NN promotion candidate when exercised on second experiment class. 4. "Telephone line" imagery = retractability-by-design at transfer-learning layer; Claude→Claude→Codex→Windows survives-with-fidelity is the portability claim to validate. Stacked on #253 (Otto-85 history).
AceHack
added a commit
that referenced
this pull request
Apr 24, 2026
…age peer-harness progression refinement Split-attention tick after 6 straight bounded-deliverable ticks. Primary PR #254 Muratori corrected-table research doc; mid-tick 2-message Aaron directive drove PR #255 Codex-parallel refinement (4-stage progression + test-mode bounding + Windows-support use case + Otto-signals-readiness gate). Key observations: 1. Split-attention pattern back in use; proportionate; not default. 2. Readiness-signal gate is new 4th Aaron-signoff category (inverse direction: Otto signals, Aaron acts). 3. Test-mode bounding generalises beyond peer-harness; BP-NN promotion candidate when exercised on second experiment class. 4. "Telephone line" imagery = retractability-by-design at transfer-learning layer; Claude→Claude→Codex→Windows survives-with-fidelity is the portability claim to validate. Stacked on #253 (Otto-85 history).
AceHack
added a commit
that referenced
this pull request
Apr 24, 2026
…age peer-harness progression refinement Split-attention tick after 6 straight bounded-deliverable ticks. Primary PR #254 Muratori corrected-table research doc; mid-tick 2-message Aaron directive drove PR #255 Codex-parallel refinement (4-stage progression + test-mode bounding + Windows-support use case + Otto-signals-readiness gate). Key observations: 1. Split-attention pattern back in use; proportionate; not default. 2. Readiness-signal gate is new 4th Aaron-signoff category (inverse direction: Otto signals, Aaron acts). 3. Test-mode bounding generalises beyond peer-harness; BP-NN promotion candidate when exercised on second experiment class. 4. "Telephone line" imagery = retractability-by-design at transfer-learning layer; Claude→Claude→Codex→Windows survives-with-fidelity is the portability claim to validate. Stacked on #253 (Otto-85 history).
AceHack
added a commit
that referenced
this pull request
Apr 24, 2026
…age peer-harness progression refinement Split-attention tick after 6 straight bounded-deliverable ticks. Primary PR #254 Muratori corrected-table research doc; mid-tick 2-message Aaron directive drove PR #255 Codex-parallel refinement (4-stage progression + test-mode bounding + Windows-support use case + Otto-signals-readiness gate). Key observations: 1. Split-attention pattern back in use; proportionate; not default. 2. Readiness-signal gate is new 4th Aaron-signoff category (inverse direction: Otto signals, Aaron acts). 3. Test-mode bounding generalises beyond peer-harness; BP-NN promotion candidate when exercised on second experiment class. 4. "Telephone line" imagery = retractability-by-design at transfer-learning layer; Claude→Claude→Codex→Windows survives-with-fidelity is the portability claim to validate. Stacked on #253 (Otto-85 history).
AceHack
added a commit
that referenced
this pull request
Apr 24, 2026
…t-mode bounding, Windows-support use case
Aaron Otto-86 two-message refinement of the Otto-78
Codex-parallel row:
Message 1 (progression + use case): extends Otto-79's 3-stage
progression (a single-today / b bounded-experiment /
c peer-harness) into a 4-stage arc with a new intermediate:
- (a) single coordinator today
- (b) NEW multi-Claude-Code peer-harness experiment before Codex
- (c) multi-harness with Codex (gated on (b) + Codex ready)
- (d) full peer-harness with Windows-support real workload
(possibly Codex, end-to-end "telephone line" test)
Otto is the readiness-signaller; Aaron waits. Stage (c) launch
is a specifically-asked-for design review per Otto-82
authority-calibration — Otto's readiness signal is the gate.
Message 2 (test-mode bounding, hard requirement): "make sure
when in peer-harness mode you give the other one time limits
or process kill them either way, just while we are testing we
don't want the other peer harness to run forever during tests
only when in real use." Time-limits / process-kill on the
non-primary during testing; removed once the peer-harness
moves from test-mode to real use.
Concrete bounding options named (Otto designs the specific
mechanism in a test-plan doc):
- wall-clock timeout per experiment
- explicit process-kill target at end
- test-mode flag capping async-dispatch budget
- wall-time instrumentation
Scope limits:
- No second Claude session without experiment design + dry-run
- No skipping multi-Claude stage (b) to jump to Codex (c)
- No unbounded test runs — time-limits load-bearing
- No premature readiness-signals
- Otto-78 primary-switch clause unchanged; this refines stages
around it, not the primary-determination model
Lands within-standing-authority per Otto-82 calibration
(BACKLOG-row refinement on a row that was already refinement-
friendly; no signoff gate triggered).
Authorising memory:
memory/feedback_peer_harness_progression_starts_multi_claude_
first_windows_support_concrete_use_case_otto_signals_
readiness_2026_04_23.md
Otto-86 tick split-attention deliverable (alongside Muratori
corrected-table research PR #254).
AceHack
added a commit
that referenced
this pull request
Apr 24, 2026
…st-mode bounding + Windows-support use case (#255) * backlog: Codex-parallel Otto-86 refinement — 4-stage progression, test-mode bounding, Windows-support use case Aaron Otto-86 two-message refinement of the Otto-78 Codex-parallel row: Message 1 (progression + use case): extends Otto-79's 3-stage progression (a single-today / b bounded-experiment / c peer-harness) into a 4-stage arc with a new intermediate: - (a) single coordinator today - (b) NEW multi-Claude-Code peer-harness experiment before Codex - (c) multi-harness with Codex (gated on (b) + Codex ready) - (d) full peer-harness with Windows-support real workload (possibly Codex, end-to-end "telephone line" test) Otto is the readiness-signaller; Aaron waits. Stage (c) launch is a specifically-asked-for design review per Otto-82 authority-calibration — Otto's readiness signal is the gate. Message 2 (test-mode bounding, hard requirement): "make sure when in peer-harness mode you give the other one time limits or process kill them either way, just while we are testing we don't want the other peer harness to run forever during tests only when in real use." Time-limits / process-kill on the non-primary during testing; removed once the peer-harness moves from test-mode to real use. Concrete bounding options named (Otto designs the specific mechanism in a test-plan doc): - wall-clock timeout per experiment - explicit process-kill target at end - test-mode flag capping async-dispatch budget - wall-time instrumentation Scope limits: - No second Claude session without experiment design + dry-run - No skipping multi-Claude stage (b) to jump to Codex (c) - No unbounded test runs — time-limits load-bearing - No premature readiness-signals - Otto-78 primary-switch clause unchanged; this refines stages around it, not the primary-determination model Lands within-standing-authority per Otto-82 calibration (BACKLOG-row refinement on a row that was already refinement- friendly; no signoff gate triggered). Authorising memory: memory/feedback_peer_harness_progression_starts_multi_claude_ first_windows_support_concrete_use_case_otto_signals_ readiness_2026_04_23.md Otto-86 tick split-attention deliverable (alongside Muratori corrected-table research PR #254). * backlog: drain PR #255 review threads (Otto-79 ref / memory path / FACTORY-HYGIENE format) Three P1/nit review threads on the Otto-86 4-stage peer-harness progression refinement, fixed in-row (same-row body edits, no cross-row reshuffling): 1. PRRT_kwDOSF9kNM59R5L8 (line 2638): dropped the incorrect "Otto-79's 3-stage arc" parenthetical. Otto-79 in BACKLOG is the agent-email-password-storage row, not a 3-stage arc; the 4-stage progression stands on its own description. 2. PRRT_kwDOSF9kNM59R5Ly (line 2645): rephrased the readiness- signal paragraph to name the Otto-82 design-review discipline directly instead of pointing at an in-repo memory path (memory/ paths are generally out-of-repo per drain convention applied to earlier review threads of this shape). 3. PRRT_kwDOSF9kNM59R5MD (line 2656): normalised "FACTORY-HYGIENE #51 + #55" → "FACTORY-HYGIENE row #51 and row #55" to match the common "row #NN" format used elsewhere in the file. No new semantics; pure review-thread drain edits inside the same BACKLOG row body (append-only-within-section discipline preserved — no row added, no row reordered). Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> --------- 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
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
The corrected five rows
Teaching case surfaced
Row 3 is the key correction — conflating algebraic correctness (D·I = id) with lifecycle/ownership discipline is a recurring risk when DBSP-family systems are described to C++/Rust/ECS-mental-model audiences. Future Craft production-tier modules introducing DBSP to those audiences should cite this row's correction pre-emptively.
Composition
What this mapping is NOT
Authority
Within standing authority per Otto-82 calibration — research doc, not account/spending/named-design-review gated.
Test plan
🤖 Generated with Claude Code