I have seen teams afraid to ask their product owner to create a GitHub account.
Not unwilling. Afraid. So instead they build a bridge: a bot that copies tickets from the tool product uses into issues, a sync job that copies comments back, a dashboard that renders the markdown specs somewhere product will look at them. Weeks of engineering so that nobody outside engineering has to change anything.
Every bridge is a place where the record can split in two. And the record is the whole point.
Software is not only engineering
A software factory is a trust problem more than a speed problem , and trust needs a chain: request, spec, plan, change, verification, handover. Every link reads what the previous one wrote down. I call it chain of custody , and it deserves its own post.
Look at who holds the links. The request comes from product or a stakeholder. The definition of done needs product. Acceptance needs whoever asked. Design decides what the screen looks like before anyone builds it.…