Great, thanks for the comments. I figured that naming conventions were just semantic. I don't want to use the term 'work instruction' as it implies detailed steps. Instead, I want to have much looser quality indicators; eg, you know how to build this product because you are a qualified technician and have seen the device technical documentation / image archive, but this is what 'quality' looks like for this device family, and we'll measure quality against these.
Quality System docs sit underneath corporate policy and alongside uncontrolled documents for each department; but if and when work activities hit the QMS scope, work is controlled and directed by the system. Only a very small amount of what we do hits the scope, so the system is nestled amongst much wider / informal systems.
Clear as mud! The Quality manual should clarify things I hope
Thanks again
James