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

Lower Forgejo issues into OKF evidence with provenance #1

New issue
Open
opened 2026-09-02 07:53:30 +00:00 by larandar · 1 comment
larandar commented 2026-09-02 07:53:30 +00:00
Owner
Copy link

Proposal

Every reconciliation reads Forgejo state; that state becomes authoritative evidence before any rule or model touches it (ADR-0001: curation writes OKF, never only Mnestic).

Design

docs/handoff.md §Fact pipeline 1 (structural extraction), §HydraMem. Crate: currycomb-intake output feeding the HydraMem OKF bundle interface.

Tasks

  • map issue, comments, labels, links, revisions → assertions + provenance records
  • emit OKF bundle writes through HydraMem's existing file contract

Requirement scenario

GIVEN a captured Forgejo issue fixture, WHEN lowering runs twice, THEN the OKF bytes are identical and every assertion names its source (repo id, issue id, revision).

## Proposal Every reconciliation reads Forgejo state; that state becomes authoritative evidence before any rule or model touches it (ADR-0001: curation writes OKF, never only Mnestic). ## Design `docs/handoff.md` §Fact pipeline 1 (structural extraction), §HydraMem. Crate: `currycomb-intake` output feeding the HydraMem OKF bundle interface. ## Tasks - [ ] map issue, comments, labels, links, revisions → assertions + provenance records - [ ] emit OKF bundle writes through HydraMem's existing file contract ## Requirement scenario GIVEN a captured Forgejo issue fixture, WHEN lowering runs twice, THEN the OKF bytes are identical and every assertion names its source (repo id, issue id, revision).
larandar commented 2026-09-02 08:46:48 +00:00
Author
Owner
Copy link

Lower Forgejo issues into OKF evidence with provenance

State: open · Labels: Kind/Feature · Comments: 0

Rendered by CurryComb slice 1 projection v1. The body will be replaced by rule-derived content in Slice 3.

<!-- currycomb:refinement:v1 repo=Ting/CurryComb issue=1 --> # Lower Forgejo issues into OKF evidence with provenance State: `open` · Labels: Kind/Feature · Comments: 0 _Rendered by CurryComb slice 1 projection v1. The body will be replaced by rule-derived content in Slice 3._
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
larandar
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Blocks
#28 Slice 2 — persistent facts in HydraMem
Ting/CurryComb
Reference
Ting/CurryComb#1
No description provided.