Find the fit
Clarify the real opening, the host, the people affected, and the decision in front of them.
Streamlet is a distribution and delivery function for modular community projects. It turns one clear need into a bounded pilot that a willing host can understand, authorize, staff, support, and improve.
Available now: paid research, scoping, package design, facilitation, documentation, and pilot support. Streamlet as a repeatable distribution business and coordinated delivery network remains in development.
Where it sits
Streamlet is the independent delivery practice that carries selected parts of LIVING—including AACDI co-design work and Refugia place concepts—into bounded, host-authorized engagements.
It does not turn the wider ecology into one organization or imply that every concept is available as a program.

Why the name
A streamlet does not carry the whole landscape with it. It carries what can move, follows the ground, and joins larger systems along the way.
Streamlet uses the same rule: preserve the living pattern, then adapt the package to the actual site, people, permissions, and resources. It is not a franchise stamp or a fixed program dropped onto a community from above.
Where Streamlet works
Many good projects stall in the middle. The vision is compelling, but the host, roles, materials, authority, support, and next decision have not been assembled. Streamlet works in that gap.
Clarify the real opening, the host, the people affected, and the decision in front of them.
Select the useful project elements and connect them to appropriate roles, resources, safeguards, and specialist support.
Prepare orientation and launch, accompany the bounded test, and leave a usable learning and handoff record.
This is the public shape of the work—not a turnkey sequence. A real package is configured through a paid scope with a willing host and the people who hold the relevant knowledge and authority.
Possible cargo
Depending on the place and scope, a Streamlet package may carry one selected piece of the wider ecology—not the whole universe in a wheelbarrow.
Nothing becomes a local program by appearing on this site. A real package requires a willing host, explicit authority, adequate resources, appropriate specialists, and a written scope.
Meet the public access crew
These working names help distinguish jobs that are often collapsed into one overwhelmed person or program. They are an orientation key, not the full network protocol.
Where can a person actually enter, borrow, reach, learn, or reconnect?
What care, maintenance, accompaniment, and return path keep the opening usable?
How does someone arrive without already knowing the system? House of Workshop is a place-form; Hospitality, Orientation, and Welcome is its operating function.
How does a request reach the right place—and how does a reliable answer travel back?
What is a good fit for this person, group, place, moment, and level of responsibility?
Do the physical, digital, material, and procedural supports actually fit the people, place, and task?
How can story, place knowledge, art, architecture, craft, and cooperative design shape one usable room or intervention?
Open learning · Controlled implementation
Public pages teach the problem, principles, vocabulary, selected examples, and questions worth carrying into other rooms.
Facilitation scripts, assessments, editable templates, staffing logic, cost models, partner notes, training standards, site records, and implementation procedures remain protected. They travel only through a written collaboration, consulting, or licensing agreement.
Read use + permissionsCommission the missing middle
A scoped engagement can clarify the opportunity, shape the first package, prepare decision and public-facing materials, convene needed expertise, and support a bounded launch.
An engagement can end with a pilot brief, a host-ready package, launch accompaniment, or a learning-and-handoff record. The fit conversation decides what is useful before a larger scope is proposed.