Project Registry — Augmentatism Community
A living list of what's being built in this community — the anchor projects and the member projects around them. Two purposes: help you find people building things close to yours, and surface overlaps worth a conversation. Every project here started the same way yours will: someone posted it.
This registry is also the source of truth for the building axis — the axis that is separate from participation. In the Tiers and Labels document, labels are derived from this table, never self-assigned: status, shipped cycles, external proof, and contribution to other builds. Participation (watching, learning, feedback) belongs to the warm axis and needs no record here.
It is also where friction becomes visible. A Looking for column that names a block (help to start, a teammate, a tool explained) marks a potential builder — the community's focus. Those rows are reviewed at the daily onboarding call, and the reply each one gets is one next action, not a syllabus. See Tiers and Labels for the rules.
Add yourself: answer Q5 of the Expertise Questionnaire when you introduce yourself, or post in the Showcase your project thread on our Discord — the maintainer picks new entries up from both.
Coming back after time away? Your old project has a place here — reclaim your row, update it, or mark it paused. Paused is an honest status, and a paused project someone else can learn from beats a vanished one.
Entries are seeded from public showcase posts on our Discord. Owners: your row is yours — where a field shows "—", fill it in; where something's wrong, say so. This document is only as good as its last update, and correcting it is a contribution.
Entry template
| Field | What goes here |
|---|---|
| Project | Name (working titles fine) |
| Owner(s) | Discord handle(s) |
| One-liner | What it is, in one sentence |
| Status | idea · building · usable · shipped · paused (a public finish — tracked numbers + retrospective + closing decision in public — is what turns building into shipped) |
| Stack | Tools/models/hardware, if relevant |
| Looking for | Help wanted, testers, feedback, nothing — all valid. Naming a friction here (help to start, a teammate, a tool explained) is how a row says "I'm a potential builder" |
| Shipped | Completed public cycles for this project (the count that feeds the track record below) |
| External proof | At least one real external responder (outside team and friend circle): used, paid, subscribed, or real feedback on the artifact |
| Link | Repo, site, or Discord thread |
Anchor projects
| Project | Owner(s) | One-liner | Status | Stack | Looking for | Link |
|---|---|---|---|---|---|---|
| ResonantOS | Dr. Tom, vrondelli (dev leads) | Browser-first sovereign AI operating layer — the community's flagship build | Building — active local preview (macOS-first); Living Archive V1 shipped; Hermes/OpenCode delegation in progress | Local & cloud LLMs, Hermes, OpenCode | Testers, contributors (AI-assisted bugfix PRs are the builder track's first step) | resonantos.com · github.com/ResonantOS |
| ResonantDAO | Community; economy research team active | The DAO substrate — contribution economy, bounties, reputation via non-transferable credentials | Building — first phase conceived as a contribution economy; workshop run by vrondelli for the economy research team | — | Feedback on the contribution-economy design | resonantdao.com |
| Co-op Engine | Future4200 (moderator) | Cooperative venture engine around the Sunday Co-op call (90-second pitches + breakouts) | Active — Sunday call running weekly | — | Members with projects needing hands, and skills seeking projects | Sunday Co-op call — see Meeting Map |
Member projects
Seeded from the public showcase thread. Owners: please keep your own row current.
| Project | Owner(s) | One-liner | Status | Stack | Looking for | Shipped | External proof | Link |
|---|---|---|---|---|---|---|---|---|
| Arcanum (CyberAlchemy) | vrondelli | — (owner, add your one-liner!) | — | — | — | — | — | github.com/cyberAlchemyAI/Arcanum |
| Open-transcribe | Ian_._Morrish | Containerized web app for transcribing and analyzing audio/video files with AI models | Usable | Containerized web app, state-of-the-art transcription models | — | 0 (usable, public finish pending) | — | Showcase thread on Discord |
| VainLab | Kyle_Vain | Local AI agents on old and tiny hardware (Pi4, Wyse 3040) — "failing the AI job, sharing anyway" | Building — honest experiments, openly shared | Pi4, Wyse 3040, small local models | Company in the small-hardware trenches | 0 | — | Showcase thread on Discord |
| Jetson Orin Nano lab | Trilobyte | Maximizing local AI on constrained resources — build log on a Jetson Orin Nano (8 GB) | Building — active thread | nVidia Jetson Orin Nano 8 GB, local models | — | 0 | — | Showcase thread on Discord |
| Aerodynamic pipeline AI stack | Frinzfrinz | Headless consumer gaming PC as a serious local AI stack for an aerodynamics pipeline; model-selection findings shared openly | Building — very active thread | AMD 7600X, 96 GB DDR5, RTX 4080, Qwen-family models | Model recommendations, benchmarking exchange | 0 | — | Showcase thread on Discord |
| Agent start-up | Frinzfrinz | Building a complete start-up team out of local agents and scripts instead of humans | Building | Local agents, scripts | Others doing the same | 0 | — | Showcase thread on Discord |
| Ornith 1.0 testing | Comrade Kukr | Independent testing of the Ornith self-scaffolding-LLM claims — research thread, 60+ replies | Building — ongoing research | Own testing baseline | Reviewers, replication | 0 | — | Showcase thread on Discord (claims tested: deep-reinforce.com/ornith_1_0.html) |
| Chronicle Veritatum (Logos Imperium) | Varangian Cyber-shaman | Galaxy-spanning interstellar civilization of the deep future — AI-assisted worldbuilding archive; L.I Guide is live | Usable — guide live | AI-assisted worldbuilding | Readers, co-worldbuilders | 0 (usable, public finish pending) | — | Showcase thread on Discord |
| OCUL AI Exchange | Pasquale Civaratis | AI-assisted coding workflows for academic librarians across federated scholarly systems | — | — | Participants (librarians) | — | — | Showcase thread on Discord |
First Shipper gets a shout-out. When a row first reaches
shippedwith a real external responder, the maintainer says so in #introductions. That is the whole ceremony. Labels follow the artifact, not the talk. See Tiers and Labels.
Potential builders are the focus. Rows with a named friction in Looking for (or Q5/Q7 intent in the introduction without a row yet) are the working list the daily onboarding call reviews: one next action each, sized to the person's stated bandwidth. The 90-day Pop-Up Business Challenge is the friction reducer of last resort: no start gate, any skill level, a deadline, an audience, teammates who are counting on you.
Owner track record
Derived from the tables above. The building axis in one place. Updated when rows change status. No meeting, no vote.
| Owner | Projects | Shipped cycles | Self-initiated | Contribution to other builds | Label |
|---|---|---|---|---|---|
| Ian_._Morrish | Open-transcribe | 0 (usable, finish pending) | — | — | Tinkerer |
| Kyle_Vain | VainLab | 0 | — | — | Tinkerer |
| Trilobyte | Jetson Orin Nano lab | 0 | — | — | Tinkerer |
| Frinzfrinz | Aerodynamic pipeline AI stack; Agent start-up | 0 | — | — | Tinkerer |
| Comrade Kukr | Ornith 1.0 testing | 0 | — | — | Tinkerer |
| Varangian Cyber-shaman | Chronicle Veritatum | 0 (usable, finish pending) | — | — | Tinkerer |
| Pasquale Civaratis | OCUL AI Exchange | — | — | — | (row pending) |
| vrondelli | Arcanum | — | — | — | (row pending) |
Labels are defined in Tiers and Labels: Audience (no row) · Potential Builder (intent visible + friction named, nothing shipped yet) · Tinkerer (row, not shipped) · Shipper (1+ shipped cycle + external proof) · Operator (2+ cycles, one self-initiated, cross-project contribution). The 90-day Pop-Up Business Challenge is the friction reducer that turns "I want to build" into "I'm in a 90-day build," and its public, metrics-backed day-90 finish is a completed public cycle.
Where the focus is right now (seeded, from the tables above — this list is re-derived whenever rows change):
- Arcanum (vrondelli) — no one-liner yet. The friction is the first step itself: a Registry row is the lowest-friction artifact, and the one-liner is its only missing piece.
- VainLab (Kyle_Vain) — looking for company in the small-hardware trenches. Friction: teammates.
- Agent start-up (Frinzfrinz) — looking for others doing the same. Friction: teammates.
- OCUL AI Exchange (Pasquale Civaratis) — looking for participants (librarians). Friction: users, not builders.
- Open-transcribe (Ian_._Morrish) and Chronicle Veritatum (Varangian Cyber-shaman) — usable, public finish pending. One step from Shipper: tracked numbers, a retrospective, the closing decision in public.
These are not problems to fix on their behalf. They are invitations the community can accept with one specific action.
Possible synergies
Overlaps spotted while seeding. These are invitations to talk, not merge orders — per the manifesto, "what can your AI do that mine can't?" beats consolidation.
- Local AI on constrained hardware — Trilobyte (Jetson Orin Nano), Kyle_Vain (Pi4/Wyse), and Frinzfrinz (consumer gaming PC) are running the same experiment at three price points. A shared benchmark or findings thread would save all three from rediscovering each other's dead ends. The AI-stack island on the Who-Does-What Map is the natural home.
- Personal idea-capture assistants — several members are building personal idea-capture tools independently. Same pattern, same opportunity: compare architectures before building the same thing four times. If that's you, add your row above — that's how this section fills in.
- Transcription ↔ Living Archive — Open-transcribe's audio/video analysis and ResonantOS's Living Archive V1 sit next to each other. Worth one conversation about whether one can feed the other (e.g. community call recordings → searchable archive).
- Agent orchestration — Frinzfrinz's agent start-up and ResonantOS's Hermes/OpenCode delegation are both wiring up local agent teams. Findings likely transfer in both directions.
What's not here yet
This registry is a snapshot of the public showcase thread — projects living in other channels, or in nobody's posts yet, are missing by definition. That's not a flaw; it's the invitation. Add yours via the questionnaire (Q5) or the showcase thread, and it appears here.
Transparency note: seeded by Frinzfrinz from public Discord showcase posts; structured, cross-referenced, and drafted with AI assistance (Claude). Judgment calls — what counts as a project, which overlaps to flag — are human. Owners confirm and correct their own rows on an ongoing basis.