CEDX Sheets · Workplace
Forty-eight workbooks holding 4.0M addressed cells — 533 of them in error, 87 formula surfaces at high debt, and 38 access grants at high overshare risk. The workbook your quarter closes on deserves the same discipline as your code.
Nobody reviews a spreadsheet until it breaks in front of the board. This estate scores the debt first: deep nests, volatile functions, cross-sheet references — named per surface, before the error cells multiply.
Runs on demo data. Workbooks and people named on screen belong to the demo workspace.
What it is
Forty-eight files with sheets, cell counts, error counts and external shares per row. The warehouse bridge carries 175K cells at health 78; the GTM model carries 63K cells, 9 errors and health 76. Average health is 68 — and the seven below 55 are named.
120 formula surfaces with family, nest depth, volatility and cross-sheet flags. The worst sit at debt 98 — an ARR rollup block, a pick-rate lookup, a summary conditional count with 8 error cells. Debt is a queue, not a surprise.
Sixty history points: 23 named and restore-ready, 20 restored recoveries, 17 automatic background saves. “Pre-board freeze” and “Baseline 8” are named on purpose — the overview calls out models where autosaves are the only discipline.
Product tour
Not a mockup and not a concept deck. This is what opens at /app/sheets.
01 — Overview
Error cells 533 and rising — import joins and unguarded lookups failing after a source-schema change. The do-this-next queue scores the fixes: clear the high-debt queue at 39.6 impact, revoke external edit on restricted files at 37, trap the import-join errors at 20.8.
02 — Workbooks
Sort by health and the weak files surface: monthly bridge at 74, cash collections weekly at 73 with 7 errors. Sort by external share and the 30 workbooks with outside collaborators surface instead.
03 — Formulas
The summary conditional count is volatile, nests three deep, crosses two sheets and holds 8 error cells. That row is why the error count keeps climbing — and it is one filter away.
04 — Versions
Collections week 31 was named before the numbers moved; the pre-board freeze on the revenue model was named before the board saw it. Twenty restores later, the point is made.
Who runs it
Roles, not references. We have no named customers yet, so nobody in these photographs is quoted, credited or claimed as one.
Owns the rollup blocks and the pre-board freeze. The ARR rollup at debt 98 is theirs to unwind before the close depends on it.
formula debt · 98 peak
Lives in the bridge workbooks — regional, warehouse, ops. Keeps the import joins guarded so a schema change stops costing 533 error cells.
error cells · 533
Works the access-risk list. Thirty-eight overshared grants, external edit on restricted files — the revoke queue is the morning's work.
access risk · 38The shape of it
Every figure below is legible in the captures above. Nothing here is a projection of your estate — it is the state of the demo data.
How it runs
Sheets and formulas land in a workbook with an owner and a space. Every surface is inventoried from the first formula.
Access is granted per workbook — and scored. External edit on a restricted file is a risk row, not a quiet permission.
Error cells accumulate where imports and lookups meet a changed schema. The count is on the overview before anyone's totals go red.
Named versions mark the points that matter — week 31, pre-board freeze — and restores have already happened 20 times in this workspace.
One record
A model is not a detached file. It pulls from the same ledgers and records the rest of the estate writes.
The close runs on the ledger; the models that explain it run here — same numbers, same record.
CEDX DocsThe playbook for the model lives as a verified page, reviewed inside its window.
CEDX DriveEvery workbook is a governed file: links, expiry, sensitivity and external shares follow it.
CEDX InsightThe numbers the model produces feed the dashboards the rest of the company reads.
Limits
Finding this out on the third call is worse for you than reading it here, and worse for us.
Start
Open it right now
Your workbooks, your models
Sheets with the rest of it
Questions
Yes. Every screenshot is a capture of the running build and you can open the same build at /app/sheets. It runs on demo data — the workbooks and people belong to a demo workspace, not to a customer.
A per-surface score built from nest depth, volatile functions and cross-sheet references. In the demo workspace 87 surfaces sit at high debt (55 or above), the worst at 98 — and the overview root-causes the cluster: deep nests plus volatile functions plus cross-sheet refs on the finance and ops models.
Cells currently evaluating to an error — 533 across the demo portfolio. The alert names the mechanism: import joins and unguarded lookups failing after a source-schema change, which is why the count keeps climbing instead of being 533 isolated accidents.
Access grants are scored per workbook: 38 grants sit at high overshare risk, and the alert describes the pattern — external edit rights and open links on restricted or confidential workbooks. The do-this-next queue scores the revoke at 37 impact.
The versions view counts 20 restored recoveries against 23 named restore-ready points and 17 background autosaves — restores are a recorded event with an editor and a timestamp, not a marketing verb.
No certification has been issued. What we can evidence about hosting, encryption, tenant isolation and production access is written up on the security page.
Live build, demo data, no card. Then count the error cells in the workbook your team opened this morning.