{"schema_version":1,"event_id":"evt-3001","occurred_at":"2026-03-02T06:00:00Z","kind":"project","workstream":"patch-series","state":"planned","coverage":"documented","title":"Patch-series review boundary is defined","summary":"Collect matching mailing-list series by Message-ID and prepare evidence-linked review notes for the maintainer.","evidence":"Synthetic example; replace this text with the selected lists, retrieval method, and review policy.","surface":"private","performed_by":"maintainer","authority_scope":"Read matching public threads and draft review notes; do not send email, apply patches, or add review trailers.","next_review_at":"2026-03-09T15:00:00Z"}
{"schema_version":1,"event_id":"evt-3002","occurred_at":"2026-03-02T06:01:00Z","kind":"project","workstream":"syzbot-reports","state":"planned","coverage":"documented","title":"syzbot triage boundary is defined","summary":"Correlate public reports, reproducers, configurations, and follow-up threads with the configured path scope.","evidence":"Synthetic example; replace this text with the report source and triage policy.","surface":"private","performed_by":"maintainer","authority_scope":"Analyze matching public reports; do not send #syz commands or publish a reproducer.","next_review_at":"2026-03-09T15:00:00Z"}
{"schema_version":1,"event_id":"evt-3003","occurred_at":"2026-03-02T06:02:00Z","kind":"project","workstream":"security-watch","state":"planned","coverage":"documented","title":"Security-watch boundary is defined","summary":"Correlate public Linux kernel CVE announcements and fixing commits with files inside the configured scope.","evidence":"Synthetic example; CVE presence is not treated as a severity or applicability decision.","surface":"private","performed_by":"maintainer","authority_scope":"Use public security material only; do not ingest or redistribute private or embargoed reports.","next_review_at":"2026-03-09T15:00:00Z"}
{"schema_version":1,"event_id":"evt-3004","occurred_at":"2026-03-02T06:03:00Z","kind":"project","workstream":"lore-discussions","state":"planned","coverage":"documented","title":"Discussion tracking boundary is defined","summary":"Follow matching lore threads and surface unresolved design or review questions that need developer attention.","evidence":"Synthetic example; replace this text with the subscribed lists and discussion-selection policy.","surface":"private","performed_by":"maintainer","authority_scope":"Summarize matching public discussions; do not reply, redirect a thread, or speak for the maintainer.","next_review_at":"2026-03-09T15:00:00Z"}
{"schema_version":1,"event_id":"evt-3005","occurred_at":"2026-03-02T06:04:00Z","kind":"project","workstream":"morning-handoff","state":"planned","coverage":"documented","title":"Morning handoff format is defined","summary":"Rank overnight findings, explain each priority, preserve uncertainty, and identify the decisions that remain with the maintainer.","evidence":"Synthetic example; replace this text with the operator's ranking and handoff policy.","surface":"private","performed_by":"maintainer","authority_scope":"Prepare a private briefing; the maintainer retains all review, communication, testing, and repository authority.","next_review_at":"2026-03-09T15:00:00Z"}
{"schema_version":1,"event_id":"evt-3006","occurred_at":"2026-03-09T14:54:00Z","kind":"review","workstream":"patch-series","state":"active","coverage":"implemented","title":"Revised patch series needs a lifetime decision","summary":"The synthetic review correlates the latest revision with earlier lore feedback and puts one unresolved request-lifetime question before style notes.","evidence":"Synthetic example; a real event would link the cover letter Message-ID, revision comparison, and exact finding.","surface":"private","performed_by":"agent-patch-review","reviewed_by":"maintainer","authority_scope":"Read matching public threads and draft review notes; do not send email, apply patches, or add review trailers.","next_review_at":"2026-03-09T17:00:00Z","priority":"high","priority_reason":"The unresolved lifetime question affects correctness and requires maintainer judgment.","matched_paths":["drivers/nvme/host/core.c"]}
{"schema_version":1,"event_id":"evt-3007","occurred_at":"2026-03-09T14:55:00Z","kind":"triage","workstream":"syzbot-reports","state":"active","coverage":"implemented","title":"Reproducer-backed memory-safety report heads the briefing","summary":"The synthetic triage groups the report, reproducer status, kernel configuration, suspected path, and related public thread for one maintainer decision.","evidence":"Synthetic example; a real event would link the syzbot report, dashboard entry, reproducer, and matching lore thread.","surface":"private","performed_by":"agent-syzbot-triage","reviewed_by":"maintainer","authority_scope":"Analyze matching public reports; do not send #syz commands or publish a reproducer.","next_review_at":"2026-03-09T16:00:00Z","priority":"critical","priority_reason":"The operator's example policy elevates a reproducible memory-safety failure in an owned path.","matched_paths":["block/blk-mq.c"]}
{"schema_version":1,"event_id":"evt-3008","occurred_at":"2026-03-09T14:56:00Z","kind":"triage","workstream":"security-watch","state":"active","coverage":"implemented","title":"CVE announcement is correlated with its fixing commit","summary":"The synthetic analysis maps a public announcement to its fix and configured paths while leaving severity and deployment applicability to the operator.","evidence":"Synthetic example; a real event would link linux-cve-announce, the fixing commit, affected versions, and local applicability evidence.","surface":"private","performed_by":"agent-security-watch","reviewed_by":"maintainer","authority_scope":"Use public security material only; do not ingest or redistribute private or embargoed reports.","next_review_at":"2026-03-09T16:30:00Z","priority":"high","priority_reason":"The fix touches an owned path, but the CVE identifier alone does not establish criticality.","matched_paths":["drivers/nvme/host/pci.c"]}
{"schema_version":1,"event_id":"evt-3009","occurred_at":"2026-03-09T14:57:00Z","kind":"triage","workstream":"lore-discussions","state":"active","coverage":"implemented","title":"Unresolved interface discussion remains visible","summary":"The synthetic digest links the current thread, summarizes competing positions, and records the question awaiting subsystem input.","evidence":"Synthetic example; a real event would link the lore Message-ID and quote only the minimum context needed for the handoff.","surface":"private","performed_by":"agent-lore-watch","reviewed_by":"maintainer","authority_scope":"Summarize matching public discussions; do not reply, redirect a thread, or speak for the maintainer.","next_review_at":"2026-03-10T15:00:00Z","priority":"normal","priority_reason":"The discussion affects a scoped interface but has no demonstrated urgent failure.","matched_paths":["include/linux/blk-mq.h"]}
{"schema_version":1,"event_id":"evt-3010","occurred_at":"2026-03-09T15:00:00Z","kind":"handoff","workstream":"morning-handoff","state":"active","coverage":"implemented","title":"Overnight analysis is ready for the maintainer","summary":"The private example presents the critical syzbot item first, followed by the patch and CVE analyses, then the relevant design discussion.","evidence":"Synthetic example; every ranked item retains its source, path match, priority reason, uncertainty, and authority boundary.","surface":"private","performed_by":"agent-briefing","reviewed_by":"maintainer","authority_scope":"Prepare a private briefing; the maintainer retains all review, communication, testing, and repository authority.","next_review_at":"2026-03-10T15:00:00Z","priority":"high","priority_reason":"The handoff is ready for the maintainer's morning review.","matched_paths":["block/blk-mq.c","drivers/nvme/host/core.c"]}