Physical Branch Model

The Member Trust Union (MTU) — the network’s credit-union-like financial institution — has one existing description of its physical space: §13.4’s Section C (“Physical Infrastructure Design”), roughly two dozen lines covering three zone types for a single generic hub — Relational Zones, Consent Terminals, and Sensory Trust Interfaces — plus a one-sentence note that the design draws on service design and ritual theory. It does not describe how a location is chosen, how it is staffed, how its space is scheduled across competing uses, or how physical and digital channels connect beneath the consent kiosks it names. This section supplies that layer: space design principles, a location-selection methodology, a staffing and competency framework, guidance for running one space across multiple uses, and the physical-digital touchpoints beneath the sensory interfaces §13.4C already describes. It is a companion to §13.4C, not a replacement for it; where the two sections describe the same feature from different angles, this section says so rather than restating the description.

Source and marker convention. The material below is drawn from a single staged extraction of six unreviewed source files, produced in one generative pass with no citations and never checked against a primary source. Roughly half of the underlying files present invented first-person quotations as field evidence; none of that testimony appears here, as quotation or as paraphrase implying a real speaker — passages that were purely quotational, with no separable design content, have been omitted rather than summarized. The source supplies almost no numeric detail. Across its full scope there is exactly one quantitative claim (§13.9D, below), and it appeared only inside a fabricated quotation; it is not reproduced here, because a figure whose sole provenance is invented testimony is fabricated data rather than an unchecked claim, and the marker (unverified) used elsewhere in this corpus would misdescribe it. Everywhere else, the source states a design category, a process, or a named list without attaching a measurement, and this section says so directly rather than supplying a plausible number. No section below carries a reference list: the source cites nothing, and supplying citations it does not have would manufacture a rigor it never had. Structural counts that describe how the source organizes its own material — four principles, six zones, five competency levels — are not measurements of anything in the world and are not separately marked; they describe the shape of an unreviewed design proposal, not a verified fact about it.

A. Space Design Principles

MTU space design is organized around four stated principles, framed throughout as a departure from traditional financial-institution design — imposing facades, formal interiors, and physical barriers between staff and members:

• Hospitality over intimidation — welcoming, low-anxiety environments; cultural relevance to the local community; accessibility across abilities and backgrounds.
• Transparency and visibility — layouts that make service processes visible to members; easy staff access; environmental design that communicates information directly rather than through signage alone.
• Flexibility and adaptability — reconfigurable areas; a design that scales across capacity levels; infrastructure built to evolve rather than be replaced.
• Resource efficiency — spaces sized to actual need rather than institutional display; sustainable-material selection; operational systems that minimize ongoing resource consumption.

The source gives no floor-area or square-footage figures, occupancy limits, or numeric zoning ratio for any of the above. Sizing is stated only as qualitative design intent, left to contextual design at each location.

Six spatial elements recur across MTU locations, adapted to context rather than applied as a fixed floor plan. The source gives no adjacency diagram and no required-adjacency rule connecting them; how they relate to each other in a given building is left to the design process described below.

MTU physical presence takes one of three forms, applied by context rather than a single template:

1. Dedicated Facilities — a purpose-built building, a renovated structure, leased dedicated space, or a mobile unit.
2. Co-Located Services — space shared with a community center, a social-enterprise hub, a public facility such as a library, or an educational institution.
3. Hybrid Physical-Digital Presence — minimal fixed space, using pop-up locations, staff who travel to members, partner-provided space, and a digital-first posture with targeted physical touchpoints.

Spaces are designed and evolved through four recurring practices: participatory design (design workshops, prototype testing, ongoing community feedback), contextual adaptation (cultural and climate fit, reuse of existing assets, explicitly framed as the alternative to a standardized branch template), progressive implementation (starting from available resources rather than an ideal end state, with defined expansion pathways), and shared learning across the network (documented design patterns, including approaches that did not work, shared across locations).

The design process itself runs in four phases:

B. Location-Selection Methodology

