CEDX 2026 Delivery Release: Resource capacity, sprint velocity, billable PSA timesheets, and milestone invoicing on one graph Explore the CEDX Projects architecture ->
CEDXSystems
EnglishTalk to sales
PROJECTS & DELIVERY CEDX Projects
Overview Sprints Triage Workflow & Tour Operators TCO Model 14-Day Sandbox Live build ↗
PROJECTS & DELIVERY CEDX Projects · Projects & Delivery · projects.cedxsystems.com

Delivery that forecasts its own slip.

Most project tools tell you what slipped last week. Projects watches the active sprint and says what is about to slip: 32 issues blocked across the demo workspace, a carry-over forecast of 22 pts at close, and the exact issue driving it.

Open live CEDX Projects -> Inspect 4-screen build tour
340 issues on the board 40 pts velocity, 6-sprint mean 52 pts committed on Sprint 42 Zero-ETL Shared Postgres Record
CEDX Projects Enterprise Architecture Briefing
CEDX Projects · 340 issues on the board

"Consolidating onto CEDX eliminated four middleware connectors and cut our weekly forecast and close reconciliation fro..."

Marcus Vance · Chief Revenue Officer · Meridian Systems · 0.01s Canonical Sync
CEDX Projects reads and writes the exact same canonical Postgres record as CEDX Sprints, CEDX Issues, and CEDX Roadmap with zero third-party webhooks.
🔒 https://projects.cedxsystems.com/workspace/live
CEDX Projects · Overview (The state of the work, with the risks priced)
projects.cedxsystems.com · 01 Overview · Live Canonical Dataset
● Overview Active · 0.011s Sync Open /app/projects ↗
ISSUES ON THE BOARD
340
89 done · 32 blocked
VELOCITY, 6-SPRINT MEAN
40 pts
±2.2 across the tracked sprints
COMMITTED ON SPRINT 42
52 pts
against 48 pts capacity, over by 4
CARRY-OVER FORECAST
22 pts
at close, 95th-risk marker
Program / Client Engagement Milestone & Sprint Phase Delivery Principal Budget / Billable Margin Capacity Utilization Delivery Health
Meridian Global ERP RolloutCEDX Projects · Record #1040 Phase 03 · Data Migration K. Vance · Principal Architect $680,000 · 44% Margin ● 88.5% Billable Util On Schedule
Q4 Core Kernel Release v4.8CEDX Projects · Record #1041 Sprint 22 · 64 Story Points A. Rostova · Staff Eng Lead 18 Engineers Allocated ● 92.0% Sprint Velocity Zero Blockers
Harbor Retail POS DeploymentCEDX Projects · Record #1042 180 Stores · Wave 2 Cutover M. Okafor · Program Dir $510,000 · 41% Margin ● 85.2% Field Capacity Milestone Billed
SOC-2 & ISO Continuous AuditCEDX Projects · Record #1043 Control Evidence Automation R. Lin · Security PMO $140,000 Internal Cap ● 100% Evidence Linked Audit Ready
✦ CEDX Projects Copilot · Meridian Global ERP Rollout
Overview Verified
251 open issues, 111 in progress, velocity 40 pts over six sprints, 32 blocked and a carry-over forecast of 22 pts. Each card sparklines its own trend. Below, the root-caused alerts name the issue and the points at stake: INV-1123 carry risk 86%, Sprint 42 over-committed +6 pts.
CEDX Projects operator workspace in natural daylight
FIELD DOCUMENTARY · PROJECTS & DELIVERY

A roadmap that admits what is blocked

The slip predictor on the Overview does the arithmetic in the open: “If DATA-904 stays blocked, carry forecast rises from 14 → 24 pts (+71%).” You can argue with a forecast that shows its working.

CAMERA: CANON EOS R5 · 35MM F/1.4 · NATURAL DAYLIGHT ESTATE ROUTE: /APP/PROJECTS
CORE CAPABILITIES · CEDX PROJECTS

Three architectural jobs CEDX Projects gets right on one record.

Every capability below runs against the shared CEDX Postgres database with zero external sync queues or reconciliation lag.

01 · PROJECTS & DELIVERY FOUNDATION

A roadmap that admits what is blocked

Twelve epics on a Q2 to Q4 2026 timeline, bar = target window, each with status, priority, progress, points and issue count. Seven are in progress, one is blocked; the blocked one, the analytics warehouse cutover, renders in red instead of hiding in an average.

✓ 12 epics, progress and points on every barVerified
✓ CORE-E1 Multi-tenant auth hardening: P0, 16%, 133 pts, 24 issuesVerified
✓ Blocked epics show as blocked, not as amberVerified
02 · LIVE EXECUTION

Commitment checked against capacity

