INTELLIGENCE LIFECYCLE · 02 / 05

Collection

Task a reviewed source. Retain what was observed.

Collection connects a retained requirement to source authority, resources, task windows, attempts and results. Original material and processing derivatives remain separate so later work can reconstruct what was acquired and what changed.

01 · Review the source and permitted use

Source records retain description, provenance, reliability, restrictions and amendments. An authorised reviewer records purpose, permitted methods and use, authority reference, discipline, control category and validity. Exact permitted requirement versions are bound to the review, with collection tasking, new material ingestion or both selected explicitly.

The review gates new tasking and acquisition. A normal amendment removes authority from the new source revision. New use must fit the latest reviewed active revision, approved requirement version, operation and validity window. A typed authority reference is not automated legal validation and does not create a collection power.

02 · Build the plan around the actual gap

Start with a Draft or Active non-RFI requirement, an appropriately reviewed source, an eligible collector and a realistic UTC window. State the objective and handling, then retain the requirement version used by the plan. Assign an exact source revision and collector account, with start and end times, risks and mitigations.

Activate the plan through a reasoned transition. The assigned collector records task progress. The plan describes what is authorised and intended; it is not evidence that acquisition has occurred or that the resulting information is accurate.

03 · Check capacity and resolve conflicts

Planners maintain approved resource availability, capacity and reservations. Task proposals are checked against authorised existing reservations before assignment. Conflicting allocations require a recorded priority or deconfliction decision, with an accountable owner and a revised window for displaced work.

Capacity views do not expose another team’s protected allocations. Unmet requirements can compare lawful alternatives and retain why the selected source is suitable. Completion, delay and remaining gaps inform effectiveness review without automatically satisfying Direction.

04 · Record an observation for each attempt

Retain the observed information, acquisition time, credibility assessment, rationale and remaining gaps. A task can complete only after a result exists for its current attempt. A plan completes when all tasks are completed or cancelled. Terminal work can be retasked into a new attempt where justified.

An earlier attempt’s result cannot complete a new attempt. Reassessment retains the original observation and grade instead of rewriting history. Source reliability and information credibility remain separate; A–F and 1–6 labels describe different assessments and do not mechanically certify truth.

05 · Preserve originals before processing

The acquisition path accepts TXT, PDF, DOCX, CSV and JSON within documented size, type and duplicate bounds. Original bytes, integrity hash, acquisition provenance and source/requirement context are retained. Processing state is inspectable rather than replaced by fabricated extraction results.

Approved exact-byte scanning binds verdicts to the original hash, engine/signature identity and policy. Unavailable, expired, unknown, failed or infected outcomes remain quarantined. Scanner adoption and freshness are deployment-specific. Uploading material does not certify accuracy, lawful use or corroboration.

06 · Keep extraction separate from interpretation

An isolated parser creates retained derivatives with structured segments and locators. Job handling includes requester-bound authority, leases, retries and explicit outcomes. Reprocessing can add a new extraction while earlier information references stay pinned to the old derivative.

Analysts accept, reject or correct suggestions with reasons and provenance. Extraction decisions do not automatically create entities, relationships or judgements. Interpretation and translation annotations attach to exact spans, preserve the original and retain uncertainty and reviewer information.

07 · Assess independence and retain authority history

Source-lineage records expose authorised reporting origins and common roots for human circularity assessment. Different document identifiers do not establish independent corroboration. Unknown origins remain recorded limitations rather than being treated as independent sources.

Expiry or withdrawal stops unauthorised new use without erasing historical source, tasking or information records. Completing collection records what happened in an attempt; it neither proves the information true nor authorises arbitrary subsequent acquisition.

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.