Skip to content

docs: define deals, retrievals, and metrics#164

Open
SgtPooki wants to merge 7 commits intomainfrom
docs/whats-it-doing
Open

docs: define deals, retrievals, and metrics#164
SgtPooki wants to merge 7 commits intomainfrom
docs/whats-it-doing

Conversation

@SgtPooki
Copy link
Collaborator

This PR attempts to handle the documentation parts of #158, #159, #160.

This is all in a single PR to make the entire scope of documentation changes easier to review.

Copilot AI review requested due to automatic review settings January 28, 2026 14:40
@FilOzzy FilOzzy added this to FOC Jan 28, 2026
@SgtPooki SgtPooki requested a review from BigLep January 28, 2026 14:40
@github-project-automation github-project-automation bot moved this to 📌 Triage in FOC Jan 28, 2026
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

Adds public “source of truth” documentation for Dealbot’s Data Storage and Retrieval checks, plus a consolidated reference for check events and dashboard metrics (addressing #158, #159, #160).

Changes:

  • Introduces a Data Storage Check specification and lifecycle description.
  • Introduces a Retrieval Check specification, including selection logic and recorded metrics.
  • Adds an Events & Metrics reference for dashboard consumers (with TBD markers for not-yet-implemented items).

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 8 comments.

File Description
docs/checks/data-storage.md Defines intended Data Storage check behavior, lifecycle, assertions, metrics, and configuration.
docs/checks/retrievals.md Defines intended Retrieval check behavior, deal selection, assertions, recording, metrics, and configuration.
docs/checks/events-and-metrics.md Documents a canonical event/metric model and links expected sources of truth in code.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@rjan90 rjan90 moved this from 📌 Triage to ⌨️ In Progress in FOC Jan 28, 2026
@rjan90 rjan90 added this to the M4.0: mainnet staged milestone Jan 28, 2026
@rjan90 rjan90 moved this from ⌨️ In Progress to 🔎 Awaiting review in FOC Jan 28, 2026
Copy link
Contributor

@BigLep BigLep left a comment

Choose a reason for hiding this comment

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

Thanks for putting this together Russell. I think this will be a useful artifact going forward, and I think it's useful right now for making sure we're fully aligned on what #158 and #159 should implement. I think it was smart to start with it.

I have read through everything, but because of time I didn't comment on each thing I saw. I have a few inline comments and some more general things. If I had more time tonight, I would have just created a PR on top of yours to point out some other suggestions or changes. I think in terms of next steps it would be great if you can review/incorporate the feedback I have provided so far. I'll then checkout the change and as I read through it again, make any other changes in a PR on top so it's easy for you to review/accept/reject my items. Sound good?

Generall items

  • I think we should write this document assuming the flow for when #158 and #159 are done (since they will be completed soon). It's fine/good to denote the parts that aren't complete as TBD or TBI (to be implemented). For example, lets write it assuming the IPNI advertising and verification happens as part of the sequential "data storage" flow
  • What retries are we doing?
  • Rather than stating line number in text can we just #123 in the URLs (more convenient and less text presented to user)
  • Maybe this is a losing battle, but rather than use the word "deal" throughout the document, do we use "piece" since that has a definition throughout FWSS?
  • Some parts in each document seem duplicative? Maybe ask AI for ideas to reduce redundancy?
  • In particular, there seems to be some duplication of the metric definitions across the files? Either reference events-and-metrics.md as much as possible or inline that content into the other two files?
  • Not critical, but maybe do mermaid diagrams?

@BigLep BigLep moved this from 🔎 Awaiting review to ⌨️ In Progress in FOC Jan 29, 2026
@SgtPooki SgtPooki mentioned this pull request Jan 29, 2026
@BigLep BigLep linked an issue Jan 30, 2026 that may be closed by this pull request
@SgtPooki
Copy link
Collaborator Author

@BigLep I addressed all comments.. lmk if you need anything else from me

@rjan90 rjan90 moved this from ⌨️ In Progress to 🔎 Awaiting review in FOC Jan 30, 2026
@BigLep BigLep mentioned this pull request Jan 31, 2026
@rjan90 rjan90 requested a review from BigLep February 2, 2026 09:44
@timfong888
Copy link

Is this mean to include the thresholds from https://linear.app/filoz/document/public-definition-of-thresholds-for-dealbot-ccf29ae32583

I scanned in manually and had AI do a check as well. AI output:

  1. No success rate targets (97% for storage/retrieval)
  2. No TTLB threshold (20 seconds for retrieval)
  3. No PDP/Data Retention documentation (the entire third pillar is missing)
  4. Retrieval selection algorithm differs from Linear spec (this one this document might be correct since we froze the Linear so this may represent other changes).

@BigLep
Copy link
Contributor

BigLep commented Feb 5, 2026

@timfong888 : I am active in adding a lot more content to this including thresholds - I'll ping you when it's ready for review.

@BigLep BigLep moved this from 🔎 Awaiting review to ⌨️ In Progress in FOC Feb 5, 2026
@BigLep
Copy link
Contributor

BigLep commented Feb 5, 2026

#228 is where I am working on top of this PR, but it's not ready for review yet. I need to review with fresh eyes and explain my thinking better.

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

Labels

None yet

Projects

Status: ⌨️ In Progress

Development

Successfully merging this pull request may close these issues.

Document "check" events and metrics

4 participants