CEDX Notes · Workplace
Three hundred twenty notes, 80% filed into 48 notebooks. The rest are not lost — they are queued: 203 in the orphan queue, 75 at high risk, and 71 share-sprawl items still open on anyone-with-link.
Every notes app grows a parking lot of untitled scraps. This one scores it: the note called “Random sticky, parking lot” carries orphan risk 99 and has been cold for 172 days. The queue is the feature.
Runs on demo data. Notes and people named on screen belong to the demo workspace.
What it is
Forty-eight containers — team, personal and shared — with note counts, shared counts and orphan flags per row. The incident war-room notebook holds 35 notes with zero orphans; the research scrap notebook holds 54 with 14 flagged. You can see which containers work.
Ask what the partner asked for on the last call and the answer comes back with its sources attached — n1 the call note, n7 the handoff — plus a related-by-meaning cluster underneath, so the pricing scrap and the shared deck surface too.
Sixty tags with notes, notebooks, orphans and opens per row. #meeting is heaviest at 86 notes; #do-not-share carries 67; #needs-file carries 53 — including five orphans, which is the tag doing its job.
Product tour
Not a mockup and not a concept deck. This is what opens at /app/notes.
01 — Overview
Filed 80% against a 92% target. The alerts name the work: expire the external counsel share on the MSA notes, file or archive the parking-lot sticky, revoke the stale anyone-with-link shares on the pricing scrap.
02 — Notebooks
Shared notebooks show their shared counts; personal ones show their owners. Localization holds 14 notes, 13 of them shared, with 2 orphans — a notebook working exactly as intended.
03 — Search
The demo answer names what was asked for — multi-site inventory sync by Q4, two blockers, a follow-up owed — and the notes it came from. Below it, results are typed note, notebook or tag with relevance and opens.
04 — Tags
#1on1 has 70 notes in a single notebook; #shared-wide has 71 across twelve. The tag table turns “how do we use tags” into a sortable answer.
Who runs it
Roles, not references. We have no named customers yet, so nobody in these photographs is quoted, credited or claimed as one.
Captures visits and interviews as they happen. The customer-visit dump in the orphan queue is theirs to file while it still means something.
field notes · 150d cold peak
Lives in the hiring-loop notes and the #1on1 tag — 70 notes in one notebook, owned and current.
#1on1 · 70 notes
Reads the partner cluster before the call: the call note, the handoff, the pricing scrap — one search, all three.
partner results · 27The 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
The note lands fast — a call, a visit, a sticky thought. Filing can wait; capture cannot.
Notes join a notebook and pick up tags. The filed share is 80% against a 92% target, and the gap is on the overview.
Links go out with a role and, increasingly, an expiry. The 71 high-sprawl items are the old way, queued for revocation.
Search answers from the corpus with sources, and the orphan queue keeps the unfiled visible until they are filed or archived.
One record
A note is raw material. It graduates into verified pages, tasks and conversations on the same record.
The note that becomes policy becomes a verified page with a review-by date — the orphan queue's best outcome.
CEDX Chat“Link in thread please” is a real preview in these captures; notes travel into the conversation and back.
CEDX TasksThe follow-up owed from the partner call is a task, not a hope buried in a note.
CEDX MeetThe meeting-capture notebook — 42 notes, 12K opens — is the written half of what Meet records.
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 notebooks, your corpus
Notes 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/notes. It runs on demo data — the notes, notebooks and people belong to a demo workspace, not to a customer.
A note with no notebook, weak tags and no links from related notes — the hygiene queue scores each one. The demo workspace has 203 in queue, 75 of them at high risk, the worst cold for 172 days. The fix is on the alert: file to a notebook, add tags, link from related notes.
Shares that outlived their purpose — anyone-with-link URLs, external access nobody reviews. Seventy-one items sit at high sprawl in the demo view, and the alerts name the sensitive ones, like a pricing scrap still open on an anyone link.
It reads the corpus and answers with sources. The demo question — what did the partner ask for on the last call — comes back with the ask, two blockers and a follow-up owed, citing the call note and the handoff note by id, plus a semantic cluster of related notes underneath.
Which tags carry weight and which carry orphans. #meeting leads at 86 notes across 12 notebooks; #needs-file exists precisely to hold the unfiled — 53 notes, five of them orphans. The folksonomy audits itself.
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 untitled notes in your own app.