STATIC COLLECTIVE / FIELD EXPERIMENT 001 INDEPENDENT · NOT AN MSU SERVICE
MSyoU ↗

The next piece of local infrastructure might be a table.

The community is already here.
Help the work find its way.

A small, inspectable field kit for connecting needs, offers, questions, and people—without demanding another account, another silo, or a single authority over everyone.

A PROPOSAL IS NOT A PROMISE
01Bring one thingneed · offer · question · build
02Hold it visiblynothing leaves without a choice
03Prepare a handoffportable and inspectable
04Human receptionbelongs to the actual receiver

The door opens. Nobody is compelled to enter.

What is this? An independent prototype, dated October 24, 2026. Not an official MSU Mankato, Coalition, or grocery initiative service. The demo never sends or saves your entries on a server. Use fictional examples; don't enter sensitive information.

WHY THIS EXISTS

Organizations have projects.
Projects need crossings.

A neighborhood grocery, a community group, an environmental crew, and a university laboratory may each already hold part of the same solution. We are experimenting with a way to recognize an overlap, invite participation, and preserve the handoff without treating any participant as absorbed by the others.

01 / ENTER

Anyone can arrive

Lightweight participation and readable invitations. A card works on paper as well as on a screen.

02 / CHOOSE

Every receiver keeps authority

Sending is not receiving. Receiving is not accepting. A proposed task is not completed work.

03 / RETURN

The useful trace survives

Know what was proposed, what was actually acknowledged, and what still needs a human.

THE FIELD TABLE / LOCAL DEMO

Bring one thing.

This runnable slice does one small job. No sign-in. No database. No sharing until you explicitly download a packet—and downloading does not deliver it.

HOLD
IS A
VALID
ANSWER

01 / Make a field card

02 / Choose what happens

CURRENT LOCAL STATE

NOT STARTED
Your card will appear here. Nothing has been sent.

No card created. A human receiver is required for anything beyond this demo.

Boundary: This demo records only locally asserted stages: DRAFT → LOCAL_HOLD → HANDOFF_PREPARED. It never creates ACCEPTED, WITNESSED, COMPLETED, or PUBLISHED claims. Closing or reloading the tab discards the working card.

THE SOURCE-LINKED ECOLOGY

One table. Many independent organs.

These are real source repositories with different maturity levels. We're putting interfaces between them—not pretending they are already one deployed product.

PUBLIC PORCH

webZ / Abundent

Account-light arrival, public doors and the Garden field atlas.

Inspect branch ↗
HANDOFF / CUSTODY

reLATTE

Source, proposal, reception and admission remain distinguishable.

Inspect branch ↗
MEETING INTERFACE

GHoT + CIRCULATION

Reviewable cards, prepared print artifacts and a human table.

Inspect branch ↗
QUESTION / COMPOSITION

TABLElogic + JAR;VIS

Question-to-proposed-return experiments held for human choice.

Inspect branch ↗
CONTINUITY

GRAFT

Source-owned branches, preserved context and a browsable research lineage.

Inspect repo ↗
STEWARD / FIELD

Full Measure × GrO

Real-world participation as invitations, with distinct human confirmation gates.

Inspect branch ↗

See the source atlas for exact maturity claims, code ownership and remaining evidence gaps.

GHoT / ENERGY-AWARE COMPUTE

What if spare computers could help?

One source-owned, voluntary resource network: an opt-in hardware capability and energy planner with battery, temperature and budget checks. Explore a fictional routing simulation now; no devices or campus systems are connected.

Explore Energy Commons ↗   Technical protocol

A REAL-WORLD REHEARSAL

What if we tested one complete handoff?

One community project. One real need. One willing steward. One explicit acknowledgment. One report of what changed. Paper is allowed; GitHub is not a prerequisite.

Read the two-week pilot contract ↗

What success might look like

  1. A participant knows how to offer or ask.
  2. A steward chooses whether to receive it.
  3. A next step has a named, consenting owner.
  4. Anyone can see what is still unresolved—with privacy respected.
  5. The team can decide whether to keep, change, or discard the tool.
All real deployment, contact, identity and retention decisions remain unapproved until the relevant people agree.