← Portfolio

Architecture / Product / Operations

Decision ledger.
Choices leave evidence.

Finished systems hide the forks in the road. This ledger records the constraint, rejected alternative, cost, and evidence behind consequential choices across the portfolio.

DEC-001

The Hive / Failure Lab

Treat recovery as a separate capability from access.

Tailscale made a remote Authentik change possible while physical access was hours away.

Open the evidence →
Choice
Require an independent recovery path, explicit rollback, and stop conditions for remote identity work.
Rejected
The assumption that network reachability made the change operationally safe.
Cost
More preparation—and sometimes deferring a change that is technically possible.
Evidence
A successful change became a documented near miss and a reusable change gate.

DEC-002

Bricktelligence

Make memory the product, not a chatbot feature.

A conversational interface was easy to add, but generic answers would not help a collector decide what to build or buy.

Open the evidence →
Choice
Build durable facts, event history, aggregates, inference, and tools before centering the assistant.
Rejected
A stateless chat wrapper over catalog search.
Cost
A deeper data model, asynchronous inference, and more operational surface area.
Evidence
Five product surfaces now feed one context system used by the Archivist and verdict engine.

DEC-003

The Archivist Stack

Open the mechanism. Keep the calibration.

The reusable architecture was valuable to other builders, but product voice and tuning were earned through use.

Open the evidence →
Choice
Release the engine under Apache-2.0 while keeping weights, thresholds, prompts, and routing in a private boundary.
Rejected
Hiding standard machinery as if obscurity made it defensible.
Cost
A stricter architectural seam between reusable code and product-specific judgment.
Evidence
A commercially usable repository with executable setup, tests, security defaults, and no private tuning.

DEC-004

TechBearing

Put operational context behind tools, not prompts.

Agents needed current system state, but operational truth changes faster than static instructions can be maintained.

Open the evidence →
Choice
Expose typed, live capabilities through MCP over SSE and keep history in durable application state.
Rejected
Copying snapshots into prompts or relying on a model vendor session as memory.
Cost
More service boundaries, ingestion work, authorization, and observability.
Evidence
Approximately fourteen services share a model-neutral interface to live context and persistent history.