Actually, the ‘authority’ isn’t there. We’re users, just like you. The community gratefully does the support in hopes that removing that burden from developers frees them up to do coding.
And the database structure in Gramps is currently flexible to structure the name data to reflect the couverture cultural bias. It just has to be done manually. Just like the Icelandic and Combination options for the Surname Guessing preference started as a manual process, then someone went to the trouble of codifying the those cultural idiosyncrasies and added them to Gramps.
Anyway, it is morelike “not until someone decides they want this recording keeping method automated instead of manually maintained”.
Gramps evolves when some sees enough reason to add the code… then shares the code with the community. Then, if our architect and ‘benevolent dictator’ decides that the patch conforms to guidelines, he’ll roll the enhancement into the core.
This one is complicated. The original Surname Guessing feature only considered the relationship between the Father and his Child for surname guessing. The Icelandic adds gender bias and parses a given name. The Combination requires 3 people for a valid guess. Adding Couveture cultural guessing makes it consider as many as 4 people with Gender bias. And, given the way trees are built, at LEAST 1 of these would be unavailable while adding the wife to a relationship. That means applying Couveture bias would necessarily be a post-process AFTER all the relationships had been put in place.
@kku was kind enough to provide some SuperTool sample code for evaluating relationships to set the Patrilineal Origin values for surnames all the way back in July of 2021. Logically, the next step would be to assess spouses to set “Taken” origins and set the Name type to Married Name.