# MSyoU — A Community Infrastructure Stack
### Field briefing for a possible conversation with Minnesota State University, Mankato technology leadership

**Independent work from the Static Collective · October 24, 2026 · No MSU partnership or endorsement implied**

## The premise

Southern Minnesota already has people solving pieces of the same problems: the proposed Waseca community grocery effort, a Greater Mankato care coalition, producers, neighborhood groups, local ecological projects, churches and educational institutions. What is often missing is not another general-purpose platform. It is a low-friction way to **discover an actionable overlap, make an invitation, and preserve what actually happened next**.

The Static Collective has been building independent experimental software around this crossing problem. **MSyoU** packages an institutional-legible view of the work and a runnable, account-free, intentionally local demo.

## The executable 60-second demonstration

Run `npm test && npm run serve` in this repository. On the local page, create a fictional NEED, OFFER, QUESTION or BUILD card. Explicitly move it from **DRAFT → LOCAL_HOLD → HANDOFF_PREPARED**. Export a portable JSON packet.

This proves only a bounded **local interaction contract** and a reader-friendly interface. It does **not** deliver an actual message, identify a person, record a university authorization, prove a physical act, or connect to a live organization.

## Seven source-owned building blocks

| Layer | Source | Civic purpose |
| --- | --- | --- |
| Public arrival | webZ / Abundent | Account-free or low-friction public doors and local project pages |
| Cards / meeting circulation | webZ CIRCULATION + GHoT | Move between table conversation, printable artifact, and inspectable card |
| Provenance / boundaries | reLATTE | Distinguish proposal, transport, local reception, and acceptance |
| Human coordination | TABLElogic | Compose a bounded question and several independently held returns |
| Attended inquiry | JAR;VIS | Explore questions with explicit HOLD and operator limits |
| Continuity | GRAFT | Track active experiment source and keep branches individually accountable |
| Stewardship | Full Measure × GrO | Invite repeat participation with separate human confirmation rather than points determining worth |

Source-and-proof annotations: [SOURCE-ATLAS](SOURCE-ATLAS.md). These are experimental components, **not a single integrated deployed system**.

## A researchable collaboration question

**Can a no-account, consent-driven field-card handoff reduce dropped community requests and produce clearer next actions—without building a new centralized social graph?**

This is a question, not a promised result. It is suitable for an opt-in civic technology, HCI, social research, accessibility or systems interoperability discussion if interested participants and institutional processes make that appropriate.

## Hardware and energy frontier: GHoT Energy Commons

We also built a [fictional, local-only resource planner](../resources/index.html) that asks how independent hardware owners might volunteer spare CPU capacity for bounded community work. It models owner opt-in, heterogeneous capability, battery/temperature, estimated power and energy budgets and a transparent **candidate or HOLD** disposition. The [GHoT source-boundary protocol](GHOT-ENERGY-COMMONS.md) names the native components and the permissions missing for any genuine device participation.

No campus devices, electricity, networks, students, or protected data are enrolled. A real experiment would require owner and institutional authorization first.

## Thin, intermittent discovery: Morse Cone 001

[**Morse Cone signal lab**](../radio/) now tests a different possible control plane: a very small, untrusted discovery token transmitted only within a fictional browser channel, then explicitly held rather than treated as authorization. A clean decode, corrupted timing, a collision, and non-reception have distinct, inspectable results. The A/N overlap and overhead-gap demonstration is a deliberately schematic teaching model, not measured radio propagation.

The [technical note](MORSE-CONE-001.md) maps this to our actual receive-only GHoT RADIO-EAR/ATTENTION proposals, Radio House signed-work and TranchNOSE's symbol/echo-clock distinction. It does **not** connect MSU machines, transmit radio, identify a physical endpoint, run GHoT, or establish RF source identity.

## A native two-machine trial has an explicit operator procedure

The [TWO-BODY FIELD 003](../field/) station pins a real GHoT RADIO HOUSE 004 revision, runs its native two-process protocol checks in CI and explains exactly how independent owners could try one authenticated, bounded hash operation on a private approved network. It is **not** a claim that two physical computers have yet been tested or that any university machine has been accessed. The approved runbook is [here](TWO-BODY-FIELD-003.md).

## A two-week local pilot

Choose **one** host and **one** bounded project. Example: a grocery-organizing working group has a specific volunteer or producer outreach question.

- Day 1–3: convene a consenting steward; define a written scope and sensitive-data exclusions.
- Day 4–7: run a paper-first table; optionally use locally prepared cards; human receiver independently accepts or refuses.
- Day 8–11: follow through on one real next action; distinguish reported from externally confirmed.
- Day 12–14: publish only a privacy-reviewed aggregate learning note, including failures and unmatched needs.

**Observe:** time from proposal to acknowledgment; proportion with an actual next-step owner; unresolved after 7 days; account/technical friction; access barriers; consent withdrawal; subjective usefulness. Do not count exported JSON as community impact.

## What assistance might actually be useful?

Not infrastructure access up front. A short technical review of the consent/retention boundary, one student-accessibility review where appropriately approved, and feedback on how to design a defensible field test would be more useful than a speculative institutional integration.

**The invitation:** inspect the code, challenge the assumptions, and—only if there is a mutually useful opportunity—help define a tiny test whose evidence can be reproduced and whose host retains authority. The [pilot contract](FIELD-PILOT.md) makes the stop conditions explicit.

*The table is the unit of cooperation; the receipt is an aid to memory, not a substitute for trust.*