INTELLIGENCE LIFECYCLE · 04 / 05
Dissemination
Approve exact content for an exact audience.
Dissemination covers the authored product and its separate controlled-release decision. A saved draft, an internal export, independent approval, publication and recipient acknowledgement are different events with different evidence.
01 · Author and retain the intelligence product
Products are editable, versioned reports with exact evidence and optional analytical lineage. Built-in starters are Brief, Assessment, Intelligence Assessment, Intelligence and security directive (draft), and Joint intelligence estimate / JIPOE (draft). Templates organise authored material; they do not issue an operational order or confer command authority.
Write and reorder sections, source notes and citations. An analysis-derived draft uses a selected retained revision and requires explicit confirmation before replacing editor content. Preview, save and continue are deliberate actions. Unsaved-edit warnings protect navigation; a preview is not a saved revision.
02 · Declare currency and limitations
Record information-as-of, an optional review-due time, processing and corroboration declarations, rationale and limitations. Preliminary content, unprocessed information, curtailed processing and uncorroborated information remain explicit human attestations.
A passed advisory review-due date displays a warning; it does not automatically delete the product or expire release. Older content without assurance is shown as not recorded. New release decisions require valid assurance on the exact revision under current policy. Historical package bytes are not regenerated to imply later notices were originally present.
03 · Inspect genuine draft exports
CORTEX renders PDF, DOCX and structured JSON from an exact saved product revision, including handling, authored sections, relevant source notes and provenance. Internal drafts carry a prominent notice that they are not authorised for distribution.
Rendering has text, layout, glyph and output limits. Unsupported content fails visibly rather than being silently dropped. Original evidence files and unrestricted source history are not automatically attached. Export preparation is audited, but creating bytes proves neither download nor approval.
04 · Bind the release scope
Select the exact current product revision, inspect its content hash and verify each intended internal recipient. Retain handling, the requirement relationship and the audience. Save a release draft with a reason before submitting that exact scope for review.
Recipient eligibility is checked against current authority. Content and audience changes invalidate the basis for pending approval. A contributor cannot treat an old approval as covering amended reasoning or a wider distribution list.
05 · Separate review, approval and publication
A different eligible account reviews content, assurance, handling and audience, then endorses the scope or requests changes. Review endorsement is required before independent approval. The approver must be neither requester nor any retained Product or Analysis contributor.
An authorised publisher then publishes the controlled package on the node. Publication retains genuine PDF, DOCX and JSON outputs with a manifest and integrity information. It does not email recipients or establish receipt. Current access checks still apply when the package is requested.
06 · Govern sharing and marking changes
Reviewed UK domestic sharing adds versioned agreements, recipient purpose, originator conditions, source-identification review, approved recipient projections, transfer, explicit receipt and correction or withdrawal notices. A separately authorised marking change is distinct from ordinary sanitisation.
These controls do not confer unrestricted email, public publication, foreign disclosure or cross-domain transfer. The existence of handling labels is not accreditation for a classified deployment. Deployment owners must establish the applicable acceptance and organisational approvals.
07 · Verify the received package
A named recipient can prepare and download the controlled ZIP, then calculate its SHA-256 using an approved file tool and compare it with the authenticated release record. Explicit acknowledgement binds the statement to the exact package received.
Package hashes identify exact bytes; they are not per-product digital signatures. A download or read marker is not receipt. Acknowledgement does not prove that every sentence was understood or that the recipient accepts the assessment as correct. Feedback follows the acknowledged package.
Documentation basis: CORTEX Master Project Reference, version 2.0, 28 September 2026. Capability descriptions follow its completed-scope basis; operational acceptance remains specific to the deployed release and environment.