CEDX Docs · Workplace
320 pages, 65% verified, 37 past their review-by date and 56 open contradictions. Ask for the refund policy and the answer comes back cited, with the conflict between the 14-day legacy page and the 30-day verified FAQ printed inside it.
Most wikis hide their contradictions behind whichever page ranks first. This one tables them: refund window 14 versus 30, pick the canonical value, redirect or archive the loser.
Runs on demo data. Pages and people named on screen belong to the demo workspace.
What it is
The pages table carries views, a freshness score, a verified flag and a review-by date per row. Refund policy v4 has 12K views, a fresh score of 40 and no verification, which is exactly the kind of page the queue exists for.
Spaces sum their pages: Support holds 48 pages at 62% verified with 11 stale; Warehouse holds 40 at 94% with none. The owner is on every row, and the three spaces without one are visible by their absence.
The answer to “refund” is synthesised from workspace docs, team chat and shared mailboxes at 71% confidence, and it ends by naming the open conflict and which page is the current source of truth, with cited pages P1, P2 and P10 underneath.
Product tour
Not a mockup and not a concept deck. This is what opens at /app/docs.
01 Overview
Verified 65% against a target of 85%. Thirty-seven pages past review-by. The do-this-next queue scores the fixes: resolve the refund-window pair at 41 impact, assign owners to 16 unowned pages at 29, re-verify the Support space.
02 Spaces
A space's verified percentage and stale count travel together, so you can see that Security runs 81% verified while Billing ops runs 48%, and staff accordingly.
03 Pages
Three hundred twenty pages with views, freshness, verification and review-by dates. The archived playbook with 11K views and a fresh score of 20 is the sort of row this table exists to catch.
04 Search
Two results for “refund”: the policy at relevance 92 and the FAQ at 84, each with views and an updated date. Above them, the synthesised answer cites three pages and flags the contradiction the queue is already tracking.
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 contradiction queue. The 14-versus-30 refund window gets a canonical value, a redirect and an archived loser: their call, with the evidence tabled.
contradictions · 56
Keeps the Support space (48 pages, 42K views a month) verified, because the team answers from it every day.
Support space · 62% verified
Works the policy-critical stale list. The fail-open exception page at 154 days stale is a risk decision, not a wiki chore.
policy-critical stale · SecurityThe 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
A page starts in a space with an owner and a template: 458 pages, spaces and templates sit in the search index.
Verification is a dated act, not a vibe. The review-by date is on the row, and 65% of the base is inside its window.
When two pages disagree, the contradiction queue catches the pair: 56 open, each waiting for a canonical call.
Search synthesises across docs, chat and mailboxes, cites its pages, and prints the conflict it had to work around.
One record
The answer on the search screen says where it read: workspace docs, team chat, shared mailboxes. Those are products on this estate, not connectors to someone else's.
Team chat is one of the cited sources behind the synthesised answer. Decisions made in channels feed the base.
CEDX MailShared mailboxes are the second cited source; the refund answer read them.
CEDX DriveThe file-drive connector is visible on the search screen as the next source, shown honestly as not yet connected in the demo.
CEDX NotesMeeting capture and call notes graduate from notebooks into verified pages on the same record.
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 spaces, your pages
Docs 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/docs. It runs on demo data. The pages, spaces and people belong to a demo workspace, not to a customer.
A page is verified when someone has reviewed it inside its review window. The review-by date is on every row. 65% of the demo base is currently verified, and the 37 pages past their date are listed by name with a stale-risk score.
The base tracks claims that disagree: 64 contradictions in the demo view, 56 still open. The top pair is the refund window: a legacy policy page says 14 days for all plans, the verified FAQ says 30 for annual plans. The queue asks an owner to pick the canonical value and redirect or archive the loser.
From the connected sources printed on the screen: workspace docs, team chat and shared mailboxes. The answer cites its pages (P1, P2, P10 on the demo query) and prints its confidence, 71%, next to the synthesis.
Yes. Sixteen published pages in the demo base have no owner, they are filterable, and the do-this-next queue scores the fix at 29 impact.
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 check when your own refund policy was last reviewed.