Skip to content

[spdd] Daily spec work plan - 2026-10-06 #66218

Description

@github-actions

Summary

Reviewed 5 specs (rotation indices 10-14 of 20). The specs are mature and already carry Safeguards/Sync Notes sections. Remaining gaps are mostly maintenance: the oversized intent-attribution spec, an unspecified drift-detection mechanism, and test-ID mapping for OTel stubs and replace-label partial-success handling.

Priority Work Queue

  • P0: Specify the concrete drift-detection CI check and tracking-issue contract (the intent-attribution Sync Notes escalation norm names no implementing target).
  • P1: Map OTel stubs T-OT-001..011 to named tests; add compliance fixtures for replace-label partial-success (RL-057..059); execute the intent-attribution maintenance split.
  • P2: Reduce SHOULD/MAY ambiguity in the otel spec (~128 normative keyword hits); add cross-spec sync notes.

SPDD Checklist

  • [Analysis] specs/intent-attribution-agent-governance.md (Sync Notes): define where the "consecutive CI runs" counter lives and how the "on-call maintainer" assignee is resolved. Done when the spec names both sources.
  • [Reasons Canvas] specs/intent-attribution-agent-governance.md: add Entities/Operations notes for drift-detection output (keys, first-detected date). Done when each REASONS section has a heading or cross-reference.
  • [Generate] specs/intent-attribution-agent-governance-implementation.md (new): move "Current implementation" and the AuthorizeTool audit per the proposed split. Done when the original links to it and compliance README anchors still resolve.
  • [Generate] specs/otel-observability-spec.md §17.1.1: add a test-name mapping for T-OT-001..T-OT-011 like §17.1.A. Done when every test ID names a repo test or is marked "gap".
  • [Generate] specs/replace-label-compliance/README.md: add fixtures for RL-057/058/059 (partial success yields rejected / SETLABELS_FAILED). Done when the coverage map lists these RL IDs.
  • [Analysis] specs/intent-attribution-compliance/README.md: verify required scenarios cover the 3-run escalation norm and fail-closed Safeguards. Done when each MUST in Safeguards/Sync Notes maps to a scenario.
  • [Reasons Canvas] specs/otel-observability-spec.md Safeguards (§16): add a norm on sampling vs mirror writes. Done when the safeguard states mirror behavior when sampled out.
  • [Sync] specs/replace-label-spec.md §8.7 and specs/safe-output-outcome-evaluation.md §30: add reciprocal notes for RL-049a revalidation and partial-success rules. Done when both docs reference each other for those rules.
  • [Sync] specs/otel-observability-spec.md §17.3: confirm the implementation map and make validate-otel-contract agree on listed paths and fix the "version 0.4.0" wording against the 0.5.0 change log. Done when map, Makefile and version text are consistent.

Per-Spec Findings

specs/intent-attribution-agent-governance.md (~1440 lines)
  • Goals: deterministic, fail-closed intent attribution and governance.
  • Risks: file size makes review risky; the escalation norm (MUST fail CI, open issue) has no named implementing workflow; "Current implementation" can drift from code.
  • Ambiguity: "on-call maintainer" and "consecutive CI runs" lack a defined data source.
  • Canvas gaps: Operations (drift check procedure) and Structure (split layout) are only proposed.
specs/intent-attribution-compliance/README.md
  • Has Formal Model, Structure and Coverage Map. Needs scenarios for sync-warning escalation and stale-cache rejection.
specs/otel-observability-spec.md (~1025 lines)
  • Strong Level 1/2 coverage map. T-OT-001..011 stubs are not mapped to test names. Safeguards are silent on sampling and mirror writes. Heavy normative keyword use. §17.3 says "version 0.4.0" while the change log reaches 0.5.0.
specs/replace-label-compliance/README.md and specs/replace-label-spec.md
  • Spec has RL-049a revalidation and partial-success handling (RL-057..059). Confirm fixtures cover the newer RL IDs. Re-verify the retry policy reference to RATE_LIMIT_RETRY_CONFIG in actions/setup/js/error_recovery.cjs.

Sync Follow-ups

  • After any spec edit, re-run make validate-otel-contract and the relevant compliance fixture tests.
  • Keep replace-label §7 and outcome-evaluation §30 aligned on 404/5xx/429 handling.
  • Update intent-attribution anchors referenced by specs/intent-attribution-compliance/ after the split.
  • Keep the otel §17.3 map aligned with listed file paths.

Context

  • Files reviewed: specs/intent-attribution-agent-governance.md, specs/intent-attribution-compliance/README.md, specs/otel-observability-spec.md, specs/replace-label-compliance/README.md, specs/replace-label-spec.md
  • Rotation: previous last_index 9, now 14 (next run starts at index 15 of 20 files)
  • Run URL: https://github.com/github/gh-aw/actions/runs/37491422459

Generated by 📋 Daily SPDD Spec Planner · copilot · auto · 33.7 AIC · ⌖ 5.68 AIC · ⊞ 7.1K · ◷

  • expires on Oct 9, 2026, 8:01 AM UTC-08:00

Activity

  1. github-actions commented on Oct 9, 2026

    @github-actions
    ContributorAuthor

    This issue was automatically closed because it expired on 2026-10-09T16:01:50.674Z.

    Closed by Workflow

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

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions