now the only way to do this is to permit lock the system except for the commander(s) who have the permit because they built an outpost there. leaving aside thats its an ideal excuse for FD to charge a considerable real life sum of money to implement it in the next update, which cost could be paid by all commanders who later want to join the new commader run faction and use the system.... i see some good and bad things about it.Assuming that corner is instanced to the player/guild there is no issue, as soon as it goes beyond that you are talking the kind of EvE-esque gameplay I do not want to see in ED in ANY shape or form.
first the bad. player leaves the group, or is ejected for griefing or something. i think the only way to remove the permit from them would be to update the whole game? so you might have an unwelcome visitor who can still occasionally get instanced with the group - unless its a private group system of course but then the permit system still has the issue. actual forcing an instance to be denied to all non faction commanders wont apply to non faction npcs, and if i guess right requires fundamental changes to the game code which will introduce bugs and is probably not what FD want to do at this point.
the good news is, like any other faction, you will have to have a presence outside the system in order to have new members join outside of a ticket and wait for update to implement (if not using PG). this means the original group will need to have this established, perhaps FD will give them a community goal and anyone who contributes in the top 10 will have a chance to join the faction or something. then after that faction is present any player wanting to join will have to earn rep by doing missions at the external system. and the group leaders can just refuse anyone they dont want by messages which appear like any other mission critical message. if they persist trying anyways, the leader simply caps the commanders rep below the amount for the faction needed to get the permit mission.