Repository navigation
Add append-only rupture and repair events - #62
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: ae397221e4
ℹ️ 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".
| response = responses[-1] if responses else None | ||
| outcome = outcomes[-1] if outcomes else None |
There was a problem hiding this comment.
When an accepted response and outcome are followed by another response to the same offer—which respond_to_repair currently permits—these independent [-1] selections combine the later response with the earlier outcome. The reconstructed record can therefore report status: declined while retaining a completed outcome, and its provenance includes the decline instead of the accepted response that the outcome causally references. Either prevent further responses after an outcome or select the response identified by the outcome's causal parents.
AGENTS.md reference: AGENTS.md:L44-L58
Useful? React with 👍 / 👎.
| "status": ( | ||
| response.payload.get("status") | ||
| if response is not None |
There was a problem hiding this comment.
In a relationship with multiple participants, this copies a participant's accepted or declined status and actions but discards response.actor_id; the outcome projection similarly drops its recording actor. The standalone wire record consequently cannot distinguish one participant's acceptance from another's and may present an unattributable relationship-wide status, despite retaining attribution for the rupture and offer. Add responder and outcome-recorder fields to both the projection and schema.
AGENTS.md reference: AGENTS.md:L17-L21
Useful? React with 👍 / 👎.
Summary
Adds an executable rupture/repair primitive to TRIA's existing append-only relational event ledger.
New event flow
RuptureRecordedRepairOfferedRepairRespondedRepairOutcomeRecordedSafety / relational constraints
Included
RuptureStatusandRepairResponseStatusThis adds to existing TRIA governance rather than replacing or changing existing consent/covenant/lifecycle semantics.