[spdd] Daily spec work plan - 2026-05-26

[github-actions]

Summary

SPDD review of 5 specification documents (rotation index 0–4, first run — cache initialized). All specs are Draft status and well-structured. The primary gaps are:

• Forecast spec has two open issues (#31984, #31985) needing implementation follow-through
• Frontmatter Hash spec has a field-selection section marked as "future-state design intent only" — migration milestone is undefined
• MCP Scripts idempotency safeguards are described but lack concrete normative requirements
• Fuzzy Schedule Level 3 compliance (timezone, bi-weekly, tri-weekly) has no test coverage
• Effective Tokens model multiplier registry has no automated staleness check

---

Priority Work Queue

Priority	Task	Spec	SPDD Stage
P0	Add implementation assertion for λ consistency (forecast §7, open issue #31984)	forecast-specification.md	/spdd-sync
P0	Define migration milestone for field-selection in hash spec (§2 is "future-state only")	frontmatter-hash-specification.md	/spdd-generate
P1	Review Poisson branch threshold change impact (open issue #31985)	forecast-specification.md	/spdd-sync
P1	Add normative idempotency requirements to MCP Scripts §5 (currently "caller responsibility")	mcp-scripts-specification.md	/spdd-generate
P1	Add Level 3 compliance test cases for fuzzy schedule (timezone, bi-weekly, tri-weekly)	fuzzy-schedule-specification.md	/spdd-generate
P2	Add registry staleness check for model multipliers (R-REG-007 has no automation)	effective-tokens-specification.md	/spdd-sync

---

SPDD Checklist

• [/spdd-sync] In pkg/cli/forecast.go or forecast_command.go, add an assertion/test verifying verbose diagnostics and --json output use the same λ value — closes issue #31984 (forecast-specification.md §13)
• [/spdd-sync] Review Poisson branch threshold in pkg/cli/forecast_montecarlo.go and add a sync comment referencing Appendix B — closes issue #31985 (forecast-specification.md §7)
• [/spdd-generate] In docs/src/content/docs/reference/frontmatter-hash-specification.md §2, replace the "future-state design intent only" note with either a concrete migration milestone or a formal deferral note with rationale
• [/spdd-generate] In docs/src/content/docs/reference/mcp-scripts-specification.md §5, elevate the idempotency caller-responsibility note to a normative SHOULD requirement with an example
• [/spdd-generate] Add Level 3 compliance test IDs T-FZ-L3-001 through T-FZ-L3-005 (timezone conversion, bi-weekly, tri-weekly) to docs/src/content/docs/reference/fuzzy-schedule-specification.md §10 compliance table
• [/spdd-sync] Add a CI step or make target that validates pkg/cli/data/model_multipliers.json has no placeholder/null multipliers (aligns with R-REG-007 in effective-tokens-specification.md)
• [/spdd-analysis] Audit docs/src/content/docs/reference/fuzzy-schedule-specification.md §12 (Calendar Output Schema) — the section may be a stub; confirm or complete the JSON schema definition
• [/spdd-reasons-canvas] Add a Norms subsection to docs/src/content/docs/reference/mcp-scripts-specification.md §7 Security Model — currently lacks explicit secret rotation and secret scope norms

---

Per-Spec Findings

effective-tokens-specification.md (v0.2.0 Draft)

Analysis: Well-specified. Formula, aggregation, execution graph, and compliance levels are all present. Safeguards §8.5 cover overflow and unbounded accumulation.

REASONS gaps:

• Norms: The model multiplier registry MUST requirement (R-REG-007) has no automated enforcement — could silently drift
• Safeguards: Determinism safeguards are described but there is no spec-level test for non-determinism under concurrent aggregation

Generate tasks:

• Add registry validation CI step referencing R-REG-007

Sync tasks:

• Add a sync note entry for pkg/cli/data/model_multipliers.json validation script

forecast-specification.md (v0.1.0 Experimental Draft)

Analysis: Experimental draft with strong algorithm documentation. Two open tracking issues (#31984, #31985) indicate known gaps from the last SPDD review.

REASONS gaps:

• Operations: §7 Monte Carlo engine lacks a normative requirement that verbose and JSON outputs share the same computed λ (deferred to issue #31984)
• Safeguards: §10.7 safeguards are well-covered; residual risk note is appropriate

Generate tasks:

• Test assertion for λ consistency in pkg/cli/forecast_montecarlo_test.go

Sync tasks:

• Resolve #31984 and #31985; update §13 Sync Notes to mark them resolved

frontmatter-hash-specification.md (v1.0.0 Draft)

Analysis: Concise and well-focused. Text-based approach is declared authoritative (2026-05-08). However, §2 field-selection is explicitly called "future-state design intent only" — no migration milestone is defined.

REASONS gaps:

• Structure: §2 field-selection describes fields that should be included but the resolution log defers them indefinitely
• Norms: No normative statement on when the field-selection migration milestone should be scheduled

Generate tasks:

• Annotate §2 with a formal deferral note or target milestone

Sync tasks:

• After BFS diamond-import changes, re-run TestFrontmatterHash cross-language tests

fuzzy-schedule-specification.md (v1.2.0 Draft)

Analysis: Thorough specification with ABNF grammar, scattering algorithm, and safeguards. Level 3 compliance (timezone, interval, bi/tri-weekly) is defined but compliance test IDs are missing from §10.

REASONS gaps:

• Operations: §12 Calendar Output Schema section — completeness unclear without reading full file
• Safeguards: R-SAFE-003 (empty hash input) is normative but the corresponding test ID T-SAFE-003 is not listed in §10

Generate tasks:

• Add Level 3 test IDs to §10 compliance table
• Verify §12 calendar schema completeness

Sync tasks:

• After any scattering algorithm change, verify test T-SCAT-* IDs in implementation test file

mcp-scripts-specification.md (v1.1.0 Draft)

Analysis: Well-structured with Appendix D safeguards. §5 Tool Execution notes idempotency as "caller responsibility" — this is informative, not normative.

REASONS gaps:

• Norms: No normative secret rotation or scope constraint in §7 Security Model
• Safeguards: Idempotency is mentioned but not required (SHOULD/MUST)
• Entities: MCP Gateway Specification is referenced but not linked in the document

Generate tasks:

• Add SHOULD-level idempotency requirement to §5
• Add secret norms subsection to §7

Sync tasks:

• After adding new language support, update §6 Language Support and Appendix D threat model

---

Sync Follow-ups

• forecast-specification.md §13: Mark issues #31984 and #31985 resolved once implementation assertions are added
• frontmatter-hash-specification.md §2: Schedule field-selection migration milestone in a future SPDD cycle
• mcp-scripts-specification.md Appendix D: Re-review threat model when new runtime languages (Python, Go) reach full GA support
• effective-tokens-specification.md Model Registry: Add to CI pipeline so R-REG-007 is machine-verified

---

Context

• Files reviewed (rotation index 0–4, first run):
  • docs/src/content/docs/reference/effective-tokens-specification.md
  • docs/src/content/docs/reference/forecast-specification.md
  • docs/src/content/docs/reference/frontmatter-hash-specification.md
  • docs/src/content/docs/reference/fuzzy-schedule-specification.md
  • docs/src/content/docs/reference/mcp-scripts-specification.md
• Next rotation will continue from index 5 (model-alias-specification.md)
• Workflow run: §26462785179
• Note: Cache-memory write was blocked (read-only mount); rotation state was not persisted — next run will restart from index 0

Generated by 📋 Daily SPDD Spec Planner · sonnet46 1.7M · ◷

• expires on May 29, 2026, 5:05 PM UTC