Skip to main content

Hidden / coupled producer census — 2026-09-12

This second census looks beyond obvious scheduled jobs. A component is admitted as a producer only when it has an independently meaningful artifact, release, judgment, projection, or terminal-acceptance boundary.

Scheduled surfaces recovered after the first seed​

  • argentina-geography weekly integrity workflow — admitted as an integrity sentinel, explicitly not a provider-refresh claim.
  • atlas-pobreza-docs weekly engineering-doc build verification — admitted as documentation/build coherence only.
  • encuestador-de-hogares weekly exact real-EPH 2024-Q3 acceptance — admitted as an expensive bounded scientific acceptance producer.
  • min-economia-arg-datos weekly updater — admitted as unresolved/hold because it is still configured and mutation-capable while existing estate evidence classifies it as structurally broken.

The scheduled GitHub surface census is therefore represented without pretending all scheduled producers are healthy or authoritative.

Hidden / coupled producer chains admitted​

Political speeches​

politics-wiki already exposes a real source-owned chain:

official speech sources
  -> stable speech identity + immutable captures
  -> deterministic corpus release
  -> deterministic speech chunk projection
  -> Knowledge Inspect bounded lexical consumer

The corpus and chunk projection are distinct semantic producers even though the current real proof can execute them inside one workflow.

Governed monitored media / YouTube​

media_monitor already owns producer-local stable YouTube/media-item identity, immutable metadata snapshots, governed text provenance, segments, appearance evidence, and regenerable operational indexes. This is admitted separately from the hourly public-publication producer because the corpus/output boundary can be reused by future consumers without redefining Media Monitor's source semantics.

Paper knowledge​

paper-kb already produces governed paper chunks plus paper-owned review/catalog records. These are admitted as candidate producers because repository-local authority is proven but estate authority remains proposed.

The review/catalog projections feed already-proven consumers such as the immutable abstract-scroller review snapshot and the collection/experience composition layer.

Collections and experiences​

knowledge-experiences already implements collection and experience specs/releases and declares authority for frozen collection membership and experience composition. It is admitted conservatively as a candidate until its estate identity/topology is fully reconciled.

Evidence selection​

kb-artifacts is admitted as a candidate deterministic selected-evidence producer. No direct Knowledge Inspect -> KB Artifacts handoff is invented; the current input remains producer-agnostic JSONL evidence collections.

Estate sensing​

projects:make sense is itself a manual producer: it creates factual GitHub observation evidence, drift projections and downstream repository context. It is not just a maintenance command.

Geography releases​

argentina-geography real source/product materialization is distinct from its scheduled integrity sentinel. The manual release producer owns governed geography/relation/crosswalk releases; scheduled CI only proves executability.

Accounting reports​

accounting-workflows:make run-full is admitted as a candidate report-pack producer over canonical accounting transformation/reporting semantics. Execution remains manual/accounting-close-driven and downstream privacy/publication remains separately governed.

Predictive welfare release​

The Sep-11 predictive welfare builder has an independently meaningful content-derived research.household-welfare-predictive/v1 release boundary. It is admitted as a candidate event-driven producer without claiming that the surrounding research promotion/publication path is fully canonical.

Deliberately not admitted​

  • every Make target;
  • internal helper functions;
  • fixture-only builders without an independent consumer/output boundary;
  • speculative ASR, embeddings, entity-resolution or generic workbench infrastructure;
  • legacy local timers from old host census evidence that have not been reconciled after scheduler hygiene;
  • downstream relationships that are merely plausible but not actually proven.

The intent is to make composition visible while keeping the registry a semantic control surface rather than a command inventory.