Location selection is framed throughout the source as a departure from how traditional bank branches are sited — a process the source characterizes as driven primarily by market opportunity and profit potential. MTU siting instead applies four criteria and a four-phase process, and the source quantifies neither: it gives no numeric scoring rubric, no weighting across the four criteria, and no minimum-viability threshold — no minimum member count, no income figure, and no dollar threshold anywhere in the location-selection material. Where a scoring or weighting scheme would ordinarily go, the source names a category of analytical tool (“Viability Modeling,” below) without a formula.

The four selection criteria:

• Community need prioritization — financial-service gaps in the area; potential to improve local economic resilience; existing-member requests for physical service; explicit attention to demographic groups traditional institutions often overlook.
• Existing-asset leveraging — identifying underused space for repurposing; co-location with aligned organizations; integration with existing community gathering places.
• Sustainability and viability — long-term operational viability; a realistic read of the resources needed to establish and maintain the location; risk and resilience factors. The source states this criterion explicitly as not profit-driven, while still requiring the location to be sustainable.
• Network considerations — how a new location’s coverage complements the existing network of MTU locations; potential for resource-sharing with nearby locations; alignment with regional development strategy.

The selection process runs in four sequential phases:

Three location types, each with distinct siting criteria:

• Urban Neighborhood Locations — connection to a recognized neighborhood identity; public-transit accessibility; cultural alignment with the neighborhood; visibility and safety sufficient that members feel comfortable visiting.
• Rural Service Hubs — located at an existing community gathering point, within reasonable travel distance of the communities served (described only as centrally accessible; the source gives no mileage figure), with multiple-use potential and resource-efficient operation suited to limited infrastructure.
• Special-Purpose Locations — hubs for specific cultural or linguistic communities, financial-education centers, nodes supporting local economic-development initiatives, and sites used to test new physical-presence formats.

Three named categories of analytical tool, none with a stated formula:

• Geographic Information Systems (GIS) — service-gap mapping, demographic overlays, transportation and access analysis, and mapping of existing community assets.
• Community Needs Assessment Toolkit — quantitative survey instruments, qualitative methods, and participatory assessment techniques.
• Viability Modeling — cost-projection models, service-volume scenario planning, resource-requirement analysis, and identification of sustainability thresholds. The source names this last item only as a concept; no numeric threshold accompanies it anywhere in the material.

Short of a full permanent site, the source describes transitional presence (scheduled mobile-service visits, temporary pop-ups, phased establishment), technology-enhanced reach (digital services treated as complementary to physical presence, not a substitute), and community ownership models (mechanisms for local members to invest in their local space, with democratic decision processes for location decisions specifically).

Three implementation challenges and their named responses:

The source states that the selection methodology itself is revised over time, through case-study documentation, periodic process review, and adjustment based on how prior location decisions performed. It gives no specific review cadence.

C. Staffing Model and Competency Framework

Staffing rests on four stated principles: people over positions (valuing a person’s full range of capability rather than a fixed job description, strengths-based rather than deficit-based), community-connection priority (local knowledge, cultural competence, and existing community relationships treated as staffing criteria in their own right), balanced expertise (four knowledge types treated as co-equal: formal professional and technical skill, lived experience, community wisdom, and diverse perspective), and collaborative focus over hierarchy (team complementarity, distributed leadership and accountability, mutual peer support).

Four staffing models, not mutually exclusive and applied by context:

The source gives no headcount ratio anywhere in this material — no staff-per-member figure and no staff-per-square-footage figure for any of the four models.

The competency framework has three layers. Six core domains — Financial Knowledge, Community Connection, Operational Capability, Educational Facilitation, Technological Facility, and Collaborative Practice — are each assessed across five levels: Emerging, Applied, Proficient, Advanced, and Mastery. Teams are expected to combine a mix of levels across the six domains rather than have every member reach Mastery in each; the source frames this explicitly as a correction adopted after internal review found an earlier version of the framework implicitly required unrealistic universal expertise. Beyond the six core domains, the source names five specialized competencies — Cultural Facilitation, Conflict Resolution, Specialized Financial Expertise, Program Development, and Network Weaving. Each competency has a stated developmental pathway (entry points, learning resources, practice opportunities, an assessment approach, guidance on advanced application), but the source names no specific curriculum or certification requirement for any of them.

