Early accessShape the first fields before the public story hardens.
Community
Early builders shape the first living systems.
The community direction is for people who want to run Lazing, write packs, build in public, teach methods and test the Manifestation Layer in real work.
Pack directionHelp define what useful expert systems should feel like.
Quiet updatesFollow build decisions without joining another noisy channel.
Ways To Join
Pick the role that matches what you want to make better.
Early builders
Run the runtime, report friction and help shape the first useful fields.
Creator program
Turn repeatable expertise into packs, routines, lenses and expert tracks.
Pack authors
Write domain systems with inputs, risks, confirmations and trace.
Showcase submissions
Share real systems built with Lazing once the public gallery opens.
GitHub contributors
Help with adapters, docs, examples, privacy posture and runtime polish.
Build in public
Follow product decisions, changelog notes and program calls as they happen.
Community Roles
The community starts as a quality loop, not a chat room.
Lazing needs people who run systems, write methods, review claims and make the open source layer easier to trust.
- Gives
- Friction reports from real local/VPS use.
- Gets
- First install paths, field examples and early runtime calls.
- Gives
- Domain logic, data requirements, risk boundaries and useful surfaces.
- Gets
- A review path for turning expertise into Lazing packs.
- Gives
- Quality checks, privacy questions and claims discipline.
- Gets
- A voice in the standard before public gallery mechanics appear.
- Gives
- Docs, adapters, examples and contribution structure.
- Gets
- A focused OSS layer instead of a noisy platform backlog.
Showcase Submissions
Submit work when it has a boundary.
The first showcase should not reward noise. It should reward a clean method, scoped data, honest constraints and outcomes that can be inspected.
One useful system, not a vague category.
Inputs, steps, decisions, risks and expected surface.
A few real users, honest friction, no marketplace pressure.
Only packs with a clear boundary and trace should be visible.
Build In Public
Follow decisions, not noise.
The public update stream should explain what changed, why it changed and what still needs proof.
Read the build notesRuntime firstLocal/VPS authority, scoped memory and adapter boundaries.
Packs secondCreator methods become reusable only after quality review.
Gallery laterPublic discovery should wait until trust mechanics exist.
Trust alwaysPrivacy posture, DOI, consent and claims stay part of the story.
Builder Use Cases
Community starts with real systems, not a channel list.
Run Lazing from a real machine and record what blocks first-time setup.
Test a remote runtime path with scoped credentials, trace and phone-first control.
Try an early pack in real work and report where the system asks too much or too little.
Bring one useful daily system that should become easier than a dashboard.
Founding Circle
Apply to the Founding Circle.
The first community cohort is a quality loop: builders, creators and maintainers proving what Lazing should become through real work.
Founding Builder
Run early systemsUse Lazing on local/VPS workflows and report what breaks before the public story hardens.
Shape UX from real useYour friction reports influence fields, packs, runtime setup and mobile command surfaces.
Earn early builder creditUseful feedback can lead to Founding Builder status and future showcase consideration.