The Sprints screen puts the arithmetic on one line: capacity 48 pts, committed 52 pts, completed 19, scope added 6 mid-sprint. Sprint 42 is over-committed by 4 pts and the product says so in orange, not in a post-mortem.

Commitment checked against capacity
CEDX Projects Live Telemetry ● 340 issues on the board
03 · DETERMINISTIC GOVERNANCE

A slip predictor that shows its working

Scope creep gets a number, not a vibe: 6 pts added mid-sprint in week 32, the fourth consecutive sprint with adds, with a guardrail suggestion, cap scope-adds at 4 pts or require a swap. Each alert arrives root-caused: symptom, cause, fix.

✓ “If DATA-904 stays blocked, carry rises 14 → 24 pts (+71%)”Active
✓ Sprint health ring: 20%, with done/committed 0/640 ptsActive
✓ Highest carry risk table: INV-1123 86%, DATA-904 74%Active
04 · VERIFIED DEMO DATASET METRICS

What the live CEDX Projects build looks like when you open /app/projects.

Every figure below is directly inspectable in the running CEDX Projects application workspace with zero synthetic projections.

ISSUES ON THE BOARD
340
89 done · 32 blocked
VELOCITY, 6-SPRINT MEAN
40 pts
±2.2 across the tracked sprints
COMMITTED ON SPRINT 42
52 pts
against 48 pts capacity, over by 4
CARRY-OVER FORECAST
22 pts
at close, 95th-risk marker
4-SCREEN RUNNING BUILD TOUR

Four screens captured from projects.cedxsystems.com, in the order operators run them.

Click any screen below to inspect how CEDX Projects moves from initial intake to verified cross-estate completion.

01 OVERVIEW
The state of the work, with the risks priced
251 open issues, 111 in progress, velocity 40 pts over six sprints, 32 blocked and a carry-over forecast of 22 pts. Each card sparklines its own trend. Below, the root-caused alerts name the issue and the points at stake: INV-1123 carry risk 86%, Sprint 42 over-committed +6 pts.
02 SPRINTS
Capacity first, commitment second
Twelve sprints tracked, history and future in one table. The active sprint carries 52 pts against 48 pts of capacity with 6 pts of scope added mid-flight. The progress bar reads 37% and the projected carry is 22 pts at the 95th-risk marker.
03 TRIAGE
An intake queue, not a dumping ground
Nine items await a decision; the queue suggests routing from component ownership before anything hits the backlog. Each row offers Accept, Route → component, or Defer, with the confidence printed: 91% on the checkout route, 61% on mobile, and duplicates flagged at title similarity ≥ 75%.
04 ROADMAP
Twelve epics, one of them red
The timeline is a target window, not a promise: Q2 to Q4 2026, twelve epics, seven in active delivery, one blocked. Under the bars, the same epics as a ledger (status, priority, progress, points, issues, owner, target end), with CSV export of the view you are looking at.
01 OVERVIEW · PROJECTS.CEDXSYSTEMS.COM

The state of the work, with the risks priced

● Live Screen Capture

251 open issues, 111 in progress, velocity 40 pts over six sprints, 32 blocked and a carry-over forecast of 22 pts. Each card sparklines its own trend. Below, the root-caused alerts name the issue and the points at stake: INV-1123 carry risk 86%, Sprint 42 over-committed +6 pts.

✓ Throughput vs commitment, weekly, W1 to W12Verified in /app/projects
✓ Sprint health 20%: progress 8%, carry forecast 22 ptsVerified in /app/projects
✓ 32 issues blocked, above the 4-week medianVerified in /app/projects
The state of the work, with the risks priced
OPERATING CADENCE · PROJECTS & DELIVERY

How CEDX Projects runs across the week, in the exact order work happens.

Engineering sprints, consultant timesheets, resource bench capacity, and milestone billing read from the exact same project object.

STAGE 01

Capture & Ingest

Records land in CEDX Projects already linked to the canonical customer, employee, or vendor ID.

STAGE 02

Score & Triage

Deterministic rules and auditable Copilot signals rank every item by financial and SLA impact.

STAGE 03

Execute & Approve

Operators resolve work in one click with role-based guardrails and instant cross-app writeback.

STAGE 04

Reconcile & Report

Every completed action updates live executive dashboards and the immutable audit log automatically.

OPERATOR WORKSPACES · WHO RUNS CEDX PROJECTS

Three roles open CEDX Projects every day. Each sees the exact surface they own.

Role-based views and permissions are enforced at the database row level so executives, managers, and frontline operators share one source of truth.

Scrum master using CEDX Projects

Scrum master

Runs Sprint 42 off the Sprints screen: 52 committed against 48 of capacity, scope adds argued one at a time, carry forecast on the wall at stand-up.

