A file drop is an integration contract
The operational and semantic rules that turn a delivered file into accepted business input.
4 min read
Singular State / Perspectives
Perspectives
Practical thinking on what to build, how to make it work, and what it takes to own it.
A governance policy change can be an application change
How environment policies and credential changes can alter deployed behavior without changing application source.
4 min read
A knowledge graph that can explain a proposed migration path
Representing migration candidates, prerequisites, evidence, and unknowns without turning graph paths into guarantees.
3 min read
A successful API facade can make the underlying system harder to retire
How easier access to retained behavior can increase the obligations that a later replacement must satisfy.
3 min read
A successful restore can change the case for replacement
How resolving recovery uncertainty can alter modernization timing and the credibility of retention alternatives.
3 min read
Acceptance criteria for a system that does not repeat itself
A fixed seed makes a best effort, not a guarantee. Acceptance shifts from exact output to declared task properties, a predeclared sampling rule, and uncertainty measured at the unit actually sampled.
4 min read
What the accounting boundary does to your architecture
Capitalisation rewards crossing from exploration into development, so the boundary quietly rewards early commitment to a design. An incentive on technical decisions nobody describes as technical.
5 min read
Adverse action notices when the model is a language model
Regulation B requires the specific principal reasons the decision actually used. A fluent explanation of a decision the model did not make is the failure, and the CFPB circulars people cite were withdrawn in 2025.
4 min read
AI business-rule extraction needs a chain of evidence
Connecting generated rule descriptions to code, configuration, observed work, and confirmed business meaning.
3 min read
An archive and a backup preserve different things
Backups support restoration of operation. Archives support continuing access to records and their meaning after the original application is removed.
4 min read
An archive can outlast the people who understand it
The long-term dependency on schemas, code meanings, and operational knowledge after an application is retired.
3 min read
API facades and the behavior behind the interface
A facade exposes a consumer contract over retained behavior. Translation and routing do not remove the operational obligations of the underlying application.
4 min read
Application consolidation changes the concentration of operational risk
How merging applications can reduce duplicate work while changing shared failure and recovery consequences.
3 min read
Application outsourcing, managed services, and business-process outsourcing
Distinguishing outsourced application work, operational services, and responsibility for an entire business process.
3 min read
Batch checkpoints, event streams, and duplicate business actions
Connecting restart positions and messaging acknowledgments to the business effects that must not be repeated.
3 min read
The benefit decays before the transfer completes
Month-one and month-nine measurements are different quantities. A gate reading the early number transfers a system whose case has already expired, and time released is capacity rather than cash.
5 min read
Boring technology, and the debt you write down
Familiar means familiar to the receiving team, not old. And the ledger records what the code cannot do, including the debt nobody chose.
6 min read
Build-operate-transfer already means two other things
BOT names an infrastructure concession, an offshore entity handover, and a prototype transfer. The phrase does not say which, and the acronym family does not say when responsibility moves.
4 min read
Business capabilities and the applications that implement them
Capability mapping connects required business outcomes to processes, people, information, and applications. Shared labels do not establish interchangeable implementations.
3 min read
Change data capture from snapshot to ongoing replication
Change data capture combines an initial state with subsequent changes. Offsets, source-history retention, duplicate handling, and excluded objects determine continuity.
4 min read