Hiring follows three linked practices: community-integrated recruitment (relationship-based identification of candidates, community nomination, structured pathways for members to gradually take on larger roles before being formally brought on), collaborative selection (current team members and community members both participate; selection draws on multiple kinds of interaction, including informal observation in a community setting, rather than a single formal interview), and mutual assessment (selection treated as two-directional — organizational needs and the candidate’s own goals are both made explicit, and developmental feedback is given regardless of outcome).

Team development operates at three scales: individual (personalized learning plans, mentorship, structured reflection, stretch opportunities), team-level (shared learning processes, conflict-transformation capability, collective adaptation), and cross-team or network-wide (communities of practice across similar roles, staff learning exchanges between locations, shared problem-solving on common challenges).

Compensation rests on a living-wage floor for all contributors, a transparent framework for setting compensation, and regional cost-of-living adjustment. The source also states a narrower gap between the highest- and lowest-paid roles than is typical for the sector, but gives no specific ratio or number for it. Contribution is recognized through paid staff roles, stipended positions, honoraria for specialized expertise, and unspecified non-monetary exchanges; benefits cover financial security, schedule flexibility, access to learning and development, and support for community-engagement time.

Three implementation challenges recur in the source: staffing rural or underserved areas (a smaller local talent pool, gaps in specialized technical expertise, resource constraints on competitive pay, geographic isolation from broader support networks); a structural tension between role clarity and adaptive capacity, and between network-wide consistency and local contextual adaptation; and long-term sustainability (career-pathway design, burnout and workload management, knowledge continuity through staff transitions, and how the staffing model scales as the network grows).

Effectiveness is assessed across three categories — team wellbeing (engagement, sustainability, growth, relationship health), service impact (member feedback, coverage, quality, responsiveness), and community integration (breadth of relationships, trust indicators, how community knowledge flows into the work) — with no numeric target given for any of them.

D. Multi-Purpose Usage Guidance

Running one space across multiple uses is justified on four grounds: asset optimization, community integration, service enhancement, and financial sustainability. Asset optimization rests on the observation that a conventional branch stands empty for most of the week. The source offers one figure for this and it is not reproduced here: the number appeared only inside an invented first-person quotation, with no citation and no calculation method, and a figure whose sole provenance is fabricated testimony is fabricated data rather than an unchecked claim. The unverified marker used elsewhere in this section signals a real claim nobody has checked; it would misdescribe this one. The qualitative point stands on its own and does not depend on the number. Community integration treats non-financial visits as building familiarity ahead of financial engagement; service enhancement frames non-financial engagement as a path toward financial-service use; financial sustainability points to shared infrastructure costs and efficiency gains from higher utilization.

Four primary usage categories:

Scheduling and coexistence rest on four mechanisms: usage frameworks (stated priority guidelines and a process for assigning specific activities to specific spaces, with no specific priority order and no numeric balance target given across use types), coordination systems (shared scheduling tools, defined transition protocols between uses, a defined approach to resolving scheduling conflicts), community voice in scheduling (usage advisory groups of community members, a proposal process for new uses, regular usage reviews), and partner-use agreements (formal usage agreements, joint planning, and cost-sharing with regular non-MTU users of the space).

Four categories of physical-design feature enable multi-use: flexible elements (movable furniture, modular components, adjustable lighting and acoustics), storage (activity-specific, organized for rapid setup and takedown between uses), technical infrastructure (systems usable across purposes, with security calibrated to context rather than uniformly maximal), and environmental adaptability (lighting, acoustics, temperature, and capacity flexibility for groups of varying size).

Four usage policy areas recur: accessibility (inclusive physical design, economic access, cultural accessibility, workable scheduling), shared responsibility (explicit use agreements, space-stewardship practices, a defined problem-solving process), safety and security (risk assessment per usage scenario, with a stated principle that security should not create unnecessary access barriers), and resource allocation (cost distribution across uses, equipment-access rules, consumable-supply management).

Coexistence raises four further considerations: regulatory navigation (delineating which activities are subject to which regulation, with no specific regulatory citation given in this material — jurisdictional detail is out of scope for this section); balancing non-financial use against the overall mission; community leadership over usage decisions; and concurrent-use management. On the last point, the source frames its hardest test case — a financial-counseling session, a youth program, and a member needing a quiet space, all running at once — as an illustrative scenario, not a documented incident.

