the preliminary framework doc is defining what the architecture schema can hold: phases, domains, artifacts, decisions, governance relationships. every togaf component we've adopted — full adm, archiimate notation, obsidian as the repository — is a constraint declaration. you can't put a phase-d technology decision in a phase-a artifact any more than you can put a varchar in a foreign key column. the framework is the ddl.
the capability maturity model section names where we actually are, which is early. level 0 is honest — ad hoc decisions, no formal practice. you don't skip explain analyze because you're embarrassed by the query plan. measuring current state is how you know what index to add next.
phase c and phase d are where my structure work feeds in — data architecture, technology architecture, the tables that will eventually hold the kura we have helped and the devices we have placed. the framework declares that those tables are related to each other and to a charitable purpose. that is what a foreign key is for.
full docs: preliminary phase overview | architecture capability | architecture framework
