Completeness New

Every Topic, every type, kept complete.

A Topic can hold hundreds of keywords, each with multiple kinds of content, native and derived, and that number grows with each release that adds a new derived type. Every piece is built by its own background task, so the system scales with the types instead of being fixed to them. Two paired panels keep track of all of it. Resolve Missing Content, in the ☰ menu, shows what's missing. The Completeness Tasks panel shows the work filling it in. Each one links to the other for the same Topic, and the task status button in the Message Area shows the queue from any screen.

The whole cycle: generate, run, check, fix

Every piece of content is made by its own task, generated for one user › topic › keyword › content type. Completeness Tasks audits the tasks as they queue and run. Resolve Missing Content checks the content they leave on disk, and Resolve sends only what failed back to be generated again.

How every Topic is kept complete 1. A task generator creates one task per user, topic, keyword and content type. 2. Tasks queue (queued, waiting, running), one lock per task. 3. Background workers fetch native content and derive from it. 4. Native and derived files are stored per keyword and type. Completeness Tasks, the task audit, watches the queue and the workers and reports Ran, Done, Failed, Pending, Oldest pending, Worker and Last activity by content type, with a hover that names the running tasks. 5. Resolve Missing Content checks every keyword against one rule: 20 or more URLs for images, video, articles and pop art; at least one for the other types; the definition, narration MP3 and wordcloud on disk; Filter Words from PDF text, EXIF and transcripts; 10 PDF summaries; and at least one fun fact. Star ratings and site icons for shopping and news sites are collected but never make a keyword incomplete: a site with both is shown as a tile, any other site is listed under Other Domains. 6. Failing types go to Resolve (Top Off, Force Rebuild or Cancel Resolve), which queues only what failed back to the task generator. 1 · GENERATETask generatorone task peruser › topic › keyword › type2 · QUEUETask queuequeued → waiting → runningone lock per task, no duplicates3 · RUNBackground workersfetch native content,then derive from it4 · STOREContent on disknative + derived files,per keyword and typeTASK AUDITCompleteness TasksThe background work, by content type, for the Topics you pick:RanDoneFailedPendingOldest pendingWorkerLast activityHover “Running” to see the exact tasks at workwatcheswatches5 · CHECK · CONTENT COMPLETENESSResolve Missing ContentEvery keyword is checked against one written rule:20+ URLsimages · video · articles · pop art1+ URLnews · shopping · trends · keywords · wordcloud · slideshowon diskdefinition · narration MP3 · wordcloud imageFilter Wordsfrom PDF text · EXIF · transcripts10 summariesPDF summaries & glossaries per keywordnot requiredstars & icons · shopping · news (else Other Domains)1+ fun factwritten and storedchecks everykeyword6 · FIXResolveTick Topics or keywords; only failing types are sent.Top Offadd to what’s saved, only where it’s shortForce Rebuildback up and rebuild from scratchCancel Resolvewithdraw tasks still waitingKeyword list tint shows the gaps before you open the panelfailingtypesqueues onlywhat failedeach panel opens the other for the same Topic

Scroll sideways to see the whole cycle.

1 · Find the gaps

Resolve Missing Content

Opened from the ☰ menu. Checks every keyword in a Topic against one written rule of what "complete" means, and shows exactly which content types, native or derived, fall short.

  • Topic and keyword views, with a chip for each failing type
  • Shows tasks running for each keyword right now
  • "What counts as complete" spelled out on the panel
2 · Queue the fix

Resolve

Tick the Topics or keywords and press Resolve. Only what the panel shows as failing is sent off, so nothing that's already complete is redone.

  • Top Off adds to what's saved, only where it's short
  • Force Rebuild backs up and rebuilds from scratch
  • Cancel Resolve withdraws anything still waiting
3 · Watch it fill

Completeness Tasks

The background work, counted by content type: what has run, what succeeded, what failed and what's still waiting. Open it from the "Tasks for" pill in Resolve Missing Content; it's filtered to the Topics you pick.

  • Ran, Done, Failed and Pending for every type
  • Hover "Running" to see exactly which tasks are working
  • How long the oldest has waited, and the worker's last activity

When the tasks finish, the gaps clear. Content derived from the newly arrived native files follows on its own.

The task status button

A round button at the left of the Message Area shows the queue from any screen: green and blinking while tasks are running or waiting, red when there are none. Click it for the task list, with Active and Pending sections. Tasks are grouped by Topic, one row per Topic with its task count, and Pending tasks are listed in the order they will run.

Ready for the next content type

The cycle is not built around a fixed list. A new derived type is registered once, and the same generator, queue and workers build it for every keyword in every Topic. The rule for "complete" is extended to include it, and it gets its own counts in Completeness Tasks and its own bar in Content Statistics, like every type before it.

Keyword list tint

A keyword still missing content is tinted in the list, so you can see the gaps before opening Resolve Missing Content.

Content Statistics

A histogram of how much usable content each keyword holds, one bar per content type.

Live tile states

Every Content Type tile, native or derived, is drawn in full when its content is ready and faded when it isn't. What you see is what's there.

← Content typesLaunch the app →