Three people asked for three different things this week, so there are three ways in below. Everything here is generated from the repo that runs the pipeline: no page carries a number, date or count that someone typed, which is why nothing here goes stale between builds.
| page | what it answers | built |
|---|---|---|
| How it worksasked for by Palwashae Azhar | Every document that enters the machine, left to right, plus the full vocabulary with each term marked industry-standard, EZO's own, or ours. | 2026-08-05 18:20 |
| What is builtasked for by Shoaib Hassan | All five stages, every moving piece, what is live, what is in motion, and every blocker with a named owner. | 2026-08-05 18:20 |
| Why a page scoredasked for by Qasim Humayun | Every pipeline run, auditable: checkpoints per stage, timings, the models used, and the score before and after. A run that died mid-flight shows a red INCOMPLETE banner. | 2026-08-05 18:20 |
| The rulesasked for by Qasim Humayun | Every rule the checker applies, with the source line it came from and its severity, per page type. | 2026-08-05 18:20 |
| Step by stepasked for by Shoaib Hassan | The top-down process view: each step, whether it is locked, in progress or blocked, and where you can assist. | 2026-08-05 18:20 |
| Inside stage 1 and 2: the briefasked for by anyone reviewing a brief | Stage 1 and 2 in detail: how a topic becomes a brief. | 2026-08-05 18:20 |
| Inside stage 3: the draftasked for by the writers | Stage 3 in detail: one ruleset feeding both the writing instructions and the checks that grade the result. | 2026-08-05 18:20 |
| Inside stage 4: the checksasked for by Qasim Humayun | Stage 4 in detail: the checks running on the team's real in-flight pages, with the findings they produced. | 2026-08-05 18:20 |
| Where the inputs come fromasked for by Shoaib Hassan | Every document the team shared and whether the machine reads it yet, including the ones it does not. | 2026-08-05 18:20 |
| Review today, and where it goesasked for by Shoaib Hassan | EZO's 11 review steps today and how they collapse into the checks, cheapest pass first. | 2026-08-05 18:20 |
4 drafts went through the checks. Each row links to the Asana task that already owns that page, so a disagreement lands in the notification stream you already read. There is no new login and no comment box on this site, on purpose.
| Hardware Asset Discovery & Tracking Software Feature Pagehardware-asset-discovery | 89/100 passed | Disagree, on the task that owns it →Copy: [Features page] Hardware Discovery |
| SaaS Management Platform Feature Pagesam-saas-management-software | 100/100 passed | Disagree, on the task that owns it →Copy: SaaS Management Platform |
| IT Asset Management Solution Pageitam-software | 67/100 did not pass | No Asana task is recorded against this draft, so there is nowhere to route a comment yet. Tell Brent and it gets linked. |
| Feature Pageproblem-management | 89/100 passed | Disagree, on the task that owns it →Copy: [Features page] Problem Management |
So a rule you want to argue with goes on [Across products] Standardizing money pages format. Name the rule and what it got wrong. If it is one specific page rather than the rule itself, use the row for that page above, which opens the task that already owns it.
28ee43c by
scripts/build_site.py. Every page here is regenerated by re-running
that script, and it refuses to build if a page still carries retired jargon or
if anything reached the output folder that the allowlist did not put there.