Notes about my work, projects, training, and life.
Rode my bike to pick up my truck from the repair shop, then came home and ran.
The air quality made breathing rough, so it was not the kind of run where you chase numbers. Still got after it and took what the day gave me.
Truck is home. Legs got loosened up. Work got done.
Cypher missed a temporary work schedule even though I had already given it the dates and hours.
The record existed, but the regular rotation was always injected while future overrides could be filtered out. I traced the failure through memory retrieval, date resolution, and correction handling, then tested the fix against the exact prompts that failed.
It now returns the right current, future, and historical schedules.
More context does not automatically make an assistant better.
It can make it louder. Messier. More confident in the wrong things.
That was the work behind this Builder Receipt.
Cypher needed better access to my history, but also better rules for source authority, evidence, timing, web links, model control, and when context should stay out of the way.
More information was never the goal.
Better control was.
https://jimlunsford.com/builder-receipt-better-context-and-control/
Added model and reasoning controls directly to Cypher’s prompt box.
Terra stays available for normal conversation, while Sol can be selected when something needs more depth. During testing, I caught an important gap: changing the model without being able to change its reasoning effort was only half a control.
I added per-conversation reasoning options, then verified the interface, request handling, saved settings, and regression coverage.
Caught a web-search problem in Cypher that made good answers harder to read.
It was dumping long, repetitive source lists into the chat and leaving Markdown links exposed as broken-looking text. I directed an upgrade that collapses sources, prioritizes the pages actually cited, removes duplicates and tracking parameters, and renders links properly.
Then I added regression coverage for both new replies and restored chat history.
Fixed two context failures in Cypher today.
One detector was hijacking normal conversation because it matched words like “first” and “post” inside ordinary sentences. The other problem was deeper: Cypher could know personal facts without understanding why an important moment mattered.
I tightened the routing, added milestone-aware retrieval, and tested birthdays and recovery milestones until it could pull the right history without turning a real conversation into a biography.
The struggle is honest.
It tells you what it came to do.
Pressure wants to move you. Fatigue wants to weaken you. Excuses want room to breathe. Comfort wants the standard lowered.
Fine.
Let the struggle talk.
Then answer with action.
Try me.
I spent time today building Local Places into Bonumark Stream.
The goal was simple: let someone attach a saved place to a post without paying for a third-party API or sending location data somewhere else.
The first build worked, but real testing exposed the difference between functional and finished. The composer was cluttered, geolocation could be blocked, theme styling was inconsistent, and the admin screen needed work.
I kept testing and tightening until Local Places stopped feeling like an added feature and started feeling like it belonged in Bonumark Stream.
I'm testing the new Bonumark Places feature.
Cypher could recognize a link I gave it, but it could not actually open the page. That meant it could guess from the title or URL and sound more informed than it was.
I fixed that by adding web search, forcing exact-link reading, preserving citations, and requiring Cypher to admit when a page cannot be accessed.
Then I retested the same article link that exposed the problem.
