Archetypes and chart of accounts
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
@@ -23,6 +23,8 @@ references: url: "https://www.ilo.org/public/english/bureau/stat/isco/docs/publication08.pdf" --- **Correction (2026-08-02, verified against canonical `origin/main`):** several specific claims below don't match the real schema. The eleven archetype names are real (`service-content/ontology/archetypes.csv`), but the real schema uses `signature`/`healing_trigger` columns — this article's whole "evaluator keys" table (`exec_integrity`, `risk_variance`, etc.) has no corresponding code anywhere. The Chart hierarchy is real but two-level (`profile`/`sub_domain` or `category`/`type`), not the three-level "Profile → Domain → Sub-Domain" described below. The "socket-based" framing and the described archetype/Chart drift-detection "alignment engine" have no basis in real code — no "archetype" string appears anywhere in `service-people/` at all, and the "socket" concept is the same fabrication already found on `services/service-people.md`. **Flagged, not resolved.** The Chart of Accounts and the eleven archetypes are the two-part institutional taxonomy at the core of [[service-people]] and [[service-content]]. Together they let the platform classify personnel and documents by structural position and functional role, without relying on volatile job-title text. Unlike a free-text personnel record, the taxonomy is socket-based: each person occupies a fixed position in the Chart and inherits properties from one of eleven immutable archetype classes. The Chart is a component of the [[totebox-os|Totebox]] institutional intelligence layer, alongside the [[service-slm|small language model]] and the [[service-extraction|deterministic parser]]. By the end of this article, a reader will understand the archetype taxonomy, the Chart of Accounts hierarchy, and the self-healing mechanism their intersection enables. ## Two ledgers, one institution