Summary
This run reviewed 5 specification documents (indices 0–4 of 20): effective-tokens-specification, forecast-specification, frontmatter-hash-specification, fuzzy-schedule-specification, and mcp-scripts-specification. All are in Draft status with varying completeness. Key gaps: (1) forecast has explicit sync follow-up tasks still outstanding; (2) mcp-scripts has an acknowledged but unfiled implementation issue for per-string 10KB enforcement; (3) frontmatter-hash has a deferred v2.0.0 field-selection alignment with no scheduled milestone; (4) effective-tokens Safeguards section (§8.5) is thin; (5) fuzzy-schedule lacks explicit Sync Notes.
Rotation: files 0–4 of 20. Next run starts at index 5.
Run: §26525689639
Priority Work Queue
| Priority | Count | Theme |
|---|---|---|
| P0 | 2 | Outstanding TODOs explicitly flagged in specs |
| P1 | 5 | Missing REASONS Canvas sections across specs |
| P2 | 4 | Norms/safeguard tightening and sync alignment |
SPDD Checklist
P0 — Outstanding flagged gaps (act now)
- [/spdd-generate]
docs/src/content/docs/reference/mcp-scripts-specification.md§4.7 — File the follow-up implementation issue for per-string 10KB env-var size limit enforcement; add a normative MUST requirement and link the issue in the spec. Done when: §4.7 contains a normative MUST sentence and an issue reference. - [/spdd-sync]
docs/src/content/docs/reference/forecast-specification.mdAppendix sync follow-ups — Execute the sync follow-up tasks listed under "Sync follow-up tasks"; verify each maps to a real file change or closes as already-done. Done when: All listed sync follow-ups are addressed or tracked as issues.
P1 — Missing REASONS Canvas sections
- [/spdd-reasons-canvas]
docs/src/content/docs/reference/effective-tokens-specification.md— Add a## Sync Notessection mapping §4–§8 to implementation files (pkg/cli/effective_tokens.go,pkg/cli/forecast_montecarlo.go). Done when: Section exists with a file→spec-section table. - [/spdd-reasons-canvas]
docs/src/content/docs/reference/fuzzy-schedule-specification.md— Add a## Sync Notessection mapping grammar and error-norms sections to implementation files. Done when: Section exists with table linking spec sections to Go parser files. - [/spdd-generate]
docs/src/content/docs/reference/effective-tokens-specification.md§8.5 — Expand Safeguards: add at least two named safeguards (S-2: Negative/zero multiplier rejection; S-3: Graph cycle detection) with Threat/Mitigation/Residual-risk format. Done when: §8.5 contains ≥3 named safeguards in standard format. - [/spdd-analysis]
docs/src/content/docs/reference/frontmatter-hash-specification.md— Schedule or formally defer the v2.0.0 field-selection alignment; add a dated decision entry to §Versioning → Future Versions with clear criteria for when the migration will be revisited. Done when: A decision entry with acceptance criteria exists. - [/spdd-reasons-canvas]
docs/src/content/docs/reference/mcp-scripts-specification.md— Verify §3 Architecture has an explicit Operations ordering subsection cross-linked to §5.1.1; make ordering normative. Done when: Cross-link exists and ordering is normative.
P2 — Norms, safeguards, and tightening
- [/spdd-analysis]
docs/src/content/docs/reference/forecast-specification.md— Define concrete promotion criteria (e.g., ≥3 successful production uses, stable API) that graduate it from Experimental Draft to Draft. Done when: §Status lists named promotion criteria. - [/spdd-generate]
docs/src/content/docs/reference/fuzzy-schedule-specification.md— Add norms for duplicate/conflicting schedule expressions; define error code and rejection behavior. Done when: Error table contains entry for duplicate-expression conflict. - [/spdd-sync]
docs/src/content/docs/reference/frontmatter-hash-specification.md— Wire Appendix A cross-language test vectors into CI against both Go and JS implementations. Done when: CI job runsFH-TV-001throughFH-TV-NEG-001and fails on divergence. - [/spdd-reasons-canvas]
docs/src/content/docs/reference/effective-tokens-specification.md§7.1 — Add a MUST-reject norm for negative ET values in exported OTel spans. Done when: §7.1 contains normative rejection rule for negative values.
Per-Spec Findings
effective-tokens-specification.md (v0.2.0, Draft)REASONS Canvas
| Section | Status | Gap |
|---|---|---|
| Requirements | ✅ Good | §8 has 5 implementation requirements |
| Entities | ✅ Good | §3 Terminology well defined |
| Approach | ✅ Good | §4–§5 accounting model clear |
| Structure | ⚠️ Weak | No Sync Notes section |
| Operations | ✅ Good | §6 execution graph defined |
| Norms | ⚠️ Weak | §7.1 OTel missing negative-value rejection norm |
| Safeguards | ⚠️ Weak | §8.5 has only 1 safeguard (overflow capping) |
REASONS Canvas
| Section | Status | Gap |
|---|---|---|
| Requirements | ✅ Good | §4 command interface well specified |
| Entities | ✅ Good | §3 terminology thorough |
| Approach | ✅ Good | §6–§8 Monte Carlo algorithm detailed |
| Structure | ⚠️ Weak | Sync follow-up tasks listed inline, not tracked |
| Operations | ✅ Good | §5 workflow discovery ordered |
| Norms | ⚠️ Weak | No promotion criteria for experimental status |
| Safeguards | ✅ Good | §10.7 Safeguards present |
REASONS Canvas
| Section | Status | Gap |
|---|---|---|
| Requirements | ✅ Good | Conformance well defined |
| Entities | ✅ Good | Algorithm steps clear |
| Approach | ✅ Good | Text-based approach documented |
| Structure | ✅ Good | Sync Notes section exists |
| Operations | ✅ Good | Hash Algorithm steps ordered |
| Norms | ⚠️ Weak | v2.0.0 migration lacks scheduled criteria |
| Safeguards | ✅ Good | S-1 through S-6 defined |
REASONS Canvas
| Section | Status | Gap |
|---|---|---|
| Requirements | ✅ Good | Error table with codes defined |
| Entities | ✅ Good | Grammar BNF provided |
| Approach | ✅ Good | §3–§5 well detailed |
| Structure | ❌ Missing | No Sync Notes section |
| Operations | ✅ Good | §3.1 grammar steps ordered |
| Norms | ⚠️ Weak | No conflict/duplicate expression error |
| Safeguards | ⚠️ Weak | No explicit safeguards section |
REASONS Canvas
| Section | Status | Gap |
|---|---|---|
| Requirements | ✅ Good | §4.7 Validation Requirements present |
| Entities | ✅ Good | §3 Architecture thorough |
| Approach | ✅ Good | §5 execution model well specified |
| Structure | ✅ Good | Security Marker Sync Map exists |
| Operations | ⚠️ Weak | §3 ops order not cross-linked to §5.1.1 |
| Norms | ⚠️ Weak | 10KB per-string limit is SHOULD not MUST |
| Safeguards | ✅ Good | Appendix D Safeguards present |
Sync Follow-ups
effective-tokens-specification.md→ add Sync Notes mapping topkg/cli/effective_tokens.gofuzzy-schedule-specification.md→ add Sync Notes mapping to relevant parser filesfrontmatter-hash-specification.md→ wire Appendix A test vectors into CImcp-scripts-specification.md→ file implementation issue for 10KB env-var enforcement
Context
| Field | Value |
|---|---|
| Files reviewed | 5 (indices 0–4 of 20) |
| Next rotation index | 5 |
| Run | §26525689639 |
| Date | 2026-05-27 |
Generated by 📋 Daily SPDD Spec Planner · sonnet46 1.6M · ◷
- expires on May 30, 2026, 5:01 PM UTC