Four illustrative usage archetypes, presented as generic models rather than case studies:

Usage expands in phases: assessment and planning, core financial functions established first, gradual expansion of additional uses as capacity develops, pilot-testing of new uses, and adaptive development based on experience, with partnership development running alongside. Evaluation covers four categories — utilization metrics (usage hours, user counts, activity diversity, resource efficiency), community-impact assessment (who can access the space, relationship formation, unplanned benefit), financial-sustainability analysis (cost-sharing effectiveness, revenue generated, long-term viability), and mission-alignment evaluation (service quality, member experience, trust development) — and the source gives no numeric target for any of them.

E. Physical-Digital Touchpoints

Physical-digital integration rests on four principles: human-centered technology (meant to strengthen human relationships and augment physical interaction rather than replace it, with members retaining control over their own level of engagement), contextual appropriateness (technology choices account for a community’s existing access, cultural attitudes, and comfort level, matching the tool to the function needed rather than deploying an advanced one where a simpler tool suffices), seamless transitions across channels (a consistent experience whether a member engages physically or digitally, with relationship context and appropriate information flowing between the two), and progressive introduction (new technology introduced in graduated steps, opt-in rather than mandatory, with supported exploration for less-comfortable members).

Five concrete integration-point categories:

These are carried by four physical mechanisms. Technology access points — member-facing access stations, staff-support technology, and environmental displays that surface digital information in the physical space — overlap directly with the projection surfaces and status displays §13.4C already describes; this section treats them as the same category of feature, not a second one. Physical-digital interfaces include interactive surfaces, environmental sensors, and physical objects with embedded digital capability; augmented-reality overlays are named as a category but not described as deployed (see Future Directions, below). Technology support zones provide dedicated space for building technology skills, staffed helper stations, peer-support areas, and private space for sensitive digital activity. Infrastructure covers reliable connectivity, accessible power, and environmental controls suited to housing technology.

Four supporting roles bridge the channels: Technology Guides (staff who help members use digital tools), Integration Specialists (make channels interoperate), Community Tech Stewards (peer members who help other members), and Experience Designers (own the end-to-end journey across channels). These are distinct from the consent-terminal and kiosk interactions §13.4C describes; they staff the connective layer beneath those interfaces rather than the interfaces themselves.

Three named implementation challenges: digital divides (access disparities, skill-level variation, generational differences in technology comfort), technology evolution (integration complexity across systems, legacy-technology constraints, future-proofing requirements), and resource constraints (implementation cost, need for specialized expertise, ongoing maintenance burden).

Evaluation covers experience quality (cross-channel journey smoothness, friction points, satisfaction, issue-resolution efficiency), inclusion (access equity, utilization patterns, barriers, adaptability to diverse needs), relationship impact (effect on connection, trust, and depth of engagement), and operational effectiveness (resource-use efficiency, cross-channel information flow, system reliability) — again with no numeric target for any of them.

The source names four directions as exploratory or aspirational, not as deployed capability: ambient computing (technology that recedes into the background, context-aware systems), enhanced reality (informational overlays on the physical environment, shared visualization tools), distributed presence (richer embodied remote participation, ambient awareness of others), and ethical integration (transparency by design, technology framed as preserving rather than undermining member agency). None of the four is described as implemented anywhere in the material.

Conclusion of 13.9

Read together with §13.4C, this section states the physical layer at two grains: §13.4C describes the sensory and consent-interface texture of a single generic hub, and this section states how that hub gets sited, staffed, scheduled across competing uses, and connected to the MTU’s digital systems beneath the kiosk layer. Three gaps recur often enough to name once more, rather than only at each occurrence above: the source gives no floor-area or square-footage figures anywhere in the material, no staff-to-member or staff-to-space headcount ratio for any staffing model, and no numeric scoring or weighting scheme for location selection. Filling any of the three with an estimate would misrepresent the source; this section states that they are unaddressed and leaves them for a later pass with access to a primary source or an operating location.

This section also does not cover community-integration strategy — the source’s parallel material on embedding an MTU location within a community’s existing organizations and relationships. That material sits outside the space, siting, staffing, and technology scope set for this section, and the underlying source file is itself truncated partway through its final subsection. That gap remains open for later work.