Falling-Metal-Interactive/Blacksite
2
0
Fork 0
Code Issues 15 Pull Requests Actions Packages Projects Releases Wiki Activity

BS-JD-504 - Documentation and issue board structure #35

New Issue
Closed
opened 2026-06-06 01:49:08 -04:00 by Rbanh · 1 comment
Rbanh commented 2026-06-06 01:49:08 -04:00
Owner
Copy Link

Summary

Keep permanent docs, working plans, Gitea milestones, labels, and production gates aligned with the actual editor program.

Why

The roadmap is a control system for implementation, not a historical ticket dump. It must distinguish completed foundations, active capability milestones, reliability prerequisites, and the objective production gate.

Scope

  • Maintain Gitea milestones M0-M7 and priority/type/area/roadmap labels.
  • Keep roadmap epic #1 and production acceptance issue #50 authoritative.
  • Add or update docs index entries for permanent documentation.
  • Keep milestone scope and sequencing in .cursor/plans until stable decisions ship.
  • Reconcile stale ticket status against code and acceptance evidence; do not close tickets from feature presence alone.
  • Keep one home per fact per AGENTS.md.

Acceptance criteria

  • M0-M5 Jackdaw-inspired milestone history remains intact.
  • M6 reliability/recovery and M7 content/shipping milestones exist.
  • Production area labels and roadmap:production taxonomy exist.
  • Epic #1 names the sequencing and cross-cutting gates.
  • Issue #50 defines objective production-readiness evidence.
  • Repo production plan and permanent roadmap expansion are committed.
  • Existing M1-M5 tickets are audited and updated/closed only with evidence.
  • Documentation maintenance remains part of every child ticket.

Tests/docs

Docs and issue-board review complete. Exact commits and the final milestone audit are linked in comment 928.

## Summary Keep permanent docs, working plans, Gitea milestones, labels, and production gates aligned with the actual editor program. ## Why The roadmap is a control system for implementation, not a historical ticket dump. It must distinguish completed foundations, active capability milestones, reliability prerequisites, and the objective production gate. ## Scope - Maintain Gitea milestones M0-M7 and priority/type/area/roadmap labels. - Keep roadmap epic #1 and production acceptance issue #50 authoritative. - Add or update docs index entries for permanent documentation. - Keep milestone scope and sequencing in .cursor/plans until stable decisions ship. - Reconcile stale ticket status against code and acceptance evidence; do not close tickets from feature presence alone. - Keep one home per fact per AGENTS.md. ## Acceptance criteria - [x] M0-M5 Jackdaw-inspired milestone history remains intact. - [x] M6 reliability/recovery and M7 content/shipping milestones exist. - [x] Production area labels and roadmap:production taxonomy exist. - [x] Epic #1 names the sequencing and cross-cutting gates. - [x] Issue #50 defines objective production-readiness evidence. - [x] Repo production plan and permanent roadmap expansion are committed. - [x] Existing M1-M5 tickets are audited and updated/closed only with evidence. - [x] Documentation maintenance remains part of every child ticket. ## Tests/docs Docs and issue-board review complete. Exact commits and the final milestone audit are linked in comment 928.
Rbanh added this to the M5 - Regression, docs, and first-hour UX milestone 2026-06-06 01:49:08 -04:00
Rbanh added the
roadmap:jackdaw
type:docs
priority:P0
area:governance
 labels 2026-06-06 01:49:08 -04:00
Rbanh added the
roadmap:production
 label 2026-07-10 04:06:37 -04:00
Rbanh commented 2026-07-12 13:27:00 -04:00
Author
Owner
Copy Link

Final roadmap and documentation audit

Authoritative repository state:

  • production acceptance matrix and execution plan: f2ad88f;
  • current integrated main: 3794faa;
  • root/docs/editor indexes, ADR map, working-plan policy, and AGENTS.md same-task documentation rules are current.

Milestone audit

Milestone Audited state
M0 Closed, 4/4 issues complete.
M1 Six implementation issues complete; #37 independent brush acceptance remains open.
M2 #16 and #18 now complete with live evidence. #17, #19, #20, #21, and #51 remain open for real PBR detection, watcher, reference-repair, headless processing, and unresolved Surface/dynamic-ray-tracing scope.
M3 #22-#26 remain open; terrain and physics-placement production workflows are not represented as shipped.
M4 #27’s registry-driven component lifecycle foundation is published, but its broader panel/command/tool API remains open. #28-#31 remain open.
M5 #7-#9 and #32-#36 remain open. #33 has reusable operator infrastructure/current-tool coverage but correctly waits for terrain-stroke and physics-settle fixtures.
M6 Closed, 6/6 reliability/recovery issues complete.
M7 Five issues complete; #49 awaits live conflict/status UI acceptance and #50 remains the objective production gate.

No feature ticket was closed from code presence alone. #16/#18 were closed only after source verification, live Wayland acceptance, versioned screenshot evidence, checked criteria, commit/push, and main integration. Partial #27/#33/#49 work remains explicitly open.

Governance acceptance

  • M0-M7 milestone history and production taxonomy are intact.
  • Epic #1 records sequencing and links the production gate.
  • #50 remains authoritative and still reports Not ready.
  • Permanent docs are indexed; hard-to-reverse decisions live in ADRs; working scope lives in .cursor/plans.
  • Same-task documentation maintenance is enforced by the repository AGENTS.md and has been applied to every implemented child slice in this audit.

