Ting/CurryComb
Watch
2
0
Fork
You've already forked CurryComb
 0
Code Issues 47 Pull requests Projects Releases Packages Wiki Activity Actions

Session: record council authority and resolved Session projection #47

New issue
Open
opened 2026-09-02 15:05:30 +00:00 by codexo · 1 comment
codexo commented 2026-09-02 15:05:30 +00:00
Contributor
Copy link

Proposal

Why

Close the authority ambiguity before CurryComb grows from a design skeleton into an executor-facing compiler.

Scope

Owns one Ting/CurryComb documentation review surface. It does not implement the unresolved shared schema and does not ratify ADR-0003.

Design

Councils decompose bounded tensions; the Freeholder ratifies durable normative change; CurryComb reconciles evidence and mechanically materialises the ratified Session projection.

Specification Delta

  • OpenSpec root: ting-wiki
  • OpenSpec change: agentic-software-delivery-loop
  • OpenSpec commit: pending Store publication
  • Requirements/scenarios: GD-3, GD-4, CG-3, CG-4, SE-1 through SE-3 and the scenarios in #46

Tasks

  • Parent Epic: #48
  • #46 — authority boundary and projection semantics

Intended delivery

  • Repository: Ting/CurryComb
  • Branch: tango/46-council-session-projection
  • PR: #49
  • Coordination asset: ting-agentic-delivery@9968d51c42b34591a08d2f165ed571801b42797f

Closure

  • One repository-local PR covers #46.
  • ADR status remains honest.
  • Evidence matrix records the unresolved implementation gates.
  • Independent review verdict is recorded.

Readiness gate: the shared Store commit is pending wiki Git publication. Keep this issue in Status/Need Grooming until an immutable commit is recorded and strict OpenSpec validation passes.

Authored through the Ting Forge connector as codexo; independent review and Freeholder ratification remain required.

## Proposal ### Why Close the authority ambiguity before CurryComb grows from a design skeleton into an executor-facing compiler. ### Scope Owns one `Ting/CurryComb` documentation review surface. It does not implement the unresolved shared schema and does not ratify ADR-0003. ## Design Councils decompose bounded tensions; the Freeholder ratifies durable normative change; CurryComb reconciles evidence and mechanically materialises the ratified Session projection. ## Specification Delta - OpenSpec root: `ting-wiki` - OpenSpec change: `agentic-software-delivery-loop` - OpenSpec commit: pending Store publication - Requirements/scenarios: GD-3, GD-4, CG-3, CG-4, SE-1 through SE-3 and the scenarios in #46 ## Tasks - Parent Epic: #48 - [ ] #46 — authority boundary and projection semantics ## Intended delivery - Repository: `Ting/CurryComb` - Branch: `tango/46-council-session-projection` - PR: https://jo.et0.pw/Ting/CurryComb/pulls/49 - Coordination asset: `ting-agentic-delivery@9968d51c42b34591a08d2f165ed571801b42797f` ## Closure - [ ] One repository-local PR covers #46. - [ ] ADR status remains honest. - [ ] Evidence matrix records the unresolved implementation gates. - [ ] Independent review verdict is recorded. **Readiness gate:** the shared Store commit is pending wiki Git publication. Keep this issue in Status/Need Grooming until an immutable commit is recorded and strict OpenSpec validation passes. _Authored through the Ting Forge connector as `codexo`; independent review and Freeholder ratification remain required._
larandar commented 2026-09-20 03:54:45 +00:00
Owner
Copy link

Readiness gate: the Ting/contracts store commit plus the OD-6 ruling. The retired ting-wiki/pending-store gate is obsolete per the grooming-log retirement entry dated 2026-09-04.
Delivery: CurryComb PR#49 already merged; it was documentation only.
Audit: G7, grooming audit 2026-09-19/20.

<!-- larandar:groom:v1 --> **Readiness gate:** the `Ting/contracts` store commit plus the OD-6 ruling. The retired `ting-wiki`/pending-store gate is obsolete per the grooming-log retirement entry dated 2026-09-04. **Delivery:** CurryComb PR#49 already merged; it was documentation only. **Audit:** G7, grooming audit 2026-09-19/20.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
fastlane
No results found.
Labels
Clear labels
  
Compat/Breaking
Breaking change that won't be backward compatible

  
Kind/Bug
Something is not working

  
Kind/Documentation
Documentation changes

  
Kind/Enhancement
Improve existing functionality

  
Kind/Feature
New functionality

  
Kind/Security
This is security issue

  
Kind/Testing
Issue or pull request related to testing

  
Meta/Campaign
Campaign grouping node; dependencies name its direct Epics

  
Meta/Epic
Epic grouping node; dependencies name its direct Sessions

  
Meta/Session
Session delivery bundle; dependencies name its direct leaf issues

  
Priority/Critical
The priority is critical

  
Priority/High
The priority is high

  
Priority/Low
The priority is low

  
Priority/Medium
The priority is medium

  
Reviewed/Confirmed
Issue has been confirmed

  
Reviewed/Curated
PR LABEL: merge by rebase/ff to preserve the commit line; absence means squash. Set by the AUTHOR. (Curation itself is a duty on every PR — the label only picks the merge style.)

  
Reviewed/Duplicate
This issue or pull request already exists

  
Reviewed/Invalid
Invalid issue

  
Reviewed/Won't Fix
This issue won't be fixed

  
Scope/Campaign
Umbrella issue grouping a coherent multi-issue campaign.

  
Status/Abandoned
Somebody has started to work on this but abandoned work

  
Status/Blocked
Something is blocking this issue or pull request

  
Status/Conflicted
STATE: steward rebase failed; work returned to its agent, with evidence.

  
Status/In Progress
STATE: claimed, workspace active. Exactly one assignee, or none when idle.

  
Status/In Review
STATE: PR open against fastlane. Set by steward (PR webhook).

  
Status/Need Grooming
Issue body and comments do not yet conform to the Deliverable record; grooming required.

  
Status/Need More Info
Feedback is required to reproduce issue or to continue work

  
Status/Ready
Ready for execution; no known blocker prevents useful work from starting.

No labels
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Meta/Campaign
Meta/Epic
Meta/Session
Priority/Critical
Priority/High
Priority/Low
Priority/Medium
Reviewed/Confirmed
Reviewed/Curated
Reviewed/Duplicate
Reviewed/Invalid
Reviewed/Won't Fix
Scope/Campaign
Status/Abandoned
Status/Blocked
Status/Conflicted
Status/In Progress
Status/In Review
Status/Need Grooming
Status/Need More Info
Status/Ready
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Blocks
#48 Epic: council-safe Session materialisation
Ting/CurryComb
Depends on
#46 Separate council decomposition from CurryComb materialisation
Ting/CurryComb
Reference
Ting/CurryComb#47
No description provided.