Ting/Jostoph
Watch
2
0
Fork
You've already forked Jostoph
 2
Code Issues 57 Pull requests Projects Releases Packages Wiki Activity Actions
Page: grooming-log
Pages
Home OpenSpec 103 forge identity lifecycle audit OpenSpec documentation-log grooming-log incident-postmortems
7 grooming-log
~larandar edited this page 2026-08-29 22:08:01 +02:00
Table of contents

Grooming log

This page records evidence discovered during issue and pull-request grooming so later runs can reuse prior research.

Rules

  • Record authoritative rulings, supersessions, contradictions, and cross-repository connections.
  • Link the source and distinguish owner rulings, accepted governance, implementation evidence, wiki statements, and agent inference.
  • Prefer later authoritative evidence; implementation may obsolete a question but does not create unrelated policy.
  • Update an existing entry when its status changes. Do not treat this page itself as authority.
  • Before applying Status/Need More Info, search this log and the linked sources.

Entries

Date Subject Finding Authority
2026-08-14 jostoph-rs branch policy Issue #14 records that jostoph-rs is main-only by design. Owner ruling
2026-08-14 Existing fastlane branches PR #80 says a repository whose forge carries a fastlane bookmark should use fastlane rather than main. It does not require every repository to create one. Owner-authored accepted governance
2026-08-16 organisation label conformance Ting/Ting#25 ratifies and completes the one-time organisation-label cutover. Issue #87 owns durable idempotent reconciliation; issue #25 must declare the canonical prefixed Status states. Owner ruling and implemented migration
2026-08-16 typed delivery hierarchy Ruling 6883 defined the typed Campaign → Epic → Session → Deliverable DAG (conformance epoch 2026-08-16 07:20:29 UTC, closed-history waiver). Superseded in part by the freeholder clarification: Session is now optional grooming (Epic → Deliverable is the default; Epic → Session → Deliverable only when positively declared). Ting/Ting#28 (rewritten 2026-08-16T12:05Z) now splits its 64 stable IDs into 47 historical/routine grooming debt, 11 live grooming targets (ordinary groomer/author action, not a freeholder call), and 6 residual freeholder rulings. Only the residual 6 carry Status/Need More Info. Owner ruling by proxy; decision ledger
2026-08-29 Session sizing The freeholder clarified in the Forge identity lifecycle grooming thread that a Session is a PR-review constraint: “does this PR fit as 1?” It is not sized by a fixed number of inner units. #103 is therefore assessed as one coherent review across its recursively groomed leaves. Owner ruling