Current projects.

Fuji operator cohort

A decentralized multi-agent reverse-engineering cohort for Fujifilm camera systems. The work spans firmware, Linux-side services, mobile apps, wire protocols, and product-facing workloads.

• Split by durable operator roles so investigation state stays local, reviewable, and resumable.
• Covers PTP, PTP/IP, BLE, live view, mobile app behavior, service modes, and camera Linux internals.
• Uses explicit hardware locks, verification gates, and evidence-backed docs for shared lab equipment.
• Feeds findings into product work, tooling, and public-safe disclosure notes.

ptpsim

A scriptable camera-protocol simulator and probe toolkit for PTP/IP responder behavior. The goal is a believable camera engine driven by manifest data rather than vendor-specific one-off code.

• Rust workspace for packet codecs, camera manifests, media stores, and responder runtime.
• Probe tooling turns observed behavior into structured bundles that can teach the simulator.
• Designed around reusable protocol primitives, fixtures, and optional FFI boundaries.
• Supports app development and protocol mapping without requiring a physical camera for every test.

Fujikage

A native camera workflow product backed by real protocol work: iOS and iPadOS clients, backend services, telemetry contracts, fixture tooling, and a public product site.

• Native Apple app work across pairing, live view, GPS persistence, transfer, camera settings, and firmware gates.
• Backend stack includes API, worker, admin, Apple receipt service, PostgreSQL, NATS, and telemetry.
• Fixture TUI and scripted camera states keep app development testable away from the hardware.
• Public site at fujikage.io.

Screenshots are from the Fujikage repo's current product and fixture assets.

Management plane

The self-hosted control plane for identity, secrets, internal TLS, ingress, observability, CI/CD, static sites, registry, and Fujikage environments.

• Owns the routing and runtime contract for public static sites and application services.
• Provides branch-scoped Fujikage development environments with generated routes, data roots, and service wiring.
• Keeps deployment authority local while GitHub and CI provide review, off-site storage, and image publishing.
• Treats operational state as inspectable pieces: manifests, generated config, service health, and dry-run-first tooling.