One wonders if the accreditation agencies are neutral, or if they're going to say "well, you're not a real school, so we're not going to accredit you."
Can’t speak for the east coast, but the west coast accreditation organization (I forget the name) has a fairly clear set of standards for accreditation that boil down to:
1. Facilities required for accreditation (library, labs, offices, etc)
2. Degree programs and learning objectives (e.g. Bachelors of Computer Science and a list of competencies said degree asserts)
3. Processes and procedures, particularly around course management and curriculum. A big part of this is mapping out your listed degree requirements to classes that either provide those competencies or provide building blocks required for those competencies. E.g. Calc -> Lambda Calc -> Category Theory to provide a lot of fundamental math skills for a proposed CS curriculum.
I saw a university accrediting its new engineering department during a tour. It is a bunch of bueracracy and standards as opposed to something adhoc and fiefdom style. In that case the first few waves of graduates were conditionally accredited as graduates were required to accredit. Standards here seemed to be aligned in interests - they want to preserve reputations more than gatekeep. Given the sheer university volume gatekeeping is a dubious approach anyway.
> accreditation agencies are neutral, or if they're going to say "well, you're not a real school, so we're not going to accredit you."
Saying "you're not a real school, so we're not going to accredit you" is literally the sole job of an accreditation agency. Well, that and figuring out how to define a "real school".
One wonders if the accreditation agencies are neutral, or if they're going to say "well, you're not a real school, so we're not going to accredit you."