Conversation
…klog/README.md schema Sister-row schema fix sweep flagged in PR #85 commit message. All three 2026-04-28-authored backlog rows had the same off-schema shape that codex/copilot caught on B-0069: - status: backlog → status: open (the documented enum is open|closed|superseded-by-B-NNNN|deferred per tools/backlog/README.md) - dropped non-schema fields slug, maintainer, ownership (and B-0071's one-off opened/class/trigger) - added required last_updated: 2026-04-28 - added optional ask, effort, tags fields per the schema Per the schema fields table in tools/backlog/README.md: - id (req), priority (req), status (req, enum), title (req), created (req), last_updated (req) - tier, effort, ask, composes_with, tags (optional) The ask field carries origin-attribution (Otto-293 mutual-alignment language: "ask" not "directive"), which composes with Otto-357 (no directives framing). All three rows correctly attribute the ask to the maintainer's 2026-04-28 input or the codex review on PR #17. Why this matters: the B-NNNN rows are the durable substrate for factory-discipline work. Schema drift compounds — every fresh-session read of these rows would hit the divergence and either (a) propagate the off-schema shape to new rows or (b) waste cycles reconciling. The schema source-of-truth lives in tools/backlog/README.md and any strict-lint Phase-2+ tooling will use that as the canonical contract. Otto-275-FOREVER application: I authored the rows from a stale mental template instead of re-reading tools/backlog/README.md for each. Same schema-drift class would have repeated on the next batch authored without this fix landing first. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
There was a problem hiding this comment.
Pull request overview
Aligns three P2 backlog row files to the tools/backlog/README.md frontmatter schema (fixing the same schema drift previously corrected for B-0069).
Changes:
- Updates frontmatter to the supported
statusenum (open) and removes off-schema keys. - Adds required/expected schema fields (
last_updated) and standard optional fields (ask,effort,tags, pluscreatedwhere needed). - Normalizes B-0071 from the older
opened/class/triggershape to the current schema shape.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| docs/backlog/P2/B-0068-local-ai-trajectory-forge-ollama-direct-integration-aaron-2026-04-28.md | Replaces off-schema frontmatter with schema-aligned fields (status/open, ask, effort, last_updated, tags). |
| docs/backlog/P2/B-0070-orphan-role-ref-detector-lint-aaron-2026-04-28.md | Replaces slug/maintainer/ownership/status: backlog with schema fields and adds last_updated + standard metadata. |
| docs/backlog/P2/B-0071-rename-otto-275-forever-out-of-live-lock-class-codex-pr-17-2026-04-28.md | Drops opened/class/trigger and adds schema-aligned created/ask/effort/last_updated/tags. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Schema-drift fix for 3 sister rows authored 2026-04-28 in parallel.
All shared the same off-schema shape that codex/copilot caught on
B-0069 in PR #85 (just merged).
What
Schema source-of-truth:
tools/backlog/README.md.Why
Per Otto-275-FOREVER (knowing-rule != applying-rule): I authored the
rows from a stale mental template instead of re-reading the schema
for each. Same drift would have compounded on the next batch unless
fixed.
The
askfield carries origin-attribution per Otto-293 mutual-alignmentlanguage ("ask" not "directive"), composing with Otto-357 (no
directives framing).
Verification
Each file's frontmatter now matches the field table in
tools/backlog/README.mdexactly.🤖 Generated with Claude Code