# halo-platform — shared Halo platform corpus

The canonical, drift-proof home for shared Halo PSA / GRCITSM platform knowledge. Every file in this directory is **vendored byte-identical** into each plugin that carries the corpus; `check_consistency.py` (manifest ids `halo-platform-*`) enforces identity, and `sync-halo-platform.sh` re-vendors after edits.

**Do not hand-edit a vendored copy.** In the marketplace repo, the canonical copy is the one registered as `template` in the consistency manifest (the plugin that owns Halo dev tooling); edit there, then run the sync script. In a mirrored standalone repo, this directory is refreshed from upstream — treat it as read-only.

| File | Contents |
|---|---|
| `data-model.md` | Table domains, column-naming gotchas, JOIN patterns, EAV asset pattern, dual role model, client→site→user model, standard GRCITSM ticket/asset taxonomy |
| `sql-dialect.md` | The three SQL execution contexts, MindsDB dialect + MSSQL translation, the no-ORDER-BY rule, STRING_AGG rules, probe-first CF rule, rich-text column triples |
| `api-mcp-semantics.md` | OAuth/pagination/IDs/errors; MCP tool families, relay semantics, read-tool caps and staging discipline, SLA-scoped priority labels, tool-authoring caps |
| `write-semantics.md` | The write-verification doctrine: null-handling per tool, lookup rules, framework-CF ordering, new-asset-type gotchas, payload cliff, who-fields, verify-every-write, KB API |
| `ssp-narrative-doctrine.md` | The by-who taxonomy + decision rule, inheritance documentation rules, SAR-aligned status vocabulary |

Domain-specific layers (SSP write pipeline, bulk orchestration, runbook authoring, billing, project ops) stay in their owning plugins' skills as thin deltas over this corpus.