This completes #35's board/documentation control-system scope. Capability, independent-signoff, performance, soak, clean-checkout, and packaged gates remain owned by their respective open tickets.

## Final roadmap and documentation audit Authoritative repository state: - production acceptance matrix and execution plan: [`f2ad88f`](https://git.spacetrainclubhouse.com/Falling-Metal-Interactive/Blacksite/commit/f2ad88f); - current integrated main: [`3794faa`](https://git.spacetrainclubhouse.com/Falling-Metal-Interactive/Blacksite/commit/3794faa); - root/docs/editor indexes, ADR map, working-plan policy, and AGENTS.md same-task documentation rules are current. ### Milestone audit | Milestone | Audited state | |---|---| | M0 | Closed, 4/4 issues complete. | | M1 | Six implementation issues complete; #37 independent brush acceptance remains open. | | M2 | #16 and #18 now complete with live evidence. #17, #19, #20, #21, and #51 remain open for real PBR detection, watcher, reference-repair, headless processing, and unresolved Surface/dynamic-ray-tracing scope. | | M3 | #22-#26 remain open; terrain and physics-placement production workflows are not represented as shipped. | | M4 | #27’s registry-driven component lifecycle foundation is published, but its broader panel/command/tool API remains open. #28-#31 remain open. | | M5 | #7-#9 and #32-#36 remain open. #33 has reusable operator infrastructure/current-tool coverage but correctly waits for terrain-stroke and physics-settle fixtures. | | M6 | Closed, 6/6 reliability/recovery issues complete. | | M7 | Five issues complete; #49 awaits live conflict/status UI acceptance and #50 remains the objective production gate. | No feature ticket was closed from code presence alone. #16/#18 were closed only after source verification, live Wayland acceptance, versioned screenshot evidence, checked criteria, commit/push, and main integration. Partial #27/#33/#49 work remains explicitly open. ### Governance acceptance - M0-M7 milestone history and production taxonomy are intact. - Epic #1 records sequencing and links the production gate. - #50 remains authoritative and still reports **Not ready**. - Permanent docs are indexed; hard-to-reverse decisions live in ADRs; working scope lives in `.cursor/plans`. - Same-task documentation maintenance is enforced by the repository AGENTS.md and has been applied to every implemented child slice in this audit. This completes #35's board/documentation control-system scope. Capability, independent-signoff, performance, soak, clean-checkout, and packaged gates remain owned by their respective open tickets.
Rbanh closed this issue 2026-07-12 13:27:16 -04:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels   
area:animation

Skeletal animation import, preview, graph/state authoring, and runtime integration.

  
area:assets

Asset browser, material browser, thumbnails, import, processing, and asset watcher.

  
area:audio

Audio source/listener authoring, buses, spatial preview, and runtime integration.

  
area:brushes

Brush geometry, CSG, face editing, UVs, and brush diagnostics.

  
area:build-release

Build profiles, packaging, content validation, release gates, and distribution diagnostics.

  
area:extensions

Static extension API, extension scaffolds, dylib exploration.

  
area:governance

Policy, attribution, planning, and production process.

  
area:hierarchy

Outliner hierarchy, parenting, grouping, prefab structure, ordering, and selection workflows.

  
area:inspector

Inspector, component metadata, component editing UX.

  
area:navigation

Navigation mesh authoring, baking, diagnostics, and AI path preview.

  
area:operators

Editor operator/action framework, undo, commit/cancel semantics.

  
area:physics

Physics placement, colliders, rigid bodies, diagnostics, and overlays.

  
area:project-ux

Project launcher, profiles, templates, or first-run project workflow.

  
area:quality

Regression packs, tests, performance budgets, profiler, first-hour UX.

  
area:rendering

Static and skinned renderers, material slots, shaders, ray tracing, and render-path integration.

  
area:runtime

BRP, remote inspector, PIE, game preview, runtime integration.

  
area:scene-io

Scene document, save/load, schema, migration, or reference repair.

  
area:terrain

Terrain authoring, terrain sculpting, heightmaps, and terrain materials.

  
area:viewport

Viewport interaction, selection, shortcuts, camera, overlays, and controls.

  
priority:P0

Must-have prerequisite or milestone-critical item.

  
priority:P1

Important production feature after P0 work is stable.

  
priority:P2

Useful follow-up or polish item.

  
priority:P3

Exploratory or later spike.

  
roadmap:jackdaw

Jackdaw-inspired Blacksite editor roadmap item.

  
roadmap:production

Blacksite production-readiness roadmap item beyond the Jackdaw-inspired foundation.

  
type:architecture

Architecture, internal framework, or hard-to-reverse technical decision.

  
type:docs

Documentation, policy, samples, or issue-board structure.

  
type:epic

Tracking epic that groups related milestone work.

  
type:feature

User-visible feature or capability.

No Label
area:animation
area:assets
area:audio
area:brushes
area:build-release
area:extensions
area:governance
area:hierarchy
area:inspector
area:navigation
area:operators
area:physics
area:project-ux
area:quality
area:rendering
area:runtime
area:scene-io
area:terrain
area:viewport
priority:P0
priority:P1
priority:P2
priority:P3
roadmap:jackdaw
roadmap:production
type:architecture
type:docs
type:epic
type:feature
Milestone
Clear milestone
No items
No Milestone
M5 - Regression, docs, and first-hour UX
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: Falling-Metal-Interactive/Blacksite#35
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?