Structural fact extraction: events, subjects, fields, nests — no LLM #7
Labels
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
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Blocks
#29 Slice 3 — rules before models
Ting/CurryComb
Reference
Ting/CurryComb#7
Loading…
Reference in a new issue
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?
Proposal
Where syntax or the Forgejo API already gives the fact, extraction is deterministic (
docs/handoff.md§Fact pipeline 1): identifiers, cross-references, state, timestamps, fenced metadata, typed markers.Design
Lower into the shared relation surface —
event,subject,field,nests— ofdocs/handoff.md§Minimal shared relation model, usingcurrycomb-schemacanonical values.Tasks
currycomb_forgejo_client::has_canonical_markerRequirement scenario
GIVEN a fixture issue with known identifiers and links, WHEN extraction runs offline, THEN the emitted relation set is complete for the fixture and byte-stable under the canonical profile.
Structural fact extraction: events, subjects, fields, nests — no LLM
State:
open· Labels: Kind/Feature · Comments: 0Rendered by CurryComb slice 1 projection v1. The body will be replaced by rule-derived content in Slice 3.