Accommodation. Combat sports. Contextual AI. Street-level language. Different machines, built around the people who need them.
CampStay and Nocturne Labs are the co-flagships. Security infrastructure, client systems, research and prototypes stand alongside them — distinctly labeled, not dressed up as finished products. Source-reviewed foundations and supplied dossiers describe the work; portfolio captures are not production certification.
NL / 001FLAGSHIP
CampStay LMT
Accommodation operations
Client hospitality system
Manager overviewSynthetic demo data
1 / 4
The accommodation operation behind a Muay Thai training camp, brought into one working environment.
Follow an inquiry through booking and approval
Coordinate arrivals, pickups and room readiness
Explain pricing exceptions and keep an activity record
Technical dossier for CampStay LMT
Origin
Built around camp accommodation in Koh Samui, Thailand — where guest logistics and daily staff work have to meet.
The problem
Bookings, deposits, room changes, airport pickups and cleaning responsibilities lose context when they live in separate tools.
Implemented foundations
Reservation review, approval, deposits and confirmation
Guest records and arrival/departure logistics
Pricing adjustments with documented context
Staff and housekeeping coordination
Activity alerts and operational audit records
FRONTEND
React and TypeScript interfaces for guest, front-desk and staff workflows, with mobile-oriented views.
BACKEND
Structured reservation and operations records; authenticated role boundaries, storage, activity tracking and coordinated updates.
Milestones in the record
Accommodation workflow assembled around camp requirements
Guest and staff views connected to booking context
Mobile and alert-readiness refinements recorded
Next / limits
Continued operational refinement; this exhibit makes no performance or availability guarantees.
Showroom entrancePublic-page capture · no private records
1 / 6
The workshop you are standing in: custom technology work carried from first inquiry to governed delivery.
Screen a work order with optional identity context and private attachments
Review client milestones, quotes and agreements in the Garage
Triage, dispatch and approve work in Command
Technical dossier for Nocturne Labs
Origin
A founder-led shop needs its public front, client workspace and operating floor to share the same job context.
The problem
Blind service purchases and disconnected project tools separate scope, approval and delivery.
Implemented foundations
Intake → fenced Scout research → founder Triage
Hash-locked quotes and agreements
Single-use approved execution and immutable receipts
Client Garage projects, invoices and additional-work requests
Signature-verified test-mode invoice payments
Capture-only Telegram and persistent public radio
FRONTEND
React 19 and TanStack Start / Router, Vite and Tailwind v4; Industrial OS typography and separate public, client and staff surfaces.
BACKEND
Lovable Cloud records with row-level access, private storage and founder-checked functions. Server functions run on edge workers; consequential execution verifies scope, payload and single-use approval.
Milestones in the record
Public Showroom and client/staff environments assembled
Quotes, Contract Forge and execution receipts integrated
Existing invoice checkout hardened in test mode
Next / limits
Screens show public pages and intake, not private Garage or Command records. The archive capture shows the earlier six-project edition. Live payments, provider availability and physical-device playback are not certified by these captures.
Public security hubPublic-page capture · no private records
1 / 4
Designed for securing platform assets: an encrypted vault and security intelligence workspace for independent operators.
Store credentials and documents in an encrypted vault
Review security posture, incidents and connector signals
Assess analyst recommendations before human-approved actions
Technical dossier for Fenrir Lock
Origin
Small teams and researchers operate real infrastructure without a dedicated security operations center.
The problem
Credentials, device trust, alerts and incident context become fragmented across security tools.
Implemented foundations
Supplied dossier describes client-side AES-256-GCM and a zero-knowledge vault design
Security-score, threat-stream and incident-timeline modules documented
Device-trust, connector and authentication modules documented
Analyst recommendations use Plan → Approve → Execute
FRONTEND
Supplied dossier: React 18, TypeScript and Vite, shared UI controls, TanStack Query and installable PWA foundations.
BACKEND
Supplied dossier: access-scoped Postgres records, realtime and server-side ingestion/analysis; signed connector traffic and redaction before model calls. Encryption keys are described as staying client-side, not independently cryptographically audited here.
Milestones in the record
Public hub, capability grid and secure-access views captured
Vault and security-intelligence foundations documented
Partner monitoring remains subject to connection and deployment verification
Next / limits
Active development, not a security certification. No supplied implementation evidence establishes live CampStay protection. Captures show public hub/capabilities/sign-in/mobile pages, not private command or vault contents.
Digital Corner introductionSynthetic showcase · illustrative data
1 / 4
Training footage becomes a timestamped first pass that a coach can approve, correct or overrule.
Review pad, bag, shadow or sparring clips by timestamp
Give coach verdicts on evidence-backed observations
Debrief in Digital Corner without treating conversation as authorization
Technical dossier for FightIQ Coach
Origin
Inspired by Muay Thai: fighters capture footage, but useful review depends on the coach’s method and available time.
The problem
Generic analysis can confuse what is visible with what it means, while corrections disappear between sessions.
Implemented foundations
The Eyes: sampled frames and confidence-scored observations
The Library: gated, source-ranked skills and drills
The Corner: clip-scoped coaching and approval-aware drafts
Coach corrections retain original machine reads and audit history
Timestamp seeking, frame stepping, debrief evidence and exchange intervals
FRONTEND
React 19, TanStack Start / Router, Vite 7 and Tailwind v4; timestamp-aware video controls and reduced-motion presentation.
BACKEND
Lovable Cloud account/gym-scoped records and footage storage. Edge-worker functions use a server-only model registry, explicit fallback and provenance labels.
Milestones in the record
Read-only demo review and debrief captured
Evidence, coach correction and audit presentation documented
Coach-supervised beta described in supplied dossier
Next / limits
Owner-designated Active Research. Synthetic sample footage and coach notes illustrate review, not live model accuracy or sporting/medical advice. Unclassified exchange gaps remain unclassified.
Scattered captures, commitments and local context become a situational read with approval boundaries and receipts.
Read Today’s schedule, promises and approval queue
Route captures, projects and documents through Work
Ask Echo contextual questions and inspect Receipts
Technical dossier for Metro Echo
Origin
Daily commitments cross documents, schedules, messages and places; useful context needs to meet in one environment.
The problem
People reconstruct context repeatedly and risk mistaking a conversation for permission to execute.
Implemented foundations
Today, Work, Echo and Receipts share context
Document intake, validation, review and export pathways
Places, weather and topic-watch modules with provenance
In-app and Telegram capture pathways
Approval-aware drafting and recorded lifecycle outcomes
FRONTEND
React 18, TypeScript and Vite, TanStack Query, shared context/scope providers and URL-backed four-room navigation; graffiti and transit instrumentation.
BACKEND
Lovable Cloud access-scoped records, storage, realtime and server-side context orchestration. Weather, watches, calendar and messaging depend on consent, configuration and provider health.
Milestones in the record
Four rooms captured with isolated synthetic fixtures
Context-bound Echo thread and illustrative receipts documented
Document and watch workflows described in supplied dossier
Next / limits
Active Prototype, not maintenance-free production certification. Fixture receipts, weather and prose are simulated; native Android, full offline resilience and notification consistency remain development work.
Thai language & cultural intelligence · mobile-first
Implemented V1 · reliability work continues
Language hubSynthetic showcase · illustrative data
1 / 4
Practical Thai, pronunciation and cultural context for moments when a literal translation is not enough.
Translate phrases with romanization and tone guidance
Explain cultural meaning and practice pronunciation
Save phrases and complete everyday street missions
Technical dossier for SoiCat AI
Origin
Life in Thailand calls for local phrasing and social understanding, expressed through a street-smart cat companion.
The problem
Textbook translations miss tone, context and the conversational reply someone actually needs.
Implemented foundations
Translate, Explain and two-person Conversation
Pronunciation coaching and pitch-focused practice tools
Saved vocabulary, slang libraries, missions and review
Shared AI timeouts, retry and circuit-breaker pathways
Versioned local cache and labeled fallback phrasebook
FRONTEND
React 19 and TypeScript, TanStack Start / Router and Query, Tailwind v4 and custom SoiCat artwork; mobile-first content column on desktop.
BACKEND
Lovable Cloud user-scoped records and server functions; language, speech and pronunciation calls use a shared resilience layer. Browser storage mirrors selected state with cache versions and sign-out cleanup.
Milestones in the record
Implemented V1 language and cultural workflows documented
Four synthetic mobile-first interfaces captured at desktop resolution
Reliability and fallback foundations assembled
Next / limits
Active Companion with ongoing reliability work. Community feed and unsent-input queue are planned, not shipped. Real-device microphone/lifecycle tests and exhaustive offline certification are outstanding; sample outputs and progress are illustrative.
