coulomb/issue-core
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

docs: align issue-core with work-record connector role (ISSUE-WP-0004)
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 2s
Details

Browse source 
Retarget INTENT, SCOPE, README, ROADMAP, and agent docs from "task landing
zone" to external-tracker connector per work-record canon and architecture
draft §4.2. Add UUID↔external-id mapping design; mark ISSUE-WP-0004 finished
and cross-file activity-core ACTIVITY-WP-0022 for IssueSink policy.
This commit is contained in:
tegwick 2026-07-21 04:22:12 +02:00
parent 5e556028ab
commit d60175c354
9 changed files with 760 additions and 226 deletions
Download patch file Download diff file Expand all files Collapse all files

32
workplans/ISSUE-WP-0004-align-with-work-record-canon.md
View file

@ -4,11 +4,11 @@ type: workplan
title: "Align issue-core with the work-record canon (connector, not landing zone)"
domain: infotech
repo: issue-core
status: ready
status: finished
owner: codex
topic_slug: infotech
created: "2026-07-20"
updated: "2026-07-20"
updated: "2026-07-21"
state_hub_workstream_id: "ee47385f-aadb-4dba-b39f-148ac1444c3d"
---
@ -64,11 +64,14 @@ external-tracker projection when one is in use.* Green lane (docs only).
```task
id: ISSUE-WP-0004-T01
status: todo
status: done
priority: high
state_hub_task_id: "ae1e2a1e-8127-46bb-b7d7-be5c647f61ef"
```
**Done 2026-07-21:** `INTENT.md` rewritten with connector framing, dated
pivot, and expanded "What it is NOT".
## Task: Rewrite SCOPE.md — mapping table, not ingestion primary path
Current SCOPE.md lists activity-core's `POST /issues/` `TaskSpec` path as
@ -82,11 +85,14 @@ implemented — name the target shape before building it. Green lane.
```task
id: ISSUE-WP-0004-T02
status: todo
status: done
priority: high
state_hub_task_id: "cd0422f6-6921-4ac6-a484-19b6777d99bc"
```
**Done 2026-07-21:** `SCOPE.md` reframed; mapping table concept named;
TaskSpec retained as optional intentional path.
## Task: Audit and update README / ROADMAP for the same framing
`README.md`'s "Why Issue Tracking for Agent Coordination?" section and
@ -98,11 +104,14 @@ and the architecture draft. Green lane.
```task
id: ISSUE-WP-0004-T03
status: todo
status: done
priority: medium
state_hub_task_id: "746d090d-ebed-4328-bcd8-d531706ae795"
```
**Done 2026-07-21:** README + ROADMAP updated; Phase 0 + Phase 1.5 mapping
called out.
## Task: Design the UUID ↔ external-id mapping surface (design only)
Specify (not implement) how issue-core will record the internal work-record
@ -118,11 +127,14 @@ Green lane.
```task
id: ISSUE-WP-0004-T04
status: todo
status: done
priority: medium
state_hub_task_id: "61ba9b84-a2cc-4b20-b8d3-9fc8487f7acf"
```
**Done 2026-07-21:** `docs/uuid-external-id-mapping.md` — extend
`triggering_event_id`, add `work_record_uuid` + mapping rows; no code.
## Task: Fix activity-core's IssueSink call site to match
`activity-core`'s `issue_sink.py` (`IssueCoreRestSink`) currently treats
@ -136,7 +148,13 @@ implement the activity-core change itself. Green lane.
```task
id: ISSUE-WP-0004-T05
status: todo
status: done
priority: medium
state_hub_task_id: "944e0510-42c3-48f3-a7d2-86853468f816"
```
**Done 2026-07-21:** Filed
`activity-core/workplans/ACTIVITY-WP-0022-issuesink-no-default-forgejo.md`
(`status: proposed`) with tasks for default sink policy, implementation,
definition reroute, and deploy docs. Cross-links ISSUE-WP-0004 and
CUST-WP-0060 item 6. Implementation remains in activity-core.