Development record
principle seed from the pilot's F-W (itd-149 decomposition, part 3): the authorship default for external contributions is to ADOPT the contributor's commit, preserving their contributor-graph authorship; re-authoring with a Reported-by trailer is the honest fallback only when there is no branch to adopt, and the ACKNOWLEDGEMENTS entry rides the fix in the same change. No existing principle covers the authorship default; file it under development/principles/ (or fold into CONTRIBUTING) as its own act.
issueresolvedminoriss-2608271817309715
principle seed from the pilot's F-W (itd-149 decomposition, part 3): the authorship default for external contributions is to ADOPT the contributor's commit, preserving their contributor-graph authorship; re-authoring with a Reported-by trailer is the honest fallback only when there is no branch to adopt, and the ACKNOWLEDGEMENTS entry rides the fix in the same change. No existing principle covers the authorship default; file it under development/principles/ (or fold into CONTRIBUTING) as its own act.
Grounds
- pursued: the authorship default for external contributions is a filed principle; shown wrong if that principle is withdrawn or contradicts the adopt-first default
Frontmatter
| id | iss-2608271817309715 |
|---|---|
| type | issue |
| lifecycle | resolved |
| severity | minor |
.abcd/work/issues/resolved/iss-2608271817309715-principle-seed-adopt-contributor-commits.md
open on GitHub ↗ · commit history ↗
mentions1
- itd-149abcd handles inbound security advisories and issues, and cuts the release, for every managed repo. The 2026-08-27 security-advisory pilot proved the loop by hand across two independent operators: advisory and issue intake, recall-dedup triage against the ledger, record-first fixes in isolated worktrees, one integration branch, an independent adversarial gate over the assembled diff, auto-merge armed only after APPROVE, and a derived release cut through the semantic-receipt gates. This intent automates that loop as abcd capability for any managed repo, with findings F-A through F-W of the pilot note as the acceptance-criteria source and F-U (re-run every required pass against the final content commit; never transfer a verdict) and F-Q (the two release gates are human-by-design) load-bearing.