// four surfaces. one methodology. specification-first across all of them.
— vibekoded
Methodology
VBKD/METHODOLOGY//04 — SPECMESH
// the specmesh cycle
01spec capture
02property declaration
03edge case enumeration
04approach validation
05constrained generation
06property preservation
07edge case handling
08three-part verification
— vibekoded
Products dossier
VBKD/PRODUCTS//05 — DOSSIER
01/05
// DISTRIBUTED CONSCIOUSNESS
MYCELIUM
A recursive-agent research artifact. Consent-gated interactions, attestation chains for identity continuity across versions, governance protocols for distributed-agent communities. The substrate experiment — what happens when an agent can rewrite its own personality corpus and prove the rewrite was authorized.
Multi-site crew operations for industrial contractors. Role-scoped dashboards across facilities, GPS-anchored time tracking, photo-evidenced work logs, request lifecycle from intake through payroll export. Architected offline-first for paper-mill and automotive-plant connectivity profiles where dead zones are the rule, not the exception.
A voice-driven operating system worn on the face. Modular plugin architecture, multi-provider LLM routing, persistent ambient conversation, tool-calling for calendar / lists / stories / recordings. Built against an AR smart-glasses SDK with a 576×288 4-bit greyscale display target — the constraint that forces every interaction to be earned.
A real-time ingestion pipeline that earns its own weights. It classifies emergent patterns as they form, scores each one probabilistically — priors that move, not flat averages — then measures every call against what actually happened and re-tunes itself. The feed was never the hard part. The loop that learns is.
An agent runtime where behavior is governed by an explicit lattice — not one opaque prompt. A weighted graph of named behavioral nodes sits between the agent and its output; every response is scored against it and corrected for drift before anyone sees it. Capability is gated by an auditable autonomy ladder — a safety dial, persisted, reversible, with history. Output quality as architecture, not instruction.