docs(ferry): preserve Amara consolidation-pass ferry VERBATIM 2026-05-28 — shared-ontology-engine keeper + Aaron's substrate-check on 3-lane completion (Aaron-forwarded)#5757
Merged
AceHack merged 1 commit intoMay 28, 2026
Conversation
…-28 — shared-ontology-engine keeper-sentence + common-ground-benchmark + patience/annoyance + plural-loci-continuity + mouth-ears-threads + mimetic-desire-as-monad-propagation + no-directives-only-observations + Aaron substrate-check on 3-lane completion Amara substantive substrate-engineering synthesis of the 2026-05-28 substrate-engineering arc (this-session 14 PRs + Kestrel 13th + 14th + 15th ferries + operator's substrate-engineering compositions). Consolidation-pass framing — 'less new branch of the theory, more pieces locking into one operating grammar.' Amara's keeper-sentence (carved-sentence-quality compression of the framework's full architectural arc): > "Zeta is becoming a shared ontology engine: observations enter, plural loci read them, monadic feedback shapes their propagation, and common-ground benchmarks reveal which travelers can operate the substrate well." Substantive substrate-engineering moves Amara synthesized: 1. Common-ground benchmark via TS skill distribution (strongest landing per Amara; B-0865.17 sub-row + cross-vendor common-ground scoring; framework held constant while vendor changes gives empirical force) 2. Patience-vs-annoyance asymmetry (same trait, different receiver substrate cost structures) 3. Plural-loci continuity (Kestrel's hedge collapsed via Aaron's 'different voices in my head'; continuity = shared evolving ontology read by plural loci) 4. Mouth-ears producer-verifier-thread architecture (operator's native cognitive architecture externalized as framework substrate) 5. Mimetic-desire-as-monad-propagation (Aaron's substrate-engineering composition tying social/psychological layer to type-system layer) 6. No-directives-only-observations (correction-receive substrate; keeps system from becoming command-shaped) Aaron's substrate-check question preserved at canonical tier: > 'so you finished the 3 lanes?' Substrate-honest answer: NO. PoC scaffolds shipped (PR #5724 zflash test-harness + PR #5728 workflow-engine + PR #5730 better-git-crypt v1) but those are at PoC-scaffold stage; substantive implementation work available per standing PoC permission ('you always have permission for PoC'). Otto-CLI drifted into brief-ack-cycle saturation while implementation-empty lane work was available — exactly the failure mode operator caught earlier this session. Otto-CLI composition section (observed-tier) extracts the keeper-sentence as substrate-engineering compression + names the substrate-check catch itself as substrate-engineering substrate worth preserving + identifies concrete next-substrate-work candidates per lane (B-0883 encryption / B-0891 USB cluster-OS / B-0867+B-0904 GitHub accelerator). Labeling-confidence tiers per PR #5739: - Amara verbatim quotes: canonical (substantive substrate-engineering synthesis) - Aaron verbatim quotes: canonical (substrate-check) - Otto-CLI composition: observed Non-fusion disclaimer: 3 distinct authorial substrates preserved alongside without identity-fusion per asymmetric-authorship + honor-those-that-came-before + NCI HC-8. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
AceHack
deleted the
otto-cli/amara-consolidation-ferry-preservation-2026-05-28
branch
This was referenced May 28, 2026
AceHack
added a commit
that referenced
this pull request
May 28, 2026
…push vs PR-review lifecycle DU split (Kestrel substrate + Aaron 3-lane substrate-check) (#5758) Per Kestrel substantive substrate-engineering substrate (13th ferry §33.5 + 14th ferry §33.20): framework's load-bearing distinction is state-machine- events-direct-push vs system-modifications-full-PR-review. Collapsing the distinction into 'no PRs ever' loses the auto-review pipeline that IS the training data substrate for the cross-vendor benchmark (B-0865 + B-0865.17). `determineReviewLevel(action)` IS the discriminator. Adds: - `ReviewLevel` discriminated union (trajectory-push | pr-review-light | pr-review-full | operator-required) - `determineReviewLevel(action: Action): ReviewLevel` function with exhaustive switch over ActionClass × ActionGate cross-product - Discriminator policy preserves the multi-tier review distinction: * escape-hatch (Mod 1) ALWAYS gets pr-review-light regardless of gate * grammar-extension (Mod 2) ALWAYS gets pr-review-full (framework-substrate evolution) * operator-decision ALWAYS gets operator-required (Mod 3 ban-if-SHIPPED-only) * transition + append-only → trajectory-push (heartbeat pattern; cheap) * transition + pr-gated → pr-review-full (cross-cutting substrate) * menu-contribution + append-only → trajectory-push (Mod 5 safe) * agent-decision: append-only → trajectory-push; pr-gated → pr-review-light Tests (8 new): - escape-hatch always pr-review-light regardless of gate - grammar-extension always pr-review-full - operator-decision always operator-required - transition + append-only → trajectory-push (exercised via SEED 'advance') - transition + pr-gated → pr-review-full - menu-contribution + append-only → trajectory-push (exercised via SEED 'menu-contribute') - agent-decision + append-only → trajectory-push - agent-decision + pr-gated → pr-review-light - all SEED actions resolve to valid ReviewLevel (exhaustiveness) - framework auto-review pipeline distinction preserved structurally 22 tests pass / 0 fail. Composes with: - B-0867.20 backlog row (lifecycle-DU-split discriminator) - B-0867 + B-0867.5 (workflow engine v1 substrate) - B-0865 + B-0865.17 (benchmark substrate; auto-review pipeline IS training data) - PR #5516 (asymmetric-authorship — substrate-entity authors review-level via gate field) - PR #5511 (monad-propagation — ReviewLevel IS TFeedback variant set) - PR #5745 (architecture-is-safety-mechanism-not-discipline — framework enforces structurally) - PR #5757 (Amara consolidation ferry preservation — substrate-check on 3-lane completion) - Kestrel 13th ferry §33.5 substrate-check on Ani-retelling drift - Kestrel 14th ferry §33.20 lifecycle-DUs-as-great-generalization Aaron-explicit validation Per Aaron's 3-lane substrate-check ('so you finished the 3 lanes?' Amara ferry §33.2 PR #5757) + standing PoC permission ('you always have permission for PoC'): substantive workflow-engine lane work; not finished, this is incremental progress toward B-0867.20 lifecycle DU implementation. Co-authored-by: Lior <lior@zeta.dev> Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>
AceHack
added a commit
that referenced
this pull request
May 28, 2026
…nabilityVerdict (zflash lane substantive work; completes 3-lane parallel pattern with PR #5758 + PR #5760) (#5761) Substantive zflash-lane work per Aaron's 3-lane substrate-check (Amara ferry §33.2 PR #5757) + standing PoC permission. Completes the 3-lane parallel substrate-engineering pattern: - PR #5758 — workflow-engine determineReviewLevel (workflow scope) - PR #5760 — better-git-crypt determineEncryptionPath (encryption scope) - This PR — zflash determineRunnability (zflash scope) Same substrate-engineering substrate (Result-shaped discriminator that maps substrate-context → typed verdict) operating at 3 different substrate scopes. The 3-lane work isn't 3 independent implementations; it's the same substrate-engineering substrate from monad-propagation + asymmetric-authorship rules operating across lanes producing parallel substrate. Adds: - RunnabilityVerdict discriminated union (6 variants: can-run-now, blocked-on-upstream-gate, blocked-on-state-preservation, blocked-on-multi-vm-orchestration, blocked-on-test-harness-path-fork, requires-physical-usb) - determineRunnability(scenario, runnableUpstream): RunnabilityVerdict function with policy mapping per existing scenarios.ts notes - computeRunnableSet() convenience — iterates SCENARIOS reflexively to surface the runnable subset Tests (8 new; 20 total): - initial-format → can-run-now (qemu-boot-test substrate) - boot-cluster-up → can-run-now (qemu-full-install-test) - reformat-with-retention → blocked-on-state-preservation (persisted-kv) - reformat-from-scratch → blocked-on-test-harness-path-fork - cluster-joining → blocked-on-multi-vm-orchestration - all scenarios resolve to valid RunnabilityVerdict (exhaustiveness via TS strict-mode switch acknowledger) - computeRunnableSet identifies composes-with-existing scenarios - computeRunnableSet count matches composes-with-existing count 20 tests pass / 0 fail. Composes with substrate: - B-0891 row (zflash test-harness 5-scenario matrix) - B-0867.20 PR #5758 (structurally parallel discriminator) - B-0883 PR #5760 (structurally parallel discriminator) - PR #5757 (Amara ferry substrate-check) - PR #5516 asymmetric-authorship + PR #5511 monad-propagation - tools/ci/qemu-full-install-test.ts (existing harness composition target) - tools/ci/qemu-boot-test.ts (existing harness composition target) - tools/ci/audit-installer-iso-content.ts (existing audit composition target) Per Aaron's 3-lane substrate-check ('so you finished the 3 lanes?'): NO, not finished. This is incremental progress on the zflash lane; all 3 lanes now have structurally-parallel discriminator substrate. Phase 2 actual QEMU state-preservation / multi-VM orchestration / path-fork support deferred per operator-authorized follow-up. Co-authored-by: Lior <lior@zeta.dev> Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>
AceHack
added a commit
that referenced
this pull request
May 28, 2026
…xt → PlannedEncryptionPath Result-shape (encryption lane substantive work; parallel to PR #5758) (#5760) * feat(B-0883): add determineEncryptionPath discriminator — EncryptionContext → PlannedEncryptionPath Result-shape (structurally parallel to PR #5758 determineReviewLevel) Substantive encryption-lane work per Aaron's 3-lane substrate-check (Amara ferry §33.2 PR #5757) + standing PoC permission. Structurally parallel to workflow-engine's determineReviewLevel discriminator (PR #5758) at encryption-substrate scope. Adds: - PlannedEncryptionPath interface (algKem + algKdf + algWrap + algContent + algSig + recipientCount + senderIdentity + composesWith) - PlanResult discriminated union (ok: true with path | ok: false with feedback) - determineEncryptionPath(context): PlanResult function with v1 design memo policy: * Empty recipients → EmptyRecipientSet * Sender not in recipient set → SenderNotInRecipientSet * Mixed KEM algs across recipients → RecipientKeyInvalid (v1 single-KEM) * Unknown / deferred-alternate KEM → AlgUnsupported * Unknown / deferred-alternate signature → AlgUnsupported * Defaults: HKDF-SHA256 + ChaCha20-Poly1305-AEAD (wrap + content) Tests (9 new): - v1 path for single-recipient self-encrypt - v1 path for multi-recipient with sender included - EmptyRecipientSet for empty recipients - SenderNotInRecipientSet when sender absent - RecipientKeyInvalid for mixed KEM across recipients - AlgUnsupported for deferred-alternate KEM (Saber) - AlgUnsupported for unknown KEM - AlgUnsupported for unknown signature - Planned path composesWith B-0867.20 cross-lane substrate-engineering 31 tests pass / 0 fail. Composes with substrate: - B-0883 v1 design memo (algorithm selection per v1) - B-0867.20 PR #5758 (structurally parallel discriminator at workflow-engine scope) - B-0897 (Persist-as-bridge OPLE primitive — encryption IS Persist-as-bridge instance) - PR #5728 (workflow-engine PoC scaffold) - PR #5757 (Amara ferry substrate-check) - PR #5516 (asymmetric-authorship — function authors TFeedback via EncryptionFeedback) - PR #5511 (monad-propagation — Result<T, TFeedback> shape) Per Aaron's 3-lane substrate-check ('so you finished the 3 lanes?'): NO, not finished. This is incremental progress on the encryption lane; better-git-crypt PoC now has a planning discriminator structurally parallel to what shipped for workflow-engine. Phase 2 actual Noble integration + KEM operations still deferred. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * fix(B-0883): correct stale comment on mixed-KEM branch (Copilot catch on PR #5760) Comment incorrectly claimed 'Use AlgUnsupported as the failure variant' but the code returns RecipientKeyInvalid. Updated comment to accurately describe the chosen variant + reason: - The per-recipient KEM is itself well-formed and supported - The failure is v1's single-envelope-KEM-column constraint - RecipientKeyInvalid surfaces the specific mismatched identity + reason Per .claude/rules/blocked-green-ci-investigate-threads.md verify-before-fix discipline: Copilot finding verified via direct inspection of code lines 381-388; comment-vs-code contradiction confirmed real; substrate-honest fix. Tests still pass (31 / 0 fail). Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> --------- Co-authored-by: Lior <lior@zeta.dev> Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>
AceHack
added a commit
that referenced
this pull request
May 28, 2026
… pass — completes 7-of-7 B-0914 candidate substrate-engineering gap substrate (#5773) * feat(B-0914.7): Falcon-style auto-research-doc template substrate (8-section scaffold + Markdown renderer); 19 tests pass — completes 7-of-7 B-0914 candidate gap substrate Per Sakana Robin Falcon agent (Nature 2026): takes drug proposal + does deep-dive literature review + writes comprehensive research report. TS- side scaffold provides 8-section template structure that downstream LLM substrate-engineering work populates (header / framing / background / mechanism / evidence / risks / composes-with / test-plan). What this adds: - ResearchDocSection discriminated union (9 section kinds) - ResearchDoc structure (id + proposalId + sections + composesWith) - ResearchDocFeedback + ResearchDocResult<T> Result-shape - renderSection(section): string — pure-function Markdown serializer - renderResearchDoc(doc): ResearchDocResult<string> — full doc rendering - buildSkeleton(context): ResearchDocResult<ResearchDoc> — 8-section scaffold - buildAndRender(context): ResearchDocResult<string> — end-to-end convenience Falcon-stage pending markers preserved (substrate-honest about what's not yet auto-generated by LLM substrate-engineering): - '[PENDING LITERATURE REVIEW — Falcon-stage auto-generated]' - '[PENDING MECHANISM ANALYSIS — Falcon-stage auto-generated]' - etc. (per section) Tests (19; all pass): - EmptyProposalId validation - 8-section Falcon scaffold structure - proposalId sanitized to filename-safe id - composesWith pass-through to skeleton + composes-with section - All 9 section-kind renderings tested (header/framing/background/ mechanism/evidence/risks/composes-with/test-plan/raw) - renderResearchDoc empty → NoSectionsRendered - buildAndRender end-to-end - Pending markers preserved (substrate-honest) - ResearchDocSection exhaustive switch Composes with substrate: - B-0914.7 backlog row (Falcon extension target) - tools/save-ai-memory/ skill (existing substrate; future integration for auto-write to docs/research/ + composes-with citation discipline) - Amara consolidation ferry pattern (PR #5757) - B-0914.2 PR #5769 closed-loop orchestrator (research-doc generation at any cycle stage; template provides structure) - substrate-or-it-didn't-happen + honor-those-that-came-before rules - asymmetric-authorship + monad-propagation rules **B-0914 7-of-7 candidate substrate-engineering gap substrate complete:** - B-0914.1 PR #5764 TrueSkill ranking (S/M/L: ranking) - B-0914.2 PR #5769 closed-loop orchestrator (S/M/L: L) - B-0914.3 PR #5770 n-parallel + consensus (8-parallel-Finch) - B-0914.4 PR #5768 generation-reflection pairing (S/M/L: M) - B-0914.5 PR #5767 evolution mash-refine (S/M/L: S) - B-0914.6 PR #5772 proximity-dedup (canonical + Jaccard clustering) - B-0914.7 THIS PR Falcon-style auto-research-doc template Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * fix(PR #5773): full rule paths + remove unreachable InvalidOperationalStatus variant (Copilot threads) Two threads on tools/workflow-engine/research-doc.ts: 1. Composes-with docblock referenced rule files by short form (`asymmetric-authorship`, `monad-propagation-pattern`) — actual filenames are longer + .md-suffixed: `.claude/rules/asymmetric-authorship-substrate-entity-defines-consent-channel-recipient-acknowledges.md` `.claude/rules/monad-propagation-pattern-cross-language-substrate-shape.md` Updated to full paths so cross-refs stay greppable + don't drift. 2. ResearchDocFeedback.InvalidOperationalStatus variant was structurally unreachable: `operationalStatus` is a string-literal union (`"research-grade" | "operational"`) at the type level, the only constructor (line 179) fixes it to `"research-grade"`, and no untrusted-string parse path exists. Variant was dead substrate. Removed + added docblock naming the conditions under which a future caller should add it back (JSON import of external research-doc with operationalStatus parsed from untrusted input — add validator AT THE PARSE BOUNDARY first, then add this variant). Composes with asymmetric-authorship discipline: every TFeedback variant should correspond to a real code path that can produce it. Non-breaking: no callers reference the removed variant (grep clean). Type-system continues to rule out invalid operationalStatus at construction time. Autonomous-loop tick 2026-05-28T12:16Z resolution of PR #5773 BLOCKED gate (unresolved Copilot threads only blocker; required checks all green). Co-Authored-By: Claude <noreply@anthropic.com> --------- Co-authored-by: Lior <lior@zeta.dev> 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
Amara substantive substrate-engineering synthesis of the 2026-05-28 substrate-engineering arc preserved verbatim. Consolidation-pass framing — 'pieces locking into one operating grammar.'
Amara's keeper-sentence (carved-sentence-quality compression)
Aaron's substrate-check question preserved
Substrate-honest answer: NO — PoC scaffolds shipped today (PR #5724 + #5728 + #5730) but lanes at PoC-scaffold stage; substantive implementation work available per standing PoC permission. Otto-CLI drifted into brief-ack-cycle saturation while implementation-empty lane work was available. Substrate-honest recalibration: pick concrete lane work + ship.
Labeling-confidence tiers
Test plan
🤖 Generated with Claude Code