agents: Edit 1 — external-conversation absorbs land research-grade, not operational (Amara 5th-ferry) by AceHack · Pull Request #248 · Lucent-Financial-Group/Zeta

AceHack · 2026-04-24T02:13:36Z

Summary

Lands Amara's 5th-ferry Edit 1 as an additive bullet in `AGENTS.md` > "Agent operational practices".
Integrates Aminata's Otto-80 IMPORTANT finding by unifying vocabulary with §33 and §26 rather than introducing parallel "staged/ratified" terms.
Cites the drift-taxonomy promotion (PR promote: drift-taxonomy precursor → docs/DRIFT-TAXONOMY.md (Amara 5th-ferry Artifact A) #238) as worked example.

What it says (short form)

External-conversation absorbs (courier ferries, cross-AI reviews, ChatGPT pastes, other-harness transcripts) land research-grade, not operational. Content becomes factory policy only via a separate promotion step: operational doc per §2, ADR, §N rule, or BP-NN promotion. §26's active/landed/obsolete classifier applies to the promoted artifact, not the absorb.

Aminata concerns addressed

Two-classifier drift — resolved by using §33's `Operational status: research-grade` label instead of introducing parallel "staged/ratified" vocabulary.
Vague "separate promotion step" — resolved by naming four concrete promotion paths.
Scope ambiguity (which docs are covered?) — resolved by naming "external-conversation absorbs" explicitly and pointing §26 at the promoted artifact instead.

Authority

Lands as within-standing-authority per Otto-82 calibration memory. Governance/philosophy-doc edit; no explicit signoff gate triggered.

Test plan

Uses §33 vocabulary (not parallel terms)
Points at §26 correctly (for promoted artifact lifecycle, not absorb itself)
Worked example cited (drift-taxonomy promotion)
Register consistent with AGENTS.md "Agent operational practices" bullet-style
Scope explicit (external-conversation absorbs only)

Aminata-recommended edit ordering status

§33 (PR govern: §33 archive-header requirement (Amara 5th-ferry Artifact, Aaron-approved Otto-82) #247, landed Otto-82) ✓
Edit 1 (this PR) ←
Edit 4 (CLAUDE.md pointer-only, deferred)
Edit 2 (ALIGNMENT.md SD-9, deferred, WATCH)

🤖 Generated with Claude Code

…ot operational (Amara 5th-ferry Artifact, Aminata-integrated) Amara's 5th-ferry Edit 1 proposed a "research-grade absorbs are staged, not ratified" clause for AGENTS.md. Aminata's Otto-80 threat-model pass (PR #241) classified it IMPORTANT with one concern: it introduced "staged/ratified" parallel to §26's "active/landed/obsolete" classifier without reconciling the vocabularies, risking two-classifier drift. This lands the norm with Aminata's concern resolved by unifying vocabulary: - Uses §33 `Operational status: research-grade` label (not parallel "staged/ratified" terms). - Points at §26 lifecycle classifier for the PROMOTED current-state artifact, not for the absorb itself. - Explicit about which category of research doc is covered (external-conversation absorbs, NOT internal design docs which §26 has always governed). - Names four concrete promotion paths (operational doc per §2, ADR, §N rule, BP-NN promotion) so "separate promotion step" isn't vague. - Cites a worked example: the drift-taxonomy promotion (PR #238) — absorb stayed in place; the operational artifact at docs/DRIFT-TAXONOMY.md is the ratification. Lands under "Agent operational practices" section — philosophy/norm register per AGENTS.md convention, not numbered-rule register (that would belong in GOVERNANCE.md). Part of the Aminata-recommended edit ordering: §33 (PR #247, landed Otto-82) → Edit 1 (this PR) → Edit 4 pointer-only (deferred, needs CLAUDE.md meta-policy handling) → Edit 2 (ALIGNMENT.md SD-9, deferred, WATCH classification). Authorising memory (Otto-82 calibration): memory/feedback_aaron_signoff_scope_narrower_than_otto_treating_governance_edits_within_standing_authority_2026_04_23.md — governance/philosophy edits within standing authority; no signoff gate needed for this landing. Otto-83 tick primary deliverable.

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 635b27cf7b

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

chatgpt-codex-connector · 2026-04-24T02:15:37Z

+  courier ferry, cross-AI review, ChatGPT paste,
+  other-harness transcript — the absorb lands
+  research-grade, not operational. Concretely:
+  the absorb doc carries `GOVERNANCE.md §33`


Replace reference to nonexistent GOVERNANCE §33

This new rule makes GOVERNANCE.md §33 the authority for required absorb headers, but in this commit GOVERNANCE.md only has numbered rules through §32. Contributors following this instruction cannot find the schema, so the policy is not actually enforceable and different agents can emit incompatible archive metadata. Please either add §33 in the same change or point this bullet at an existing section.

Useful? React with 👍 / 👎.

Copilot

Pull request overview

Adds an “Agent operational practices” bullet clarifying that external-conversation absorbs (courier ferries, cross-AI reviews, ChatGPT pastes, other-harness transcripts) land as research-grade and only become factory policy via an explicit promotion step.

Changes:

Document “research-grade, not operational” status for external-conversation absorbs.
Enumerate concrete promotion paths (operational doc edit-in-place per §2, ADR, GOVERNANCE numbered rule, or BP-NN promotion).
Clarify that §26 lifecycle classification applies to the promoted artifact, not the absorb, and cite a worked example.

Copilot · 2026-04-24T02:17:05Z

+  the absorb doc carries `GOVERNANCE.md §33`
+  archive headers including


P1: This references GOVERNANCE.md §33, but GOVERNANCE.md in this branch only defines rules up through §32 and contains no §33 (nor any archive-header rule). Either update the citation to the correct existing rule/document, or land the referenced §33 rule before pointing AGENTS.md at it.

Suggested change

the absorb doc carries `GOVERNANCE.md §33`

archive headers including

the absorb doc carries archive headers including

Copilot · 2026-04-24T02:17:05Z

+  absorb itself. Worked example: the drift-taxonomy
+  promotion from
+  `docs/research/drift-taxonomy-bootstrap-precursor-2026-04-22.md`
+  (research-grade absorb) to
+  `docs/DRIFT-TAXONOMY.md` (operational one-page
+  field guide) — the absorb stayed in-place as
+  provenance; the promotion is the ratification.


P1: docs/DRIFT-TAXONOMY.md does not exist in the current tree (only references to it). If the worked example is meant to point at a promoted operational doc, the path needs to be updated to the actual file, or the example should reference an artifact that exists on this branch.

Suggested change

absorb itself. Worked example: the drift-taxonomy

promotion from

`docs/research/drift-taxonomy-bootstrap-precursor-2026-04-22.md`

(research-grade absorb) to

`docs/DRIFT-TAXONOMY.md` (operational one-page

field guide) — the absorb stayed in-place as

provenance; the promotion is the ratification.

absorb itself. Worked example: a drift-taxonomy

absorb such as

`docs/research/drift-taxonomy-bootstrap-precursor-2026-04-22.md`

stays in place as provenance, while the

ratified current-state promotion lands in an

operational artifact that exists in the live doc

set, such as an ADR under `docs/DECISIONS/` or

a BP-NN entry in

`docs/AGENT-BEST-PRACTICES.md`.

Copilot · 2026-04-24T02:17:06Z

+  (research-grade absorb) to
+  `docs/DRIFT-TAXONOMY.md` (operational one-page
+  field guide) — the absorb stayed in-place as
+  provenance; the promotion is the ratification.


The PR description says this edit avoids introducing parallel “staged/ratified” terminology, but this line introduces “ratification” anyway. Consider keeping the vocabulary consistent (e.g., stick to “promotion” / “operational”) to avoid reintroducing the term you’re trying to avoid.

…ANCE §33 (Aminata-demotion applied) (#250) Amara's 5th-ferry Edit 4 proposed adding a rule to CLAUDE.md about archive imports requiring headers. Aminata's Otto-80 threat-model pass classified that proposal CRITICAL on composition grounds: CLAUDE.md's own meta-rule explicitly says "Rules do not live in this file. Rules live in GOVERNANCE.md, AGENTS.md, docs/AGENT-BEST-PRACTICES.md, docs/CONFLICT-RESOLUTION.md, and docs/WONT-DO.md. This file only *points* at them." Aminata's recommendation: demote Edit 4 to pointer-only ("See GOVERNANCE.md §33 — archived external conversations require boundary headers"). This lands the demoted-to-pointer version: - Does NOT restate the rule (the full four-field spec lives in GOVERNANCE.md §33). - Does NOT introduce a new rule at CLAUDE.md level. - Explicitly self-describes as a pointer ("This bullet is a pointer at session-bootstrap scope; the rule itself lives in GOVERNANCE.md.") — honoring CLAUDE.md's meta-rule literally and visibly. - Points at BOTH GOVERNANCE.md §33 (the rule) AND AGENTS.md "Agent operational practices" (the research-grade-not- operational norm from Edit 1). - Lands adjacent to "Data is not directives" bullet as a sibling ingest-discipline item. Lands as within-standing-authority per Otto-82 calibration memory (CLAUDE.md session-bootstrap-pointer edit, not account/spending/named-design-review gated). Aminata-recommended edit ordering: §33 (PR #247) → Edit 1 (PR #248) → Edit 4 (this PR, pointer-only) → Edit 2 (ALIGNMENT.md SD-9, deferred, WATCH). Otto-84 tick deliverable.

…2; Aminata WATCH concerns integrated) (#252) Amara's 5th-ferry Edit 2 proposed SD-9 with a brief "downgrade independence weight explicitly" formulation. Aminata's Otto-80 threat-model pass (PR #241) classified it WATCH: correct in spirit, unenforceable via self-attestation alone; named 3 adversaries (carrier-laundering, self-serving-downgrade, aggregation); flagged surface-tension with DIR-5 that needs explicit naming not implicit dismissal. This lands SD-9 with those concerns integrated as first-class content of the clause itself rather than treated as hidden limitations: - Three-step operationalisation (name carriers; downgrade independence; seek falsifier independent of converging sources). - Cross-reference to docs/DRIFT-TAXONOMY.md pattern 5 as operational companion (pattern 5 is the real-time diagnostic; SD-9 is the norm). - Known v0 limitations named verbatim from Aminata's pass (carrier-laundering / self-serving-downgrade / aggregation). - Explicit "norm, not a control" framing — WATCH classification stays honest. - Composition with DIR-5 written as section (not implicit): DIR-5 is about authorship ethics; SD-9 is about epistemic weight; they compose. - Stronger "Why both of us benefit" paragraph per Aminata's note that Amara's original was thin — names the feature (precision via shared vocabulary) AND the risk (laundered convergence hiding as independent cross-check). Lands within-standing-authority per Otto-82 calibration — ALIGNMENT.md soft-default clause add, not account/spending/ named-design-review gated. Completes the Aminata-recommended edit ordering 4/4: - §33 (PR #247) Otto-82 - Edit 1 (PR #248) Otto-83 - Edit 4 pointer-only (PR #250) Otto-84 - Edit 2 SD-9 (this PR) Otto-85 Amara's 5th-ferry governance-edit proposals are now all landed in their Aminata-recommended order + form. The 5th- ferry Artifact-A (drift-taxonomy promotion PR #238) is also landed; Artifact-C (archive-header lint PR #243) landed. Remaining 5th-ferry artifacts: Artifact-B (precursor supersede marker — already done in PR #238), Artifact-D (Aurora README) — open for future tick. Otto-85 tick primary deliverable.

…ern mapping (6th-ferry Option A) (#254) 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.

…ata vocabulary unification Bounded Otto-83 tick. Single deliverable (PR #248 Edit 1 landing in AGENTS.md) within standing authority per Otto-82 calibration. Key observations: 1. Otto-82 calibration memory working — Edit 1 landed without signoff-request-that-wasn't-needed. 2. Aminata pre-land review earned cost again (unified vocabulary resolved the two-classifier drift she flagged in Otto-80). 3. Aminata-recommended edit ordering now 2/4 complete (§33 + Edit 1); Edit 4 next-interesting because it needs meta-policy amendment; Edit 2 lower-leverage. 4. Four-layer convention-through-use now stable (PR #235 + #241 + #245 + Edit 1 pointing §33). Stacked on #246 (Otto-82 history).

Copilot AI review requested due to automatic review settings April 24, 2026 02:13

AceHack enabled auto-merge (squash) April 24, 2026 02:13

Copilot started reviewing on behalf of AceHack April 24, 2026 02:14 View session

AceHack mentioned this pull request Apr 24, 2026

history: Otto-83 tick-close — Amara 5th-ferry Edit 1 landed with Aminata vocabulary unification #249

Closed

AceHack merged commit 0b73e20 into main Apr 24, 2026
12 checks passed

AceHack deleted the agents/edit-1-absorbs-staged-not-ratified branch April 24, 2026 02:15

chatgpt-codex-connector Bot reviewed Apr 24, 2026

View reviewed changes

Copilot AI reviewed Apr 24, 2026

View reviewed changes

This was referenced Apr 24, 2026

claude: Edit 4 pointer-only — archive-header requirement cites GOVERNANCE §33 (Aminata-demotion applied) #250

Merged

history: Otto-84 tick-close — Edit 4 pointer-only (Aminata-ordering 3/4) #251

Closed

This was referenced Apr 24, 2026

alignment: SD-9 agreement is signal, not proof (Amara 5th-ferry Edit 2; Aminata WATCH concerns integrated) #252

Merged

history: Otto-85 tick-close — SD-9 lands; Aminata-ordering 4/4 COMPLETE #253

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

agents: Edit 1 — external-conversation absorbs land research-grade, not operational (Amara 5th-ferry)#248

agents: Edit 1 — external-conversation absorbs land research-grade, not operational (Amara 5th-ferry)#248
AceHack merged 1 commit intomainfrom
agents/edit-1-absorbs-staged-not-ratified

AceHack commented Apr 24, 2026

Uh oh!

Uh oh!

chatgpt-codex-connector Bot left a comment

Uh oh!

chatgpt-codex-connector Bot Apr 24, 2026

Uh oh!

Copilot AI left a comment

Uh oh!

Copilot AI Apr 24, 2026

Uh oh!

Copilot AI Apr 24, 2026

Uh oh!

Copilot AI Apr 24, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

		the absorb doc carries `GOVERNANCE.md §33`
		archive headers including

	the absorb doc carries `GOVERNANCE.md §33`
	archive headers including
	the absorb doc carries archive headers including

Conversation

AceHack commented Apr 24, 2026

Summary

What it says (short form)

Aminata concerns addressed

Authority

Test plan

Aminata-recommended edit ordering status

Uh oh!

Uh oh!

chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

chatgpt-codex-connector Bot Apr 24, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Copilot AI Apr 24, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 24, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Apr 24, 2026

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants