ONE LIGHTHOUSE. MANY DOORS. Statewide does not mean one building.

A statewide system can fail in two opposite ways. It can centralize so much that people in rural and local communities must travel, call, wait, translate, and repeat their story just to reach the state. Or it can decentralize so completely that every county, partner, provider, library, school and public office improvises its own rules.

ANCHOR's proposed answer is neither. The project architecture combines a central Lighthouse with Regional Docks, community anchor sites, mobile access, the Access Exchange and Provider Network, Academy training, and a Center for Research Studies. The proposed Authority Act describes the Lighthouse as a statewide hub for administration, board support, policy, training, data governance, research, public education, field coordination, help-desk operations and reporting. It also authorizes Regional Docks through libraries, health units, schools, higher education, public offices, nonprofits, providers and other approved hosts, with Dock Lite, Standard and Plus configurations tied to readiness and approved roles.

01 · The Lighthouse

The statewide hub is where the system holds together.

The Lighthouse is the place—physical, distributed, or both—where statewide operating responsibility is concentrated. It supports the governing board and executive team, maintains standards, coordinates the help desk and multi-channel public access, manages publications and public education, supports Academy operations, oversees statewide field coordination, and provides a controlled home for data governance, document control, reporting, digital continuity and research administration.

That does not make it a hospital, disability benefits office, school district, police agency, Medicaid eligibility office, or diagnostic clinic. ANCHOR's proposed boundaries preserve the legal duties of existing agencies, providers, courts, schools and licensed professionals.

What could physically live at the Lighthouse?

Depending on the final fiscal and facilities plan: public access/help-desk space; training rooms; Academy studios; accessible meeting rooms; research and evaluation workspaces; digital operations; publication/print production; secure document and data-governance functions; assistive-technology demonstration and lending space; partner convening rooms; field-operations coordination; and quiet, sensory-aware public areas.

Some functions do not need permanent public-facing floor space. Secure computing may be provided through contracted state-compliant infrastructure. Research partners may work from universities. Training can occur at Docks or partner sites. Publication teams can work remotely. The useful question is not “How big can the building be?” but “Which functions genuinely benefit from being centralized, and which should remain distributed?”

02 · The Dock Network

A Dock is a local access point—not automatically a new building.

The proposal deliberately allows Docks and community anchor sites to live inside institutions that already exist: libraries, health units, schools, institutions of higher education, public offices, nonprofits, providers and other approved hosts. That lowers the risk of building a costly statewide real-estate system before local demand, operating cost, privacy needs and service patterns are understood.

Co-location also changes the social problem of access. A person may already know the library, health unit, education cooperative or public office. They may be able to reach it by an existing transit route. A Dock can therefore act as a familiar place to get written help, use a private portal, prepare a Passport or CARD, connect to the Academy, search ARCHIE or the Resource Map, join an appropriate tele-support session, or receive a warm handoff to another service.

This is where the network architecture becomes more than a facilities plan. The same person may touch a physical Dock, a digital system, a partner office and the Lighthouse in one support journey. The system should preserve context so each step is not a restart.

03 · The Research Center

The Research Center is how ANCHOR learns whether its own ideas work.

ANCHOR's Center for Research Studies is proposed as a community-guided center for implementation studies, tool testing, data governance, rural access research, workforce training research, public-system design and evaluation. Its job is not to turn autistic and neurodivergent people into a permanent subject pool. Its job is to make the public system more accountable to evidence, lived experience, field results, rights and real-world constraints.

That is closely aligned with implementation science. CDC's NIOSH describes implementation science as the study of methods that increase the adoption, implementation and maintenance of evidence-based interventions in real-world settings.4 ANCHOR needs that discipline because a tool can look excellent in a design meeting and still fail at a rural library counter, a school front office, a clinic waiting room or a mobile event.

What the Research Center could study

Rural service deserts; communication access in healthcare and public offices; the effectiveness of Academy training; usability of Passport, CARD and MICA; failed-referral patterns; sensory-access design; mobile access; digital and paper access; tele-support readiness; transition points; workforce readiness; public education; assistive technology; and whether a proposed intervention reduces friction without creating new privacy, equity or rights problems.

The logic has a real-world analogue. HRSA describes a traditional telehealth hub-and-spoke model in which a patient at one site can connect to a specialist at another.1 HRSA also supports rural network planning built around collaboration among organizations to strengthen local capacity and care coordination in underserved communities.2 ANCHOR is broader than a telehealth network, but the design principle is similar: specialized statewide capacity can support local access without requiring every locality to duplicate every function.

04 · The statewide/local feedback loop

The most important thing a Dock sends back may be evidence that the system is wrong.

A statewide office can see totals, queues, maps and reports. A local Dock sees the person who drove an hour to reach a provider that no longer accepts adults; the parent who cannot use a phone-only intake; the school worker who needs a written communication tool; the clinic whose referral keeps returning; the county where public transit ends before the appointment; and the local practice that solved a problem in a way the statewide office had not considered.

This is why the Research Center and Docks should not be separate initiatives. The Docks create structured observation points across different local conditions. The Research Center provides a disciplined way to test whether the patterns are real, what caused them, which intervention works, and whether the result is safe to scale.

05 · Build the network before building the monument

Infrastructure should scale by readiness, evidence and use—not by architectural ambition.

The project documents already preserve this discipline. The Lighthouse site, ownership, staffing and capital model require fiscal and procurement review. Docks require host agreements and readiness standards. Mobile access should compare co-location, contracted capacity and practical vehicle upfit before a costly custom fleet. Research should move through listening, study, design, pilot, evaluation and scaling.

That produces a defensible startup sequence: establish governance and a digital/public access core; pilot one or more Dock models using existing host sites; connect a small provider/access exchange; launch Academy training; stand up an evaluation/research function; deploy mobile capacity where the fixed network demonstrably fails; then use field evidence to decide where standalone facilities, expanded Dock Plus sites, dedicated research space or additional fleet capacity are justified.

What belongs where?

06 · The public-facing promise

The person should experience one network even when the work happens in many places.

Someone should be able to start online, at a Dock, through a partner, at a mobile event, with a printed form, or through the Lighthouse help desk and still enter the same basic framework: ask → understand → route → prepare → connect → learn. The exact service may belong to another agency or provider. ANCHOR's job is to make the path clearer, preserve useful context, reduce repeated explanation, and learn when the path repeatedly fails.

Telehealth is one tool inside that architecture, not the architecture itself. HRSA notes that telehealth can improve access in rural, urban and underserved areas, but a usable network still needs connectivity, accessible communication, local preparation, appropriate providers, privacy, and a plan for what happens when virtual access is not enough.3