Resources
How to think about the software you depend on.
Practical guides for investigating, protecting and advancing systems. Foundry appears only at the end of each, where it fits.
Understand
- How to build an inventory of undocumented dependenciesA method for finding what a system calls, reads, writes and waits on, when nobody wrote it down, and for recording how sure you are about each item.
- How to define an effective software intelligence engagementWhat to pin down before anyone analyzes a system for you: the decision, the authorized target, data handling, success criteria, deliverables and limits.
- How to investigate an undocumented system without confusing inference with factA working method for learning what an undocumented system does, and for keeping what you saw separate from what you assumed.
- How to measure the cost of repeated engineering investigationA method for counting the time engineers spend re-learning how a system works, so the cost of undocumented behavior can be compared with the cost of fixing it.
- What a useful software behavior report should containThe sections, evidence labels and level of detail that make a behavior report usable by engineers, not just readable by managers.
Protect
- Discovery, verification and security assurance are three different thingsWhat behavioral discovery establishes, what verification adds, and why neither is a security audit or a compliance result.
- Why generated SDKs need conformance testsWhy an SDK generated from a specification can still be wrong, and what a conformance suite must cover before anyone builds on it.
Advance
- How to preserve business behavior during modernizationHow to find the behavior a legacy system's users depend on, decide what must survive a rewrite or migration, and prove afterwards that it did.
- What to establish before connecting an AI agent to a sensitive systemThe facts, boundaries and tests to have in place before an AI agent is allowed to act on a system that matters.
- Wrap, replace, or modernize? Deciding what to do with a legacy interfaceA decision framework for legacy interfaces: when to put a facade in front, when to rebuild, and when to change the interface itself.