unknowni have atttached the details in notepad file build as per requested
Sign in to leave a comment
This document specifies the requirements for FluxGet, a production-quality, cross-platform desktop download manager. FluxGet reproduces the useful functional capabilities expected of a modern high-performance download manager — parallel multi-connection transfer, pause/resume, crash recovery, queueing, scheduling, categorization, browser integration, media detection, authentication, bandwidth control, and integrity verification — while remaining an entirely original implementation built on standard, documented networking protocols, documented browser APIs, and original engineering.
FluxGet MUST be installable and usable locally on Windows without requiring a hosted service or external cloud account for download management.
The system MUST NOT copy proprietary source code, binaries, private algorithms, branding, icons, or reverse-engineered implementation details from any existing download manager. All architecture, UI, branding, codebase, and assets are original. FluxGet is a general-purpose download manager that downloads only resources a user is authorized to access, and it explicitly excludes DRM removal, paywall bypass, credential theft, session hijacking, CAPTCHA bypass, and access-control circumvention.
The document provides canonical requirements for architecture, functional behavior, UI, security, privacy, performance, testing, delivery phases, and technical boundaries.
chat_media/64e0f427-c865-48a4-84ab-27b1846f0b5a/f4891c9a_You_are_a_senior_systems_engineer_.txt containing the authoritative FluxGet requirements.FluxGet is a desktop application composed of a Rust download engine, a modern desktop UI shell, and companion browser extensions. It is organized as a modular architecture comprising:
The core download engine is asynchronous and streams network data directly to disk across multiple parallel Range-request segments. Persistent state is maintained in SQLite with a fully defined download state machine. A browser extension (Manifest V3) communicates with the desktop application over Native Messaging (preferred) or a secure authenticated local service. The UI subscribes to an internal event bus and renders a compact, high-density productivity interface with live per-connection progress visualization.
The application works locally by default and does not transmit download history, URLs, cookies, filenames, clipboard data, or credentials to external analytics servers.
Content-Disposition header so that server-suggested filenames are used.Content-Length so that expected size is known.Content-Type so that MIME type is determined.ETag so that remote file identity is validated.Last-Modified so that remote change detection is possible.Accept-Ranges so that resume support is detected.Transfer-Encoding so that transfer framing is respected.CREATED state so that new downloads begin lifecycle tracking.ANALYZING state so that metadata probing is represented.QUEUED state so that waiting downloads are represented.CONNECTING state so that connection establishment is represented.DOWNLOADING state so that active transfer is represented.PAUSED state so that suspended downloads are represented.RETRYING state so that retry activity is represented.VERIFYING state so that integrity checking is represented.COMPLETED state so that finished downloads are represented.FAILED state so that failed downloads are represented.CANCELLED state so that cancelled downloads are represented.Accept-Ranges before segmentation so that ranges are only used when supported.Content-Range response so that returned ranges are validated.ETag or Last-Modified before segmentation so that segments belong to the same file version.filename.iso.part) so that partial downloads are isolated.Retry-After so that server guidance is honored.Content-Disposition filename*, Content-Disposition filename, URL filename, MIME-derived fallback, generated filename, so that naming is deterministic.file.zip, file (1).zip, file (2).zip so that duplicates are distinguished..m3u8 manifest parsing so that HLS streams are recognized..mpd manifest parsing so that DASH streams are recognized.image[001:100].jpg → image001 … image100) so that numbered URL sets are generated.downloads table.segments table.queues table.queue_items table.categories table.scheduler_rules table.settings table.host_rules table.history_events table.downloads fields: id, url, resolved_url, filename, temp_path, destination_path, file_size, downloaded_bytes, status, etag, last_modified, mime_type, category_id, queue_id, priority, connections, created_at, updated_at, completed_at.segments fields: id, download_id, start_byte, end_byte, current_byte, status, retry_count.../../evil.exe so that files cannot escape the destination..part file into the final filename where possible.DownloadAdded event.DownloadStarted event.DownloadProgress event.DownloadPaused event.DownloadResumed event.DownloadFailed event.DownloadCompleted event.QueueStarted event.QueueFinished event.NetworkChanged event.DiskSpaceLow event.
FluxGet · local Windows download manager
Install FluxGet on Windows and keep every transfer in view: parallel Range connections, pause and resume, crash recovery, queues, schedules and integrity checks — all running locally on your machine, without a hosted service or external cloud account.
Capability ledger / 08 modules
Eight accepted capability groups, recorded as numbered modules. Values below are the shipping defaults — every one of them is configurable inside the local desktop application.
Spec / Split each file into parallel HTTP Range segments so transfers use the bandwidth the server actually offers — with an explicit, conservative cap on how many connections a single download may open.
Spec / Interrupt a transfer and continue it later without losing progress. Before any range is re-issued, the remote identity is revalidated so a changed file is never stitched onto an old partial.
Spec / Organise transfers into named queues, each with its own concurrency ceiling, priority order, active window, bandwidth ceiling, and retry policy.
Spec / Run transfers inside a chosen window rather than around the clock, repeating only on the days you select.
Spec / Completed files land in a category folder derived from their file type, so a downloads directory stays organised without manual sorting.
Spec / A companion extension hands browser-initiated downloads to FluxGet instead of letting the browser manage them.
Spec / An opt-in watcher recognises copied HTTP and HTTPS links and offers them as a download. It is off until you turn it on, and every offer can be declined.
https://releases.example.org/ubuntu/Ubuntu.isoMonitoring is off. Checking the form above is an explicit opt-in.
Spec / Reach credentialed hosts, keep transfers inside a bandwidth budget, route through your network proxy, and confirm a finished file byte for byte.
Credentials are held in operating-system credential storage. Passwords are never written to the database in plain text.
Every value above is a shipping default, not a promise about your network — connection counts, bandwidth ceilings, and schedules are all yours to change. FluxGet is installable and usable locally on Windows without a hosted service or external cloud account.
Queues & Scheduler
Queue board
Priority levels
HighRuns before normal and low itemsNormalDefault order within a queueLowYields to every higher priorityScheduler strip
Windows outside the window are held in the night queue until the next 01:00 AM start.
No power action. FluxGet stays open after the queue finishes.
06Recovery & Integrity
FluxGet keeps the real transfer state visible: what is on disk, what the server still reports, and exactly when a retry is allowed. Nothing is marked complete until file integrity checks pass.
Selected download ledgerarchive-7z
Remote revalidation differs
The stored file no longer matches the server’s current ETag or Last-Modified value. Resume is withheld and the partial data stays on disk until you revalidate or restart the transfer.
Records read: 3Source: local SQLite storeMode: read onlyRuntime: local Windows desktop
Local runtime requirement
The desktop application runs on your own machine and needs no server round-trip to queue, pause, resume, or verify a transfer. Your queue lives on your disk, in a local SQLite database you can inspect.
Never transmitted to external analytics servers:
Credentials are held by the operating system, never in plaintext SQLite fields.
TLS certificate validation is never disabled globally.
FluxGet · local Windows download manager
Install FluxGet on Windows and keep every transfer in view: parallel Range connections, pause and resume, crash recovery, queues, schedules and integrity checks — all running locally on your machine, without a hosted service or external cloud account.
Capability ledger / 08 modules
Eight accepted capability groups, recorded as numbered modules. Values below are the shipping defaults — every one of them is configurable inside the local desktop application.
Spec / Split each file into parallel HTTP Range segments so transfers use the bandwidth the server actually offers — with an explicit, conservative cap on how many connections a single download may open.
Spec / Interrupt a transfer and continue it later without losing progress. Before any range is re-issued, the remote identity is revalidated so a changed file is never stitched onto an old partial.
Spec / Organise transfers into named queues, each with its own concurrency ceiling, priority order, active window, bandwidth ceiling, and retry policy.
Spec / Run transfers inside a chosen window rather than around the clock, repeating only on the days you select.
Spec / Completed files land in a category folder derived from their file type, so a downloads directory stays organised without manual sorting.
Spec / A companion extension hands browser-initiated downloads to FluxGet instead of letting the browser manage them.
Spec / An opt-in watcher recognises copied HTTP and HTTPS links and offers them as a download. It is off until you turn it on, and every offer can be declined.
https://releases.example.org/ubuntu/Ubuntu.isoMonitoring is off. Checking the form above is an explicit opt-in.
Spec / Reach credentialed hosts, keep transfers inside a bandwidth budget, route through your network proxy, and confirm a finished file byte for byte.
Credentials are held in operating-system credential storage. Passwords are never written to the database in plain text.
Every value above is a shipping default, not a promise about your network — connection counts, bandwidth ceilings, and schedules are all yours to change. FluxGet is installable and usable locally on Windows without a hosted service or external cloud account.
Queues & Scheduler
Queue board
Priority levels
HighRuns before normal and low itemsNormalDefault order within a queueLowYields to every higher priorityScheduler strip
Windows outside the window are held in the night queue until the next 01:00 AM start.
No power action. FluxGet stays open after the queue finishes.
06Recovery & Integrity
FluxGet keeps the real transfer state visible: what is on disk, what the server still reports, and exactly when a retry is allowed. Nothing is marked complete until file integrity checks pass.
Selected download ledgerarchive-7z
Remote revalidation differs
The stored file no longer matches the server’s current ETag or Last-Modified value. Resume is withheld and the partial data stays on disk until you revalidate or restart the transfer.
Records read: 3Source: local SQLite storeMode: read onlyRuntime: local Windows desktop
Local runtime requirement
The desktop application runs on your own machine and needs no server round-trip to queue, pause, resume, or verify a transfer. Your queue lives on your disk, in a local SQLite database you can inspect.
Never transmitted to external analytics servers:
Credentials are held by the operating system, never in plaintext SQLite fields.
TLS certificate validation is never disabled globally.
No comments yet. Be the first!