Current State
Latest implementation tracker for scoring, identity, governance, and the remaining open phases.
This page distills the latest architecture tracker in the repo into a docs-friendly form. It exists so the docs app has a current implementation page that is closer to March 2026 reality than older audits or theory notes.
Confirmed As Implemented
| Area | Status | What changed |
|---|---|---|
| Canonical contribution property | Done | m.contribution_level is the normalized field across the stack |
| Shared contribution type | Done | ContributionLevel is the canonical type across surfaces |
| CES scoring alignment | Done | Ranking cron uses the same CES scoring function as the service layer |
| Member standing model | Done | Standing is lifecycle state, not a synonym for contribution level |
| Member identity resolver | Done | Identity data now exposes standing, ring, expertise, and persona context |
| Governance re-enable | Done | Governance-related wiring was brought back into the active architecture |
| Docs / weight sync | Done | Equal-weight scoring defaults and CES language were synced across architecture docs |
The Current Member Model
The repo now treats these as separate axes:
- Standing: lifecycle state such as
GUEST,ACTIVE, orSUSPENDED - Contribution level:
OBSERVERthroughFOUNDER - Ring: percentile-relative ranking bucket
- Expertise: domain profile and rites
That separation matters because older docs and older work logs often collapse those ideas into one tier field.
Live Scoring Posture
- CES scoring is active with equal default weights and an HHI diversity bonus.
- The rankings cron computes synthesized scores from token balances and then writes cache and percentile data back to Neo4j.
- Investment thresholds can still raise the floor on contribution level where later phases rely on that model.
What Is Still Open
| Phase | Status | Remaining work |
|---|---|---|
| On-chain identity | Open | sol-did integration comes later in the stack |
| NFT live updates | Open | Metadata refresh is not fully triggered by every relevant state change |
| Privacy / CryptoGrapher | Open | Designed, partially framed, not fully surfaced |
| Bridge compliance | Open | Compliance and production hardening are still active tracks |
How To Read Older Docs
Use these rules when older architecture pages or work logs disagree:
- Prefer the current code over older synthesis docs.
- Prefer the unified architecture tracker over February "state of play" audits.
- Treat work logs as evidence of decision history, not as current product truth.
The strongest source documents behind this page are docs/architecture/unified-architecture-state.md,
docs/plans/2026-03-11-full-architecture-integration.md, and the live scoring code in
packages/neo4j/src/services/contribution-score.ts.