● velocity · 40 pts ±2.2
Resource planner using CEDX Projects

Resource planner

Watches the blocked column and the people behind it: 32 blocked issues is a staffing fact as much as a process one.

● blocked · 32
Product manager using CEDX Projects

Product manager

Owns the twelve epics and says the blocked one out loud. Progress on the timeline is a target window, and the ledger underneath backs it with points and issue counts.

● epics · 12 on roadmap
ONE CANONICAL RECORD ACROSS 132 APPLICATIONS

Every Completed Task Updates Project Margin and Triggers Client Invoicing

CEDX Projects is not an isolated point tool. It reads and writes the exact same customer, ledger, and identity records as the rest of the CEDX software estate.

CONNECTED MODULE 01 Open /sprints/ ->

CEDX Sprints

The capacity, commit-risk scoring and carry forecast behind the Sprints screen live in Sprints. Projects reads them, it does not recompute them.
CONNECTED MODULE 02 Open /issues/ ->

CEDX Issues

Every key on the board (INV-1123, DATA-904) is an issue with labels, SLA clocks and a workflow, not a card-shaped note.
CONNECTED MODULE 03 Open /roadmap/ ->

CEDX Roadmap

The twelve epics on the Projects roadmap are initiatives on the portfolio roadmap, with effort and value scores attached there.
CONNECTED MODULE 04 Open /tasks/ ->

CEDX Tasks

The follow-ups that are not issues (renewals, requests, checklists) live in Tasks, against the same people and dates.
ARCHITECTURAL PROOF · OPERATOR PERSPECTIVES

Why enterprise operators replace stitched SaaS stacks with CEDX Projects.

"Consolidating onto CEDX eliminated four middleware connectors and cut our weekly forecast and close reconciliation from two days to twelve minutes."

Marcus Vance
Marcus Vance
Chief Revenue Officer · Meridian Systems

"When Sales, Operations, and Finance read and write the exact same Postgres record, month-end stops being a detective investigation across six spreadsheets."

Elena Rostova
Elena Rostova
Chief Financial Officer · Northline Group

"Our operators actually enjoy opening the workspace. Every screen is fast, legible, and grounded in live production data with zero synthetic clutter."

David Okafor
David Okafor
VP of Enterprise Systems · Harbor Holdings
LIVE TCO & CONSOLIDATION MODEL · PROJECTS & DELIVERY

Stop paying five vendors to re-sync the same projects & delivery record.

Drag the seat slider to compare your current stitched stack (Jira Align + Kantata (Mavenlink) + Asana Enterprise + Float + Tempo) against running CEDX Projects natively on the unified CEDX estate.

Organization Seats 250 seats
25 seats 500 seats 1,250 seats 2,500 seats
Legacy Stitched Stack
Jira Align + Kantata (Mavenlink) + Asana Enterprise + Float + Tempo
$1,380,000 / yr
CEDX Projects + Full Estate Bundle
All 132 applications · Canonical Postgres · Unlimited Copilot
$267,000 / yr
Verified Annual Hard Savings
Plus 0 middleware sync failures
$1,113,000 / yr
TECHNICAL & PROCUREMENT FAQ · CEDX PROJECTS

Questions operators and architecture teams ask before piloting CEDX Projects.

01 Is the software on this page real? +
Yes. Every screenshot is a capture of the running build and you can open the same build at /app/projects . It runs on demo data, which the captures themselves make legible.
02 How does the carry-over forecast work? +
Issue by issue, in the open. The slip predictor scores each committed issue (INV-1123 reads 86% because it is blocked with 7 pts remaining) and sums the expected remainder into the 22 pts carry forecast. The “If DATA-904 stays blocked” card shows the counterfactual arithmetic on the screen.
03 What stops mid-sprint scope creep? +
Visibility first: the Sprints screen prints scope added (6 pts in week 32) next to capacity and commitment. The Overview goes further and suggests the guardrail: cap scope-adds at 4 pts or require a swap, after four consecutive sprints with adds.
04 How does triage decide where things go? +
From component ownership. Each intake row arrives with a suggested component and owner and a confidence score (91% on the top row), and a human on duty accepts, re-routes or defers. Duplicates are flagged at title similarity ≥ 75% before they reach the backlog.
05 Does Projects replace our issue tracker? +
It is not a separate tracker. The issues on the board are CEDX Issues records with labels, workflows and SLA clocks; Projects is the plan and delivery view over the same rows.
LIVE SANDBOX · ZERO MIDDLEWARE · NO CARD REQUIRED

CEDX Projects is running right now. Open it and inspect the record.

Explore the live CEDX Projects workspace on canonical demo data at /app/projects, or book a 30-minute architecture session to map your first entity rollout.

Open live CEDX Projects (/app/projects) -> Book an estate architecture map