The bridge between OmarchyPi and a future sponsorship request to the Omacom Foundation: concrete offerings built in public, with receipts and reasons they might fail.
Public proposal only. Sponsorship has not been agreed. No contributor endorsement is implied.
Respond to something each contributor has already built. Make the proposed artifact concrete. State what would falsify it. Then ask whether the connection is real.
A tool, curriculum, experiment, or field test that can exist outside the pitch.
What ran, what changed, what remains unknown, and what the receipt actually proves.
The observation that would lower the offering’s priority or stop it entirely.
A narrow question the relevant contributor can answer without being asked to endorse the whole program.
OmarchyPi demonstrates the machine. The next build, Agent Literacy, tests what a person does with a more capable machine. The remaining offerings widen the experiment across memory, building, infrastructure, hardware, protocols, trust, interfaces, and daily life.
Artifact: A reproducible Raspberry Pi field build with bootstrap instructions, boundary tests, node identity, and a public field receipt.
Question: Can a computer become a personal instrument for building and solving problems?
Artifact: Five matched manual-versus-agent tasks with permission boundaries, human review, receipts, and total-burden comparisons.
Question: When does delegation make a person more capable rather than merely more occupied with reviewing machines?
Artifact: A portable workspace and migration receipt showing what survives a machine or service change.
Question: What does a person actually need to carry forward when their computer changes?
Artifact: A seven-day cohort where every participant ships a useful tool, documents it, and leaves a maintenance receipt.
Question: Can more people shape the tools around them without becoming professional programmers?
Artifact: A cohort of public projects with source, receipts, maintenance plans, and a public outcome report.
Question: What should count as infrastructure when the scarce resource is human capability?
Artifact: A measured workstation build with setup, recovery, power, thermal, and first-week learning receipts.
Question: What turns capable hardware into actual human capability?
Artifact: A bounded self-hosted communication experiment with portable identity, governance rules, and participant readbacks.
Question: What is the difference between participating in a platform and having agency within a system?
Artifact: A personal-infrastructure lab with threat models, fail-closed defaults, recovery drills, and incident receipts.
Question: Can trustworthy computing become understandable enough for ordinary people to practice?
Artifact: Interface prototypes tested through participant behavior and reflection, not novelty alone.
Question: Which relationships should an interface strengthen, weaken, or leave alone?
Artifact: A small project with deliberate non-features, scope cuts, attention boundaries, and a post-ship burden report.
Question: Can powerful tools make people more capable without colonizing their attention?
OmarchyPi demonstrates the machine. The next artifact tests what a person does with a more capable machine: five matched tasks, explicit boundaries, human review, and a published burden comparison.
The next public synthesis will report what OmarchyPi demonstrated, what remains unverified, why Agent Literacy comes next, and whether the Omacom connection became stronger or weaker.