Publishing Policy
Status: Draft
Purpose: Define how project material may be moved from private working files into the controlled publishing layer.
Publishing Model
The Markdoc content folder at ZZZ HUMANS DO NOT TOUCH/publishing/markdoc/markdoc/content/ is the controlled publishing layer for the project. The website build must only render reviewed content from this layer and its controlled assets.
The publishing layer should provide controlled transparency by showing the project purpose, research trail, assumptions, evidence summaries, gaps, risks, source summaries, analysis summaries and business case drafts when they are reviewed and safe to publish.
The publishing layer should preserve the substantive content of working documents wherever safe and useful. Summaries may be used for navigation and executive readability, but they must not replace detailed working content unless publication would create sensitivity, confidentiality or readability issues.
Working files outside the controlled Markdoc content and asset folders remain private project material unless explicitly reviewed and approved for publication.
Material That Can Be Published
- Project purpose, scope, research questions and methodology.
- Reviewed scoping summaries.
- Reviewed evidence summaries with appropriate source context.
- Aggregated and anonymised primary research themes after Phase 3 is authorised.
- Assumptions, limitations, uncertainty, gaps and risks.
- Analysis summaries and business case drafts when clearly labelled by status.
Material That Must Not Be Published
- Personal contact details.
- Buyer, processor, exporter or grower contact sheets.
- Raw interview notes.
- Private internal comments.
- Commercially sensitive information, including confidential prices, volumes, margins, contract terms or buyer requirements.
- Information provided in confidence.
- Anything identifying a person without consent.
- Unverified claims unless clearly labelled as unverified and included for evidence-trail reasons.
Material Requiring Review Before Publishing
- Any interview-derived material.
- Any buyer, processor, exporter, price, volume, contract or commercial detail.
- Draft findings, options, conclusions or recommendations.
- Negative findings that could identify a person or organisation.
- Any source summary based on restricted-access or supplied documents.
Redaction Rules
Sensitive information must be removed before content is placed in the Markdoc publishing layer.
Redaction should remove names, phone numbers, email addresses, business identifiers, site-specific information, exact contract terms, confidential source details and any combination of details that could reasonably identify a person or confidential commercial arrangement.
Where the information is decision-relevant, publish an aggregated, anonymised or generalised version instead.
Source Citation
Published pages should cite source documents by title, organisation or author, publication date, source type, geography and product category where available.
Working source logs and evidence registers remain the authoritative internal record. Published pages should not copy raw registers wholesale unless explicitly reviewed for sensitivity.
Showing Uncertainty
Published findings must show uncertainty clearly. Use High, Medium, Low or Unknown confidence where relevant.
Claims based on international, non-local, product-specific, advocacy or limited evidence must be labelled with appropriate caveats.
Draft Labelling
Every Markdoc content page must include a visible status such as Draft, In review, Final, Not commenced or Placeholder.
Draft material must not be presented as settled evidence, final analysis or a recommendation.
Relationship Between Published Pages and Working Files
Working files are the private research record. Published pages are reviewed derivatives.
When a working research file is materially updated, the project maintainer must assess whether a corresponding Markdoc page should also be updated.
Before committing, the project maintainer must check whether the publishing layer is consistent with the current project state.