You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
forecast-specification.md: Promotion tracking has only 1 of 3 required confirmed runs
SPDD Checklist
[/spdd-generate]effective-tokens-specification.md: Add ## Deprecation Lifecycle section with sunset date/criteria, removal procedure, and backward-compat obligations (≥3 normative requirements).
[/spdd-generate]effective-tokens-specification.md: Update §8 with deprecation-era conformance clause — ET emission in logs/audit is backward-compat only, MUST NOT be extended.
[/spdd-sync]forecast-specification.md: Fill empty Sync follow-up tasks: list in §13 with ≥3 items (AIC/ET migration, promotion-gate tracking, compliance-test gap).
[/spdd-generate]frontmatter-hash-specification.md: Add inputs field to §2 Field Selection table with merge-strategy annotation.
[/spdd-generate]mcp-scripts-specification.md: Elevate §7.6 Norms and Appendix D threat model to top-level ## Safeguards and ## Norms sections with labeled S-* and N-* requirements.
[/spdd-sync]mcp-scripts-specification.md: Add compliance test T-MCP-051 to §10 for secret-scope norms (SN-SCOPE-01–04); link to pkg/ test file in Sync Notes.
[/spdd-generate]fuzzy-schedule-specification.md: Expand §12 Calendar Output Schema with a field-level table (≥6 defined fields: name, type, description, required/optional).
[/spdd-generate]fuzzy-schedule-specification.md: Add R-SAFE-004 norm mandating a parse-time error for unsupported period types (monthly/yearly).
Analysis: ET metric deprecated 2026-06-05; superseded by AIC. Spec still fully present in docs at same depth as active specs — confusing for contributors. No sunset date, no removal criteria, no deprecation-era exception in §8.
REASONS gaps: Requirements (§8 no deprecation clause) · Norms (no N-DEP-* lifecycle norms) · Operations (no sunset ops) · Safeguards (no guard on deprecated-but-active code paths).
Analysis: Defines gh aw forecast Monte Carlo projection command. Only 1/3 production-use confirmations for Draft promotion. Sync follow-up tasks: in §13 is an empty header. AIC declared primary metric in caution box but §3.1 Terminology still leads with ET definition.
REASONS gaps: Norms (none at top level) · Requirements (promotion 1/3) · Structure (§13 tasks empty) · Approach (§3.1 ET-first inconsistent with AIC-primary stance).
frontmatter-hash-specification.md — Draft v1.0.0
Analysis: Well-specified SHA-256 hash with BFS traversal, normalization rules, and 4 test vectors. Missing Terminology section. inputs field appears in ToC Import Metadata but merge strategy is unspecified. v2.0.0 planning section is empty.
REASONS gaps: Entities (no Terminology section) · Requirements (inputs merge strategy missing) · Structure (v2.0.0 planning empty) · Norms (Security Considerations not labeled as Norms).
fuzzy-schedule-specification.md — Draft v1.2.0
Analysis: Most complete spec in batch. Has Safeguards (§8), Sync Notes (§11), Norms (§13). FNV-1a scattering well-specified. Main gaps: §12 Calendar Output Schema lacks field-level table; no error handling for out-of-scope patterns (e.g., monthly).
REASONS gaps: Structure (§12 schema thin) · Safeguards (no R-SAFE-004 for unsupported patterns).
mcp-scripts-specification.md — Draft v1.1.0
Analysis: Inline MCP tools in frontmatter with containerized execution. Security norms (§7.6) and Appendix D threat model are embedded inside §7 and an appendix, not top-level. Compliance test T-MCP-050 (Go sandbox network isolation) listed without CI verification evidence.
REASONS gaps: Safeguards (Appendix D non-normative) · Norms (§7.6 embedded, not top-level) · Structure (no ## Safeguards or ## Norms at ## level).
Sync Follow-ups
effective-tokens: After deprecation-lifecycle section added, verify pkg/cli/audit_report.go emits AIC as primary metric with ET as alias only.
forecast: When second confirmed run documented, verify stable API surface (criterion 2) before promotion-review PR.
frontmatter-hash: After Terminology added, confirm FH-BFS-001–003 test vectors exercised in both Go and JS CI.
mcp-scripts: Locate or create test for T-MCP-050 Go sandbox network isolation; link in Sync Notes Security Marker Map.
fuzzy-schedule: After §12 expanded, add R-SAFE-004 for unsupported period-type error handling.
Summary
SPDD rotation batch 3/26 — reviewed 5 specs:
effective-tokens(Deprecated),forecast(Experimental Draft),frontmatter-hash(Draft),fuzzy-schedule(Draft),mcp-scripts(Draft). Key gaps: missing deprecation-lifecycle norms in ET spec, empty Sync follow-up tasks in Forecast, buried Safeguards in MCP Scripts, and missing Terminology section in Frontmatter Hash.Priority Work Queue
P0 — Structural gaps blocking spec completeness
effective-tokens-specification.md: No deprecation-lifecycle norms or sunset operationsmcp-scripts-specification.md: Safeguards in Appendix D (non-normative); §7.6 Norms buried inside §7P1 — Missing required SPDD sections
forecast-specification.md: No top-level Norms section; §13 Sync follow-up tasks emptyfrontmatter-hash-specification.md: No Terminology section;inputsfield absent from §2 field-selection tableP2 — Quality improvements
fuzzy-schedule-specification.md: §12 Calendar Output Schema needs field-level definitionsforecast-specification.md: Promotion tracking has only 1 of 3 required confirmed runsSPDD Checklist
effective-tokens-specification.md: Add## Deprecation Lifecyclesection with sunset date/criteria, removal procedure, and backward-compat obligations (≥3 normative requirements).effective-tokens-specification.md: Update §8 with deprecation-era conformance clause — ET emission in logs/audit is backward-compat only, MUST NOT be extended.forecast-specification.md: Add top-level## Normssection with ≥3 N-* requirements covering: minimum sample-size floor, projection immutability, caller P10/P50/P90 obligations.forecast-specification.md: Fill emptySync follow-up tasks:list in §13 with ≥3 items (AIC/ET migration, promotion-gate tracking, compliance-test gap).frontmatter-hash-specification.md: Add## Terminologysection defining ≥4 terms: frontmatter, BFS traversal, diamond dependency, canonical JSON.frontmatter-hash-specification.md: Addinputsfield to §2 Field Selection table with merge-strategy annotation.mcp-scripts-specification.md: Elevate §7.6 Norms and Appendix D threat model to top-level## Safeguardsand## Normssections with labeled S-* and N-* requirements.mcp-scripts-specification.md: Add compliance testT-MCP-051to §10 for secret-scope norms (SN-SCOPE-01–04); link topkg/test file in Sync Notes.fuzzy-schedule-specification.md: Expand §12 Calendar Output Schema with a field-level table (≥6 defined fields: name, type, description, required/optional).fuzzy-schedule-specification.md: AddR-SAFE-004norm mandating a parse-time error for unsupported period types (monthly/yearly).Per-Spec Findings
effective-tokens-specification.md — Deprecated v0.4.0
Analysis: ET metric deprecated 2026-06-05; superseded by AIC. Spec still fully present in docs at same depth as active specs — confusing for contributors. No sunset date, no removal criteria, no deprecation-era exception in §8.
REASONS gaps: Requirements (§8 no deprecation clause) · Norms (no N-DEP-* lifecycle norms) · Operations (no sunset ops) · Safeguards (no guard on deprecated-but-active code paths).
forecast-specification.md — Experimental Draft v0.1.0
Analysis: Defines
gh aw forecastMonte Carlo projection command. Only 1/3 production-use confirmations for Draft promotion.Sync follow-up tasks:in §13 is an empty header. AIC declared primary metric in caution box but §3.1 Terminology still leads with ET definition.REASONS gaps: Norms (none at top level) · Requirements (promotion 1/3) · Structure (§13 tasks empty) · Approach (§3.1 ET-first inconsistent with AIC-primary stance).
frontmatter-hash-specification.md — Draft v1.0.0
Analysis: Well-specified SHA-256 hash with BFS traversal, normalization rules, and 4 test vectors. Missing Terminology section.
inputsfield appears in ToC Import Metadata but merge strategy is unspecified. v2.0.0 planning section is empty.REASONS gaps: Entities (no Terminology section) · Requirements (
inputsmerge strategy missing) · Structure (v2.0.0 planning empty) · Norms (Security Considerations not labeled as Norms).fuzzy-schedule-specification.md — Draft v1.2.0
Analysis: Most complete spec in batch. Has Safeguards (§8), Sync Notes (§11), Norms (§13). FNV-1a scattering well-specified. Main gaps: §12 Calendar Output Schema lacks field-level table; no error handling for out-of-scope patterns (e.g., monthly).
REASONS gaps: Structure (§12 schema thin) · Safeguards (no R-SAFE-004 for unsupported patterns).
mcp-scripts-specification.md — Draft v1.1.0
Analysis: Inline MCP tools in frontmatter with containerized execution. Security norms (§7.6) and Appendix D threat model are embedded inside §7 and an appendix, not top-level. Compliance test T-MCP-050 (Go sandbox network isolation) listed without CI verification evidence.
REASONS gaps: Safeguards (Appendix D non-normative) · Norms (§7.6 embedded, not top-level) · Structure (no
## Safeguardsor## Normsat##level).Sync Follow-ups
pkg/cli/audit_report.goemits AIC as primary metric with ET as alias only.R-SAFE-004for unsupported period-type error handling.Context
Files reviewed (rotation batch 3/26):
docs/src/content/docs/specs/effective-tokens-specification.md(Deprecated, v0.4.0)docs/src/content/docs/specs/forecast-specification.md(Experimental Draft, v0.1.0)docs/src/content/docs/specs/frontmatter-hash-specification.md(Draft, v1.0.0)docs/src/content/docs/specs/fuzzy-schedule-specification.md(Draft, v1.2.0)docs/src/content/docs/specs/mcp-scripts-specification.md(Draft, v1.1.0)Rotation: index 3/26 — next run starts at
model-alias-specification.mdReferences: §28533031607