PLDG Dashboard & Storacha Integration - 2025-06-12 (PLDG Cohort-3) - Real-Time Metrics, CID Provenance Layers, Historical Charting, Storacha integration

[seetadev]

PLDG Dashboard & Storacha Integration – 2025-06-12 – CID Provenance Layers, Agent Prompting Enhancements & Migration Toolkit UI

Contributors

Cohort-3 PLDG Contributors:
@seetadev, @Naman26, @HarshS1611, @kaf-lamed-beyt, @sumanjeet0012, @Pfed-prog, @CeylonT, @Nkovaturient, @Chaitu-Tatipamula

Accomplished Tasks

• Finalized ElizaOS role-specific agents with prompt profiles for contributor, maintainer, and reviewer contexts.
• Completed the design for workflows and GUI for MongoDB → Storacha migration tool, now usable by non-dev team members for manual syncs.
• Discussed CID version resolution in the dashboard timeline to explore past states with diff overlays.
• Structured the role of real-time CID log viewer from Storacha into the historical chart UI for granular auditability.
• Introduced agent prompt versioning, tied to CID lineage for reproducible summarization and report generation.

In Progress

Agent + CID Integration Enhancements:

• Agents can now tag and retrieve context scoped to CID intervals (e.g., “all issues tagged ‘bug’ since CID-xyz”).

• Prompt refinement allows insight generation per role:

  • Maintainer → PR review cycle efficiency
  • Contributor → summary of commits + reviews
  • Reviewer → feedback loops and tagging metrics

• CID annotations include:

  • Task ID
  • Insight lineage (generated vs curated)
  • Retrieval origin (Mongo vs Storacha MCP)

Dashboard Evolution:

• Visual diff overlays allow clicking through changes between CID snapshots.
• Users can toggle between Mongo-based and Storacha-based source modes.
• Real-time CID activity feed supports event-level drilldowns.
• Improvements in rendering performance for CID-based snapshots.

Migration Toolkit GUI Milestone (in progress):

• GUI will support:

  • Drag-n-drop Airtable/GitHub JSON
  • Batch processing with live CID preview
  • Error debugging panel and schema override

• Successfully testing in onboarding sessions with new contributors.

MongoDB → Storacha Toolkit Enhancements:

• Added support for:

  • Plugin-based schema inference modules
  • Batch migration with parallelized CID chunking
  • CID-to-path mapping for selective retrieval

• Toolkit now tested with 3 real PLDG data formats (GitHub, Airtable exports)

Demo Links

• Historical dashboard snapshot viewer:
  https://pldg-dashboard-theta.vercel.app/

• Screencast (CID diff): We are planning to first integrate at https://pldg-dashboard.vercel.app/

• MongoDB → Storacha Migration Toolkit (GUI branch):
  https://github.com/HarshS1611/storacha-migration-tool/tree/feat/mongo-db-integration

• Lit protocol integration with Storacha storage for PLDG Contributor's Invoice Data: please visit https://invoice-ppt-subscribe-storacha-storage-fu8zai4p1.vercel.app/

Screencast: https://drive.google.com/file/d/1sWoH96REZHJcPRP1ivIYigAFZguq8XX_/view?usp=drive_link

Github: https://github.com/seetadev/pldg-dashboard

Github Branch: https://github.com/seetadev/Invoice-PPT-Subscribe-Storacha-Storage/tree/lit-encryption

What Went Well

• Refactored CLI improved testability and onboarding for new contributors

In Progress

• CID scope-based prompting has increased the contextual relevance of generated summaries.
• New GUI-based tooling helped onboard non-dev contributors to participate in snapshot uploads.
• CID versioning allowed for consistent historical tracking even during format transitions.

R&D tasks

• Investigating batch DAG optimization to reduce depth-related fetch latency from Storacha.
• Refining CID registry proposal for cross-agent linking and efficient lookup.
• Improving UI clarity around CID states and lineage paths during async interactions.

Next Tasks

• Launch user testing of CID-guided agent reports for project retrospectives.
• Benchmark Storacha retrieval latency under different DAG shapes and sizes.
• Release beta of shared CID registry module with alias support and access controls.
• Expand prompt metadata to include engagement tags (e.g., “high-velocity issue”, “stale PR”) tied to CID history.
• Initiate weekly auto-snapshot pipeline from staging DB to Storacha with diff alerts.

Questions

1. Would CID aliasing benefit from integration into ElizaOS’s prompt engine, or should it remain external?
2. How do we handle schema evolution across CID diffs — should snapshots store field metadata deltas?
3. Can the dashboard integrate a trust layer for agents, indicating whether a summary was AI- vs human-generated?
4. Should we standardize how CID annotations are stored in MCP vs raw Storacha access logs?

[Nkovaturient]

Outstanding work on the Lit Encryption protocol and overall 🔥⚡
I will follow ur work on the Encryption and decryption mechanism for my project. Thanks!

[Pfed-prog]

Very cool

I wonder if it is worthwhile creating an ipfs client rather than accessing public gateways

[Pfed-prog]

I am also diving into storacha updated docs and wonder if it is possible to create a single communication stream under a storacha space
https://www.npmjs.com/package/@storacha/client