Public system map · selected relationships

In Development

See the constellation. Enter through one real need.

The names describe different jobs, places, methods, and scales. This page shows enough of the relationship to orient a visitor—not the complete operating architecture required to reproduce it.

Seven public relationships

A landscape, a set of doors, and a way to carry what works.

Read these as connected functions rather than departments already staffed or programs already adopted. A real pilot still needs a willing host, authority, resources, specialists, and a written scope.

01

Landscape

Möbius Refugia corridors

A distributed landscape of safer thresholds, habitat, rest, learning, making, support, and return—not one giant site expected to solve everything.

02

Places + interfaces

Homeitat + House of Workshop

Homeitat makes systems playable and tangible. House of Workshop is a physical access lobby, shop, and workroom where the wider ecology can be entered and used.

03

Access crew

DAN · SAN · HOW · CAN

Distributed access, support and continuity, hospitality and orientation, and communication each receive a distinct job instead of disappearing into one overloaded role.

04

Fit + tools

DAP · DAT

Appropriate practice asks what fits the actual person and context. The Department of Appropriate Technology asks whether the physical, digital, material, and procedural supports actually work.

05

Co-design + build

AACDI

Art, archive, architecture, craft, cooperative design, and local knowledge meet around one bounded, permission-based intervention people can actually use.

06

Delivery spine

Streamlet

Streamlet carries selected parts of LIVING—including AACDI co-design and Refugia place concepts—into a bounded, host-authorized package, then returns the learning.

07

Authorized project lane

Projects apparatus + funding

A separate project lane can research, budget, sponsor, and track a bounded pilot while actual hosts and governing bodies retain the authority to approve, fund, pause, or end it.

DAVISIAN · emerging local protocol

Distributed access needs a vision large enough to coordinate the small parts.

DAVISIAN currently names a Davis-rooted inquiry into distributed access, integrative systems, appropriate infrastructure, and a network that can learn from real local tests.

It is an independent working protocol and a piece of the project's lore—not an adopted City framework, public agency, or claim of local consensus. The public question is simple: what would help people enter, use, maintain, and improve the systems around them?

The deeper conceptual ground

The public ecology rests on an older body of work.

These foundations shape the questions and ethics of the work. A client can hire one bounded contribution without adopting or mastering the entire framework.

LIVING

The public body of work: an umbrella for the wider ecology without claiming every future relationship already exists.

Open the public doorway

Oiko Ways

A developmental map for asking how capacity, practice, responsibility, exchange, and stewardship grow together.

Open the public doorway

Five Element + Lunisolar

A field rhythm for observation, action, reflection, restoration, memory, material conditions, and return.

Open the public doorway

Braid Commons

The deeper coordination layer for roles, agreements, records, permissions, resources, review, and responsible handoff.

Open the public doorway

Public map · Protected machinery

Useful enough to learn from. Incomplete enough to require relationship.

This public map introduces purpose, language, and selected relationships. It is not a staffing plan, training manual, governance instrument, site protocol, or implementation license.

Full sequences, templates, assessments, costs, criteria, operating agreements, and project records remain in protected development or are prepared for a specific paid engagement.