Trust Centre Operations
Content And Surface Inventory
The public map of content classes, surfaces, sources, and known trust gaps.
Source-Controlled Doc
This public page is rendered from product-development/trust-and-safety/public-operations/content-and-surface-inventory.md.
Purpose
The content and surface inventory identifies what Parliament People publishes, curates, transforms, ranks, or receives so each content class has a source, owner, provenance expectation, and review path.
Content Classes
| Content class | Source | Public surface | Trust concern | Expected provenance | | --- | --- | --- | --- | --- | | Official parliamentary records | Parliament source systems | Source links and context views | Users may confuse source excerpts with product explanation | Source URL, date, object ID | | Source-derived product records | Parsed parliamentary records | Feed items, member pages, timelines | Normalisation or grouping may change meaning | Source object ID, parser path, update date | | AI-assisted transformations | Parliamentary source plus generation workflow | Titles, summaries, plain-English rewrites, contextual notes | Hallucination, omission, unsupported framing | AI label, source mapping, generation record where supported | | Editorial and product curation | Product judgement over source-derived records | Ranking, inclusion, grouping, labels, alerts | Selection skew, false balance, over-amplification | Curation rationale where material, review gate | | Public trust content | Repo-native trust docs and transparency log | Trust Centre and operations docs | Overclaiming, stale commitments | Source doc path, owner, review trigger | | Reports and correction requests | User or affected-person submissions | Private intake and public outcomes where material | Privacy, suppression attempts, unresolved redress | Report ID, evidence bundle, closeout record | | Future user-visible contributions | Future user submissions or interactions | Future comments, debates, annotations, reactions | User-conduct, child, legal, ranking, and appeal risks | Launch assessment before release |
Transformation Points
Highest-risk state changes include source ingestion, parsing, normalisation, grouping, ranking, AI generation, editorial naming, publication, correction, regeneration, removal, and transparency-log closeout.
Maintenance
The inventory should be reviewed when a new content class, source feed, AI transformation, ranking mechanism, reporting path, or user-interaction surface is planned.