My point was that your theme only partially support child themes because the swift framework itself does not.
Since the theme is so tightly coupled with the actual framework it is not possible to really use child themes effectively, this is bad practice and planning, it does not follow standards that WP strives for.
Something as simple as changing the header menu output (sf-header.php) had to be done via the changing files in the swift framework theme folder, which as I mentioned do not work using a child theme hierarchy. The only solution was to completely decouple the swift framework from the parent theme using define(‘SF_FRAMEWORK_PATH …) which defeats the whole reason to use child themes.