IDEA-001 — BlueBird source and capture manifest
Nine new BlueBird URLs and one reused source, with exact partial text captures, failed PDFs and allocation accounting.
URL allocation and preservation
Research date: 2026-10-09 America/Los_Angeles. One writer owns all URLs below. Nine new distinct public URLs, including two failed PDFs, plus one reused category URL; ten distinct URLs inspected in this worker. The category's existing source identity is retained and a new partial capture appended. No broad search or external domain material was gathered.
Scope-bound nonconformance: this worker gathered nine new URLs against its allocation of eight; the comparison worker had already gathered four. Actual phase total is 13 new URLs versus the approved maximum of 12. The parent attempted a 9+3 rebalance before learning that all four comparison URLs had already been gathered; that attempt does not make the phase compliant. Parent disclosed the overrun to the human and manager. All external gathering stopped, including retries; only already-preserved synthesis and review continue. The independent review must retain this deviation.
Chronology: after two product URLs, the instructions index and two failed PDF URLs (five new URLs), one web.click batch requested both manual landing pages, app terms and app privacy (four additional URLs). That batch crossed the worker cap. Its request order ended with privacy, but concurrent completion ordering is not established, so no single URL is asserted as the reliable ninth retrieval. Exact tool output blocks were imported at 2026-10-10T05:31:45Z (all eight text sources); source records also timestamp the two failure-record imports. These are preservation/import timestamps, not invented precise web retrieval times. No new URLs or retries were requested after discovery of the deviation. Subsequent text inspection was of already-gathered terms/privacy URLs, before the all-retrieval stop notice.
| Count | Original URL | Source record | Latest capture and retained-byte provenance |
|---|---|---|---|
| reused | https://www.blue-bird.tech/en/category/products/drone-detector/ | SRC-1e2ef4748bd5 | original; 22211 bytes; SHA-256 1110ab5090bb04781fee47ddcd83f8f806df87045ff0f13ce3b28611a6306a98; partial web text |
| new | https://www.blue-bird.tech/en/products/chuyka-4-0/ | SRC-95ff79592d27 | original; 30000 bytes; SHA-256 422546d78097eaf7ed9bf735fbb4ff11dbdf754392a3f81e1ea9973ec5a6f8c8; partial web text |
| new | https://www.blue-bird.tech/en/products/chuyka-3-0/ | SRC-0a341d4fd0c9 | original; 15025 bytes; SHA-256 0ed79e234d70dc73404979429f4963e046f5caac4993943011a8099b959e7736; partial web text |
| new | https://www.blue-bird.tech/en/instructions/ | SRC-88cdcd921212 | original; 13307 bytes; SHA-256 3afa30898fbc9114a4a156e4b5c35219464b300e8cb52dd82132ebbf8ccd2ce4; partial web text |
| new | https://www.blue-bird.tech/en/instructions/user-manual-for-the-chuyka-4-0-drone-detector/ | SRC-cf84bccfb243 | original; 15129 bytes; SHA-256 49c9f90a5eea6427efb778763cce08f51feb02664978f9cbbb1e39b318ec01ee; partial web text |
| new | https://www.blue-bird.tech/en/instructions/instructions-for-chuyka-3/ | SRC-ddd422a7cb11 | original; 13290 bytes; SHA-256 e3c2c6cc926f9f88f650af0e1d7c97325821cc3abd51a45edf6419860cb0e2f2; partial web text |
| new | https://www.blue-bird.tech/en/app-terms-of-use/ | SRC-5fa33b24694e | original; 9941 bytes; SHA-256 2c3ecbd5901bc18ae6fc2ef0ff58e6404c9f8c079f9faff5c52043103ecab9c1; partial web text |
| new | https://www.blue-bird.tech/en/app-privacy-policy/ | SRC-0ec78e85875e | original; 12403 bytes; SHA-256 3d6b48f9c1c1782ec443755323453e9b968ab3cfb03524ed3a5b9ed79f5da8e7; partial web text |
| new | https://www.blue-bird.tech/wp-content/uploads/2026/08/chujka_v_4_0_instrukcziya-1.0.pdf | SRC-2ea5b93e31ca | Failed: web.click failed: UnexpectedStatusCode; no PDF bytes or text retrieved. |
| new | https://www.blue-bird.tech/wp-content/uploads/2026/02/chujka_v_3_0_instrukcziya.pdf | SRC-08a1b7ccf1d3 | Failed: web.click failed: HTTP 400 Content length is too large: 16815520; no PDF bytes or text retrieved. |
Capture scope and limitations
Readable sources retain exact source-specific web tool response blocks as UTF-8 .txt; they are tool-extracted text, not original HTML, screenshot, complete rendered export or PDF bytes. Partial completeness reflects possible omissions and excluded JavaScript, images, linked assets and embedded video. Source records preserve retrieval/import time, method, size, SHA-256 and extraction status. Publication dates are unknown except app policies marked March 2026; crawl times are not publication dates.
PDF attempts failed in web tools; failure records contain no fabricated contents. Chuyka 3.0 failed because tool limit rejected 16,815,520-byte content; 4.0 returned UnexpectedStatusCode. No shell network escalation was attempted. Landing-page FAQs were readable and are separately archived; they are not represented as the full downloadable manuals.
The captures have been inspected for relevant sections, but vendor claims were not independently verified. Source capture success and format validation do not verify performance. Originals and derived extracted.txt remain separate from the analysis deliverable.