Skip to content

Scheduled discovery: 0 new signal(s), 0 updated, 0 failed - #13

Open
github-actions[bot] wants to merge 1 commit into
mainfrom
automation/discovery
Open

github-actions[bot] wants to merge 1 commit into
mainfrom
automation/discovery

Conversation

@github-actions

@github-actions github-actions Bot commented Sep 29, 2026 •

Copy link
Copy Markdown
Contributor

Scheduled discovery

  • run: discovery.20261119T120745.54fbee86; command: python3 scripts/dk.py discover --trust ecosystem --due; dry run: False
  • started 2026-11-19T12:07:45Z, completed 2026-11-19T12:07:46Z
measure count
attempted 2
not due 0
observed 2
unavailable 0
invalid or malformed 0
signals created 0
signals updated 0
signals reused 10
review work created 0
corroboration results 10
failures 0
engine defects 0
  • engine exit code: 0 (0 clean, 1 source failure, 3 engine defect)
  • dk.py validate exit code: 0 — repository contracts current
  • trusted knowledge mutations: 0
  • persistence: pending on automation/discovery

Source changes and discovery signals are review work. Nothing here becomes trusted knowledge without a human edit in a separately reviewed commit.

What this pull request may contain

Only these paths, enforced by scripts/dk_automation.py check-paths before anything is committed:

  • sources/snapshots/
  • sources/state/
  • discovery/candidates/
  • discovery/signals/
  • discovery/review/
  • public-site/dataset/manifest.json
  • public-site/dataset/sources.json
  • public-api/examples/
  • release/checksums.json

Review

  • This branch is rebuilt from main by every scheduled run and force-pushed with a lease; review it here rather than committing to it.
  • Merge requires the branch ruleset: every required check green, no auto-merge, no bypass.
  • GitHub does not start push/pull_request workflows for changes made with the workflow token. To run the required checks on this branch, use Update branch or close and reopen the pull request.
  • A red dk.py validate (and test_finding_model_boundaries.py) means a pinned source changed and its reviewed context must be re-normalized by a human in a separate commit; that is the trust boundary working.
  • A red test_community_boundary.py means new snapshots are not yet inventoried: every redistributed snapshot must be listed in THIRD_PARTY_LICENSES.json with its SHA-256, licence and evidence by the reviewer. Automation never writes that manifest.

@github-actions
github-actions Bot force-pushed the automation/discovery branch from dcdde21 to 47297e7 Compare October 6, 2026 10:46
@github-actions
github-actions Bot force-pushed the automation/discovery branch from 47297e7 to d8a3e89 Compare October 13, 2026 11:05
@github-actions
github-actions Bot force-pushed the automation/discovery branch from d8a3e89 to 46b15b6 Compare October 21, 2026 08:52
@github-actions
github-actions Bot force-pushed the automation/discovery branch from 46b15b6 to c4c6502 Compare October 28, 2026 10:00
@github-actions
github-actions Bot force-pushed the automation/discovery branch from c4c6502 to 4a49547 Compare November 4, 2026 11:33
@github-actions github-actions Bot changed the title Scheduled discovery: 0 new signal(s), 0 updated, 0 failed Scheduled discovery: 1 new signal(s), 0 updated, 0 failed Nov 4, 2026
@github-actions
github-actions Bot force-pushed the automation/discovery branch from 4a49547 to 58db707 Compare November 12, 2026 11:50
Automated output of `python3 scripts/dk.py discover --trust ecosystem --due` (run discovery.20261119T120745.54fbee86).
Source state, immutable snapshots and review candidates only, plus the
derived public artifacts regenerated from them. No trusted knowledge was
changed; review is required before merge.
@github-actions
github-actions Bot force-pushed the automation/discovery branch from 58db707 to 40582bd Compare November 19, 2026 12:08
@github-actions github-actions Bot changed the title Scheduled discovery: 1 new signal(s), 0 updated, 0 failed Scheduled discovery: 0 new signal(s), 0 updated, 0 failed Nov 19, 2026

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants