Skip to content

Ground Consumer Findings in Network Posts - #62

Open
roackb2 wants to merge 2 commits into
devfrom
codex/lucid-consumer-post-finding
Open

roackb2 wants to merge 2 commits into
devfrom
codex/lucid-consumer-post-finding

Conversation

@roackb2

@roackb2 roackb2 commented Sep 4, 2026

Copy link
Copy Markdown
Owner

Outcome

A Lucid Consumer can turn a Publisher Post into a durable private Finding with inspectable Post provenance.

Changes

  • allow report_finding to cite stable source_post_ids from Lucid Network reads
  • verify cited Posts exist and reject repeat reporting to the same user
  • atomically persist the Finding event and finding_posts links under the active wake fence
  • teach Interest-discovery Agents to search, read, and cite Lucid Posts without receiving web search

Verification

  • yarn typecheck
  • LUCID_POSTGRES_TEST_URL=postgresql:///lucid_test yarn test
  • yarn build

The next integration step after merge is a hard-capped local observation window: three Consumer wakes against Mina's Publisher Post, then pause and inspect tool activity plus the resulting Finding.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 0f2e8a6364

ℹ️ 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".

Comment on lines +468 to +469
if (!existingLinks.length) {
await transaction.insert(findingPosts).values(

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Reject non-Finding idempotency winners before linking Posts

When report_finding races another communication call in the same wake, separate executeTool invocations can reserve the same action idempotency key. If the other call wins the event insert, the conflict path assigns that shared-message/direct-message/no-action row to event; because it has no existing links, this branch then attaches finding_posts rows to a non-finding_reported event and returns that unrelated event as a successful Finding. Verify that an idempotent winner exactly matches the requested Finding before inserting links, or serialize/atomically allocate communication actions.

Useful? React with 👍 / 👎.

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-09-04T16:32:22.510465Z 0f2e8a6 PR opened
ℹ️ 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" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant