The proofreading pipeline's wire contract
Maintained by PointSav Digital Systems. Each revision is content-addressed by its commit hash.
- Track-B documentation wave: services category — mandatory Test-1 self-contradiction fix (service-fs-data-lake), Test-3 split, structural + mechanical frontmatter fixes across 17 articles
- editorial(services): rewrite editorial-pipeline-three-stages (Track-B) — confirmed zero LanguageTool/Banned-Mechanical-Generative-severity/service-proofreader-crate references anywhere in source; confirmed real client contract (app-console-content/src/proofreader.rs): 9-protocol list, tenant scoping, response fields tier_used/degraded/audit_ledger_id/request_id; confirmed real verdict flow is SSH-signed binary accept/reject via the Doorman's apprenticeship /v1/verdict, same mechanism as service-content's write-governance checkpoint; dropped the specific fabricated 3-stage server architecture since no server-side handler for /v1/proofread was found anywhere in this monorepo checkout; register-clean EN+ES per register-documentation.yaml
- fix(index-group): resolve orphaned articles across 8 categories, add infrastructure's Compute and VM fabric group
- fix(services): add dated Correction callouts to 10 of 13 services/ batch-1 articles — worst defect ratio of any category (fabricated proofreader/message-courier/chart-of-accounts mechanics, reversed egress data-flow direction, wrong Graph vs real EWS integration, wrong extraction routing model, understated service-fs capability; private-git-paid-customer-endpoint.md finding disproven, agent checked wrong crate, no correction applied; service-input.md and service-fs-data-lake.md already correctly self-corrected
- Phase C A1b: rebalance PPN/OS/substrate/services out of architecture/ (16 articles, 32 files); resolve 8 of 9 slug collisions (aliases + redirects); language-protocol-substrate left for editorial call
- Metadata heal (documentation): 25 short_descriptions (EN+ES) + drop leading article/sentence-case 39 titles (EN+ES); title/frontmatter-only, slugs unchanged
- feat(media-knowledge-documentation): add content_type field to all TOPIC + GUIDE files
- docs(media-knowledge-documentation): add editorial-pipeline-three-stages + customer-tier-catalog-pattern — two EN+ES pairs from project-console/project-proofreader skeleton drafts