Notes on the decisions behind the projects: what the data can support, where a workflow needs a boundary, and how an interface makes that boundary understandable.
/ blipmap / repository note
An observation is not an accessibility promise
A map pin can look authoritative long before its data deserves that authority. blipmap treats a Patch as an observation with category, severity, status, and notes. A record can help someone review a trip without claiming the route is usable for them.
Path Check asks a deliberately narrower question: which recorded observations lie within 15 meters of this drawn line? It does not prove continuity, legal access, or the absence of barriers. Likewise, refreshing the source dataset does not make every underlying report recent.
The same discipline shapes routing. Mobility aids are not a shortcut for explicit access requirements. When the provider cannot honor a requirement, the application explains the limitation and does not generate a route. The useful design decision is preserving the user's constraint, even when that means returning less.
Elsewhere explores three distinct visual directions without making three different planners. Field Journal, Nocturne, and Civic Modern share the same itinerary model and component identity, with independent light and dark modes.
That separation is tested by ordinary planning work. A person can explore places, reorder stops, edit timing, inspect the day map, and undo a change. Switching a visual lens should not reset the itinerary or change what a control means. On a narrow screen, the layout becomes separate views rather than a compressed desktop split.
Source quality also shapes the workflow. The live city calendar is useful for discovery, but its entries lack the verified coordinates and visit durations needed by the planner. Linking out is more honest than inventing those fields. An event can be real without being ready to schedule.
Agent observability begins with a vocabulary problem. A skill may be available in a repository, configured for an agent, loaded during a session, referenced by text, or supported by execution evidence. Those are different facts, not interchangeable versions of a used flag.
Glasshouse's domain contracts retain those distinctions alongside evidence source and confidence. Its drift model describes expected-versus-observed differences without turning every unexpected file or tool into a claim about intent.
The project is still a foundation: schemas, parsing, and server routes are present; the inspected web source is not implemented. That makes the immediate design work unusually concrete. Before drawing a convincing trace, the system needs a defensible account of what each connection means and what remains unknown.
Care Booking makes a small fictional domain carry real interaction questions. What happens when the chosen slot is taken during confirmation? When a transient failure leaves the result uncertain? When staff book on behalf of someone else?
The demo exposes those situations through deterministic scenarios. A retry of the same action is not the same thing as choosing a new slot. Idempotency protects the former; conflict handling supports the latter. Rescheduling has another obligation: retain the existing appointment unless the replacement succeeds.
Identity needs similar precision. The person operating the interface and the patient receiving care can differ. A new record also does not establish an existing relationship with the practice. Keeping these concepts separate makes the screen's promises match the domain, even in a browser-only demonstration with simulated sign-in.