Roadmap

Hypergraph Framework

Geo Apps Integration

• https://github.com/graphprotocol/hypergraph/issues/526
• https://github.com/graphprotocol/hypergraph/issues/527
• https://github.com/graphprotocol/hypergraph/issues/427
• https://github.com/graphprotocol/hypergraph/issues/542
• https://github.com/graphprotocol/hypergraph/issues/513
• https://github.com/graphprotocol/hypergraph/issues/529
• https://github.com/graphprotocol/hypergraph/issues/528
• https://github.com/graphprotocol/hypergraph/issues/521
• https://github.com/graphprotocol/hypergraph/issues/518
• https://github.com/graphprotocol/hypergraph/issues/525

High level roadmap third party integration Roadmap

• Figure out App registry
• Rework Invitations with all our lessons learned
• Fix all open issues in Schema handling
• Restructure CRDT syncing using Keyhive with 1 CRDT doc per entity instead of 1 per space
• Settle on sync server architecture (federation?)
• Add permission functionality to Connect app
• Re-evaluate group key management (XMPT vs Beekem vs Lockboxes) based on all the lessones/requirement learned
• Typesync improvements
• Re-evaluate security ideally even a Security audit?
• File handling (maybe post 1.0?)
• Real-time awareness features (maybe post 1.0?)

Prioritised Issues

Non-breaking

• https://github.com/graphprotocol/hypergraph/issues/513
• https://github.com/graphprotocol/hypergraph/issues/428
• https://github.com/graphprotocol/hypergraph/issues/381
• https://github.com/graphprotocol/hypergraph/issues/456
• https://github.com/graphprotocol/hypergraph/issues/440
• https://github.com/graphprotocol/hypergraph/issues/441
• Relation filtering for private spaces
• Relation filtering for public spaces
• Typescript issue: nested includes
• Account registry / Profile?
• success/error Promise for publishing
• https://github.com/graphprotocol/hypergraph/issues/521
• Implement App Identity signature validation (private & public)
• https://github.com/graphprotocol/hypergraph/issues/438
• https://github.com/graphprotocol/hypergraph/issues/494
• https://github.com/graphprotocol/hypergraph/issues/493
• https://github.com/graphprotocol/hypergraph/issues/492
• https://github.com/graphprotocol/hypergraph/issues/491
• https://github.com/graphprotocol/hypergraph/issues/447
• https://github.com/graphprotocol/hypergraph/issues/273
• https://github.com/graphprotocol/hypergraph/issues/248
• https://github.com/graphprotocol/hypergraph/issues/237
• https://github.com/graphprotocol/hypergraph/issues/503
• https://github.com/graphprotocol/hypergraph/issues/504
• https://github.com/graphprotocol/hypergraph/issues/203
• https://github.com/graphprotocol/hypergraph/issues/183
• https://github.com/graphprotocol/hypergraph/issues/505
• https://github.com/graphprotocol/hypergraph/issues/506
• https://github.com/graphprotocol/hypergraph/issues/8

Breaking Changes

• https://github.com/graphprotocol/hypergraph/issues/199
• https://github.com/graphprotocol/hypergraph/issues/461
• https://github.com/graphprotocol/hypergraph/issues/462
• https://github.com/graphprotocol/hypergraph/issues/463
• https://github.com/graphprotocol/hypergraph/issues/427
• Renderable types? -> root types or something else?
• Value Options? -> how to implement?
• Replace Automerge sync and switch to 1 doc per entity
• Re-evaluate signature chain for Member management
  • Investigate Keyhive or Semaphore
• https://github.com/graphprotocol/hypergraph/issues/224
• https://github.com/graphprotocol/hypergraph/issues/19

Typesync

• https://github.com/graphprotocol/hypergraph/issues/496
• https://github.com/graphprotocol/hypergraph/issues/468
• https://github.com/graphprotocol/hypergraph/issues/498
• https://github.com/graphprotocol/hypergraph/issues/497
• Sort type search results by by totalCount

create-hypergraph

• https://github.com/graphprotocol/hypergraph/pull/522
• https://github.com/graphprotocol/hypergraph/issues/386
• https://github.com/graphprotocol/hypergraph/issues/481

Connect

• Implement loading indicators while the signing processes @benface
• Implement new design @benface
• Selection of spaces (public) @nikgraf (in the sync server we need store the info which app has access to which space)
• Delegation of space creation (private)
• Delegation of space creation (public)
• Remove an app from a space
• Verify app + domain -> public knowledge graph?

Sync Server

• Tracing https://github.com/graphprotocol/hypergraph/pull/420
• https://github.com/graphprotocol/hypergraph/issues/518
• https://github.com/graphprotocol/hypergraph/issues/519
• https://github.com/graphprotocol/hypergraph/issues/520
• https://github.com/graphprotocol/hypergraph/issues/362
• https://github.com/graphprotocol/hypergraph/issues/525

Schema Browser future? https://schema-browser.vercel.app/

• regenerate schema

Overall Specification

• Re-evaluate new version of XMTP for e2e encryption https://docs.xmtp.org/sdks/browser
• Property IDs -> get inspired by Bluesky?

Docs

• Add info how to use with V0 - see https://community.vercel.com/t/custom-instructions-in-v0/16782
• https://github.com/graphprotocol/hypergraph/issues/398
• https://github.com/graphprotocol/hypergraph/issues/323

Repository Infrastructure

• https://github.com/graphprotocol/hypergraph/issues/517
• https://github.com/graphprotocol/hypergraph/issues/391
• https://github.com/graphprotocol/hypergraph/issues/369
• https://github.com/graphprotocol/hypergraph/issues/370

Empieza revisando las secciones de la hoja de ruta y los issues y pull request vinculados, especialmente las entradas Geo Apps Integration, Typesync, Connect, Sync Server, Docs y Repository Infrastructure. Este issue solo estará completo cuando las prioridades y el estado de la hoja de ruta se hayan concretado y hecho accionables, pero aquí no se identifica ningún archivo, prueba ni cambio individual.