@unknownuser said:
......I think I may have missed an example model along the way so can you permalink me to the post which contains this solution you're talking about ? johns example which I remember didn't have any accurate arc points 
fwiw, chord length between segments doesn't have anything to do with accuracy of an arc. and I can show you a few examples where you'll need oddball segment length which varies over the course of an arc.. what matters is that the vertices (no matter how they're spaced) remain a true radial distance from the cpoint.
You've got the correct model as I can see in later posts.
I know that there are minor differences, maybe even due to having things separated in groups. But the idea is good. That fact that they do not exactly share the same center if you zoom way in, yes you are right. But maybe this is due to speedy modeling to get the idea across. I stick with accepting this as a good offset solution.
And come on, segments not being parallel? so what? If I say corresponding vertices do not line up, then you say 'so what'. Sorry Jeff, in most offsets you can't have both at the same time, that is with arcs being segmented!. I left the idea of vertices being in line towards the center for what it is. I'm going for: all vertices on a true circle, equal segments (number can still be altered) and points at center in the same spot.
And you can't be serious when saying that a chord doesn't have anything to do with the accuracy of an arc. Not on its own, but together with the defined radius there's only one arc on either side of the point at center, all vertices on a true circle.
The chord, together with the radius, defines the angle that is covered by the arc.
How could the 'Arc' tool work if this weren't true: draw chord > specify (input) radius. Two possibilities as a result. Together one circumference of a whole circle, consisting of two arcs.