Ideas/Universal Node + Edge data layer — single source of truth for all entities

Universal Node + Edge data layer — single source of truth for all entities

Replace 10+ separate tables with 2: nodes (id, type, name, description, properties JSONB, created_at, updated_at) and edges (id, from_id, to_id, type, properties JSONB, strength, created_at). Every entity is a node: idea, concept, contributor, spec, task, asset, news_item, federation_node, axis, frequency. Every relationship is an edge: resonates-with, implements, contributes-to, part-of, etc. Type-specific fields live in properties JSONB. Existing API endpoints keep their shape — routers become thin adapters. Migration: (1) Create nodes + edges tables. (2) Seed ontology (184 concepts, 46 edge types, 53 axes). (3) Migrate ideas first (highest risk, most data). (4) Add /api/nodes and /api/edges generic endpoints. (5) Migrate remaining types one at a time. (6) Remove old tables when all types migrated. This is the single most important architecture change — everything else (belief system, geo-location, concept translation, fractal zoom) builds on this.

Current proof level: Proven in real use

𝕏 in r/

How real it is

Proven in real use

Best time to work on this

Good next step

Promising, but not the very first thing to do.

Value still available

0 CC

How sure we are

70%

See this idea through a worldview

Same idea, different emphasis — not a rewrite of facts, but a bridge across perspectives.

Lens

Loading translation…

Update What You Have Learned

Save what this idea has delivered so far, how much it has cost, and how proven it feels right now.

Value seen so far (USD)Cost so far (USD)How sure are you? (0 to 1)How proven is this?

Tip: use the same money assumptions each time so changes stay easy to compare.

Start A Piece Of Work

Create a work card from this idea without leaving the page. This is a good place to capture the next small step.

What kind of help do you want?What should happen next?

Turn This Idea Into A Clear Plan

Start with the big idea, then make it easier to act on. This view helps you name the direction, keep the scope small, break the work into smaller parts, and say how you will know it worked.

This creates plan cards only. You can review them first, then start work from the plan you want to use.

Direction

Clarify the first real-world outcome Universal Node + Edge data layer — single source of truth for all entities should create and the person it helps first.

Scope

Keep the first version tight: one walkable flow, one visible result, and only the minimum support needed. Replace 10+ separate tables with 2: nodes (id, type, name, description, properties JSONB, created_at, updated_at) and edges (id, from_id, to_id, type, properties JSONB, strength, created_at). Every e…

Smaller parts

Split the idea into promise, flow, and proof so each plan stays small enough to build and check.

Proof of success

A human can understand the value, walk the flow, and answer this open question next: Should we use PostgreSQL JSONB or Neo4j for the graph? We have both. JSONB is simpler, Neo4j is purpose-built for graph queries.

Plans you place here carry the name you choose.

You can shape the preview below now. To place a plan, first be welcomed: choose a name. You will return here, and the plans will carry your name.

Universal Node + Edge data layer — single source of truth for all entities: promise and audience

Lock the first audience and promise for Universal Node + Edge data layer — single source of truth for all entities so the first version says something concrete.

Define who this helps first, what tension it resolves, and what the first visible result should be. Replace 10+ separate tables with 2: nodes (id, type, name, description, properties JSONB, created_at, updated_at) and edges (id, from_id, to_id, type, properties JSONB, strength, created_at). Every entity is a node: ide…

How you will know it worked: A new user can tell who this is for, why it matters, and where to start without extra explanation.

Be welcomed to place this planExpected impact 70.0 | Work size 7.5

Universal Node + Edge data layer — single source of truth for all entities: end-to-end human flow

Turn Universal Node + Edge data layer — single source of truth for all entities into one walkable flow instead of a loose collection of internal actions.

Map the creation, update, review, and follow-up loop in plain language. Use this open question as a design constraint: Should we use PostgreSQL JSONB or Neo4j for the graph? We have both. JSONB is simpler, Neo4j is purpose-built for graph queries.

How you will know it worked: Someone can complete the core journey locally without needing hidden IDs, inside language, or hard-to-find navigation.

Be welcomed to place this planExpected impact 80.0 | Work size 13.5

Universal Node + Edge data layer — single source of truth for all entities: measurement, trust, and follow-up

Make progress for Universal Node + Edge data layer — single source of truth for all entities credible by showing what changed, what is blocked, and what should happen next.

Define the status signals, proof markers, human review points, and follow-up rules that keep the first version trustworthy.

How you will know it worked: The experience makes value movement, blockers, and next actions visible without extra technical interpretation.

Be welcomed to place this planExpected impact 50.0 | Work size 9.0

Back this idea

Enter your contributor name to stake CC on this idea.

Questions still to answer

Should we use PostgreSQL JSONB or Neo4j for the graph? We have both. JSONB is simpler, Neo4j is purpose-built for graph queries.
No answer yet.
How do we migrate 200 ideas without downtime? Dual-write during migration?
No answer yet.
What indexes are needed on edges for fast traversal? (from_id, to_id, type) composite?
No answer yet.
How can we improve this idea, show whether it is working yet, and make that proof clearer over time?
No answer yet.

Investment

CC staked on this idea and what it produced.

No CC staked on this idea yet.

Work cards: 0 created