Skip to content

Define Software Factory activity through shared primitives (DRU-509) - #500

Open
czpython wants to merge 2 commits into
codex/dru-506-output-activityfrom
codex/dru-509-factory-activity
Open

Define Software Factory activity through shared primitives (DRU-509)#500
czpython wants to merge 2 commits into
codex/dru-506-output-activityfrom
codex/dru-509-factory-activity

Conversation

@czpython

@czpython czpython commented Sep 9, 2026

Copy link
Copy Markdown
Owner

Record prepared plans, revised plans, and completed reviews through saved output artifacts. Review artifacts include each finding's summary, evidence, and source location.

Announce rejected builds and owner-confirmed pull request outcomes. Keep operator stops separate from owner close events. Add Factory Activity labels through the shared frontend registry and link identity-only pull requests to GitHub.

Decisions

  • Use WorkItem.stop() to store operator cancellation without an owner announcement.
  • Reject a branch fallback when its current PR number differs from the observed PR.
  • Use AppUI.activityLabel for app-owned topic and gate wording.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant