Technology Stack
Tools are chosen for the work they support: readable interfaces, dependable software, connected devices and knowledge that survives a handoff. Current use is distinguished from directions still being explored.
Preferred languages
A technology matters here when it makes a behavior safer, clearer, more recoverable, or easier to reason about.
Elm supports public interactive pages where state and behavior should remain predictable. This matters for access tools, content instruments, and interfaces that should not hide accidental complexity behind decorative motion.
Used in this site
Rust is a candidate for lower-level tools where memory safety, parsers, signing flows, device-adjacent systems, or dependable agent infrastructure matter.
Candidate for systems workElm logo source: Elm foundation asset via Wikimedia Commons. Rust logo: Rust Foundation, CC BY 4.0. Artwork unchanged; SVG formatting normalized. Used as a language identification mark.
Capability areas
Decentralized energy and battery systems point toward homes, sites, and devices that can continue operating with more local awareness, local control, and recoverable continuity.
Capability directionConnected electronics allow physical objects to carry state, intent, sensing, and constraint. The useful capability is not connectivity alone; it is behavior that can be understood after it happens.
Capability directionVite prepares the website's pages and assets for static delivery. Reading content can arrive before optional interactive graphics, with no application server needed for each visit.
Used in this siteAI can help turn conversation, research, and review into publishable structure when the page role, access level, and editorial voice are explicit before generation begins.
Emerging practiceA shared work record connects a request to its supporting information, decisions and results. A timeline, document view or review screen can then show a different part of the same history.
Capability directionA command asks for work. Events record what the system reports happened, while verification establishes what those records support. Keeping these roles distinct helps people inspect an action and decide what recovery requires.
Capability directionAgentic systems become more useful when delegation is scoped, observable, interruptible, and recoverable. The future behavior is not autonomous action everywhere; it is useful action inside a known boundary.
Capability directionSigning, HSM concepts, scoped delegation, and revocation make authority visible when intelligent systems, devices, or rooms are allowed to act beyond an ordinary screen.
Capability directionEvent streams, device signals, and traceable state help people understand what is happening while the operation is still alive, not only after a report is assembled.
Capability directionMarkdown, ledgers, decision records, and structured content let a project preserve why choices were made, so future work can inherit understanding instead of only files.
Used to document this site's developmentSelected telemetry can reveal whether content works while avoiding unnecessary profile building or exposed visitor detail.
Exploratory directionVercel, static assets, and versioned builds allow public pages to evolve quickly while keeping reference archives and private notes out of deployment.
Used in this siteFurther reading
Explore how these choices relate to a possible workshop interaction, a local introduction experiment, and earlier software and connected-system work.
